September 20, 2022 at 9:30 am
Hi
I'm looking at the process for patching our failover clusters. I always thought it was best practice to pause the node you were patching to stop unexpected failover. However this Microsoft article seems to say that whilst the setup.exe is running for patching the node is removed from the preferred owners. https://learn.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/upgrade-a-sql-server-failover-cluster-instance?view=sql-server-ver16&viewFallbackFrom=sql-server-2019
To upgrade a SQL Server failover cluster instance, use SQL Server setup to upgrade each node participating in the failover cluster instance, one at a time, starting with the passive nodes. As you upgrade each node, it is left out of the possible owners of the failover cluster instance. If there is an unexpected failover, the upgraded nodes do not participate in the failover until Windows Server failover cluster role ownership is moved to an upgraded node by setup
Does anyone know if that's correct?
Cheers
Alex
September 20, 2022 at 10:29 am
I haven't experienced any issues just performing the upgrade on passive nodes.
The upgrade process handled it all very well.
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply