8.1

7 On the Target datastore page, select a datastore on which to replicate files.
When replicating multiple virtual machines, you can configure a different target datastore for each
virtual machine.
8 (Optional) Select the Select seeds check box.
Replication seeds can reduce the network traffic during the initial full synchronization, but unintended
use of replication seeds might lead to data loss.
9 Click Next.
10 (Optional) On the Select seed page, review the suggested replication seeds and change them if
necessary.
11 Select the The selected seeds are correct check box and click Next.
12 On the Replication settings page, use the RPO slider to set the acceptable period for which data
can be lost in the case of a site failure.
The available RPO range is from 15 minutes to 24 hours.
13 (Optional) To save multiple replication instances that can be converted to snapshots of the source
virtual machine during recovery, select Enable point in time instances and adjust the number of
instances to keep.
Note You can keep up to 24 instances for a virtual machine. For example, if you configure
vSphere Replication to keep 6 replication instances per day, the maximum number of days you can
set is 4 days.
The number of replication instances that vSphere Replication keeps depends on the configured
retention policy, but also requires that the RPO period is short enough for these instances to be
created. Because vSphere Replication does not verify whether the RPO settings will create enough
instances to keep, and does not display a warning message if the instances are not enough, you
must ensure that you set vSphere Replication to create the instances that you want to keep. For
example, if you set vSphere Replication to keep 6 replication instances per day, the RPO period must
not exceed 4 hours, so that vSphere Replication can create 6 instances in 24 hours.
14 (Optional) Enable quiescing for the guest operating system of the source virtual machine.
Note Quiescing options are available only for virtual machines that support quiescing.
vSphere Replication does not support VSS quiescing on Virtual Volumes.
15 (Optional) Select Enable network compression for VR data.
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.
16 Click Next.
17 On the Ready to complete page, review the replication settings, and click Finish.
vSphere Replication for Disaster Recovery to Cloud
VMware, Inc. 29