Failover Cluster - Add node

Question

Post reply

Failover Cluster - Add node

Viewing 15 posts - 16 through 30 (of 32 total)

You must be logged in to reply to this topic. Login to reply

SQLSACT SSC-Insane Points: 21838 More actions · Answer 1

SQLSACT

SSC-Insane

Points: 21838

October 18, 2011 at 1:58 am

#1395729

Thanks

SQLSACT SSC-Insane Points: 21838 More actions · Answer 2

Hi Perry

Is this process in any way different when you have an existing 2 node cluster and adding a 3rd node?

Thanks

Derek

Perry Whittle SSC Guru Points: 234013 More actions · Answer 3

Regardless, when you're adding a new node you need to attach any storage that the cluster groups rely on

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQLSACT SSC-Insane Points: 21838 More actions · Answer 4

SQLSACT

SSC-Insane

Points: 21838

October 18, 2011 at 4:46 am

#1395796

Great!!

Thanks Again

Derek

SQLSACT SSC-Insane Points: 21838 More actions · Answer 5

Hi Perry

Thanks again for all your help re the above.

I started a new thread at http://www.sqlservercentral.com/Forums/Topic1195591-1549-1.aspx

My question was

Hi Guys
Win2008/SQL 2008
What is the process of adding a previously evicted node to a Cluster.
We have evicted a Node from our Cluster and now we want to bring it back..
The evicted node was not rebuilt, it was just evicted from Failover Cluster Management.
What considerations do I need to take
Thanks
Derek.

I don't seem to be getting any bites on that one

Is there any any way you could be of some assistance in this

Basically we had a 2 node cluster (Node A and Node B)

We evicted Node B from Failover Cluster management, we didn't remove SQL or anything else from Node B once it was removed.

We then added Node C, all went well there - No issues

Now we want to add Node B back into the cluster

Here is where I am lost as to the process....

Any help is appreciated

Thanks

Derek

Perry Whittle SSC Guru Points: 234013 More actions · Answer 6

if the node was previously a member and was evicted cleanly then there shouldnt be any reason why you cant re introduce the server, although i always prefer a clean re installation.

As before, make sure any required storage is attached to the node to allow it to fully participate, obviously you'll need to re install any clustered applications such as SQL Server

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQLSACT SSC-Insane Points: 21838 More actions · Answer 7

So when we evicted the Node - We didn't uninstall SQL

Does this mean that I would have to uninstall SQL and reinstall it using the Add Node feature of the SQL Install.

Thanks

Derek

Perry Whittle SSC Guru Points: 234013 More actions · Answer 8

hmm, you should always uninstall the clustered applications if possible before evicting the node. I would go for a clean install and then re introduce the node and re install the clustered applications.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQLSACT SSC-Insane Points: 21838 More actions · Answer 9

Ok

So In future, Best practice would be to uninstall any Clustered application before evicting the Node..

SQLSACT SSC-Insane Points: 21838 More actions · Answer 10

Hi Perry

If not going for the best practice of reinstalling the clustered applications

Do you think the following could work?

1. Present Shared storage to Node

2. Add Node in failover cluster management

3. Add Node to possible owners list for all services and applications.

Remember that we are attempting add a Node that we previously removed from the Cluster, nothing was done to the node. We removed it using the "evict" option in failover cluster management. Nothing else was done, at all.

Thanks

Derek

Perry Whittle SSC Guru Points: 234013 More actions · Answer 11

never tried it myself, i have always cleaned up the clustered applications and then evicted the node. After evicting the node if you attempt to add it back it will probably join the Windows cluster quite happily but i think you will have issues attempting to rejoin the clustered SQL Server instance(s). After a node eviction, in my opinion, always perform a clean install. Questions;

why did you evict the node in the first place?

Why are you so against performing a clean install and reinstall of the SQL Server software?

If you attempt to rejoin the node as it is, you'll only end up running the SQL Server installer anyway to try and repair the current install. If you are under the impression that adding the server back as it is will not require any effort you will be sorely mistaken 😉

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 12

I'm largely going along with Perry on this one.. I would wipe the node and rebuild it, I think trying to re-add it is simply asking for trouble.

CEWII

SQLSACT SSC-Insane Points: 21838 More actions · Answer 13

Perry Whittle (10/31/2011)
never tried it myself, i have always cleaned up the clustered applications and then evicted the node. After evicting the node if you attempt to add it back it will probably join the Windows cluster quite happily but i think you will have issues attempting to rejoin the clustered SQL Server instance(s). After a node eviction, in my opinion, always perform a clean install. Questions;
why did you evict the node in the first place?
Why are you so against performing a clean install and reinstall of the SQL Server software?
If you attempt to rejoin the node as it is, you'll only end up running the SQL Server installer anyway to try and repair the current install. If you are under the impression that adding the server back as it is will not require any effort you will be sorely mistaken 😉

why did you evict the node in the first place?

There was no real reason for evicting the Node, We evicted it and added another node - Now we need to evict the one we added and add the one we evicted.

Why are you so against performing a clean install and reinstall of the SQL Server software?

Time constraints - But I think we can work that out.

I think that the clean install is the best option...

How does this sound??

1. Rebuild the Node we evicted, OS etc

2. Present shared storage to the node

3. Add Failover clustering feature to the rebuilt node

4. Run the add node wizard from Failover Cluster Management.

5. Run Add Node from SQL Installation.

6. Add the Node to the possible owners list for all Services and Apps

Am I missing something here?

Thanks

Derek

SQLSACT SSC-Insane Points: 21838 More actions · Answer 14

Elliott Whitlow (10/31/2011)
I'm largely going along with Perry on this one.. I would wipe the node and rebuild it, I think trying to re-add it is simply asking for trouble.
CEWII

Thanks Elliot

I think that's the best option as well

Perry Whittle SSC Guru Points: 234013 More actions · Answer 15

Seems good to me, although

derekr 43208 (11/1/2011)
6. Add the Node to the possible owners list for all Services and Apps

The sql server installation routine takes care of this for you, the only option you need to configure if requirerd is the group preferred owner(s)

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉