October 21, 2011 at 3:23 am
We have a 3 node cluster..Lets say, the names of nodes are A, B and C
We have 2 instances running Inst1 and Inst2 on these nodes..Both are SQL Server 2005
The current setup is like this
Inst1 can run on A and B Nodes
Inst2 can run on B and C Nodes
Now, Customer wants to phase out node A from this cluster..
What steps and precautions are to be taken to remove the node A from this cluster..
This is very urgent and immediate help is appreciated
October 21, 2011 at 3:29 am
itsamarnath (10/21/2011)
We have a 3 node cluster..Lets say, the names of nodes are A, B and CWe have 2 instances running Inst1 and Inst2 on these nodes..Both are SQL Server 2005
The current setup is like this
Inst1 can run on A and B Nodes
Inst2 can run on B and C Nodes
Now, Customer wants to phase out node A from this cluster..
What steps and precautions are to be taken to remove the node A from this cluster..
This is very urgent and immediate help is appreciated
uninstall the sql server instance from Node A, to do this you need to failover the INST1 to node B and go to add\remove programs on the active node B and click the SQL Server software then click change. During the setup process select maintain virtual server when prompted and remove the Node A. Once setup finishes the SQL Server instance will be removed from Node A, you may then evict this node from the cluster
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 21, 2011 at 3:31 am
Perry Whittle (10/21/2011)
itsamarnath (10/21/2011)
We have a 3 node cluster..Lets say, the names of nodes are A, B and CWe have 2 instances running Inst1 and Inst2 on these nodes..Both are SQL Server 2005
The current setup is like this
Inst1 can run on A and B Nodes
Inst2 can run on B and C Nodes
Now, Customer wants to phase out node A from this cluster..
What steps and precautions are to be taken to remove the node A from this cluster..
This is very urgent and immediate help is appreciated
uninstall the sql server instance from Node A, to do this you need to failover the INST1 to node B and go to add\remove programs on the active node B and click the SQL Server software then click change. During the setup process select maintain virtual server when prompted and remove the Node A. Once setup finishes the SQL Server instance will be removed from Node A, you may then evict this node from the cluster
Awesome...I had actually recommended the same to the client..Just wanted to get some expert inputs about it 🙂
Also, after this activity, since Inst2 is not recognizable on NodeC, we will have to do the add node activity right?
October 21, 2011 at 3:43 am
itsamarnath (10/21/2011)
Perry Whittle (10/21/2011)
itsamarnath (10/21/2011)
We have a 3 node cluster..Lets say, the names of nodes are A, B and CWe have 2 instances running Inst1 and Inst2 on these nodes..Both are SQL Server 2005
The current setup is like this
Inst1 can run on A and B Nodes
Inst2 can run on B and C Nodes
Now, Customer wants to phase out node A from this cluster..
What steps and precautions are to be taken to remove the node A from this cluster..
This is very urgent and immediate help is appreciated
uninstall the sql server instance from Node A, to do this you need to failover the INST1 to node B and go to add\remove programs on the active node B and click the SQL Server software then click change. During the setup process select maintain virtual server when prompted and remove the Node A. Once setup finishes the SQL Server instance will be removed from Node A, you may then evict this node from the cluster
Awesome...I had actually recommended the same to the client..Just wanted to get some expert inputs about it 🙂
Also, after this activity, since Inst2 is not recognizable on NodeC, we will have to do the add node activity right?
INST1 will not be recognisable on Node C so yes you would have to launch change setup again on Node B, select maintain virtual server and this time add node C. You could do this all in the same step if you wanted
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 21, 2011 at 3:50 am
Thanks. Isn't there a need to run setup on node C also and do the manage virtual cluster procedure there?
Coz, Our Inst1 is currently not recognized on Node C?
October 21, 2011 at 3:52 am
itsamarnath (10/21/2011)
Thanks. Isn't there a need to run setup on node C also and do the manage virtual cluster procedure there?Coz, Our Inst1 is currently not recognized on Node C?
no, setup is run on the active node for the instance you are joining. Dont get confused with SQL Server 2008 thats a totally different kettle of fish 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 21, 2011 at 4:30 am
Perry Whittle (10/21/2011)
itsamarnath (10/21/2011)
Thanks. Isn't there a need to run setup on node C also and do the manage virtual cluster procedure there?Coz, Our Inst1 is currently not recognized on Node C?
no, setup is run on the active node for the instance you are joining. Dont get confused with SQL Server 2008 thats a totally different kettle of fish 😉
he he..SQL 2005 and SQL 2008 look like two different technologies all together..
Thanks for your inputs..
October 21, 2011 at 4:43 am
the setup process has changed totally
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 21, 2011 at 5:47 am
Perry Whittle (10/21/2011)
itsamarnath (10/21/2011)
Perry Whittle (10/21/2011)
itsamarnath (10/21/2011)
We have a 3 node cluster..Lets say, the names of nodes are A, B and CWe have 2 instances running Inst1 and Inst2 on these nodes..Both are SQL Server 2005
The current setup is like this
Inst1 can run on A and B Nodes
Inst2 can run on B and C Nodes
Now, Customer wants to phase out node A from this cluster..
What steps and precautions are to be taken to remove the node A from this cluster..
This is very urgent and immediate help is appreciated
uninstall the sql server instance from Node A, to do this you need to failover the INST1 to node B and go to add\remove programs on the active node B and click the SQL Server software then click change. During the setup process select maintain virtual server when prompted and remove the Node A. Once setup finishes the SQL Server instance will be removed from Node A, you may then evict this node from the cluster
Awesome...I had actually recommended the same to the client..Just wanted to get some expert inputs about it 🙂
Also, after this activity, since Inst2 is not recognizable on NodeC, we will have to do the add node activity right?
INST1 will not be recognisable on Node C so yes you would have to launch change setup again on Node B, select maintain virtual server and this time add node C. You could do this all in the same step if you wanted
To just make sure that we do not go wrong during the outage, should we have the SQL Server 2005 installation files ready on that particular node? Even though we would launch the setup from add/remove programs, from where will the setup pick the installation files from?
October 25, 2011 at 10:11 am
Now, Node A is rebuilt with new OS and other settings.
I believe, we have to install only the SQL Server client tools on this node before inducting it into the failover cluster back.
And when we have the downtime, we perform the add node to map the instance1 back to this node...
Inputs please
October 25, 2011 at 10:13 am
what service pack is the live instance currently at?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 25, 2011 at 10:16 am
I am not in a position to login to the server
Whats the condition if its SP2 or if its SP3?
October 25, 2011 at 10:46 am
there's a nasty bug in the sp2 installer which if i remember correctly doesnt affect the sp3 installer.
with sp2 you cant run the installer and patch only the one node. The installer sees the active node at the correct version and stops, there are specific steps to take when patching a single node to SP2 that require an outage of the clustered instance. Nasty i know, thats why the 2008 installations are a god send 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 25, 2011 at 10:45 pm
Perry Whittle (10/25/2011)
there's a nasty bug in the sp2 installer which if i remember correctly doesnt affect the sp3 installer.with sp2 you cant run the installer and patch only the one node. The installer sees the active node at the correct version and stops, there are specific steps to take when patching a single node to SP2 that require an outage of the clustered instance. Nasty i know, thats why the 2008 installations are a god send 😉
hmm..But should I install client tools on the new node now only?
As you said, we have a seperate downtime to do the add node activity by installing Instance1 on this..
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply