This Knowledgebase article provides information about the occurrence of VirtualCenter when deployed with a remote SQL Server database not being accessible after a failover.
When VMware VirtualCenter is deployed with a remote SQL Server database and Neverfail for Virtual Center is installed, after a failover, VirtualCenter is not accessible and the following error is displayed:
SQLExecDirect failed: HYT00:0
[yyyy-mm-dd hh:mm:ss.546 'App' 3872 error] Unable to get exclusive access to VC repository. Please check if another VirtualCenter instance is running against the same schema.
During normal operations, VMware VirtualCenter places a 60s lock on a database table. The default missed heartbeat interval for Neverfail to trigger a failover is 60s. To guarantee the lock on the VirtualCenter database has been released during the failover, the Heartbeat interval needs to be increased.
Configure the Neverfail Heartbeat Interval to a minimum of 70 seconds. To do this, follow the steps below:
- Launch the Neverfail Heartbeat Management Client.
- Navigate to Communication -> Configuration .
- Change the Heartbeat Interval to 70.
- Click on the Apply button.
Neverfail for VirtualCenter