remember when installing sql on the repaired node, use same name and ip. Check Port number for named instances, after sql is restored set the old port numbers for each instance.
/Marten
Main Topics
Browse All TopicsHello, We are currently running SQL 2005 Standard edition on a two node active/passive cluster. The OS is Windows Server 2008 Enterprise edition. The cluster is composed of two Dell 1950 PowerEdge servers and a shared Dell Power Vault MD3000. One of the nodes has gone bad and needs to be rebuilt. I am trying to determin the best way to do this - specifically how to re-add the node after it has been rebuilt. Some research seems to indicate that I have to re-install and reconfigure SQL 2005 on the entire cluster in order to get the clustered SQL service to install on the new node. This would cause the cluster as a whole to be interupted and thus goes against the entire idea of a redundant system. Is there a way to add a node without having to do a complete re-install of SQL? Any information would be helpful.
Thank you,
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for the info.
Just too make sure : when you say to move the SQL files, are you refering to the files located in "C:\Program Files\Microsoft SQL Server"? Aside from these all of the there database file are stored on the PowerVault that is shared between the nodes so I assume they should not be a problem.
How do I check the port numbers for the named instances to make sure is is restored to the correct one. Sorry - I am still new to this.
Thank you.
No I mean the files on the powervault. Install to the same location and then move the files back.
This is assuming that the cluster nodes master, model, tempdb databases reside on the powervault. You dont have to bother about collation and stuff since its stored in master database, witch you replace with the old ones after installation. These files have information about all other databases, location, jobs, users etc.
/Marten
I may have been wrong. The powervault files should remain untouched.
Do a backup as suggested just in case.
This document implies that the only thing needed is the binaries, the right service pack and the same accounts for the services and off you go.
http://technet.microsoft.c
This document is old but the steps remain the same. find 'To rebuild a node' far far down:
http://www.microsoft.com/t
I was confusing things with a total rebuild, witch I did some weeks ago!
/Marten
I did the rebuild thing on SQL 2005 Windows 2003 cluster:
1. Go to add-remove programs, and choose change on sql server on the active node. Remove SQL from the passive node.
2. Evict passive node from cluster.
3. rebuild the passive node and install drivers and patches up to the same level as on the live node.
4. Add the node back to the cluster.
5. The tricky part to add the SQL back to the cluster node. Run add-remove programs on the active node, change the cluster and add teh passive node to the cluster. SQL will be installed there, however not the service packs and not the patches.
To run the servicepack and patches, I had to fail the cluster over to the new node, stop cluster service on the old node, then run the sql servicepacks and the cumulative update and patches. then start the cluster service again on the old node. fail SQL back to that and restart the new node.
6. Test failover and failback.
All working fine :)
Business Accounts
Answer for Membership
by: martenrunePosted on 2008-12-11 at 06:57:38ID: 23148731
Im not sure about w2008 cluster. But in the good ol days:
Failover all SQL instances to the working node.
Open up cluster admin, evict the node.
Stop sql services
Move all sql files to an alternate location, i e sql directory containing databases, master db etc
Repair OS n stuff. Then join the node again.
Install SQL on the node using exactly the same paths as before
Stop SQL, move the backed up sqlfiles to the old location
Start SQL services.
Try and failover and test your cluster
/Marten