6.5
Table Of Contents
- Using VMware vSphere Replication
- Contents
- About Using VMware vSphere Replication
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- How the 5 Minute Recovery Point Objective Works
- How Retention Policy Works
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Using vSphere Replication with Virtual SAN Storage
- Using vSphere Replication with vSphere Storage DRS
- How vSphere Replication Synchronizes Data Between vCenter Server Sites During Initial Configuration
- Replicating Virtual Machines Using Replication Seeds
- Replicating a Virtual Machine in a Single vCenter Server Instance
- Best Practices For Using and Configuring vSphere Replication
- Configure Replication for a Single Virtual Machine to vCenter Server
- Configure Replication for Multiple Virtual Machines to vCenter Server
- Move a Replication to a New vSphere Replication Server
- Stop Replicating a Virtual Machine
- Reconfiguring Replications
- Reconfigure Recovery Point Objectives (RPO) in Replications
- Resize the Virtual Machine Disk Files of a Replication that Uses Replication Seeds
- Resize Virtual Machine Disk Files of a Replication that Does Not Use Replication Seeds
- Change the Point in Time Settings of a Replication
- Change the Target Datastore Location of a Replication
- Monitoring and Managing Replications in vSphere Replication
- Performing a Recovery with vSphere Replication
- Troubleshooting vSphere Replication
- Generate vSphere Replication Support Bundle
- vSphere Replication Events and Alarms
- Solutions for Common vSphere Replication Problems
- Error at vService Bindings When Deploying the vSphere Replication Appliance
- OVF Package is Invalid and Cannot be Deployed
- Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved
- Application Quiescing Changes to File System Quiescing During vMotion to an Older Host
- Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores
- vSphere Replication Service Fails with Unresolved Host Error
- Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0
- vSphere Replication Sites Appear in the Not Authenticated State
- Error Recovering Virtual Machine in a Single vCenter Server Instance
- vSphere Replication RPO Violations
- vSphere Replication Appliance Extension Cannot Be Deleted
- vSphere Replication Does Not Start After Moving the Host
- Unexpected vSphere Replication Failure Results in a Generic Error
- Reconnecting Sites Fails If One Of the vCenter Servers Has Changed Its IP Address
- Uploading a Valid Certificate to vSphere Replication Results in a Warning
- vSphere Replication Server Registration Takes Several Minutes
- Generating Support Bundles Disrupts vSphere Replication Recovery
- vSphere Replication Operations Take a Long Time to Complete
- vSphere Replication Operations Fail with Authentication Error
- vSphere Replication Does Not Display Incoming Replications When the Source Site is Inaccessible
- vSphere Replication is Inaccessible After Changing vCenter Server Certificate
- vSphere Replication Cannot Establish a Connection to the Hosts
- Anti-virus Agent in Firewall Terminates Virtual Machine Replication
- Initial Full Synchronization of Virtual Machine Files to VMware Virtual SAN Storage Is Slow
- Configuring Replication Fails Because Another Virtual Machine has the Same Instance UUID
- Not Active Replication Status of Virtual Machines
- vSphere Replication Operations Run Slowly as the Number of Replications Increases
- Error at Reconfiguring the vSphere Replication Management Server from the Virtual Appliance Management Interface
- Unable to Establish an SSH Connection to the vSphere Replication Appliance
- The Replication Pauses When You Add a New Disk To the Source VM
- The vSphere Replication Appliance Root File System Switches to Read-only Mode and Login Fails
Recover Virtual Machines by Using vSphere Replication
With vSphere Replication, you can recover virtual machines that were successfully replicated at the target
site. You can recover one virtual machine at a time.
Prerequisites
Verify that the virtual machine at the source site is powered off. If the virtual machine is powered on, an
error message reminds you to power it off.
Procedure
1 Log in to the target site by using the vSphere Web Client.
2 On the Incoming Replications tab, right-click the virtual machine to recover and select Recovery.
3 Select whether to recover the virtual machine with all the latest data, or to recover the virtual machine
with the most recent data available on the target site.
Option Description
Synchronize recent changes Performs a full synchronization of the virtual machine from the source site to the
target site before recovering the virtual machine. Selecting this option avoids data
loss, but it is only available if the data of the source virtual machine is accessible.
You can only select this option if the virtual machine is powered off.
Use latest available data Recovers the virtual machine by using the data from the most recent replication
on the target site, without performing synchronization. Selecting this option results
in the loss of any data that has changed since the most recent replication. Select
this option if the source virtual machine is inaccessible or if its disks are
corrupted.
4 Select the recovery folder and click Next.
5 Select the target compute resource and click Next.
6 If the virtual machine contains hard disks for which you have not enabled replication, select a target
destination to attach an existing disk or detach the disk, and click Next.
This page only appears if the virtual machine contains hard disks for which you have not enabled
replication.
n
To select a target destination, click Browse and navigate to a folder on a datastore in which disk
file is placed.
n
To detach the disk and exclude disk files from the recovery, click Detach.
7 (Optional) Select Power on after recovery.
8 Click Finish.
vSphere Replication validates the provided input and recovers the virtual machine. If successful, the
virtual machine status changes to Recovered. The virtual machine appears in the inventory of the target
site.
Using VMware vSphere Replication
VMware, Inc. 34