5.8

A virtual machine conguration task appears in the Recent Tasks list in the upper right of the
vSphere Web Client. A progress bar indicates that the source virtual machine is being congured for
replication.
If the conguration completes successfully, the replication task that you created appears in the list of
outgoing replications on the vSphere Replication tab under Monitor.
If the source virtual machine is powered on, the initial sync-up operation starts after the conguration . If
the source virtual machine is powered o, the initial sync starts when you power on the virtual machine.
What to do next
On the vSphere Replication tab under Monitor, you can check the status of each replication. See “States of
Replication Tasks,” on page 29.
You can click a replication task in the list and use the tabs in the boom of the vSphere Web Client to view
details about the replication, the recovery status, and the latest performed test, if test results are not cleaned
up yet.
Configure a Cloud Replication Task for Multiple Virtual Machines
To congure batches of virtual machines for replication to the cloud, you can select multiple virtual
machines and start the Congure Replication wizard.
When you congure replication, you set a recovery point objective (RPO) to determine the period of time
between replications. For example, an RPO of 1 hour seeks to ensure that a virtual machine loses no more
than 1 hour of data during the recovery. For smaller RPOs, less data is lost in a recovery, but more network
bandwidth is consumed keeping the replica up to date.
Every time that a virtual machine reaches its RPO target, vSphere Replication records approximately 3800
bytes of data in the vCenter Server events database. If you set a low RPO period, this can quickly create a
large volume of data in the database. To avoid creating large volumes of data in the vCenter Server events
database, limit the number of days that vCenter Server retains event data. See Congure Database Retention
Policy in the vCenter Server and Host Management Guide. Alternatively, set a higher RPO value.
vSphere Replication guarantees crash consistency amongst all the disks that belong to a virtual machine. If
you use VSS quiescing, you might obtain a higher level of consistency. The available quiescing types are
determined by the virtual machine's operating system. See Compatibility Matrixes for vSphere Replication
5.8 for Microsoft Volume Shadow Copy Service (VSS) quiescing support for Windows virtual machines.
Prerequisites
n
Verify that the vSphere Replication appliance is deployed in your environment.
n
Verify that the Disaster Recovery to Cloud service is enabled in your environment and in the target
cloud organization.
n
Congure a connection to the cloud organization to which you want to replicate data. See “Connect to a
Cloud Provider Site,” on page 16.
n
If you plan to use replication seeds, verify that you read and understand the information in topic
“Using Replication Seeds,” on page 25.
Procedure
1 On the vSphere Web Client Home page, click VMs and Templates.
2 Select a data center, navigate to the Related Objects tab, and click the Virtual Machines tab.
3 Use the Ctrl and Shift keys to select the virtual machines for which you want to congure replications.
Chapter 4 Replicating Virtual Machines to Cloud
VMware, Inc. 23