This article describes how to restore cluster database information.

You can back up the cluster database using several different methods. One method is to use the Backup tool (Ntbackup.exe) that is included with Windows 2000. The Backup tool uses the BackupClusterDatabase and RestoreClusterDatabase APIs, which are documented in the Platform SDK.

The Platform SDK documents that the following pieces of Cluster configuration are backed up by calling the BackupClusterDatabase API: The backup contains the following files.

   Path\File                     Description
   -----------------------------------------------------------------------
   lpszPath\chk????.tmp          Cluster Registry snapshot files.
   lpszPath\quolog.log           The quorum log file.
   lpszPath\<GUID of resource>   The registry checkpoint files for the
   \*.CPT                        resource identified by GUID.   
   lpszPath\<GUID of resource>   The crypto checkpoint files for the
   \*.CPR                        resource identified by GUID.
   lpszPath\Clusbackup.dat       Backup completion marker file (read-only,
                                 hidden, 0-byte file)
				

The Backup tool that is included with Windows 2000 backs up this information, when you choose to back up the system state. Note that the node's local cluster registry hive, Clusdb, is not backed up.

To restore a cluster using the RestoreClusterDatabase API:

1.	Stop the cluster service on all nodes except the one performing the restore.
2.	Restore the cluster database on that node by selecting to restore at least the system state. This creates a temporary folder under the Winnt\Cluster folder called Cluster_backup. You then restore the cluster configuration using the Clusrest.exe tool available in the Windows 2000 Resource Kit.
3.	After you complete the process and the Cluster service has started successfully on the newly restored node, restart the other nodes. If clusdb was not restored, perform the procedure in the following article in the Microsoft Knowledge Base to restore it from the quorum copy: 224999 (http://support.microsoft.com/kb/224999/) How to use the cluster TMP file to replace a damaged Clusdb file

If you do not follow this process, and another node with a more current database takes ownership of the quorum before you update the database from the restored node, the restore does not work.

For the latest information about the BackupClusterDatabase and RestoreClusterDatabase APIs, see the documentation in the Platform SDK or search for the APIs at the following Microsoft Web site: