This Knowledge Base article provides information on what to do when an error is encountered during a switchover operation.
A switchover operation fails and the following error message or a similar one can be found in the EVault Remote Disaster Recovery logs:
ControllerSwitch](com.neverfail.controller.ControllerCmd) - AsynchCmdThread: ControllerSwitch failed:
com.neverfail.controller.ControlException: Switchover vetoed
During the switchover operation, at least one of EVault Remote Disaster Recovery's 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 could not be verified (for example, roles may or may not have already switched). Currently, EVault Remote Disaster Recovery handles this behavior by starting the application on one of the servers but without replication.
i365 recommends that you 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, i365 recommends that the roles of the servers be changed back to their pre-switchover state. To do this, follow these steps:
Stop EVault Remote Disaster Recovery on both servers selecting
Shutdown EVault Remote Disaster Recovery and stop protected applications
Note: The protected application will be stopped immediately so the users will experience an interruption in the service until the EVault Remote Disaster Recovery is started on the new active server.
On each server:
- Open the Configure Server wizard by selecting Start > All Programs > EVault > Configure Server .
- Select the Machine tab and then set the servers' roles to what they were before the switchover was initiated.
- Click the Finish button to save the changes.
- Restart EVault Remote Disaster Recovery on both servers (starting the new passive server first).
EVault Remote Disaster Recovery All versions