Episode 16: Disaster Recovery Architectures - Backup, Pilot Light, Warm Standby & Multi-Site | SAA-C03
Notes de l’épisode
Exam favorite! Master DR strategies: Backup & Restore, Pilot Light, Warm Standby, Multi-Site. Interactive format with Pulse Checks, Trap Spotlights & Memory Hooks!
🆕 INTERACTIVE FORMAT
🎯 PULSE CHECKS - Real pauses to test yourself
⚠️ TRAP SPOTLIGHTS - Exam traps highlighted live
💡 MEMORY HOOKS - Vivid analogies that stick
📊 RPO vs RTO (Foundation!)
RPO = Data loss BEFORE disaster
RTO = Downtime AFTER disaster
Memory hook: RPO = PAST, RTO = FUTURE. Data vs downtime.
Smaller RPO/RTO = More expensive infrastructure!
🛡️ THE 4 DR STRATEGIES (cheapest → most expensive)
1️⃣ BACKUP AND RESTORE
• Nothing running in DR, just backup storage
• RPO/RTO: Hours to days
• Cheapest option
• Tools: EBS snapshots, RDS backups, AMIs, S3 + Glacier lifecycle, Snowball, Storage Gateway
• Hook: Spare keys in safe deposit box
2️⃣ PILOT LIGHT
• Critical database always running with replication
• Application servers OFF until needed
• RPO: minutes | RTO: minutes to an hour
• Moderate cost
• Hook: Engine running while you run into a store
3️⃣ WARM STANDBY
• Full system running at MINIMUM size
• Scale up upon disaster
• RPO: seconds-minutes | RTO: minutes
• Higher cost
• Hook: Backup band rehearsed and on stage, playing softly
4️⃣ MULTI-SITE / HOT SITE
• Full production scale in BOTH regions, active-active
• RPO/RTO: Seconds
• Highest cost (2x infrastructure)
• Hook: Identical twins running parallel marathons
🔧 KEY AWS SERVICES
AWS BACKUP
Centrally manage backups across AWS services (EC2/EBS, S3, RDS/Aurora/DynamoDB, EFS/FSx). Cross-region & cross-account. Tag-based policies, point-in-time recovery.
AWS ELASTIC DISASTER RECOVERY (formerly CloudEndure)
Protect on-premise & non-AWS servers. Continuous block-level replication. Recovery in minutes.
Hook: AWS Backup = INSIDE AWS. DRS = OUTSIDE AWS to inside.
DMS + SCT
• Same engine migration: DMS only
• Different engine: DMS + SCT (schema conversion)
• DMS requires an EC2 instance!
AURORA GLOBAL DATABASE
Cross-region replication < 1 second. Failover < 1 minute. Gold standard for multi-region DBs.
OTHERS
• Route 53 health checks + failover routing
• Site-to-Site VPN as cheap Direct Connect backup
• CloudFormation for fast environment recreation
• CloudWatch alarm auto-recovery for EC2 hardware failures
⚠️ TOP EXAM TRAPS
1. Confusing RPO and RTO (data vs downtime)
2. Over-engineering (don't pick Multi-Site when B&R fits!)
3. AWS Backup vs Elastic Disaster Recovery (inside vs outside AWS)
4. SCT needed only for cross-engine migrations
5. RDS Multi-AZ = HA, not DR
6. Warm Standby (minimum scale) vs Multi-Site (full production)
7. Site-to-Site VPN backs up Direct Connect cheaply
8. DMS requires EC2 instance
9. Aurora Global < 1 sec replication, < 1 min failover
10. S3 CRR for regional S3 protection
11. CloudWatch StatusCheckFailed_System → auto-recovery
12. CloudFormation = fast DR via infrastructure as code
🎯 DECISION FRAMEWORK
Cost priority, downtime OK? → Backup & Restore
DB matters but cost matters? → Pilot Light
Fast failover, cost still matters? → Warm Standby
Seconds RTO, cost no object? → Multi-Site
Protecting on-premise? → Elastic Disaster Recovery
Backing up AWS services? → AWS Backup
Perfect for SAA-C03 prep - DR is one of the most-tested topics!
━━━━━━━━━━━━━━━━━━━━
📚 FREE SAA-C03 cheat sheet 👉 https://payhip.com/b/Zv5hd
🎯 104 practice questions with full explanations - 20% off with code PASS 👉 https://payhip.com/b/CLvcu
━━━━━━━━━━━━━━━━━━━━
#AWS #DisasterRecovery #BackupRestore #PilotLight #WarmStandby #MultiSite #SAAC03
⭐ 5-star rating if this helps!