5.5

Table Of Contents
Troubleshooting
vSphere Replication 11
Known troubleshooting information can help you diagnose and correct problems that occur while
replicating and recovering virtual machines with vSphere Replication.
If you have problems with deploying vSphere Replication, replicating or recovering virtual machines, or
connecting to databases, you can troubleshoot them. To help identify the problem, you might need to
collect and review vSphere Replication logs and send them to VMware Support.
See Chapter 10 Monitoring and Managing Replications in vSphere Replication to learn about replication
states and how to identify replication issues.
You can also search for solutions to problems in the VMware knowledge base at http://kb.vmware.com.
This section includes the following topics:
n
vSphere Replication Limitations
n
Access the vSphere Replication Logs
n
vSphere Replication Events and Alarms
n
Solutions for Common vSphere Replication Problems
vSphere Replication Limitations
vSphere Replication is subject to some limitations when replicating virtual machines.
Replicating Large Volumes
vSphere Replication can replicate virtual machines greater than 2TB with the following limitations:
n
If you move a virtual machine with replicated disks over 2032GB back to a machine on an older
release, vSphere Replication cannot replicate or power on the virtual machine.
n
Full sync of very large disks can take days.
n
vSphere Replication must track changed blocks and consumes more memory on larger disks.
n
vSphere Replication tracks larger blocks on disks over 2TB. Replication performance on a disk over
2TB might be different on a disk over 2TB for the same workload depending on how much of the disk
goes over the network for a particular set of changed blocks.
n
Replication might consume more or less bandwidth depending on the workload and how it changes
blocks on the disk during the RPO interval.
VMware, Inc.
75