Emergency Repair Disk Does Not Create Cluster Configuration Database (257892)
The information in this article applies to:
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows NT Server, Enterprise Edition 4.0
This article was previously published under Q257892 SYMPTOMS
When you use an emergency repair disk that was created with Rdisk.exe, a backup copy of the cluster configuration database is not created.
RESOLUTION
To resolve this issue, use Regback.exe from the Microsoft Windows NT Resource Kit, in addition to your emergency repair disk, to back up the cluster registry.
To back up the cluster registry, type the following at a command prompt:
regback filename machinecluster NOTE: filename must be a valid path and file name, for example, C:\Clusbak.
The exit error is 0 if the backup is successful. The exit error is 1 if you encounter a hive that requires manual backup. All other errors have an exit error 2.
To restore the cluster registry, follow these steps:
- Stop the Cluster service on both nodes.
- On Node1, click Start, click Run, and then type regedt32.
- Locate and click the following registry key:
HKEY_LOCAL_MACHINE\Cluster - On the Registry menu, click Unload Hive.
- Rename %SystemRoot%\Cluster\Clusdb and %SystemRoot%\Cluster\Clusdb.log to Clusdb.old and Clusdb.log.old respectively.
- Rename your cluster registry backup file from Filename to Clusdb and copy it to the %SystemRoot%\Cluster directory
- Repeat all of the previous steps on Node2 to replace the cluster directory database (Clusdb) on that computer.
- On Node1, in Control Panel, click Services.
- Enter the -NoQuorumLogging switch into the Parameters box of the Cluster service.
NOTE: This procedure also works for Windows 2000. However, instead of starting the cluster service with the -noquorumlogging switch, use the -ResetQuorumLog switch. Then, it is not necessary to stop and restart the service; the resetquorumlog switch stops and restarts the service in one step.
Important If this cluster is running Windows 2000 Service Pack 4 and the hotfix 872970 has previously been installed, you may start the cluster service normally and skip using -ResetQuorumLog.
- Start the Cluster service.
- Open Windows Explorer and delete the Quolog.log file and all the Chkxxx.tmp files from the Mscs folder on the quorum drive.
- Stop the Cluster service, and restart it without using the -noquorumlogging switch.
NOTE: The cluster re-creates the quorum log and checkpoint file. - Start the Cluster service on Node2
STATUS
This behavior is by design.
Modification Type: | Minor | Last Reviewed: | 1/20/2006 |
---|
Keywords: | kbClustering kbprb w2000mscs KB257892 |
---|
|