I have issue in windows failover cluster with 2 nodes 2019 standard

Question

Configured windows cluster in win 2019 STD in VMware

2 nodes

cluster quorum with file share

role configured for the service apache tomcat.

Cluster failed and unable to turn ON

This has happened twice in 6 months

Cluster events shows

Error 1:The failover cluster database could not be unloaded and any potentially incorrect changes

in memory could not be discarded.

The cluster service will attempt to repair the database by retrieving it from another

cluster node.

If the cluster service does not come online, restart the cluster service on this node.

If restarting the cluster service does not fix the problem, please restart the machine.

If the cluster service fails to come online after a reboot,

please restore the cluster database from the last backup.

The current database was copied to 'C:\Windows\Cluster\CLUSDB.Corrupt.bak'.

If no backups are available, please copy 'C:\Windows\Cluster\CLUSDB.Corrupt.bak' to

'C:\Windows\Cluster\CLUSDB' and attempt to start the cluster service.

If the cluster service then comes online on this node, some cluster configuration changes

may be lost and the cluster may not function properly.

Run the Validate a Configuration wizard to check your cluster configuration and

verify that the hosted Services and Applications are online and functioning correctly.

Error 2:

Cluster node 'Node 2' was removed from the active failover cluster membership.

The Cluster service on this node may have stopped.

This could also be due to the node having lost communication with other active nodes

in the failover cluster.

Run the Validate a Configuration wizard to check your network configuration.

If the condition persists, check for hardware or software errors related to

the network adapters on this node.

Also check for failures in any other network components to which the node is connected

such as hubs, switches, or bridges.

Answer 1

Hey,

I would recommend you to start with troubleshooting recommendations covered here:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/failover-clustering-system-log-events

https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/troubleshoot-cluster-event-id-1135

You can also try searching for db in %systemroot%\cluster directory on the working node and copy it from there. https://samchounwork.wordpress.com/2014/03/10/failover-cluster-database-could-not-be-unloaded/

In addition, if you need shared storage for your cluster you can take a look at StarWind VSAN. It can be used as a shared storage and for disk quorum. https://www.starwindsoftware.com/starwind-virtual-san

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Answer 2

Hi Joseph,

Hope you're doing well.

Here are some steps you can take to troubleshoot and potentially resolve these issues:

1. Ensure that the network configuration for both nodes is correct and that there are no issues with connectivity between them. Use the Validate a Configuration wizard to check the network configuration and address any issues that are identified.
2. Check for any hardware or software errors related to the network adapters on both nodes. Make sure that all network components, such as hubs, switches, or bridges, are functioning properly and not experiencing any failures.
3. Since the cluster database has been marked as potentially corrupt, you can try restoring it from the backup file 'CLUSDB.Corrupt.bak' located at 'C:\Windows\Cluster'. If no backups are available, copy the corrupt backup file over the original 'CLUSDB' file and attempt to start the cluster service again. Be aware that some cluster configuration changes may be lost in this process.

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.