Disaster Recovery Center Formulation, DR Topologies & RTO/RPO
Idea in plain words
Disaster Recovery (DR): Policies, tools, and procedures to enable the recovery or continuation of vital technology infrastructure following a natural or human-induced disaster.
Exam tip
High-yield exam topic (Very High).
Explanation
Disasters (earthquakes, power grid collapses, cyber ransomware attacks) threaten organization survival. A comprehensive Disaster Recovery Plan hinges on two quantitative Service Level Agreements: RTO and RPO. If a bank specifies RPO = 0, every completed financial transaction must be synchronously committed to the secondary DR center before being acknowledged to the customer. Because synchronous replication requires the host to wait for acknowledgment over the fiber link (adding approx 1ms delay per 100 km), disaster recovery centers situated hundreds of kilometers away use asynchronous replication, accepting a minimal RPO (e.g., 5 seconds) to maintain production transaction throughput.
Key points
- Business Continuity Planning (BCP): Broader organizational strategy ensuring complete business operational survival through a crisis.
- Recovery Time Objective (RTO): Maximum acceptable duration of time an application can be offline after a disaster before unacceptable commercial damage occurs.
- Recovery Point Objective (RPO): Maximum acceptable amount of data loss measured in time (how far back in time data must be restored).
- DR Site Topologies: Hot Site (fully configured mirrored live replica, instantaneous failover, RTO approx 0), Warm Site (pre-installed hardware, periodic data sync, RTO minutes/hours), Cold Site (empty shell with power/cooling, hardware must be procured, RTO days/weeks).
- Data Replication Strategies: Synchronous Replication (zero data loss RPO=0, distance-limited by network latency) vs Asynchronous Replication (non-blocking, supports long distances).
Example
Example
Nepal GIDC located in Singha Durbar, Kathmandu replicates data asynchronously across the Mahabharat mountain range to its secondary Disaster Recovery Center in Hetauda.
Code examples
/*
RTO vs RPO Graphical Relationship:
[Last Data Backup] -------- Data Loss --------> [DISASTER OCCURS] -------- Downtime --------> [Services Restored]
|<------------------- RPO ------------------->| |<------------------- RTO ------------------->|
(Maximum acceptable data loss in time) (Maximum acceptable duration to restore service)
DR Site Comparison:
Site Type | Infrastructure Ready? | Data Synchronized? | RTO Metric | Cost Level
Hot Site | Fully equipped live | Real-time synced | Minutes / Instant| Very High
Warm Site | Hardware installed | Periodic backups | Hours | Moderate
Cold Site | Power & space only | Zero local data | Days to Weeks | Low
*/
Exam questions
- [10 Marks] Define Recovery Time Objective (RTO) and Recovery Point Objective (RPO) with timeline diagrams. Compare Hot Site, Warm Site, and Cold Site DR strategies.
- [8 Marks] Differentiate between Synchronous and Asynchronous data replication across primary and disaster recovery sites. What factors dictate the geographic distance between them?