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
vSphere Replication RPO Violations
You might encounter RPO violations even if vSphere Replication is running successfully at the recovery
site.
Problem
When you replicate virtual machines, you might encounter RPO violations.
Cause
RPO violations might occur for one of the following reasons:
n
Network connectivity problems between source hosts and vSphere Replication servers at the target
site.
n
As a result of changing the IP address, the vSphere Replication server has a different IP address.
n
The vSphere Replication server cannot access the target datastore.
n
Slow bandwidth between the source hosts and the vSphere Replication servers.
Solution
n
Search the vmkernel.log at the source host for the vSphere Replication server IP address to see
any network connectivity problems.
n
Verify that the vSphere Replication server IP address is the same. If it is different, reconfigure all the
replications, so that the source hosts use the new IP address.
n
Check /var/log/vmware/*hbrsrv* at the vSphere Replication appliance at the target site for
problems with the server accessing a target datastore.
n
To calculate bandwidth requirements, see http://kb.vmware.com/kb/2037268.
vSphere Replication Appliance Extension Cannot Be Deleted
If you delete the vSphere Replication appliance virtual machine, the virtual appliance management
interface (VAMI) is not available to delete the appliance extension that still exists in vCenter Server.
Problem
Deleting the vSphere Replication appliance does not remove the vSphere Replication extension from
vCenter Server.
Solution
1 Use the Managed Object Browser (MOB) to delete the vSphere Replication extension manually.
2 Redeploy the appliance and reconfigure the replications.
For more details, see Unregister vSphere Replication from vCenter Server if the Appliance Was
Deleted in the vSphere Replication Installation and Configuration guide.
Using VMware vSphere Replication
VMware, Inc. 47