6.0

5 On the Target location page, select where to store replication data.
Option Procedure
Use storage policy
From the drop-down menu, select the storage policy for replication
placement and click Next.
Use replication seeds
a Click Next to navigate to the list of available seed vApps on the target
site.
b Select a seed vApp from the list and click Next.
NOTE If you remove a disk from a replication source virtual machine, the
seed disk is not deleted from the datastore on the target site.
6 (Optional) On the Replication options page, select the quiescing method for the guest operating system
of the source virtual machine.
NOTE Quiescing options are available only for virtual machines that support quiescing.
7 (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.
8 On the Recovery settings page, use the RPO slider or the time spinners 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.
9 (Optional) To save multiple replication instances that can be converted to snapshots of the source
virtual machine during recovery, select Enable in the Point in time instances pane, and adjust the
number of instances to keep.
NOTE You can keep up to 24 instances for a virtual machine. This means that 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, and requires that the RPO period is short enough for these instances to be created.
Because vSphere Replication does not check whether the RPO settings will create enough instances to
keep, and does not display a warning message if the number of instances is not sufficient, 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 should not exceed 4
hours, so that vSphere Replication can create 6 instances in 24 hours.
10 Click Next.
11 On the Ready to complete page, review the replication settings, and click Finish.
A virtual machine configuration task appears in the Recent Tasks list at the bottom of the
vSphere Web Client. A progress bar indicates that the source virtual machine is being configured for
replication.
If the configuration operation completes successfully, the replication task that you created appears in the list
of outgoing replications on the vSphere Replication tab under Monitor.
NOTE If the replication source virtual machine is powered off, the replication remains in Not Active state
until you power on the virtual machine.
Chapter 4 Replicating Virtual Machines to Cloud
VMware, Inc. 23