Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL 2008 - Remove cluster node Expand / Collapse
Author
Message
Posted Tuesday, June 18, 2013 12:54 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, December 16, 2014 8:15 AM
Points: 224, Visits: 892
Apologies if this is a daft question (never a good start!)

Had a thought earlier, we have a very simple active passive cluster. One of the nodes went down but failover didnt occur due to the server not going down completely and was still pingable.

It took several restarts but things soon got back to normal. At one point we were considering rebuilding the box, if it was totally broke. What would happen in SQL as I would expect the new build would have to be added as a new node (or do you, can it just carry on?) but if so, how do you remove the old node as you need to be on the same instance to do the remove in memory serves me right?


'Only he who wanders finds new paths'
Post #1464838
Posted Wednesday, June 19, 2013 4:26 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 3:57 AM
Points: 2,480, Visits: 3,021
The cluster part of a clustered SQL installation is determined by the Windows cluster group. So if a node crashes, you can evict the node in Windows. No additional work needs to be done for SQL Server to not use the node anymore.

When a newly build node is added to the cluster you need to install SQL on the new node by running the SQL "setup.exe" and choose "add a node...". In addition you need to install all service packs and hotfixes (if you haven't used a slipstream installation).


** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
Post #1465050
Posted Wednesday, June 19, 2013 5:16 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, December 16, 2014 8:15 AM
Points: 224, Visits: 892
Thanks that was the part i was missing that by evicted a node in Windows, you didnt have to do anything in SQL.

Never had the pleasure thus far so wanted to clear that you, which you have, brilliant...thank you!


'Only he who wanders finds new paths'
Post #1465076
Posted Wednesday, June 19, 2013 5:16 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 12:03 AM
Points: 1,380, Visits: 2,708
In the case where one of the nodes fail and needs to be replaced:
> Evict failed node
> Add new/fixed node into failover cluster using Failover Cluster Manager
> Run SQL setup specifying "Add Node to SQL failover cluster"
> Patch new/fixed node

Full cluster verification must be run before adding the new/fixed node
Post #1465077
Posted Tuesday, July 2, 2013 9:20 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, December 12, 2014 8:24 AM
Points: 97, Visits: 782
I''ve done that and I had tons of issues adding the new node, as SQL though it already had that node.
A better, clean way of doing it, would be to remove the node (uninstall SQL) using the SQL wizard, and then evict the node from the cluster, repair all you need to do, add the node back and reinstall the SQL node
Post #1469604
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse