Recovery Point Objective (RPO)

The Recovery Point Objective is the data axis of disaster recovery. It measures backwards from the moment disruption strikes and asks how much recent data the organisation can afford to lose. A one-hour RPO means that after recovery, work from at most the last hour may be gone, which in turn dictates that backups or replication must run at least every hour.

RPO is the counterpart to RTO, and keeping the two straight is half the battle in Domain 7. RTO is about time to restore service, measured forward; RPO is about tolerable data loss, measured backward. They are set independently through the business impact analysis, and a demanding RPO drives cost just as an aggressive RTO does: near-zero data loss needs continuous replication, not nightly tape. The full timeline, with WRT and MTD, is in the recovery metrics guide.

Exam relevance: RPO versus RTO is the single most common Domain 7 distractor. Anchor it: RPO points backward and is answered in units of data or the time between backups; RTO points forward and is answered in downtime. “How often must we back up” is always an RPO question.