Prepare networking in Region B and perform failover of Realize Automation, vRealize Orchestrator, vRealize Business, and vRealize Operations Manager to Region B if Region A becomes unavailable in the event of a disaster or if you plan a graceful migration.
Reconfigure the NSX Instance for the Management Cluster in Region B In the event of a site failure, when Region A becomes unavailable, prepare the network layer in Region B for failover of management applications. Change the role of the NSX Manager to primary, deploy universal controller cluster, and synchronize the universal controller cluster configuration.
Recover the Control VM of the Universal Distributed Logical Router in Region B Because of the failure of Region A, dynamic routing in Region B is not available. Deploy a Control VM for the universal distributed logical router sfo01m01udlr01 in Region B to recover dynamic routing in the environment. You then configure the recovered Control VM to provide dynamic routing for the SDDC management applications that are failed over.
Reconfigure the Universal Distributed Logical Router and NSX Edges for Dynamic Routing in Region B Configure the universal distributed logical router sfo01m01udlr01 and NSX Edges lax01m01esg01 and lax01m01esg02 to support dynamic routing in Region B before you start disaster recovery from Region A. In this way, the management components of the SDDC will continue to communicate using optimal routes in a fault-tolerant network.
Verify Establishment of BGP for the Universal Distributed Logical Router in Region B Verify that the UDLR for the management applications is successfully peering, and that BGP routing has been established in Region B. After you perform disaster recovery, they can continue communicating to keep SDDC operational.
Enable Network Connectivity for the NSX Load Balancer in Region B Enable the network connectivity on lax01m01lb01 load balancer to support high-availability and distribute the network traffic load for vRealize Operations Manager and the Cloud Management Platform after disaster recovery to Region B.
Initiate Disaster Recovery of vRealize Operations Manager in Region B If a disaster event occurs in Region A, initiate disaster recovery of vRealize Operations Manager to fail it over to Region B and keep the monitoring functionality of the SDDC running.
Initiate Disaster Recovery of the Cloud Management Platform in Region B In the event of a disaster in Region A, initiate disaster recovery of the vRealize Automation and vRealize Business components to fail them over to Region B and keep the workload provisioning functionality of the SDDC available.