Assess whether a recovery drill meets its objectives.

Instruction: Calculate observed recovery time and data-loss window from the timestamps, distinguish objectives from observations and specify the data oracle.

Context:

Fictional case: a service has an RTO of 15 minutes and an RPO of 2 minutes. For this drill, RTO is measured from loss of service to restored service meeting the full read/write acceptance suite; RPO is measured from failure to the latest contiguous recovered acknowledged commit. All timestamps below are UTC from synchronized clocks. The service fails at 10:00:00. Process health checks turn green at 10:08:00; the full read/write and consistency suite passes at 10:12:30. An independent append-only client ledger records every acknowledged write with its ID, payload hash and commit timestamp. Comparison with restored data proves that every acknowledged write through 09:58:45 is present and correct, while acknowledged writes after 09:58:45 and before failure are absent. There are no holes or duplicates in the recovered prefix. The ledger shows 30 missing acknowledged writes. Backup configuration advertises a snapshot every minute. State whether each objective was met in this drill and what the result does not prove.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

The drill meets both defined objectives. Observed recovery time is 12 minutes 30 seconds, from 10:00:00 to the successful service acceptance suite at 10:12:30, below the 15-minute RTO...

Related Questions