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.
Event Details
Event ID:
1581
Source:
Microsoft-Windows-FailoverClustering
Symbolic Name:
CLUSSVC_UNABLE_TO_MOVE_HIVE_TO_SAFE_FILE
Message: 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.Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).
Causes
The existing configuration data file was corrupt.
Resolutions
Check for additional events related to file copying
If the Cluster service finds a corrupt instance of the cluster configuration database (ClusDB) on a node, it attempts to save a copy of that database, then restores (rebuilds) the cluster configuration database by using data stored in the cluster. Sometimes the attempt to save the copy of the database does not succeed. However, the restore operation continues.
Check for other failover cluster events that are related to this event. Also check the System or other logs for additional disk or file system events that might indicate a problem with copying files. If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering."
To perform the following procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Opening Event Viewer and viewing events related to failover clustering
To open Event Viewer and view events related to failover clustering:
If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
To clear the filter so that you can view other events, in the Actions pane, click Clear filter.
Verify
To perform the following procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
To start the Cluster service on a node and confirm that it runs successfully:
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage.
In the console tree, select Nodes and expand the tree underneath it.
In the center pane, view the status for each node. If the status is Up, the Cluster service is started on that node.
To start the Cluster service on a node, right-click the node, click More Actions, and then click Start Cluster Service.
Home
ENU