Chapter 8 · Reading 5 of 5
Testing recovery against business targets
Security+ SY0-801 · Objectives 3.4
The appointment service returns after an outage. Staff log in and find that the last half hour of bookings has disappeared. The service desk says recovery took forty minutes. The advisors say they have hours of reconciliation ahead. Each has measured a real consequence of the interruption.
The recovery time objective limits how long a business function can be unavailable. The recovery point objective limits the amount of work that can be lost, measured in time. Define both with business owners. Replication can reduce interruption but also replicate corruption, so retain independently recoverable versions. Redundant components sharing one power supply still have a common failure mode.
Rehearse the restore
Compare hot, warm and cold recovery sites by readiness, cost and time to service. During a restore test, include identity, network resolution, key access and upstream dependencies. Have a user complete a meaningful transaction before declaring recovery. Record the time of the newest recoverable transaction as well as the time service resumed. Those measurements answer different questions.
Put two rulers on one timeline
Mark the last transaction you can recover, the time the service stopped supporting work and the time a user successfully completed a meaningful transaction after restoration. The gap before the failure describes potential data loss. The gap after failure describes interruption. Compare each with the target its business owner approved. A database process restarting is a technical milestone. If advisors still cannot authenticate, the business service is not yet available.
Try a second scenario. A standby site takes over within a minute but contains the same accidental deletion as the primary. Redundancy improved continuity through a hardware loss while doing little for this particular data loss. Versioned recoverable copies, tested restore permissions and a way to reconcile transactions serve different needs. Determine which failure your test was designed to survive.
Work the numbers from an advisor’s diary
Suppose the last recoverable booking was recorded at 08:40. The system stopped accepting requests at 09:00, the database returned at 09:25 and an advisor completed the first successful booking at 09:50. The recovery point is twenty minutes before the interruption. Business recovery took fifty minutes. With a fifteen-minute recovery point objective and a sixty-minute recovery time objective, one target was missed by five minutes even though the other was met.
What should management change? Buying a faster replacement server might improve restoration time without creating a more recent recoverable transaction. More frequent recoverable copies or a durable transaction journal could address the missing interval. Investigate why the last recoverable point was so old before recommending either. Also record the time required to resolve the missing appointments. That work may continue after the system becomes available.
Recovery has a human endpoint
Ask an advisor to find a synthetic booking made shortly before the exercise and enter a new one. Check that confirmations reach the intended recipient and that queued reminders do not create duplicates. Record delayed work and assign an owner for reconciliation. This is how a recovery exercise goes beyond a successful backup job and establishes which parts of the service people can depend on.
Inspect the three records, then use the evidence to answer the question.
1. Record A
Last usable backup / 08:00
2. Record B
Service failed / 08:25 and resumed / 09:10
3. Record C
Maximum downtime / 60 minutes. Maximum data loss / 15 minutes.
Apply the reading
What evidence supports your decision in the recovery time ruler exercise?
Compare your reasoning
The recovery point is 25 minutes before failure. That exceeds the 15-minute RPO by 10 minutes, even though restoration met the RTO.