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
Transferred Bytes
Corelating the total number of transferred bytes and the number of RPO violations can help you make
decisions on how much bandwidth might be required to meet RPO objectives.
Table 3‑3. Analysing the Rate of Transferred Bytes and RPO Violations
Graph Values Probable Cause Solution
n
High rate of transferred bytes and high number of RPO
violations
n
Low rate of transferred bytes and high number of RPO
violations
The network bandwidth might
be insufficient to
accommodate all replications.
n
Maximize the transferred
bytes graph and use the
drop-down menu to filter
the data by virtual
machine. Disable the
replication on some virtual
machines with high change
rate to allow lower change
rate virtual machines to
meet their RPO objectives.
n
Increase the network
bandwidth for the selected
host.
n
High rate of transferred bytes and a few or no RPO
violations
n
Low rate of transferred bytes and a few or no RPO violations
The environment operates as
expected.
N/A
Replicated Virtual Machines by Host
The number of replicated virtual machines by host help you determine how replication workload is
distributed in your environment. For example, if the number of replicated virtual machines on a host is
high, the host might be overloaded with replication jobs. You might want to verify that the host has enough
resources to maintain all replication jobs. If needed, you can check for hosts with low number of
replicated virtual machines and optimize the allocation of resources in your environment.
Identifying Replication Problems in the Issues Tab
You can view and troubleshoot possible vSphere Replication problems that might occur during replication
at the Issues tab of the corresponding vCenter Server.
Table 3‑4. Possible Replication Problems
Problem Cause Solution
Not
Active
The replication is not active because the virtual machine is
powered off and a warning icon appears. Replication is not running
for that virtual machine.
Power on the virtual machine to resume
replication.
Paused If you paused the replication, a warning icon appears. Resume the paused replication from the Issues
tab.
Error If you added a disk on a virtual machine which is already
configured for replication, the replication pauses and goes to an
error state.
Reconfigure the replication and enable or disable
the newly added disk.
Using VMware vSphere Replication
VMware, Inc. 30