Disactory recovery from MS SQL clustering

Hi all,
I have an MS SQL active/passive cluster with 2 nodes of windows 2000 advance
server. One of the node has hardware failure. After I restored win 2k
server from ntbackup, i can't re-join the cluster. Though I can see both
server are up in the cluster administrator, but it fails when fail over
occurs.
Please advise me how to do.
Justin
Here is a webcast that might help:
http://support.microsoft.com/default...b;en-us;822250
Or may this Q:
http://support.microsoft.com/default...b;en-us;822400
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Bill Gate" <iono@.umc.com.hk> wrote in message
news:eOGOkOxbEHA.1408@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> I have an MS SQL active/passive cluster with 2 nodes of windows 2000
advance
> server. One of the node has hardware failure. After I restored win 2k
> server from ntbackup, i can't re-join the cluster. Though I can see both
> server are up in the cluster administrator, but it fails when fail over
> occurs.
> Please advise me how to do.
> Justin
>
|||The information for such scenarios is well documented in "Help and Support Center" for Windows
Here is cut an paste from Help
Scenario 6Single Cluster Node Corruption or Failure
Symptom: The node cannot join the cluster.
If the Event Log indicates that the cluster database on the local node is merely corrupted, you can perform a System State restore on that node to replace the local cluster database. For information, see To
restore the cluster database on a local node. Alternatively, you can copy the latest checkpoint file (CHKxxx.TMP) from the quorum disk to the %systemroot%\Cluster\ directory, rename it as file CLUSDB, and
restart the Cluster service on that node.
If a single node fails in the cluster due to system disk or other hardware failure, follow these steps to rebuild the node and rejoin the cluster:
After verifying that all cluster resource groups have been successfully moved to other nodes, repair or replace the failed hardware. For information, see To move a group to another node and To manage cluster
hardware.
Perform an Automated System Recovery restore on the failed node to rebuild the node. For information, see To restore a damaged cluster node using Automated System Recovery.
If you have other files or application data for that node backed up on on tape or other backup medium, you can restore that now. For information, see To restore files from a file or a tape and Scenario 8 below.
For each cluster group and resource, verify that the newly recovered node appears as a possible owner in Cluster Administrator, then move a resource group to the newly recovered node and verify that the move
is successful. For information, see To test whether group resources can fail over.
Note
If you do not have an Automated System Recovery backup of the node, you can evict that node and add a new node to the cluster. For more information, see To evict a node from the cluster and To add
additional nodes to the cluster.
For more scenarios and options, please review the topic "Backing up and restoring server clusters" in Windows Help.
Or go online to the following link
http://www.microsoft.com/resources/d...r/proddocs/en-
us/SAG_MSCSusing_9.asp
SQL Server specific information is there in SQL Server Books Online. I am cutting and pasting the same for you.
How to recover from failover cluster failure in Scenario 1
http://msdn.microsoft.com/library/de...ering_2uax.asp (online link)
In this scenario, failure is caused by hardware failure in Node 1 of a two-node cluster. This hardware failure could be caused, for example, by the failure of a small computer system interface (SCSI) card or the
operating system.
After Node 1 fails, the Microsoft SQL Server 2000 failover cluster fails over to Node 2.
Run SQL Server Setup and remove Node 1. For more information, see How to remove a failover clustered instance .
Evict Node 1 from Microsoft Cluster Service (MSCS). To evict a node from MSCS, from Node 2, right-click on the node to remove, and then click Evict Node.
Install new hardware to replace the failed hardware in Node 1.
Install the operating system. For more information about which operating system to install and specific instructions on how to do this, see Before Installing Failover Clustering.
Install MSCS and join the existing cluster. For more information, see Before Installing Failover Clustering.
Run the Setup program on Node 2 and add Node 1 back to the failover cluster. For more information, see How to add nodes to an existing virtual server (Setup).
Hope that helps.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx