By configuring an incoming replication, you create a replication from a remote to a local cloud site. Successfully configured incoming replications are running in the remote site and are protected in the local site.


  • Verify that the vCloud Availability for Cloud-to-Cloud DR is deployed on both source and destination sites.

  • Authenticate to the cloud organizations occupying the sites from which you want to replicate data. For more information, see Authenticate to Remote Sites as a Tenant.


  1. Log in to the vCloud Availability for Cloud-to-Cloud DR portal as an organization administrator.
  2. In the Incoming Replications pane, click New.

    The New Incoming Replication configuration wizard displays.

  3. In the Source Site tab, select the remote site and click Next.
  4. If you have not authenticated against the remote site, provide your organization administrator credentials.
  5. Select the vApp that you are protecting and click Next.

    If there is powered off virtual machine inside the vApp, replication is configured but full initial synchronization is completed upon powering on the virtual machine.

  6. Select the target virtual data center (VDC) to which you want to replicate the vApp and its VM, and click Next.
  7. On the Protection Settings page, select the configurations for the replication data and click Next.



    Target Recovery Point Objective (RPO)

    Use the RPO slider or the time ranges to set the acceptable period for which data can be lost in the case of a site failure. The available RPO range is from 5 minutes to 24 hours.

    Retention Policy for Point in Time Instances

    To save multiple replication instances (snapshots) to which VMs can be recovered, enable the retention policy for point-in-time instances option, and adjust the number of instances to keep.

    The number of distinct replication instances that vCloud Availability Replicator keeps depends on the configured retention policy, and requires that the RPO period is short enough for these instances to be created. Because vCloud Availability Replicator does not check whether the RPO settings create enough distinct instances to keep, and does not display a warning message if the number of distinct instances is not sufficient, you must ensure that you set vCloud Availability Replicator to create the instances that you want to keep. For example, if you set vCloud Availability Replicator to keep six replication instances per day, the RPO period must not exceed four hours, so that vCloud Availability Replicator can create six instances in 24 hours.

    To avoid any issues, the retention policy interval must be greater than the RPO setting.

    Storage Policy

    From the drop-down menu, select the storage policy for replication placement.

    Enable Quiesce

    Select the quiescing method for the guest OS of the source VM.


    Quiescing is available only for VMs that support quiescing. For more information about quiescing, see Guest OS Quiescing Support section of the Compatibility Matrices for vSphere Replication 8.1

    Compress Replication Traffic

    Compressing the replication data that is transferred through the network saves network bandwidth and might help reduce the amount of buffer memory used on the vSphere Replication Server. However, compressing and decompressing data requires more CPU resources on both the source site and the server that manages the target datastore.

  8. In the Ready To Complete tab, review the replication details and click Finish.


A replication task appears in the Incoming Replications pane and in the Replication Tasks list in the vCloud Availability for Cloud-to-Cloud DR portal.

You can monitor the configuration progress in the Incoming Rreplications pane.


If the replication source VM is powered off, the replication data connections state is Powered off and the Overall health of the replications is displayed in a yellow state until you sync the replication manually or power on the VM.