April 25, 2013 at 2:26 pm
What is the best practice for installing a SQL Service Pack and a Cumulative Update on a clustered index during the same downtime? We have a production SQL 2008 R2 RTM 2-node cluster and want to upgrade to SP2, CU3.
Is it
1) Install SP & CU on the passive node
2) Failover
3) Install SP & CU on the other node.
OR
1) Install SP on the passive node
2) Failover
3) Install SP & CU on the other node.
4) Failover
5) Install CU on the 1st (now passive) node
OR
1) Install SP on the passive node
2) Failover
3) Install SP on the other node.
4) Failover
5) Install CU on the 1st (now passive) node
6) Failover
7) Install CU on the (now passive) node.
My concern: Is there a significant risk in installing a CU before the instance is brought online (and completes the script upgrade) for the previous Service Pack?
April 26, 2013 at 5:26 am
removed -may be incorrect
---------------------------------------------------------------------
April 27, 2013 at 12:29 am
something i've never tried actually, but i would follow this
dan-572483 (4/25/2013)
1) Install SP on the passive node2) Failover
3) Install SP on the other node.
4) Failover
5) Install CU on the 1st (now passive) node
6) Failover
7) Install CU on the (now passive) node.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 27, 2013 at 4:11 am
I have also never had to try this either so I would have to agree with Perry that thats the only safe, guaranteed way to do it.
also the fact that I could find nothing on this would suggest you have to do it that way.
Having to apply an SP and a CU (and maybe a security patch as well) cannot be that unusual so you would have thought some guru or microsoft would describe the process for a cluster, but they just stick to how to apply a single upgrade.
You could experiment for us but I wouldn't recommend it except on a sandpit server! 🙂
---------------------------------------------------------------------
April 27, 2013 at 7:22 am
You can apply an SP and CU when slipstreaming an install, but the PCUSource and CUSource parameters do not apply to straight SP or CU installs.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 29, 2013 at 9:56 am
Unfortunately the Microsoft documentation for installing CUs is sparce. Also on our nonProduction server the SP and CU were installed on different dates, since the CU is to fix a bug introduced by the SP.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply