Post reply

How to apply service pack update on SQL 2014 cluster environment without server downtime

  • October 7, 2015 at 12:33 am

    #308604

    Hi,

    I wanted to apply SQL server 2014 service pack1 and CU1 & CU2 on a two node cluster environment without server downtime. Please suggest.

    Thanks

  • October 7, 2015 at 1:59 am

    #1831924

    first of all, you only have to install the most recent CU.

    First install that CU at the non-active node.

    the you will have downtime ! for failing over the SQLinstance from the active node to the non-active node (which just got the CU installed )

    Keep in mind SQLServer may need extra time to upgrade the database stuctures.

    Then you still have to apply your chosen CU to the newly non-active node.

    I suggest leaving a couple of days in between applying the CU on the second node, just in case problems pop up on the upgraded instance.

    In case of failback to the non-CU-d node, SQLServer will undo the upgrades in the db.

    Play it safe, start with a FULL backup of all your databases !

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • October 7, 2015 at 4:46 am

    #1831949

    vijayakumarn (10/7/2015)

    Hi,

    I wanted to apply SQL server 2014 service pack1 and CU1 & CU2 on a two node cluster environment without server downtime. Please suggest.

    Thanks

    You'll first need to apply service pack 1 and then the latest CU as these updates are cumulative (hence their name Cumulative Update 😉 )

    You will incur an outage at some point, however this can be minimal if you observe the following

    • patch all passive nodes first
    • ensure you remove any passive nodes from the possible owners list for the networkname resource, this will prevent a failover during patching
    • apply all required patches and if necessary reboot the passive nodes
    • when the passive nodes have been completed add them back to the networkname possible owners list
    • failover the running instance to one of the passive nodes
    • patch the node the remaining node that is now passive

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

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

Viewing 3 posts - 1 through 2 (of 2 total)

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