After a Failover VirtualCenter is not Accessible

Follow

Summary

This Knowledgebase article provides information about the occurrence of VirtualCenter when deployed with a remote SQL Server database not being accessible after a failover.


More Information

Symptom

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:

[Vdb::LockRepositoryHelper]
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.

Cause

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.

Resolution

Configure the Neverfail Heartbeat Interval to a minimum of 70 seconds.  To do this, follow the steps below:

  1. Launch the Neverfail Heartbeat Management Client.
  2. Navigate to Communication -> Configuration .
  3. Change the Heartbeat Interval to 70.
  4. Click on the Apply button.


Applies To

Neverfail for VirtualCenter


Related Information

None

KBID-1484

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.