RPO & RTO

Overview

Overview RPO (Recovery Point Objective) and RTO (Recovery Time Objective) are the two fundamental metrics for disaster recovery planning. RPO defines the maximum acceptable amount of data loss measured in time — if your RPO is 1 hour, you can tolerate losing up to 1 hour of data in a disaster. RTO defines the maximum acceptable downtime — if your RTO is 15 minutes, the system must be operational within 15 minutes of a failure.

These are fundamentally business decisions, not technical ones. A payment processing system might require RPO=0 (zero data loss) and RTO<1 minute (near-instant recovery), while a marketing analytics dashboard might accept RPO=24 hours and RTO=4 hours. The technical architecture and cost follow directly from these requirements: tighter RPO/RTO demands more sophisticated (and expensive) infrastructure — synchronous replication across regions, hot standby databases, automated failover, and continuous data protection.

The classic mistake is designing for RPO=0 and RTO=0 for every system. This is prohibitively expensive and operationally complex. A mature organization classifies services into tiers based on business impact and assigns appropriate RPO/RTO targets to each tier. The most critical tier (Tier 1: payments, authentication) gets active-active multi-region with synchronous replication. The least critical tier (Tier 4: internal tools, batch reports) gets nightly backups with manual recovery.

Key concepts

• RPO (Recovery Point Objective) — max data loss
• RTO (Recovery Time Objective) — max downtime
• Backup strategies (full, incremental, differential)
• Disaster recovery tiers (cold, warm, hot, active-active)
• Point-in-time recovery (PITR)
• DR testing and runbook automation

Interview questions

• What are RPO and RTO and how do they drive architecture decisions?
• What are the DR tiers and how do you implement each?
• How does point-in-time recovery (PITR) work?
• How do you test disaster recovery and what should the runbook contain?

More System Design topics

• Real-time Updates
• Recommendation Engine
• Reddit
• Redundancy and Replication
• REST vs RPC vs GraphQL
• Returns and Refund Management System
• Saga Pattern for Distributed Transactions
• Scaling Reads
• Scaling Writes
• Search Ranking System
• Search System Design
• Security