Prepare networking in Region B and perform a failover of vRealize Automation, vRealize Operations Manager, and vRealize Suite Lifecycle Manager to Region B if Region A becomes unavailable.
After failover of the Operations Management and Cloud Management components, SDDC manager in Region A cannot manage the vRealize products. All relevant SDDC Manager workflows related to the vRealize products are available again after Region A is restored and the necessary post failback operations are performed.
Assign the Primary Role to the NSX Manager Instance for the Management Cluster for VMware Cloud Foundation in Region B If Region A becomes unavailable, you must prepare the network layer in Region B for a failover of the management applications. First change the role of the NSX Manager instance in Region B to primary to recreate the virtual network infrastructure in Region B.
Deploy the Control VM of the Universal Distributed Logical Router for VMware Cloud Foundation in Region B After the SDDC deployment, the universal NSX components for dynamic routing are placed in Region A. If a site failure occurs in Region A, the SDDC management applications might lose connectivity if you fail them over to Region B. Deploy and configure a control VM for the universal distributed logical router sfo01m01udlr01 in Region B to provide dynamic routing to the SDDC management applications.
Reconfigure the Universal Distributed Logical Router and NSX Edge Nodes for Dynamic Routing for VMware Cloud Foundation in Region B To support dynamic routing in Region B before you initiate disaster recovery from Region A, configure the universal distributed logical router sfo01m01udlr01 and NSX Edge nodes lax01m01esg01 and lax01m01esg02. This configuration ensures that the management components of the SDDC continue to communicate using optimal routes in a fault-tolerant network.
Verify Establishment of BGP for the Universal Distributed Logical Router for VMware Cloud Foundation in Region B Verify that the universal distributed logical router 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 the SDDC operational.
Deploy the NSX Controllers for the NSX Instance for VMware Cloud Foundation in Region B Deploy the three-node universal NSX Controller cluster in Region B for logical switching and routing in and across the clusters and regions in the SDDC.
Connect the Application NSX Load Balancer in Region B to the SDDC Network for VMware Cloud Foundation Enable the network connectivity on lax01m01lb01 load balancer to support high availability and distribute the network traffic load for vRealize Operations Manager, vRealize Suite Lifecycle Manager, and the Cloud Management Platform after disaster recovery to Region B.
Initiate Disaster Recovery of the Operations Management Applications for VMware Cloud Foundation in Region B If a site failure in Region A occurs, initiate disaster recovery of vRealize Suite Lifecycle Manager and of vRealize Operations Manager to keep the monitoring functionality of the SDDC running.
Initiate Disaster Recovery of the Cloud Management Platform for VMware Cloud Foundation in Region B If a site failure in Region A occurs, initiate disaster recovery of the vRealize Automation components to keep the workload provisioning functionality of the SDDC available.
Post-Failover Configuration of the SDDC Management Applications for VMware Cloud Foundation After failover of the Cloud Management Platform, vRealize Operations Manager, and vRealize Suite Lifecycle Manager, you must perform additional tasks to ensure that the management applications work as expected.
Additional Post-Failover Configuration After Region A Is Available Again for VMware Cloud Foundation When the original protected region, Region A, is back online, you can fully transfer all features of the SDDC configuration to Region B. Integrate the running management nodes in Region A in the main SDDC configuration that is failed over to Region B.