Repository navigation
TH7 ‐ RTO vs RPO – DR
When designing a Disaster Recovery (DR) strategy in Oracle Cloud Infrastructure (OCI), two important metrics are used to measure business continuity requirements:
- RTO (Recovery Time Objective) – How quickly the service must be restored after a disaster.
- RPO (Recovery Point Objective) – How much data loss the business can tolerate after a disaster.
Both metrics help organizations define their backup, replication, and failover strategies.
Recovery Time Objective (RTO) is the maximum acceptable amount of time an application or service can remain unavailable after a disaster or outage.
In simple terms:
RTO answers the question: "How long can the business wait before the application is back online?"
Suppose an e-commerce application goes down due to a regional outage.
- Outage occurs at 10:00 AM
- Application is restored at 10:30 AM
Total downtime = 30 minutes
If the business requirement is:
- Maximum allowed downtime = 1 hour
Then:
RTO = 1 Hour
Since the application was recovered within 30 minutes, the RTO target was successfully met.
For a production application:
- Primary Region: Mumbai
- DR Region: Hyderabad
- Load Balancer, Compute Instances, Database replicated to DR
Business Requirement:
- Application must be available within 30 minutes after a disaster.
Therefore:
RTO = 30 Minutes
Recovery Point Objective (RPO) is the maximum acceptable amount of data loss measured in time.
In simple terms:
RPO answers the question: "How much data can the business afford to lose?"
Suppose database backups are taken every 15 minutes.
- Last successful backup: 10:00 AM
- Disaster occurs: 10:10 AM
Data created between:
- 10:00 AM and 10:10 AM
may be lost.
Possible data loss = 10 minutes
If the business allows up to 15 minutes of data loss:
RPO = 15 Minutes
The RPO requirement is met.
An application database is replicated from Mumbai to Hyderabad every 5 minutes.
Business Requirement:
- Maximum acceptable data loss = 5 minutes
Therefore:
RPO = 5 Minutes
If a disaster occurs, only the last 5 minutes of transactions may be lost.
| Feature | RTO | RPO |
|---|---|---|
| Full Form | Recovery Time Objective | Recovery Point Objective |
| Focus | Service Availability | Data Protection |
| Measures | Downtime | Data Loss |
| Question Answered | How quickly must the service be restored? | How much data can be lost? |
| Unit | Minutes / Hours | Minutes / Hours |
| Related To | Recovery Process | Backup & Replication Strategy |
| Goal | Restore Service | Minimize Data Loss |
A banking application has the following requirements:
- Customers should access services again within 30 minutes
- Maximum acceptable transaction loss is 5 minutes
Therefore:
- RTO = 30 Minutes
- RPO = 5 Minutes
| Event | Time |
|---|---|
| Last Replication | 10:00 AM |
| Disaster Occurs | 10:05 AM |
| DR Failover Started | 10:10 AM |
| Service Restored | 10:30 AM |
- Downtime = 30 Minutes → RTO Achieved
- Data Loss = 5 Minutes → RPO Achieved
What is the difference between RTO and RPO?
RTO (Recovery Time Objective) defines the maximum acceptable downtime of an application after a disaster, while RPO (Recovery Point Objective) defines the maximum acceptable amount of data loss. For example, if a business requires the application to be restored within 30 minutes and can tolerate losing only 5 minutes of data, then the RTO is 30 minutes and the RPO is 5 minutes. In OCI, these objectives are achieved using backup strategies, cross-region replication, standby databases, and disaster recovery solutions.