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.
Reconfigure the NSX Instance for the Management Cluster for VMware Cloud Foundation in Region A When Region A is back online after a disaster recovery to Region B, to avoid conflicts in the management and control planes of NSX, modify the roles of the NSX Managers and delete certain NSX components in Region A.
Disconnect the Application NSX Load Balancer from the SDDC Network for VMware Cloud Foundation in Region A Because operations management and cloud management applications are failed over to Region B, disconnect the NSX load balancer for the SDDC management applications in Region A. If the load balancer remains connected to the network, the load balancer might receive data for a management application that is failed over to the other region.
Configure Routing Between Region A and Region B After Failover for VMware Cloud Foundation When Region A is back online after a disaster recovery to Region B, you must update the routing configuration to restore routing between Region B and Region A and to optimize route selection.
Restore the Original DNS Record for vRealize Log Insight for VMware Cloud Foundation in Region A When Region A is back online, update the DNS record for the vRealize Log Insight instance in Region A with the original IP address so that the management applications that are running again in Region A can start sending log data to vRealize Log Insight.
Connect vRealize Operations Manager to vRealize Log Insight for VMware Cloud Foundation in Region A After the failover of the management applications to Region B and the recovery of the Region A environment, to continue log collection from Region A, reconfigure the vRealize Log Insight Adapter to integrate vRealize Log Insight with vRealize Operations Manager.