What Is Disaster Recovery and How Do RTO/RPO Work?
Learn what disaster recovery means, how RTO and RPO differ, and the DR strategy spectrum from backup-restore to multi-site active-active.
Expected Interview Answer
Disaster recovery (DR) is the set of policies, tools, and procedures that let an organization restore critical systems and data after a catastrophic failure — such as a region outage, data corruption, or ransomware attack — and it is measured by two key targets: Recovery Time Objective (RTO), the maximum acceptable downtime, and Recovery Point Objective (RPO), the maximum acceptable data loss measured in time.
RTO answers the question of how long the system can be down, while RPO answers the question of how much data can be afforded to lose — a database backed up every 24 hours has an RPO of up to 24 hours, meaning up to a day of data could be lost in a disaster. Common DR strategies span a spectrum of cost versus recovery speed: backup-and-restore (cheapest, slowest — hours to days), pilot light (a minimal always-on core in a secondary region that is scaled up during a disaster), warm standby (a scaled-down but fully functional secondary environment, faster failover), and multi-site active-active (identical full environments running simultaneously in multiple regions, near-zero RTO/RPO but the most expensive). Choosing a strategy means matching business requirements — how much money one hour of downtime costs, and how much data loss is tolerable — against the increasing infrastructure cost of tighter RTO/RPO targets. Crucially, a DR plan that has never been tested with an actual failover drill is not a reliable plan at all; regular game-day exercises are what validate that backups actually restore correctly and that the documented runbook works under real pressure.
- Provides measurable, business-aligned targets (RTO/RPO) instead of vague promises
- Bounds financial risk by matching recovery cost to actual downtime tolerance
- Ensures backups and failover procedures are proven, not just assumed to work
- Gives incident responders a tested runbook instead of improvising during a real crisis
AI Mentor Explanation
Disaster recovery is like a team’s contingency plan for its home stadium becoming unplayable right before a match. RTO is how quickly they can get a game underway at a backup ground — a nearby club pitch used within hours (tight RTO) versus needing weeks to arrange a new venue (loose RTO). RPO is how much recent form and match data they can afford to lose — a team with daily video analysis backups loses at most a day’s worth of scouting (tight RPO), while one relying on end-of-season reviews loses months of insight (loose RPO). A franchise that has never actually rehearsed relocating a match to a backup ground will scramble chaotically the day it actually happens.
Step-by-Step Explanation
Step 1
Define RTO and RPO per system tier
Work with the business to set acceptable downtime and data-loss windows for each critical service, since not every system needs the same targets.
Step 2
Pick a DR strategy matching those targets
Choose backup-and-restore, pilot light, warm standby, or multi-site active-active based on cost versus how tight RTO/RPO must be.
Step 3
Implement replication and automated backups
Continuously replicate data or take frequent backups to a separate region, matching the defined RPO.
Step 4
Run regular failover drills
Execute scheduled game-day exercises that actually fail over to the DR site and restore from backup, validating the runbook works under real conditions.
What Interviewer Expects
- Precise definitions of RTO (downtime tolerance) vs RPO (data-loss tolerance)
- Knowledge of the DR strategy spectrum: backup-restore, pilot light, warm standby, multi-site active-active
- Understanding that DR cost scales inversely with RTO/RPO tightness
- Emphasis on regularly tested failover drills, not just a written plan
Common Mistakes
- Confusing RTO and RPO or using them interchangeably
- Assuming backups alone constitute a complete disaster recovery plan
- Never mentioning that DR plans must be regularly tested via real failover drills
- Choosing a DR strategy without weighing it against actual business downtime cost
Best Answer (HR Friendly)
“Disaster recovery is our plan for what happens if something catastrophic takes out a whole system or region — how quickly we can get back up, and how much data we could realistically lose. We measure that with two numbers: RTO, our maximum acceptable downtime, and RPO, our maximum acceptable data loss window. We pick backup strategies that match those targets to the actual cost of downtime, and just as importantly, we regularly run real failover drills so we know the plan actually works before we ever need it in a real emergency.”
Code Example
# Trigger a controlled failover drill to the standby region
aws rds promote-read-replica \
--db-instance-identifier orders-db-standby-us-west-2
# Verify replication lag before promotion to estimate real RPO
aws rds describe-db-instances \
--db-instance-identifier orders-db-standby-us-west-2 \
--query "DBInstances[0].StatusInfos"
# Log the drill outcome for the DR runbook audit trail
echo "$(date -u) failover drill completed, lag_seconds=4" >> dr-drill-log.txtFollow-up Questions
- How do you decide which DR strategy fits a given system's business criticality?
- What is the difference between pilot light and warm standby DR strategies?
- How often should disaster recovery failover drills be run, and why?
- How does disaster recovery differ from high availability?
MCQ Practice
1. What does RPO (Recovery Point Objective) measure?
RPO defines how much data (measured as a time window) an organization can tolerate losing in a disaster, driving backup/replication frequency.
2. Which DR strategy offers the fastest RTO but at the highest infrastructure cost?
Multi-site active-active runs full duplicate environments simultaneously across regions, giving near-zero RTO/RPO but at the greatest ongoing cost.
3. Why are regular failover drills essential to a disaster recovery plan?
A DR plan that has never been tested with a real failover drill cannot be trusted — drills prove backups restore correctly and the runbook is accurate.
Flash Cards
What does RTO measure? — The maximum acceptable downtime after a disaster.
What does RPO measure? — The maximum acceptable data loss, measured in time.
Name the four DR strategies on the cost/speed spectrum. — Backup-and-restore, pilot light, warm standby, multi-site active-active.
Why run failover drills? — To prove backups and the DR runbook actually work before a real disaster forces the test.