The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
Server Clocks are Different by xx:xx Min
Symptoms
After changing the server time on the active server of a VMware vCenter Server Heartbeat server pair backward by more than a couple of minutes, a false failover occurs resulting in split-brain syndrome.
Purpose
This article provides information on resolving server clocks that are out of synchronization.
Resolution
The server time-difference does not affect the operation of the server pair if it is less than 2 minutes. Larger time differences may trigger errors if the passive server is switched to the active role through either a switchover or failover.
Note: Shutting down VMware vCenter Server Heartbeat and starting it again triggers auto-checking for all protected files, so this operation is best undertaken when user load on the protected application is likely to be lower.
To synchronize the server clocks:
Shut down VMware vCenter Server Heartbeat.
On the active server, open a command window and run the following commands, substituting the domain to which the active server is joined:net time /domain: /set /y
On the passive server, open a command window and run the following commands, substituting the necessary user names and IP addresses, and giving any other responses requested:
net use\\<ip_address_channel_Active_server> /user:<locally_stored_domain_admin_credentials> net time \\<ip_address_used_previously> /set /y net use \\<ip_address_used_previously> /delete /y
Start VMware vCenter Server Heartbeat on the passive server, then on the active server.
Additional Information
This issue appears to be the result of a bug in Java 4239522: Timer seems to stop when the computer system date is turned back. Currently, there is no fix for this; therefore, the only option is to ensure that the Windows Time Service is not running on either the Primary or Secondary server in a VMware vCenter Server Heartbeat pair.
If the server time on a VMware vCenter Server Heartbeat server is changed backward (by a few minutes), that server stops issuing heartbeats, and the connected server gets heartbeats missed. If this happens to the active server, the passive server gets heartbeats missed and fails over, causing a split-brain scenario, as both servers are still connected. At that point, application protection is lost and manual intervention is required to reconfigure the VMware vCenter Server Heartbeat server pair and restart replication.
vCSHB-Ref-53
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
