Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Recovering from a failed VMware vCenter Server Heartbeat switchover
Symptoms
- A vCenter Server Heartbeat switchover operation fails
- An error similar to the following is found in the VMware vCenter Server Heartbeat logs:
ControllerSwitch](com.neverfail.controller.ControllerCmd) - AsynchCmdThread: ControllerSwitch failed:
com.neverfail.controller.ControlException: Switchover vetoed
Purpose
This article provides information on what to do when an error is encountered during a vCenter Server Heartbeat switchover.
Resolution
During the switchover operation, at least one of the VMware vCenter Server Heartbeat components has reported that it cannot switch or there has been a channel disconnection. Because of this, the state of the components on the two servers cannot be verified. For example, roles may or may not have already switched. Currently, VMware vCenter Server Heartbeat handles this behavior by starting the application on one of the servers but without replication.
VMware recommends the administrator check the data integrity of the two servers before starting replication.
If no problems are discovered, it is then safe to start replication.
If any problems are observed, VMware recommends that the roles of the servers be changed back to their pre-switchover state.
To change the roles back to the pre-switchover state:
-
Stop VMware vCenter Server Heartbeat on both servers. Click Shutdown Heartbeat and stop protected applications.
Note: The protected application is stopped immediately, so you experience an interruption in the service until the Heartbeat is started on the new active server. -
On each server:
-
Open the Configure Server wizard. Click Start > All Programs > VMware > VMware vCenter Server Heartbeat > Configure Server.
-
From the Machine tab, set the servers roles as they were before the switchover was issued.
-
Click Finish to save the changes.
-
-
Restart VMware vCenter Server Heartbeat on both servers (start with the new passive).
Additional Information
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.
Actions
- KB Article:
- Updated:
- Categories:
- Product Family:
- Products:
- Product Versions:

