June 18, 2013 at 12:54 pm
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'
June 19, 2013 at 4:26 am
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).
June 19, 2013 at 5:16 am
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'
June 19, 2013 at 5:16 am
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
July 2, 2013 at 9:20 am
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply