5.8

Table Of Contents
vSphere Web Client 5.1.x Non-Functioning Option Binds
vSphere Replication Trac to a Specific vmknic
vSphere Web Client 5.1.x contains an option that binds vSphere Replication traffic to a specific vmknic.
Problem
If you use this option in vSphere Replication version 5.1.x and then upgraded to version 5.5.x, replication
configuration fails due to the underlying connectivity issue.
Solution
Manually edit the esx.conf to remove the incorrect tag value for the specific vmknic or reconfigure the
tagged vmknic to be reachable by vSphere Replication. For details, see
http://kb.vmware.com/kb/2066230.
Configuring Replication Fails After Rebuilding VRMS
If you have two sites and reinstall the vSphere Replication Management Server appliance or reset its
database, configuring replications fails.
Problem
The other site contains information on the old appliance and database, and prevents you from configuring
new replications. You might see the following error message:
Unable to configure replication for virtual machine VM_name because group group_name cannot be created.
Another virtual machine configured_VM_name}' that has the same instance UUID instance_UUID already
exists on protection site source_site_name.
Solution
1 Reinstall VRMS at the other site or reset its database.
2 Connect the sites and register any additional vSphere Replication Server appliances.
3 Remove any temporary hbr* files left over from the target datastore folders.
4 Configure all replications, reusing the existing replica .vmdk files as replication seeds.
vSphere Replication Operations Run Slowly as the Number of
Replications Increases
As you increase the number of virtual machines that you replicate, vSphere Replication operations can
run more slowly.
Problem
Response times for vSphere Replication operations can increase as you replicate more virtual machines.
You possibly experience recovery operation timeouts or failures for a few virtual machines, and RPO
violations.
VMware vSphere Replication Administration
VMware, Inc. 95