Protect a vApp or a virtual machine from one organization to another, and keep the workload running in the source site, by configuring a protection. If the source site is unavailable, after a successful replication you can fail over and power on the source virtual machine in the destination site.


  • Verify that vCloud Availability is deployed in both the source and in the destination sites.
  • If configuring an incoming replication, verify that you are logged in to the site in which the vApp or virtual machine you are about to protect reside.


  1. In the left pane, choose a replication direction.
  2. To protect a virtual machine, in the top of the page click the VM button, or to protect a vApp, click the vApp button.
  3. Click New Protection.
  4. Follow the prompts of the New Replication wizard.
    1. On the Seed VM page, optionally select a vApp or a virtual machine to use as seed and click Next.
    2. On the Protection Settings page, select the settings for the replication, and click Next.
      Option Description
      Target recovery point objective (RPO) Use the slider or click the time intervals to set the acceptable period for which data can be lost if there is a site failure. The available RPO range is from 5 minutes to 24 hours.
      Storage policy From the Storage policy drop-down menu, select the storage policy for placing the recovered virtual machines and for the replicated data before the recovery. For seed vApps and virtual machines, vCloud Availability Replicator uses the storage policy of the seed.
      Retention policy for point in time instances

      To preserve multiple distinct replication instances (snapshots) to which VMs can be recovered, select the option, select the number of replication instances to keep, and select the preservation period.

      The number of preserved replication instances depends on the configured retention policy and requires that the RPO period is short enough for the replication instances to be created. For example, if you select to preserve four replication instances per day, the RPO period must not exceed six hours, to allow for the retention of four replication instances in 24 hours.

      Enable quiesce

      Select the quiescing method for the guest operating system of the source virtual machine.

      Compress replication traffic

      Select to compress the replication data that is transferred through the network and to reduce the network traffic. However, compressing and decompressing data requires more CPU resources on both the source site and the server that manages the target datastore.

    3. On the Scheduling page, select when to start the replication and click Next.
      • Start the replication when the wizard finishes by leaving Immediately selected.
      • (Optional) Schedule the start of the replication by selecting At a specific time.
    4. On the Ready to Complete page, verify that the configuration settings are correct and click Finish.


After the replication finishes, for the vApp and its virtual machines in the Replication type column, you see a Protection state and in the Replication state column you see a Healthy state.