To start protecting a vApp with a virtual machine from one cloud organization to another, you configure a replication by using the vCloud Availability for Cloud-to-Cloud DR portal.

When you configure a replication, you set a recovery point objective (RPO) to determine the maximum data loss that you can tolerate. For example, an RPO of 1 hour seeks to ensure that a virtual machine loses the data for no more than 1 hour during the recovery. For smaller RPO values, less data is lost in a recovery, but more network bandwidth is consumed keeping the replica up-to-date. See How the Recovery Point Objective Affects Replication Scheduling in vSphere Replication Administration.

Every time that a virtual machine reaches its RPO target, the vCloud Availability Replicator records approximately 3800 bytes of data in the vCenter Server events database. If you set a low RPO period, it can create a large volume of data in the database. To reduce the volume of data that is kept in the vCenter Server events database, limit the number of days that vCenter Server retains event data. Alternatively, set a higher RPO value.

vCloud Availability Replicator guarantees crash consistency among all the disks that belong to a virtual machine. If you use quiescing, you might obtain a higher level of crash consistency among the disks that belong to a virtual machine. The available quiescing types are determined by the virtual machine's operating system. See Compatibility Matrixes for vSphere Replication for quiescing support for Windows and Linux virtual machines.