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
2 Select the vCenter Server root folder.
3 Click the Summary tab.
Replication States for Virtual Machines
vSphere Replication shows the replication states of virtual machines that you configured for replication.
State Details for Each State
OK OK, Moving, Recovering
Warning Paused, OK(RPO violation), Not Active, Not Active(RPO violation), FullSync(RPO violation), Sync(RPO violation)
In Progress FullSync, Sync, Initial Full Sync, Configuring
Error Error, Error(RPO violation)
Recovered Recovered
Note If a replication is in the Not Active replication state, you might have connected the source and
target sites using network address translation (NAT). vSphere Replication does not support NAT. Use
credential-based authentication and network routing without NAT when connecting the sites. Another
cause for a Not Active replication state might be that the source virtual machine is powered off. Automatic
replication works only on virtual machines that are powered on.
Monitor Replication for Virtual Machines
You can monitor the replication status and view information for virtual machines configured for replication.
For more information about how to identify replication errors, see Identifying Replication Problems in the
Issues Tab.
Prerequisites
n
Verify that vSphere Replication is running.
n
Verify that the virtual machines are configured for replication.
Procedure
1 Log in to the vSphere Web Client.
2 Select the vCenter Server to which the vSphere Replication appliance is registered.
3 Click Monitor, then click vSphere Replication.
4 Select Outgoing Replications to see details of the virtual machines replicated from this site.
5 Select Incoming Replications to see details of the virtual machines replicated to this site.
According to the status of a selected replication, you can perform different actions on the replication.
Using VMware vSphere Replication
VMware, Inc. 27