8.1
Table Of Contents
- vSphere Replication for Disaster Recovery to Cloud
- Contents
- About Disaster Recovery to Cloud
- Disaster Recovery to Cloud System Requirements and Compatibility
- Installing and Configuring vSphere Replication to Cloud
- Installing vSphere Replication for Disaster Recovery to Cloud
- Upgrading vSphere Replication from Earlier Product Versions
- Configure the NTP Synchronization in Your Environment
- How vSphere Replication Connects to Cloud
- Configuring the Connection to the Cloud
- Connect to a Cloud Provider Site
- Reconfiguring a Site Pair and Breaking a Site Pair
- Select Recovery Networks on the Target Virtual Data Center
- Select Recovery Networks from Cloud to the Local Site
- Disable the Automatic Export of MAC Addresses During Replication
- Cloud Connection States
- Reconnect to a Cloud Provider Site
- Replicating Virtual Machines to Cloud
- Reconfiguring Replications to the Cloud
- Recovering Virtual Machines to Cloud
- Configuring Replications from Cloud
- Recovering Virtual Machines from Cloud
- Monitoring and Managing Replications in vSphere Replication
5 On the Virtual machines page, select the virtual machines you want to replicate and click Next.
6 Select a cloud provider site as a target site and click Next.
7 On the Target location page, select the location for the target vApp and click Next.
You can use a storage policy or a previously imported vApp on the target site as a replication seed.
8 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.
9 (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.
10 (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.
11 (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.
12 On the Ready to complete page, review the replication settings, and click Finish.
vSphere Replication starts an initial full synchronization of the virtual machine files to the designated
datastore on the target site.
If the configuration operation completes successfully, the replication task that you created appears in the
list of forward replications.
Note If a replication source virtual machine is powered off, the replication starts after you power on the
virtual machine.
vSphere Replication for Disaster Recovery to Cloud
VMware, Inc. 19