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
Reconnecting Sites Fails If One Of the vCenter Servers Has
Changed Its IP Address
When the vCenter Server address of one site changes, the connection status between two sites is
displayed as Connection issue and you cannot reconnect the sites.
Problem
If you have two connected sites, and the vCenter Server address of either site changes, the connection
status Connection issue appears and you cannot reconnect the sites.
Solution
1 Open the VAMI for the vSphere Replication appliance that is registered to the vCenter Server whose
address has changed.
2 Reconfigure the vSphere Replication appliance with the new vCenter Server address.
3 Click Save and Restart.
4 In the vSphere Web Client, verify that the status of the connection between the two sites is
Connection issue.
5
Select Reconnect to the selected site (
).
6 Enter the IP address or host name of the server where the Platform Service Controller (PSC) runs,
and provide the credentials of a user that has the VRM remote.Manage VRM privilege assigned.
You can check the PSC address in the vSphere Replication VAMI on the target site, on the SSO tab
under VR, in the LookupService Address text box.
7 In the list of available vCenter Server instances, select the vCenter Server with the changed IP
address and click OK.
8 Verify that the connection between the two sites is successfully restored and the status is Connected.
Uploading a Valid Certiļ¬cate to vSphere Replication Results in a
Warning
When you upload a custom certificate to the vSphere Replication appliance, you see a warning even if
the certificate is valid.
Problem
When you use the virtual appliance management interface (VAMI) in Internet Explorer to upload
certificates to the vSphere Replication appliance, you see a certificate error:
The certificate installed with warnings. Remote VRM systems with the 'Accept only SSL certificate
signed by a
trusted CA' option enabled may be unable to connect to this site for the following reason: The
certificate was not issued
for use with the given hostname: vr_appliance_hostname.
Using VMware vSphere Replication
VMware, Inc. 50