The Recovery Point Objective (RPO) defines the maximum amount of data that an organisation may lose after a system failure.
Teams express RPO as a period of time. For example, an RPO of 15 minutes allows the loss of data created during the final 15 minutes before the disruption.
A shorter period reduces potential data loss. However, it usually requires more frequent backups, continuous replication, or advanced storage systems. Therefore, lower targets often increase cost and technical complexity.
Business impact should determine the selected value. For example, payment systems may require almost no data loss. In contrast, an archival system may accept a longer interval.
Teams should document the Recovery Point Objective (RPO) as a measurable quality requirement. Moreover, they should verify it through backup, restoration, and failure-recovery tests.
RPO focuses on acceptable data loss. Meanwhile, the Recovery Time Objective defines the acceptable restoration time.
Clear recovery targets connect business risk with backup frequency, replication methods, system design, and verification.
« Back to Glossary Index