RPO — IT definition
Recovery Point Objective: the maximum amount of data an organization can afford to lose in a disaster, expressed as the time gap since the last usable backup.
The RPO (Recovery Point Objective) defines the maximum amount of data an organization can afford to lose in a disaster. It is expressed in time: a one-hour RPO means you accept losing, at worst, the last hour of data produced before the incident.
Together with the RTO, the RPO is one of the two key parameters of a Disaster Recovery Plan (DRP) and is often part of SLAs.
What the RPO requires technically
The RPO drives the frequency and method of backup or replication:
- •RPO of several hours: classic periodic backups (daily or several times a day).
- •RPO of a few minutes: regular asynchronous replication.
- •Near-zero RPO: synchronous replication to a remote site, where each transaction is confirmed on two sites before being committed.
RPO and data criticality
The RPO is set according to the value of the data, during the Business Impact Analysis of the BCP:
- •Financial transaction: RPO of a few seconds — no transaction should be lost.
- •CRM, ERP: RPO of a few minutes.
- •Reporting, archives: an RPO of several hours is acceptable.
RPO vs RTO
The RPO measures data loss (looking backward: how far back must we be able to recover?); the RTO measures a recovery time (looking forward: how soon is the service restored?). Both are defined together but answer distinct questions.
Frequently asked questions
How can I reduce the RPO?
+
Reducing the RPO means increasing backup frequency or moving to replication. An RPO of a few hours relies on periodic backups; an RPO of a few minutes requires asynchronous replication; a near-zero RPO requires synchronous replication to a remote site — more expensive, but with no data loss.
Is a zero RPO realistic?
+
A strictly zero RPO is technically achievable through synchronous multi-site replication, but at a high cost and with a performance impact (every write must be confirmed on two sites). In practice, near-zero RPO is reserved for the most critical data (financial transactions), while a higher RPO is accepted for the rest of the application portfolio.
All terms
5R Method
A strategy used during application rationalization to determine the best approach for managing applications.
8R Method
An extended version of the 5R method used in application portfolio management and migration strategies.
Application
A computer program or set of programs designed to automate a business process or deliver value to end users.
Architecture
Refers to the structure and behavior of IT systems, processes, and infrastructure within an organization.
Need help mapping your IT landscape?
Kabeen helps you inventory, analyze and optimize your application portfolio.