6.6

Cause
The passive node has less available disk space than the active node, preventing updates from being replicated
to the passive node. The quantity of updates from the active node exceeds the passive node's available disk
space.
Solution
◆
Free up some additional disk space on the passive node. Do not delete data from the protected set to
prevent data loss in the event of a failover.You could update the disk subsystem on the passive node.
After allocating space, start replication.
Registry Status is Out-of-Sync
The Registry can be reported as Out-of-sync when one or more Registry keys fail to synchronize.
Registry Security Issues
Inability to access the registry prevents replication of the registry.
Problem
vCenter Server Heartbeat is unable to read, synchronize, or replicate the registry.
Cause
If a protected registry key has permissions that deny Write access to the System account, this can prevent
vCenter Server Heartbeat from synchronizing or replicating it.
Solution
◆
Change the permissions on the affected registry key to grant the System account Full Control.
Channel Drops
When the VMware Channel loses connection between the nodes, the following scenarios can occur.
Performance Issues
Poor performance can be experienced as a result of a channel loss.
Problem
The message java.io.IOException: An existing connection was forcibly closed by the remote host appears in the active
server's NFLog.txt file, and the VMware Channel connection between the servers is lost.
VMware, Inc. 85
Chapter 5 vCenter Server Heartbeat Diagnostics