6.0
Table Of Contents
- vSphere Replication for Disaster Recovery to Cloud
- Contents
- About Disaster Recovery to Cloud
- Updated Information
- Disaster Recovery to Cloud System Requirements and Compatibility
- Installing and Configuring vSphere Replication to Cloud
- Replicating Virtual Machines to Cloud
- Reconfiguring Replications to the Cloud
- Recovering Virtual Machines to Cloud
- Configuring Replications from Cloud
- Monitoring and Managing Replication Tasks
- Troubleshooting vSphere Replication for Disaster Recovery to Cloud
- Index
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 In the inventory tree, right-click the virtual machine that you want to replicate and select All vSphere
Replication Actions > Configure Replication.
The Configure Replication wizard opens.
3 Select Replicate to a cloud provider and click Next.
4 Select the target site to which you want to replicate the virtual machine.
n
If you have created a connection to the cloud provider, select the target virtual data center from the
list and click Next.
If the status of the connection is Not authenticated, you must provide credentials to authenticate
with the cloud organization. If you have not selected the networks on the target site to use for
recovery operations, you are prompted to do so.
n
If you have not created a connection to the cloud provider, click New Provider VDC, click Next,
and follow the on-screen prompts to connect to the target cloud organization.
vSphere Replication for Disaster Recovery to Cloud
22 VMware, Inc.