Patching the Cluster

  • Hi Experts,
    I want to apply SP2 on two node A & B cluster, i did some tests on Dev and all is well.I want to apply first on node  A and monitor it for a week before i apply it to  node B.I am not sure that by doing so ,will it cause any inconsistencies to data.,or i must patch both nodes same day.
    Please advise

    Thank you so much

  • tmmutsetse - Wednesday, April 25, 2018 3:25 AM

    Hi Experts,
    I want to apply SP2 on two node A & B cluster, i did some tests on Dev and all is well.I want to apply first on node  A and monitor it for a week before i apply it to  node B.I am not sure that by doing so ,will it cause any inconsistencies to data.,or i must patch both nodes same day.
    Please advise

    Thank you so much

    I would be very surprised if you saw any problems after applying a service pack especially since you have applied in in a test environment first. If you are using an active/passive setup on your cluster apply the service pack to the passive node first then failover and apply to the previously active node.

    Thanks

  • You will find that the service pack will take nodes out of the potential owners list in the cluster.  If you apply the service pack to the active node, but not the passive node, the cluster will resist failing over to that passive node, as it no longer has the right version (or greater version) of SQL Server installed.  A service pack does two basic things.  Updates to .dlls, .exes, and registry settings, and then running a few SQL scripts.  The SQL scripts are portable in the cluster, because their results are in the master and msdb databases. The .dlls and assemblies that underlie the clr functions and extended stored procedures do not fail over from node to node.  If you failed to a lower versioned node, the system stored procedures, extended stored procedures, and clr functions/procedures would no longer agree, and you would get errors.

    The suggested method of applying a service pack on a cluster is to upgrade the passive node(s), then fail over to one of the upgraded nodes.  The SQL scripts get run on the instance at startup on the formerly passive node.

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

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