6.0

What to do next
On the vSphere Replication tab under Monitor, you can check the state of each replication. See “Monitoring
the Status of Replication Tasks,” on page 39.
You can click a replication task in the list and use the tabs at the bottom of the vSphere Web Client to view
details about the replication, the recovery status, and the latest performed test, if test results are not cleared
yet.
Configure a Cloud Replication Task for Multiple Virtual Machines
To configure batches of virtual machines for replication to the cloud, you can select multiple virtual
machines and start the Configure Replication wizard.
When you configure 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. The RPO value affects replication
scheduling, but vSphere Replication does not adhere to a strict replication schedule. See the topic How the
Recovery Point Objective Affects Replication Scheduling in the vSphere Replication Administration document.
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 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. See Configure 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 quiescing, you might obtain a higher level of crash consistency amongst 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 6.0 for quiescing support for Windows and Linux
virtual machines.
If you plan to use replication seeds, read and understand the information in topic “Using Replication Seeds
for Replications to Cloud,” on page 26.
NOTE By default, when you configure a virtual machine for replication to cloud, its NICs and MAC
addresses are copied automatically to the target site as part of the provisioning of the placeholder virtual
machine. If the test network is not isolated from the production network and these networks have common
routing, a test recovery of a replicated virtual machine might result in duplicate MAC addresses in your
virtual data center. See “Disable the Automatic Export of MAC Addresses During Replication,” on page 16.
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 the target cloud organization.
n
Configure a connection to the cloud organization to which you want to replicate data. See “Connect to a
Cloud Provider Site,” on page 14.
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 Select the virtual machines for which you want to configure replications.
vSphere Replication for Disaster Recovery to Cloud
24 VMware, Inc.