The vCloud Availability for Cloud-to-Cloud DR 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 virtual machines to the destination site. If a virtual machine suffers from a virus or corruption and you have configured vCloud Availability Replicator to keep point-in-time instances (snapshots), you can recover the virtual machine and then revert it to a snapshot of the virtual machine in its uncorrupted state.
To protect virtual machines or vApps, you configure a replication. When you protect a virtual machine or vApp from the local site, for example site 1, you reserve some disk space on the remote site, for example site 2.
A consecutive Failover operation recovers the vApp from the local to the remote site. The vApp, for example vApp1 is now hosted in site 2. The virtual machines in vApp1 are now running in site 2.
A Reverse operation is possible after a successful Failover operation. The Reverse operation is similar to configuring a new replication and 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 Failover operation from site 2 back to the original source site 1.
When you run a Failover operation from site 2, a vApp1(1) appears in the original source site 1 in a POWERED ON state. Your virtual machines are now running in the original source site 1, inside vApp1(1). During Failover operations back to the original source, 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 virtual machines.