Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / September 2006

Tip: Looking for answers? Try searching our database.

Please Help - Restore Node

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
EF@nospam.nospam - 22 Sep 2006 13:52 GMT
Hi All,

I really need some guidance on how to restore this.  Your help will be very
much appreciated.

Setup: 2 node clustering on Windows 2000 Advance Server with MS SQL 2000
Enterprise Edition.
Diaster: Both the hard disks in the RAID 1 configuration failed on 1 of the
nodes and the whole OS was gone.

Have replaced both hard disks and reinstalled the OS.  The question is how
can I rejoin it back to the cluster especially the SQL portion?  Do I just
add it as a new node or there is other way of doing it?

Hope that someone can help me on this.

Thanks in advance,
Alex
Tom Moreau - 22 Sep 2006 23:10 GMT
You may have to evict the bad node formally from the cluster and then rejoin
the cluster, using Cluster Admin.  From the BOL
"
How to recover from failover cluster failure in Scenario 1
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.

 1.. After Node 1 fails, the Microsoft® SQL Server™ 2000 failover cluster
fails over to Node 2.

 2.. Run SQL Server Setup and remove Node 1. For more information, see How
to remove a failover clustered instance .

 3.. 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.

 4.. Install new hardware to replace the failed hardware in Node 1.

 5.. 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.

 6.. Install MSCS and join the existing cluster. For more information, see
Before Installing Failover Clustering.

 7.. 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). "
After that, you'll need to apply the SQL Server service pack to the failed
node.  This, you do at the replacement node and not from the primary node.
However, to apply any hotfixes, you'll have to fail over to the replacement
node and re-apply the hotfix.

HTH

Signature

  Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON   Canada
.

Hi All,

I really need some guidance on how to restore this.  Your help will be very
much appreciated.

Setup: 2 node clustering on Windows 2000 Advance Server with MS SQL 2000
Enterprise Edition.
Diaster: Both the hard disks in the RAID 1 configuration failed on 1 of the
nodes and the whole OS was gone.

Have replaced both hard disks and reinstalled the OS.  The question is how
can I rejoin it back to the cluster especially the SQL portion?  Do I just
add it as a new node or there is other way of doing it?

Hope that someone can help me on this.

Thanks in advance,
Alex
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.