It is commonly expressed as the maximum acceptable period of data loss, measured backward from the disruption. A 15-minute RPO means the recovery design should provide a sufficiently consistent restore point no earlier than 15 minutes before the defined disruption.
The organization sets an RPO from business impact, legal and contractual needs, transaction volume, data criticality, and the ability to reconstruct lost work. The target then informs backup, snapshot, replication, journaling, and recovery design. Different datasets within one service may need different objectives.
Key points
Business decisionEstablish how much recent data, configuration, or transaction history the organization can tolerate recreating or losing.
Technical designSelect protection intervals and replication methods that can preserve a recoverable point within the approved window.
Dependency alignmentInclude application state, databases, identity services, encryption keys, infrastructure definitions, and other components needed for a consistent restoration.
VerificationExercise recovery from representative failure and compromise scenarios, then measure the actual restore point achieved.
Important limitationAn RPO is a target, not a guarantee. Replication can quickly copy corruption, deletion, or malicious encryption, and a recent backup may still be incomplete, inconsistent, or unusable.