Recovery hosts must be in maintenance mode so that virtual machines do not end up running in the recovery site as this would result in traffic between the recovery site and the primary site. The reason for this is that the vCloud Networking and Security Edge is only available in one site at a time. Having the hosts’ in maintenance mode also keeps them in sync, with all the changes that happen in the primary set.

If an organization has organization virtual datacenter networks that are directly attached the process is as outlined in the existing vCloud DR recovery process. All of the vApps on that network need to be re-IPed to the correct addressing used in the recovery site Layer 3 network.

However, if the organization is using isolated networks that are VLAN-backed, they need to be recreated on the recovery site using the associated VLAN IDs available in the recovery site and the vApps that are reconnected to the new network. If they were port group-backed, the port groups still exist in the recovery site, but their definitions need to be revisited to verify that they were valid from a configuration point of view. Ease of recovery is afforded by using VXLAN backed networks outlined in this scenario, be they NAT routed or isolated.