The Two Numbers That Govern Recovery
Most recovery plans die of a single confusion: treating downtime and data loss as one problem. They are two, and they cost differently. Recovery Time Objective is patience; Recovery Point Objective is memory. A team can rebuild a system in an hour and still hand back a version of reality from yesterday morning. Separate the numbers and you can price them, defend them, and test them. Blur them and you will over-invest in one while a regulator or a furious customer discovers the gap in the other. Failure is the cheapest intelligence you will ever buy. Name the two numbers first.
Knowledge check
A payment system can be brought back online within 20 minutes, but the most recent transactions are always reconstructed from a batch that runs every hour. Which objective is strong, which is weak, and why does the distinction matter?
Show the answer
The Recovery Time Objective is strong (20 minutes to restore service), but the Recovery Point Objective is weak (up to an hour of transactions can be lost between batches). The distinction matters because the two are priced and engineered separately: fast restart does nothing to protect the transactions written in the gap since the last batch. A payments business would likely find the hour of lost money intolerable and need continuous replication to shrink the Recovery Point Objective, regardless of how quickly the service restarts.