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
Solution
When running vSphere Replication, if response times are greater than 30 ms, reduce the number of
virtual machines that you replicate to the datastore. Alternatively, increase the capabilities of your
hardware. If you suspect that the I/O load on the storage is an issue and you are using VMware Virtual
SAN storage, monitor the I/O latency by using the monitoring tool in the Virtual SAN interface.
Error at Reconfiguring the vSphere Replication Management
Server from the Virtual Appliance Management Interface
When you click Save and Restart in the virtual appliance management interface (VAMI) of
vSphere Replication, the HMS service cannot start, and you can no longer manage replications.
Problem
If you use the virtual appliance management interface (VAMI) to install a new SSL certificate, to change
the IP address of the VRM host, or apply another setting on the VR tab, and you click Save and Restart,
the following error message appears:
Missing command-line argument.
Cause
The OVF environment of the vSphere Replication appliance might be missing or corrupted.
Solution
1 Establish an SSH connection to the vSphere Replication appliance and navigate
to /opt/vmware/etc/vami/.
2 Open the ovfEnv.xml.
a If the ovfEnv.xml file is not empty, search for the vServiceEnvironmentSection element. If the
vServiceEnvironmentSection element is missing, there might be a problem with the vCenter
Management Web Services process on the vCenter Server machine. Verify that the vCenter
Management Web Services is running on the vCenter Server machine and then try powering the
vSphere Replication appliance off and on. To power the appliance off and on, use the
vSphere Web Client while you are connected to the vCenter Server, and not directly to the ESXi
host.
b If the ovfEnv.xml file is empty, try to power off and on the vSphere Replication appliance by
using the vSphere Web Client while you are connected to the vCenter Server, and not directly to
the ESXi host.
3 If powering the vSphere Replication appliance does not resolve the issue, most certainly the
appliance has been temporarily removed and re-added in the vCenter Server. There is no solution for
restoring the OVF environment in that case. You must re-deploy the vSphere Replication appliance by
using an empty database, and configure all replications from scratch.
Using VMware vSphere Replication
VMware, Inc. 57