The vCloud Availability Portal User Guide describes how to replicate vApps from one vCloud Director instance to another, configure these replications and monitor their states.

You use the present workflows to protect and migrate vApps.

During replication, the vCloud Availability Replicator replicates all aspects of the VMs to the destination site. If a virtual machine suffers from a virus or corruption and you have configured vCloud Availability Replicator to keep PIT instances (snapshots), you can recover the virtual machine and then revert it to a snapshot of the virtual machine in its uncorrupted state.

When you run a Protect operation for a given vApp from the source site, for example site 1, you reserve some disk space on the target site, for example site 2.

A consecutive Failover operation recovers the vApp from the source to the target site. The vApp, for example vApp1 is now hosted in site 2. The VMs in vApp1 are now running in site 2.

A Reverse operation is possible after a successful Failover operation. The Reverse operation replicates the recovered vApp1 to the original source site and reserves some disk space in site 1. After a successful Reverse operation vApp1 is ready for a Failback operation from site 2 back to site 1.

When you run a Failback operation from site 2, a vApp1(1) appears in site 1 in a POWERED ON state. Your VMs are now running in site 1, in vApp1(1). During the Failback operation, vCloud Availability for Cloud-to-Cloud DR stores the network configuration for vApp1 as it was set when the initial Protection happened. You can browse the initial vApp1 in site 1 to review the vApp network configuration. vApp1 is an empty vApp that contains no VMs.