Failover Cluster Database CLUSDB Corruption – Hyper V

Recently had a hyper v cluster that was rebooted, however upon started 

  1. Get-VM Command produced no VM’s 
  2. Get-clusterquorum was Blank
  3. Start-clusternode Would join the node back into the cluster and Mark as Up
  4. Get-ClusterNodes would bring up errors

CLUSDB is stored on the hosts under HKLM\CLuster

The CLUSDB File Size was around 60KB , on a working cluster is was around 256kb 

There was no backup per below


In the end we had to create a new Cluster and rejoin the Hosts to this ( clear-clusternode ) 

GD Star Rating
GD Star Rating

Tags: 1057, 1593, clear-clusternode, CLUSDB, Clusdb.corrupt.bak, corrpuption, failover cluster database, get-clusternode, get-vm, hyper v

Trackback from your site.