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
2 If you cannot upgrade ESXi Server to version 5.1 or later, redistribute the replicated virtual machines
or adjust their RPO.
n
Reduce the number of virtual machines with a short RPO that replicate to a single VMFS volume,
for example by using a larger number of smaller datastores.
n
Increase the RPO of the virtual machines replicating to a single VMFS volume to create a longer
harmonic mean RPO.
vSphere Replication Sites Appear in the Disconnected State
vSphere Replication sites that you have connected appear in the disconnected state.
Problem
In configurations with two vSphere Replication sites that each include a vCenter Server instance and a
vSphere Replication appliance, the vSphere Replication sites can appear in the disconnected state, even
if you have successfully connected the sites.
Cause
Sites that you have successfully connected can appear in the disconnected state when you establish a
new login session to the vSphere Web Client and the previous login session has timed out. In this case,
the disconnected state reflects the connection to the remote site from the vSphere Web Client and not the
state of the connection between the sites. If the two sites are running, vSphere Replication still performs
replications at the schedules that you have configured. To restore the connected state in the
vSphere Web Client, you must provide the login credentials for the remote site.
Solution
1 In the vSphere Web Client, select the vCenter Server to which the vSphere Replication is registered.
2 Click the Manage tab, then vSphere Replication.
3 In Target Sites, right-click the remote site, select Reconnect site, then click Yes.
4 Enter the login credentials for the remote site, and click OK.
Error Recovering Virtual Machine in a Single vCenter Server
Instance
You might receive an error message when you are recovering a virtual machine with the same name in a
single vCenter Server instance.
Problem
Failed to register the recovered virtual machine 'VM_NAME' with
config file <path_to_config_file>.
VMware vSphere Replication Administration
VMware, Inc. 85