The process of failing over the management components or vApps from a primary vCloud to a disaster recovery site is documented in the VMware vCloud Director Infrastructure Resiliency Case Study (http://www.vmware.com/files/pdf/techpaper/vcloud-director-infrastructure-resiliency.pdf) In cases where stretched Layer 2 networks are present, the recovery of vApps is greatly simplified because vApps can remain connected to the same logically defined virtual networks regardless of the physical location in which the vApps are running. In cases where there is not a stretched Layer 2 network, VXLAN enables simplified DR and implementations of vCloud Director that span multiple locations. This is achieved by creating a Layer 2 overlay network without changing the Layer 3 interconnects already in place. This example illustrates failover of an SRM-based vCloud Director implementation without the need to reassign IP addresses to the virtual machines, as well as the scripted changes that would need to be done to simplify the process.