In the VMware Cloud Director Availability Tenant Portal or in the VMware Cloud Director Availability vSphere Client Plug-In, you can protect or migrate workloads by replicating vApps or virtual machines.

Protect or migrate vApps and virtual machines by replicating the workload from one site to another. The replications can be incoming to the site, or outgoing from the site.

Replication Types

Migrating a vApp or a virtual machine to a remote organization runs the workload in the destination site.
Protecting a vApp or a virtual machine from one organization to another keeps the workload running in the source site.

From VMware Cloud Director Availability 4.1, the service provider separately enables migrations and protections in the replication policies either only incoming or only outgoing, or both, or neither. In previous versions, the service provider controls both replication types together, as incoming replications or outgoing replications.

In a newly deployed VMware Cloud Director Availability 4.1 or later, the replications by default are disabled in the default replication policy by disabling the protections and disabling the migrations. To enable the site for replications, the service provider must modify the default policy or assign a custom policy to the organizations. For more information, see Configuring Replication Policies.

After upgrading from a previous version, replication policies with enabled incoming replications now have enabled incoming migrations and enabled incoming protections. Policies before the upgrade with disabled incoming replications now have disabled incoming migrations and disabled incoming protections. Similarly, the previous outgoing replications now control the outgoing migrations and outgoing protections.

A VMware Cloud Director Availability 4.1 site interprets previous versions of paired sites where replications are enabled as enabled both migrations and protections. For more information about pairing sites with mismatching versions, see Managing Connections Between Cloud Sites in the VMware Cloud Director Availability Administration Guide document.

Recovery Point Objective - RPO

The RPO is the longest tolerable time frame of data loss. For example, with one hour RPO the recovered virtual machine can have no more than one hour of data lost. Shorter RPO intervals, ensure less data loss during recovery, at the expense of consuming more network bandwidth to keep the replica up to date. For more information on the RPO setting, see How the Recovery Point Objective Affects Replication Scheduling in the VMware vSphere Replication Administration documentation.

When each virtual machine reaches its RPO target, the Replicator Service writes about 3800 bytes in the vCenter Server events database. Low RPO values, increase the volume of event data in the database. You can limit the number of days that vCenter Server retains event data, or set a longer RPO value to reduce the volume of event data.

Note: For a migration, the RPO is 24 hours by default.


The Replicator Service guarantees a failure consistency among all disks in a virtual machine. Enabling quiescing might obtain a higher level of failure consistency among the disks that belong to a virtual machine. The operating system of a virtual machine determines the available quiescing types. Quiescing is available only for virtual machine operating systems that support quiescing. For more information, see Guest OS Quiescing Support in the vSphere Replication documentation.

Replicated Workload Settings

VMware Cloud Director Availability preserves and periodically synchronizes the VMware Cloud Director settings that accompany the vApps or the virtual machines in a replication. After a successful protection or migration, VMware Cloud Director Availability reads these settings from the source site and applies them to the destination site, at the end of the replication workflow.
Table 1. Replicated vApp Settings
vApp Settings Replicated in Version 3.0 Replicated in Version 3.5 or Later
vApp Name Yes Yes
Description Yes Yes
Leases - -
Starting and Stopping VMs Configuration - -
Мetadata Yes Yes
vApp Networks - Yes
Table 2. Replicated VM Settings
VM Settings Replicated in version 3.0 Replicated in version 3.5 or later
VM Name Yes Yes
Computer name Yes Yes
Description Yes Yes
Hot add settings - -
Guest OS Customization - Yes
Guest properties - Yes
Resource allocation - -
Metadata Yes Yes