April 24, 2008 at 10:57 am
Hi,
I need a simple procedure to patch our SQL2005 active/active cluster. It's
presently unpatched. From what I understand I need to do the following :
1- Failover node 2 ressources to node 1
2- Log on node 1 and install the SP2 on the two instances
3- Failover node 1 and node 2 ressources to node 2
4- Reboot node 1
5- Log on node 2 and install the SP2 on the two instances
6- Failover node 2 and node 1 ressources to node 1
7- Reboot node 2
8- Failover node 2 ressources to node 2
It seems too simple .... I'm I forgetting sometings ?
Thanks
April 24, 2008 at 7:19 pm
It's a general practice to install the service pack with the virtual node residing on the physical node it was originally installed upon. What we typically do is this:
1 - Virtual Node on Each Physical Node
2 - Patch Virtual Node 1
3 - Fail-over Virtual Node 2
4 - Reboot Physical Node 2
5 - Fail-over Virtual Node 1 and 2
6 - Reboot Physical Node 1
7 - Fail-over Virtual Node 1
8 - Patch Virtual Node 2
9 - Fail-over Virtual Node 1
10 - Reboot Physical Node 1
11 - Fail-over Virtual Node 1 and 2
12 - Reboot Physical Node 2
13 - Fail-over Virtual Node 2
K. Brian Kelley
@kbriankelley
April 25, 2008 at 11:24 am
Ok, so I apply the SP on the virtual node of the physical server 1 then on the virtual node of the physical server 2.
But, since I have two instances on each virtual node ( one active, one waiting for the failover of the other node), The SP installation will complain about having an instance in passive mode, no ? So, to have the SP installing without error message, I have to failover ressources of node 2 to node 1 before run the setup the first time, no ? That's the part that I don't understand when I look at the readme ...
Thanks
April 25, 2008 at 11:34 am
The SQL 2005 service pack installs are cluster-aware, just like the base installations. Run the SP on the active node, and it will detect everything. If you supply a Windows Server login for the passive node (when asked by the installer), it will patch the passive node as well.
The installer takes several information-gathering steps before launching into the installation, so you can run the installer on the server and move through some of the steps without affecting anything (when you hit the screen that says 'Ready to Install', click the 'cancel' button instead of the 'install' button) to see what the installer says what it will do.
-Eddie
Eddie Wuerch
MCM: SQL
April 25, 2008 at 11:47 am
Ok, I will try that :-/
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply