Disaster recovery test checklist
A practical checklist for planning, running and reviewing a DR test, so you know your recovery plan works before you actually need it.
A DR plan that has never been tested is only a hope. Use this checklist to run a test that is safe, measurable and useful.
Before the test
- Define the scope: which systems, sites and scenarios are included
- Confirm the targets you’re testing against: RTO (how fast) and RPO (how much data loss is acceptable)
- Get written approval from system owners and management, with a clear go/no-go owner
- Schedule a change window and inform users, the service desk and vendors
- Check that the latest backups and replication are healthy
- Prepare a rollback plan in case the test itself causes problems
- Assign roles: test lead, technical leads per system, timekeeper, note-taker
- Prepare a test script with steps, expected results and pass/fail criteria
During the test
- Start the clock and log every step with a timestamp
- Fail over in the planned order (network, then infrastructure, then applications)
- Verify each system with real checks: login, a sample transaction, data freshness
- Record any manual workarounds or steps missing from the plan
- Measure the actual recovery time and data loss for each system
- Fail back, or confirm the plan for running on the DR site
After the test
- Compare actual results with RTO and RPO for each system
- List gaps with an owner and due date for each fix
- Update the DR plan and runbooks with what you learned
- Share a short report with management: scope, results, gaps, next test date
- Schedule the next test (at least once a year for critical systems)