Reconfigure and Power on the Virtual Machines of vRealize Log Insight for VMware Cloud Foundation in Region BAfter adding application virtual network for vRealize Log Insight virtual machines in region B and configuring dynamic routing, connect the virtual machines of vRealize Log Insight in Region B to the application virtual network. Power on the vRealize Log Insight as per the start up order. Update the NTP Sources on vRealize Operations Manager for VMware Cloud Foundation in Region ABefore you fail over vRealize Operations Manager between regions, update the NTP synchronization settings with an NTP server in each region. Place the Virtual Machines of a Management Solution in a Dedicated Folder for VMware Cloud FoundationVirtual machine folders provide a logical grouping of virtual machines. You place the virtual machines of vRealize Automation and of vRealize Operations Manager in to dedicated folders. You later create a mapping between these folders in Site Recovery Manager as a part of the fail-over setup. Create the NSX Load Balancer for vRealize Automation and vRealize Operations Manager for VMware Cloud Foundation in Region BThe NSX load balancer used for vRealize virtual machines can not be failed over, as such one must be configured in Region B to support the load balancing requirements of these applications. Update Universal Logical Switch information on the SDDC manager for VMware Cloud Foundation in Region BWhen configuring the environment for disaster recovery, the universal logical switch that is created in Region A is made available in region B and the virtual machines of vRealize Log Insight are moved to a different port group. You must update the SDDC Manager database in Region B to maintain connectivity for the virtual machines. You perform these steps in SDDC Manager in Region B only.