You can use vSphere Replication to configure a replication from cloud to your local site.
If your local site was recovered from a major breakdown and you need to restore it, or you cannot configure a reverse replication, you can configure a new replication from cloud to synchronize data from cloud to your local site.
You can configure a replication from cloud for only one virtual machine in a vApp.
Verify that the cloud site is available and connected to the local site. See Connect to a Cloud Provider Site in vSphere Replication for Disaster Recovery to Cloud.
Verify that the list of incoming replications does not contain a replication for the virtual machine that you want to configure for replication from cloud. See Stop a Replication From Cloud in vSphere Replication for Disaster Recovery to Cloud.
- Use the vSphere Web Client to connect to your local site.
- Navigate to the vSphere Replication tab under Monitor, and click Incoming Replications.
- Above the list of incoming replications, click the Configure replication from cloud provider icon ().
The Configure Replication From Cloud Provider wizard opens.
- On the Source site page, select the cloud provider site where the virtual machine is located.
If you have created a connection to the cloud provider, select the source 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 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.
- On the Available VMs page, select the virtual machine that you want to replicate.
You can select only one virtual machine from a vApp.
- Accept the automatic assignment of a vSphere Replication server or select a particular server on the local site and click Next.
- On the Target location page, click Edit to select the datastore where replication data will be saved.
If you want to use existing disks as seeds for the replication, browse the datastore to locate the folder where the seed disks are located.
- (Optional) To configure the replication of individual disks, click the name of the source virtual machine.
The list of disks on the source virtual machine expands.
For each disk, you can select the virtual format, storage policy, and a datastore where it is replicated. If the source virtual machine contains more than one disk, you can disable the replication of a disk by clicking Disable in its Replication Enabled row.
- (Optional) On the Replication options page, select the quiescing method for the guest operating system of the source virtual machine.
Quiescing options are available only for virtual machines that support quiescing. vSphere Replication does not support VSS quiescing on Virtual Volumes.
- (Optional) Select Network Compression.
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.
- On the Recovery settings page, use the RPO slider or the time spinners to set the acceptable period for which data loss is acceptable in the case of a site failure.
The available RPO range is from 15 minutes to 24 hours.
- (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.
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 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 should not exceed 4 hours, so that vSphere Replication can create 6 instances in 24 hours.
- 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 incoming replications on the vSphere Replication tab under Monitor.
If the replication source virtual machine is powered off, the replication remains in Not Active state until you power on the virtual machine.
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 in vSphere Replication for Disaster Recovery to Cloud.
You can pause, resume, sync, test, recover, and stop replications from cloud, but you cannot reconfigure or move these replications between vSphere Replication servers.