Cluster Server Has Clusdb Corruption After Power Outage (216064)

SYMPTOMS

• The cluster database file (located in the %SystemRoot%\Cluster folder) may become corrupted on both nodes (for example, the Clusdb file contains zero bytes on both nodes).
• The quorum_device:\Mscs\Chksequential_number.tmp file may be inconsistent and, if used by MSCS, may result in Clusdb corruption.
• The quorum_device:\Mscs\Chksequential_number.tmp file may be outdated as a checkpoint file may not have been written during the interval when the two nodes were up. If the computer's configuration is changed and a recent checkpoint file reflecting this change does not exist, the log files (quorum_device:\Mscs\quolog.log and quorum_device:\Mscs\Chksequential_number.tmp) may contain inconsistent quorum resource information.

• MSCS cannot be started, and both nodes are able to access and use the Clusdb file, so the cluster cannot be formed.
• MSCS cannot be started with the initial Clusdb file allowed to locate the latest checkpoint file, but its contents are inconsistent. If MSCS loads this file the Clusdb file may become corrupted. If a retry to form the cluster from the other node is done, the second Clusdb file may become corrupt.
• MSCS can start, but the cluster starts in an outdated state (for example, during a week of operation no checkpoint was taken, then the next MSCS restart uses the last checkpoint file to restore the configuration, and this file may be outdated).