Disaster Recovery Architecture Generator

RTO (Recovery Time Objective) is how long it takes to recover after disaster. RPO (Recovery Point Objective) is how much data you can afford to lose (time since last backup). Show backup frequency affecting RPO, failover automation affecting RTO. Design systems to meet business requirements for both.

Active-passive: primary region serves traffic, standby region is idle until failover (higher RTO, lower cost). Active-active: both regions serve traffic simultaneously (lower RTO, higher cost, complexity). Visualize traffic routing, data synchronization, and conflict resolution strategies.

Use database replication (streaming replication for PostgreSQL, read replicas for MySQL/MongoDB). Show primary → replica lag monitoring → automated/manual failover → promote replica to primary. Include backup strategies (snapshots, WAL archiving), point-in-time recovery, and testing restore procedures.

Layered approach: full backups weekly, incremental daily, continuous WAL/binlog streaming. 3-2-1 rule: 3 copies, 2 different media types, 1 offsite. Visualize backup schedule, retention policies, restore procedures. Test restores regularly to verify backup integrity and recovery processes.

Global load balancer with health checks → routes traffic to healthy region. Show data replication (async or sync), DNS failover, regional backups. Include automated failover triggers, runbooks for manual failover, and failback procedures. Monitor replication lag and cross-region latency.