6.6

■
The active node fails before the handshake that establishes the VMware Channel connection.The passive
node cannot detect that the active node is not responding when the failure occurs and cannot determine
the condition of the active node. The active node suffers a transient failure and the passive node cannot
respond assuming the active role, leaving both nodes in a passive state
■
Both Primary and Secondary nodes experience a power outage simultaneously, for example, they use
the same power source and neither is attached to a UPS. A failover cannot occur and when the nodes
are restarted, each displays the following error message:
Cannot start replication because previous run did not shutdown properly. Check configuration.
Note If you attempt to start vCenter Server Heartbeat without reconfiguring one node in the pair as active,
vCenter Server Heartbeat responds with the following warning:
[U16] Serious configuration mismatch between the two servers. Please reconfigure so there is one and only one Primary,
and one and only one Active.
Solution
To correct two passive nodes:
1 Determine the active node.
2 Shut down vCenter Server Heartbeat on both nodes. Leave any protected applications running on the
node to make active.
3 On the node to make active, start the Server Configuration wizard, and select the active role. Do not
change the identity (Primary or Secondary).
4 On the node to make passive, start the Server Configuration wizard, and confirm the passive node. Do
not change the identity (Primary or Secondary).
5 Restart the passive node. All protected application services stop.
6 Start vCenter Server Heartbeat on both nodes.
Synchronization Failures
When you start vCenter Server Heartbeat, a full system check occurs to verify the following:
■
All protected registry keys and values from the active node are present on the passive node
■
All protected file and folder structures from the active node are present on the passive node
After the full system check completes, the File System Status and the Registry Status display as Synchronized.
However, the File System Status or the Registry Status can also display as Out-of-sync or Synchronized and
busy processing.The following typical scenarios are described with possible causes and workarounds.
Services Running on the Passive Node
Services running on a passive node is not normal behavior and can prevent synchronization.
Problem
File System Status is Out-of-sync or Synchronized and busy processing.
Cause
A service running on the passive node opens a protected file for exclusive access. If vCenter Server Heartbeat
attempts to update this opened file, the Apply component logs the following error message:
82 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide