Recovery Point Objective (RPO)
The recovery point objective (RPO) is the maximum acceptable data loss after a disruption, measured as the time between the last recoverable copy of the data and the incident, and it determines how often data must be backed up or replicated.
The recovery point objective (RPO) is the maximum acceptable amount of data loss after a disruption, expressed as a period of time before the incident. An RPO of 24 hours means that restoring from a nightly backup is acceptable, whereas an RPO of near zero requires continuous or synchronous replication so that almost no committed transactions are lost.
Like the RTO, the RPO is set through business impact analysis for each system, reflecting the cost of recreating or losing data. Transaction systems, production records needed for traceability and quality data often need short RPOs, while archives may tolerate longer ones. The RPO determines backup frequency, the use of database transaction log shipping, snapshot schedules and whether replication is synchronous or asynchronous.
Synchronous replication can achieve near-zero RPO but adds write latency and is usually limited to short distances, such as between availability zones, while asynchronous replication across regions leaves a small window of potential loss. Replication alone does not protect against corruption or ransomware, because damage is copied too, so point-in-time backups remain necessary. Restore tests should verify both the age and the integrity of recovered data.
Key points
- Expresses tolerable data loss as a span of time before the incident
- Drives backup frequency, snapshot schedules and replication design
- Near-zero RPO needs synchronous replication, which adds write latency
- Replication copies corruption too, so point-in-time backups are still needed
Where AiVibe comes in
AiVibe Software Services delivers cloud solutions on AWS, Microsoft Azure, Google Cloud or on-premise, together with cloud security, legacy modernisation, data analytics and AI and machine learning services.