A financial analytics company runs its core reporting application in region `us-east4` (primary) with a warm standby disaster recovery setup in region `us-central1` (secondary). The primary region experiences a prolonged physical infrastructure failure. The site reliability engineering (SRE) team must execute the manual failover runbook to restore operational service in `us-central1`. Sequence the operational steps below in the correct order to successfully execute the regional failover.
- 1Promote the cross-region Cloud SQL read replica in `us-central1` to a standalone primary database instance.
- 2Update the internal Cloud DNS endpoint record to resolve database traffic to the newly promoted instance in `us-central1`.
- 3Resize the secondary Compute Engine Managed Instance Group (MIG) in `us-central1` from zero to full operational capacity.
- 4Update the Cloud Load Balancing backend service configuration to divert incoming ingress traffic to the `us-central1` MIG.
Cevap
The correct operational sequence is: 1) Promote the cross-region Cloud SQL read replica in us-central1 to a standalone primary database instance; 2) Update the internal Cloud DNS endpoint record to resolve database traffic to the newly promoted instance in us-central1; 3) Resize the secondary Compute Engine Managed Instance Group (MIG) in us-central1 from zero to full operational capacity; 4) Update the Cloud Load Balancing backend service configuration to divert incoming ingress traffic to the us-central1 MIG.
Executing a disaster recovery failover requires establishing data tier write availability first (database promotion), configuring internal service discovery, scaling out compute resources in the secondary region, and finally updating global ingress routing to direct user traffic to the newly active region.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery Regional Failover Execution Order
Tahmini Süre:1m 30s