Definition: Metric defining the maximum amount of data an organization can afford to lose, measured as the time interval between the last backup and the incident.
— Source: NERVICO, Product Development Consultancy
What Is RPO
Recovery Point Objective (RPO) is a business continuity metric that defines the maximum amount of data an organization can afford to lose in the event of a disaster. It is expressed as a time interval: an RPO of 1 hour means that in the worst-case scenario, up to 60 minutes of data would be lost since the last available recovery point.
How It Works
RPO determines how frequently backups must be performed or data replicated. An RPO of 24 hours allows daily backups, while an RPO of minutes requires continuous or near-continuous replication. In AWS, strategies for achieving low RPOs include synchronous replication between availability zones, asynchronous cross-region replication with Aurora Global Database, or continuous replication with AWS DMS. The lower the target RPO, the greater the required infrastructure and associated cost.
Key Use Cases
- Defining backup frequency for production databases based on data criticality
- Justifying the cost of multi-region replication for financial systems with zero data loss tolerance
- Negotiating service level agreements with clients requiring maximum data loss guarantees
- Designing storage architectures with replication appropriate to each service’s criticality level
Advantages and Considerations
Defining a clear RPO enables correct sizing of backup and replication infrastructure, avoiding both overinvestment and exposure to unacceptable risks. It facilitates business conversations by translating technical decisions into understandable risk terms. The main consideration is that not all data requires the same RPO: critical transactional data may need near-zero RPO, while operational logs can tolerate hours of loss.