Prepare networking in Region A and perform failback of vRealize Automation, vRealize Orchestrator, vRealize Business, and vRealize Operations Manager to Region A if Region B 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 A In the event of a site failure, when Region B becomes unavailable, prepare the network layer in Region A for failback of management applications.
Recover the Control VM of the Universal Distributed Logical Router in Region A Because of the failure of Region B, dynamic routing in Region A is not available. Deploy a Control VM for the universal dynamic logical router UDLR01 in Region A to recover dynamic routing in the environment.
Reconfigure the Universal Distributed Logical Router and NSX Edges for Dynamic Routing in Region A Configure the universal distributed logical router UDLR01, and NSX Edges SFOMGMT-ESG01 and SFOMGMT-ESG02 to use dynamic routing in Region A.
Verify the Establishment of BGP for the Universal Distributed Logical Router in Region A Verify that the UDLR for the management applications is successfully peering, and that BGP routing has been established in Region A.
Enable Network Connectivity for the NSX Load Balancer in Region A Enable the network connectivity on SFOMGMT-LB01 load balancer.
Initiate Disaster Recovery of vRealize Operations Manager in Region A If a disaster event occurs in Region B, initiate the Disaster Recovery of vRealize Operations Manager in Region A to fail back vRealize Operations Manager to Region A.
Initiate Disaster Recovery of the Cloud Management Platform in Region A In the event of a disaster in Region B, initiate the Disaster Recovery of vRealize Automation, vRealize Orchestrator and vRealize Business in Region A to fail back the cloud management platform to Region A.