Recovery Test (Wiederanlauftest)

What a recovery test checks

A recovery test simulates an outage and measures how long it takes until a business process can be worked with again, and how much data is lost along the way. It therefore tests exactly the two values the business impact analysis set as a requirement beforehand: the RTO and the RPO. ISO 22301 requires an exercise and testing programme in clause 8.5 and the evaluation of continuity capabilities in clause 8.6; BSI Standard 200-4 treats the test as the evidence behind the stated recovery time.

Why the measured value differs from the surveyed one

The BIA and the gap report record what somebody answered. The test delivers what somebody measured. Both numbers carry the same abbreviation and rarely mean the same stretch of time: an IT operations answer on the RTO often starts once the standby environment is available, while the business unit means the time until the application can be used. Detection, decision and tasking come before that and are missing from both figures.

What belongs in the test record

• The timeline with its starting point: when the clock starts, which sections were measured and which were carried over from an alerting exercise.
• Requirement, stated capability and measured value side by side, per process and per system.
• The data state reached, counted in orders or bookings rather than in the age of the most recent backup.
• The business sign-off: who grants it, what it is based on and what it does not cover.
• Whatever was substituted during the test or simply happened to be available, because the result says nothing about those parts.

How it differs from other exercise formats

A recovery test is a functional test against real technology. A tabletop exercise checks roles and decision paths around a table; a pure restore test checks that individual systems can be recovered. Only the recovery test joins both ends together up to the business sign-off, turning an assumption into evidence.