Freshness of the latest successful backup
A protected workload's most recent successful backup should be no older than the configured window — a backup product that stopped succeeding days ago gives the same false confidence as no backup at all.
Interpret the result in context
The configured value measures backup age, not how long recovery points are retained. Align it with the workload’s recovery requirements and normal backup schedule.
Configure the expectation.
Use this baseline as a starting point. You can also build your own controls and standards from integration data, with client-specific requirements and documented exceptions.
Must have completed within (days)
How long ago the most recent successful backup run may be before a protected workload counts as overdue.
Review. Remediate. Verify.
Use one-click remediation where the integration and action support it, or the evidence to guide the technician’s next step.
- 01
Compare the latest successful run with the agreed maximum age.
- 02
Investigate missed runs, scheduling, connectivity and storage issues.
- 03
Complete a successful backup and verify that the refreshed timestamp meets the window.
A completed action is only part of the record. Refresh the supporting evidence to establish whether the finding has cleared.
Make your baseline part of every client review.
Connect checks, findings and remediation to the same client record.