Windows updates and SQL patches - 2 node Active Active Cluster

  • Are these steps correct for applying Windows Updates to a SQL 2008 R2 Active Active (2 node) cluster?

    1) Clear 1st Node node by failing over to 2nd Node

    2) Remove 1st node from possible owners

    3) Run Windows Updates on 1st clear node

    4) Reboot 1st node

    5) Re-add 1st node as a possible owner

    6) Fail over both instances to 1st node

    7) Remove 2nd node from possible owners

    8) Run Windows Updates on 2nd clear node

    9) Reboot 2nd node

    10) Fail over original 2nd node instance currently on 1st node back to 2nd node

    In regard to applying a service pack to this, it mentions here about "With SQL Server 2008 failover clustering, your outage period can be significantly reduced if you follow the proper “rolling update” process." What proper rolling update process is this?

  • This is exactly what I usually do, except that I pause the node instead of removing it from possible owners.

    -- Gianluca Sartori

  • Microsoft has a best practice here > http://support.microsoft.com/kb/q174799

    Although I question why they suggest doing the Active node first if you have a simple 2 node Active / Passive environment? :unsure:

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

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