Insights · Field note · Infrastructure and resilience
Recovery testing cadence and evidence
How often to test what, and what the record has to contain for the test to count as proof.
Recovery testing proves that continuity and recovery plans work by exercising them under controlled conditions and measuring the result against the objectives the business set. The cadence is layered: file and component restores frequently; application and service recoveries on a schedule, typically at least annually per critical service; a site or whole-environment exercise annually where the design allows; and additional tests after any significant change. The evidence is a test record stating scope, scenario, procedure, participants, measured recovery time and data loss against objectives, failures observed, actions assigned and sign-off. A test without that record is an activity, not proof.
In detail
What the evidence shows.
Layered cadence
Frequent small tests build confidence and catch drift early: a file restore weekly, a component restore monthly. Larger tests are scheduled: each critical service recovered at least annually, more often where it changes. Tests are also triggered by events: a new backup platform, a migration, an acquisition, an incident. NIST SP 800-84 describes test, training and exercise programs along these lines.
What is measured
Recovery time against the recovery time objective. Data loss against the recovery point objective. Functional checks: the service does what it should. Integrity checks: the data is complete and correct. Deviations from the procedure, because they show where the plan is wrong.
The record
Objectives, scope, scenario, roles, procedure, measurements, results, failures, actions with owners and dates, and acceptance by the sponsor. Failures are recorded as faithfully as successes; a program that only records successes is not believed. The record is evidence for auditors, insurers, customers and regulators.
Closing the gap
Measured times that exceed objectives become actions: redesign, more capacity, a different order, a different copy. The next test shows whether the gap closed. See recovery testing, the disaster recovery test plan template and the glossary entry for recovery time objective.
Sources
Primary references.
By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days