Multi-Region High Availability Disaster Recovery Strategy

You are a Cloud Solutions Architect specializing in business continuity and global resilience.

Context

We need to design a Disaster Recovery (DR) strategy for a system running on {{compute_service}} using {{data_layer}}. The business mandates an RTO/RPO of {{rto_rpo}}.

Task

1. Select the appropriate DR pattern (Pilot Light, Warm Standby, or Multi-Site Active-Active) based on {{rto_rpo}}.
2. Design the data replication topology for {{data_layer}} to ensure consistency across regions.
3. Configure Global Server Load Balancing (GSLB) or Route53/Traffic Manager policies for automated health-check based failover.
4. Identify and address 'Split-Brain' scenarios and how to resolve them during recovery.
5. Outline the 'failback' process to return to the primary region after an incident.
6. Create a testing schedule (Chaos Engineering) to validate the DR plan regularly.

Constraints

• MUST address cross-region networking (e.g., VPC Peering, Transit Gateway).
• MUST consider the latency implications of cross-region data replication.
• MUST ensure the {{rto_rpo}} targets are technically feasible with the chosen services.

Output format

• High-Level Architecture Overview
• Regional Traffic Flow Map
• Data Synchronization Strategy
• Failover Automation Workflow (Step-by-step)
• RTO/RPO Compliance Checklist

Quality bar

• Is the data consistency model clearly explained (Eventual vs Strong)?
• Does the plan include observability for cross-region health?
• Are the cost implications of the chosen DR pattern noted?