Cloud Disaster Recovery Cheat Sheet

Updated 2026-05-25

Next Topic: Cloud IAM (Identity and Access Management) Cheat Sheet

🧠Study flashcards on this topic128 cards · spaced repetition→

Cloud Disaster Recovery (DR) combines cloud infrastructure capabilities with structured resilience planning to ensure business continuity when primary systems fail. Unlike traditional DR requiring duplicate physical data centers, cloud DR leverages geographic distribution, automated orchestration, and elastic scaling to protect workloads across regions. The core challenge lies in balancing recovery speed against operational cost—organizations must navigate trade-offs between infrastructure readiness (hot vs. cold sites), replication patterns (synchronous vs. asynchronous), and compliance requirements while maintaining acceptable Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO). Modern cloud DR extends beyond backup restoration to include failover automation, data consistency verification, business impact analysis, and specialized strategies for cloud-native workloads including Kubernetes-hosted applications and SaaS platforms.

What This Cheat Sheet Covers

This topic spans 15 focused tables and 133 indexed concepts, 128 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Core Recovery ObjectivesTable 2: DR Architecture StrategiesTable 3: DR Tiers and Service LevelsTable 4: Backup Strategies and TypesTable 5: Data Replication MethodsTable 6: Failover and Failback MechanismsTable 7: Testing and Validation MethodsTable 8: DR Plan Documentation ComponentsTable 9: Cloud Provider DR ServicesTable 10: Orchestration and Automation ToolsTable 11: Cloud-Native and Kubernetes DR PatternsTable 12: Compliance and GovernanceTable 13: Cost Optimization StrategiesTable 14: Recovery Procedures and OperationsTable 15: Monitoring and Alerting for DR

Quick IndexSubscribe to unlock

A jump-to index of every table row in this cheat sheet.

Mind MapSubscribe to unlock

An interactive map of every table and concept in this topic.

Table 1: Core Recovery Objectives

The four fundamental metrics—RTO, RPO, RCO, and MTTR—form the quantitative foundation of every DR plan. Setting them incorrectly wastes budget (too aggressive) or leaves the business exposed (too lenient); each must be derived from a Business Impact Analysis, not estimated arbitrarily.

Metric	Example	Description
Recovery Time Objective (RTO)	`RTO = 4 hours` `System must be online` `within 4 hrs of failure`	• Maximum tolerable downtime from failure to full service restoration • drives infrastructure readiness (hot/warm/cold site) and automation investment
Recovery Point Objective (RPO)	`RPO = 1 hour` `Max 1 hr of data loss` `acceptable`	• Maximum acceptable data loss measured in time • drives replication frequency and backup intervals.
Recovery Consistency Objective (RCO)	`RCO = 100%` `All transactions must` `be consistent at DR`	• Ensures data consistency across distributed systems • critical for databases where partial writes cause corruption
Mean Time to Recover (MTTR)	`MTTR = total downtime` `/ number of incidents`	• Average time to restore service across all incidents • measures overall DR process effectiveness and helps prioritize automation investments
Recovery Capacity Objective (RCapO)	`RCapO = 80%` `DR site must handle` `80% of prod load`	• Minimum processing capacity required at the DR site • often overlooked—a site with correct data but insufficient compute capacity cannot meet RTO
Maximum Tolerable Downtime (MTD)	`MTD = 8 hours` `Beyond 8 hrs business` `viability threatened`	• Hard upper limit on downtime before irreversible business damage occurs • sets the absolute ceiling for RTO values

Table 2: DR Architecture Strategies

DR architecture defines how your standby environment is provisioned and kept in sync with production. The choice spans a wide cost-reliability spectrum—from always-warm active-active deployments to cost-efficient cold restore-from-backup approaches—and must match both the RTO/RPO targets and the organization's budget.

Strategy	Example	Description
Active-Active Multi-Region	`Traffic split across` `us-east-1 + eu-west-1` `via Route 53 latency`	• Both regions serve live traffic simultaneously • near-zero RTO/RPO but roughly 2× cost • best for business-critical systems where downtime is unacceptable

The rest of this section is part of the full cheat sheet

Table 3: DR Tiers and Service Levels

DR tiers (0–7) provide a framework for categorizing workloads by their recovery complexity and cost. Assigning each application to the correct tier during Business Impact Analysis ensures resources are allocated proportionally to business criticality rather than uniformly across all systems.

Tier	Example	Description
Tier 7 — Zero Downtime	`Active-active global` `load balancing; zero` `RPO/RTO; 99.999% SLA`	• Zero data loss and zero planned downtime • continuous availability via active-active • most expensive tier • reserved for life-safety or revenue-critical systems

The rest of this section is part of the full cheat sheet

Table 4: Backup Strategies and Types

Backup strategy determines how much data you can lose (RPO) and how quickly you can restore (RTO). Modern environments layer multiple backup types—combining full, incremental, and immutable offsite copies—to balance storage cost, recovery speed, and resilience against ransomware that specifically targets backup infrastructure.

Strategy	Example	Description
3-2-1-1-0 Backup Rule	`3 copies, 2 media,` `1 offsite, 1 immutable` `or air-gapped, 0 errors`	• Modern evolution of the 3-2-1 rule adding an immutable or air-gapped copy and zero-error verification via automated restore testing • directly addresses ransomware that targets conventional backups

The rest of this section is part of the full cheat sheet

Table 1: Core Recovery Objectives

Metric	Example	Description
Recovery Time Objective (RTO)	`RTO = 4 hours` `System must be online` `within 4 hrs of failure`	• Maximum tolerable downtime from failure to full service restoration • drives infrastructure readiness (hot/warm/cold site) and automation investment
Recovery Point Objective (RPO)	`RPO = 1 hour` `Max 1 hr of data loss` `acceptable`	• Maximum acceptable data loss measured in time • drives replication frequency and backup intervals.
Recovery Consistency Objective (RCO)	`RCO = 100%` `All transactions must` `be consistent at DR`	• Ensures data consistency across distributed systems • critical for databases where partial writes cause corruption
Mean Time to Recover (MTTR)	`MTTR = total downtime` `/ number of incidents`	• Average time to restore service across all incidents • measures overall DR process effectiveness and helps prioritize automation investments
Recovery Capacity Objective (RCapO)	`RCapO = 80%` `DR site must handle` `80% of prod load`	• Minimum processing capacity required at the DR site • often overlooked—a site with correct data but insufficient compute capacity cannot meet RTO
Maximum Tolerable Downtime (MTD)	`MTD = 8 hours` `Beyond 8 hrs business` `viability threatened`	• Hard upper limit on downtime before irreversible business damage occurs • sets the absolute ceiling for RTO values

Table 2: DR Architecture Strategies

Strategy	Example	Description
Active-Active Multi-Region	`Traffic split across` `us-east-1 + eu-west-1` `via Route 53 latency`	• Both regions serve live traffic simultaneously • near-zero RTO/RPO but roughly 2× cost • best for business-critical systems where downtime is unacceptable

Table 3: DR Tiers and Service Levels

Tier	Example	Description
Tier 7 — Zero Downtime	`Active-active global` `load balancing; zero` `RPO/RTO; 99.999% SLA`	• Zero data loss and zero planned downtime • continuous availability via active-active • most expensive tier • reserved for life-safety or revenue-critical systems

Table 4: Backup Strategies and Types

Strategy	Example	Description
3-2-1-1-0 Backup Rule	`3 copies, 2 media,` `1 offsite, 1 immutable` `or air-gapped, 0 errors`	• Modern evolution of the 3-2-1 rule adding an immutable or air-gapped copy and zero-error verification via automated restore testing • directly addresses ransomware that targets conventional backups