Backup & Restore Readiness

Recovery risk before restore day

Checks backup age, recovery model exposure and msdb backup visibility so teams can distinguish a clean backup state from missing evidence.

2026-09-02 10:18 generated
Reset
Readiness score100
RPO tierStandard
Backup risks0
Critical0
Affected servers0
msdb gaps0
Readiness gauge100 / 100
100
Risk mix0 databases
Critical
0
High
0
msdb gaps
0
Affected serverstop risk count
No backup risk rows.
Restore chain stateevidence outcome
0review
0broken
0unknown
Action priority0 open
No restore-readiness actions.
Readiness checkpointsRPO/RTO model
Fresh full backup Valid log chain msdb evidence visible Restore test owned
Restore readiness model5 policy checks
Full backup 7 days max age

Required for every database

Creates the base restore point and resets exposure from missing full history.
Log backup 24 hours max age

Required for FULL and BULK_LOGGED recovery

Controls RPO and protects the log chain from growing unchecked.
Differential backup Optional acceleration

Recommended for large databases

Reduces restore time when full backups are large.
msdb visibility Mandatory evidence

Required for trusted readiness

Without msdb history the app must show a visibility gap, not a false green status.
Restore test 90 days process target

Required outside SQL telemetry

Fresh backups are not enough; restore success and duration need proof.
Readiness queue 0 of 0 databases
No backup risks match the current filters and available msdb evidence.
Action plan0 prioritized
No backup action plan is needed with the current thresholds.
RPOSet log-backup thresholds to match the maximum accepted data loss for FULL/BULK_LOGGED databases.
RTOAdd restore-test evidence to your process so backup freshness is not mistaken for restore readiness.
Chain healthAny missing full/log history should become action work, not just a dashboard warning.