February 28, 2013 at 3:26 pm
Hi,
Just inherited a 3 node active active active SQL 2K8 R2 cluster. 6 RTM instances, 2 on each node. I am in need to patch SP2 on only 2 of the 6 instances. Currently patching all is not an option. I see that I can pick which ever instance or services to patch during initial selection screen of the SP2 installation, BUT there is also the Shared components (including Integration Services and client connectivity tools) which is checked and grayed out.
Does it mean I have to have SP2 on them regardless of how many instances or services I select for the upgrade? and will it affect the other instances that will still be in RTM?
Also, if I patch (rolling) the passive nodes of the 2 instances I am interested first, do you think a reboot will be required for the passive nodes??
I can test the SP2 on SQL 2008 R2 stand alone server, but just don't have a test cluster that resembles the one I have above...
Appreciate any response...thanks.
March 1, 2013 at 1:13 am
TrailRunner (2/28/2013)
Hi,Just inherited a 3 node active active active SQL 2K8 R2 cluster. 6 RTM instances, 2 on each node. I am in need to patch SP2 on only 2 of the 6 instances. Currently patching all is not an option. I see that I can pick which ever instance or services to patch during initial selection screen of the SP2 installation, BUT there is also the Shared components (including Integration Services and client connectivity tools) which is checked and grayed out.
Does it mean I have to have SP2 on them regardless of how many instances or services I select for the upgrade? and will it affect the other instances that will still be in RTM?
The installer will automatically update the client tools if they're installed, wont affect connecting to the RTM instances.
TrailRunner (2/28/2013)
Also, if I patch (rolling) the passive nodes of the 2 instances I am interested first, do you think a reboot will be required for the passive nodes??
Reboot them beforehand to ensure there are no pending reboots, they'll likely want a reboot afterwards too. Since they're passive this doesnt matter.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 1, 2013 at 3:46 pm
Thank you Perry,
Good to know about the shared features. I am trying to avoid a reboot on passive nodes as I have 6 instances in the cluster. I am referring to a node passive node for the instance I am patching, but the node is active to other instances.
I tried it on a single instance 2 node cluster (Active Passive) yesterday, and it didn't require a reboot. I know this is different than the one I will be working on (Active Active Active). I am hoping that it won't ask a reboot, as I can't. Do you think I can roll it back at that point when a reboot is required at the end?
March 1, 2013 at 4:05 pm
You don't have to reboot there and then just defer it until you get the opportunity to reboot
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 1, 2013 at 4:48 pm
Thanks again,
If a reboot is indeed required after the update, then I will be for sure running the updated instance on one of the node that is pending a reboot after SQL2008 R2 SP2, will it corrupt anything, will anything bomb? How high a risk am I running?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply