Choose the right evidence
Check workload and job identity before combining observations. Two records with similar names are not automatically evidence about the same system.
Start with the supplied template
1
Copy BIOS Backup Health
Open Standards → More → Browse library and copy BIOS Backup Health. Review the disabled draft before enabling it.The template includes Backup jobs report healthy, Protected workloads back up daily, and the manual check Test a representative restore.
2
Review coverage and scope
Confirm the connected source supplies the required observations for the client. Inspect which workloads and jobs appear, their identifiers and observation times.Checkpoint: you can name the workloads being assessed and identify any that are not represented.
3
Review the recency setting
The supplied recency control defaults to one day, with an allowed range of 1–30 days. Check the effective client setting before interpreting the result. Review the window against the client’s requirements.Checkpoint: you can state the actual threshold used, including any override.
4
Enable the reviewed standard
Open the copied standard and select Review & enable. Turn on Enabled, then select Save changes.Checkpoint: the standard shows Enabled, and the controls you intend to assess are enabled too. The final Run checks action stays unavailable while the parent standard is disabled.
5
Run checks and inspect the evidence
Use Run checks, review the selected clients and settings, and inspect the resulting assessments. Follow a failure back to the workload or job and the cited observation.Checkpoint: you can explain the result using the observed value and effective expectation.
Work through a recency example
Assume a fixed evaluation time of 26 September at 12:00 UTC, an effective window of one day, and current eligible observations for a selected protected workload. These are illustrative comparisons, not client records.- Within the window
- Outside the window
- No observation
Last successful backup: 26 September at 00:00 UTC.The timestamp is 12 hours before the evaluation time, so it satisfies the one-day comparison. Check job scope and source freshness before using that comparison to explain the overall result.
The
within_days operator also accepts timestamps within the configured window after evaluation time. A timestamp 12 hours in the future can satisfy a one-day comparison. Investigate clock or source-data problems; a future “last success” is not evidence that a future backup has happened.Add the recovery question
Open Test a representative restore in the client’s manual checks and follow an approved restore procedure. The template’s default review interval is 30 days; review whether that cadence suits the client. Record the workload, recovery point, restore procedure, data checks, elapsed recovery time and any limitations. Compare the outcome with the client’s agreed recovery objectives. Enter the conclusion and supporting evidence using the manual assessment workflow. A restore of one file does not establish that an entire server or application can be recovered. Describe the scope precisely.Explain the whole picture
An illustrative handover might read:Acme’s selected workload has a recorded backup product and a successful-backup timestamp within the agreed window. We still need a current restore exercise before concluding that the required recovery process works.In a real handover, include actual identifiers, observation times and evidence references. Keep automated results and the human review distinct. You should now have: an explained assessment of backup observations, a visible list of coverage gaps, and a separate recovery review with an owner and next review date.
Investigate an unexpected result
Work backwards through configuration, scope and evidence.
Record the restore assessment
Capture the human conclusion and supporting evidence.