5.5
Table Of Contents
- VMware vSphere Replication Administration
- Contents
- vSphere Replication Administration
- Updated Information
- Overview of VMware vSphere Replication
- vSphere Replication Roles and Permissions
- vSphere Replication System Requirements
- Installing vSphere Replication
- Deploying Additional vSphere Replication Servers
- Upgrading vSphere Replication
- Reconfigure the vSphere Replication Appliance
- Reconfigure General vSphere Replication Settings
- Change the SSL Certificate of the vSphere Replication Appliance
- Change the Password of the vSphere Replication Appliance
- Change Keystore and Truststore Passwords of the vSphere Replication Appliance
- Configure vSphere Replication Network Settings
- Configure vSphere Replication System Settings
- Reconfigure vSphere Replication to Use an External Database
- Use the Embedded vSphere Replication Database
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Using vSphere Replication with Virtual SAN Storage
- Replicating Virtual Machines Using Replication Seeds
- Replicating a Virtual Machine in a Single vCenter Server Instance
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Move a Virtual Machine to a New vSphere Replication Server
- Stop Replicating a Virtual Machine
- Reconfiguring Replications
- Performing a Recovery with vSphere Replication
- Monitoring and Managing Replications in vSphere Replication
- Troubleshooting vSphere Replication
- vSphere Replication Limitations
- Access the vSphere Replication Logs
- 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 Disconnected 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
- Increase the Memory of the vSphere Replication Server for Large Deployments
- 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 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
- vSphere Web Client 5.1.x Non-Functioning Option Binds vSphere Replication Traffic to a Specific vmknic
- Configuring Replication Fails After Rebuilding VRMS
- vSphere Replication Operations Run Slowly as the Number of Replications Increases
vSphere Web Client 5.1.x Non-Functioning Option Binds
vSphere Replication Trac 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
configurating new replications. You might see the following error message:
Attempt to configure vSphere Replication for already replicated VM '<VM Name>' while creating group
'<VM Name>'.
There is another virtual machine '<VM Name>' that has the same instance UUID '<UUID>' as the one that
you
try to configure.
The existing vSphere Replication is configured for protection site '<Site Name>', please refer to the
documentation for troubleshooting options.
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.
VMware vSphere Replication Administration
VMware, Inc. 94