Test the recovery, not just the backup job. A successful backup status does not prove that the organisation can restore services within its objectives.
Choose a realistic scenario
Test scenarios such as loss of several production systems, unavailable identity services or loss of the primary backup environment.
Measure RPO and RTO
Record the actual age of restored data and elapsed time until the service is usable. Compare the results with the agreed objectives.
Test dependencies
Applications may depend on DNS, directory services, databases, certificates, file services and network infrastructure. Document and test those dependencies.
Recovery sequence
- Establish the trusted recovery environment.
- Restore identity and core infrastructure.
- Restore backup services if required.
- Restore critical applications and data.
- Validate security controls.
- Reconnect users progressively.
Record results
| Measure | Record |
|---|---|
| Recovery point | Timestamp and source backup. |
| Restore duration | Start/end time and throughput. |
| Dependencies | Systems required before service worked. |
| Failures | Manual intervention required. |
Use the Backup Resilience Calculator to explore recovery constraints.