Recovery Point Objective (RPO)
Definition
The maximum acceptable amount of data loss measured in time. It defines how far back in time the organisation is willing to restore data from a backup. An RPO of four hours means the organisation accepts losing up to four hours of transactions in a recovery scenario.
- Measures
- Maximum acceptable data loss
- Unit
- Time
- Drives
- Backup frequency decisions
- Companion metric
- Recovery Time Objective (RTO)
Common questions
How does an RPO of four hours actually shape a backup schedule?+
It sets a ceiling on the interval between backups or replication snapshots, since any gap longer than four hours would risk losing more data than the organisation has agreed it can tolerate in a recovery scenario.
Why do RPO and RTO get set separately rather than as one combined recovery target?+
They answer different questions: RPO bounds how much data can be lost, while RTO bounds how long the system can be down, and a business may tolerate more of one than the other, so each is negotiated and budgeted independently.
Related terms
- Clean Baseline
- A confirmed, verified system state that predates the compromise and is free from attacker artefacts. Establishing a clean baseline is the starting...
- Dependency Mapping
- The process of identifying all services, systems, and data flows that a given system depends on, and all systems that depend on...
- Observation Window
- A defined period after a system is restored during which enhanced monitoring is applied before the system is declared fully recovered. The...
- Recovery Time Objective (RTO)
- The maximum acceptable duration of downtime before a system must be restored to service. RTO drives decisions about recovery method: a short...
- Rollback Plan
- A documented procedure for reverting a recovery attempt if it fails or introduces new problems. A rollback plan specifies trigger conditions, the...