Failover Cluster Configuration Availability
Applies To: Windows Server 2008 R2
The cluster configuration database contains essential information for the function of a failover cluster. A copy of the cluster configuration database is maintained on each node. If the quorum configuration for the cluster includes a witness disk, a copy of the cluster configuration database is also maintained on the witness disk. The Cluster service replicates the latest version of the cluster configuration database to all locations where it is stored.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-FailoverClustering |
The cluster database could not be loaded. The file may be missing or corrupt. Automatic repair might be attempted. | |
Microsoft-Windows-FailoverClustering |
The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '%1'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data. | |
Microsoft-Windows-FailoverClustering |
The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine. | |
Microsoft-Windows-FailoverClustering |
An attempt to forcibly start the cluster service has failed because the cluster configuration data on this node is either missing or corrupt. Please first start the cluster service on another node that has an intact and valid copy of the cluster configuration data. Then, reattempt the start operation on this node (which will attempt to obtain updated valid configuration information automatically). If no other node is available, please use WBAdmin.msc to perform a System State Restore of this node in order to restore the configuration data. | |
Microsoft-Windows-FailoverClustering |
The restore request for the cluster configuration data failed to make a copy of the existing cluster configuration data file (ClusDB). While attempting to preserve the existing configuration, the restore operation was unable to create a copy at location '%1'. This might be expected if the existing configuration data file was corrupt. The restore operation has continued but attempts to revert to the existing cluster configuration may not be possible. | |
Microsoft-Windows-FailoverClustering |
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 '%1'. If no backups are available, please copy '%1' to '%2' 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. |