Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 2783

Will it cause any problems if two cluster nodes run with two different OS patch versions?

$
0
0

Hi experts,

  If my memory served my right, Microsoft's best practice always recommend all nodes in one cluster should run the same OS patch version. We decide to patch one node first and patch the second after one week later. Would this cause any negative malfunction on Windows Server Cluster.

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

TLDR; (too long don't read)

https://social.technet.microsoft.com/Forums/en-US/baa4a8b1-39b7-4dd3-b692-bdab5ccd30ae/what-is-best-practice-to-keep-windows-server-201620122008-most-secured-and-high-available?forum=winservergen

"Since Microsoft decides to deliver cumulative updates only(I don't know, maybe in these two years), I guess the windows updates will take a very long time. I download Nov 2019 cumulative update and its size is incredible 1.2GB. WOW!! I guess 80% ~ 90% are features updates maybe 10% or less are security updates. Why don't Windows split features updates and security updates. Install features on Windows Server are really unnecessary.

  And Also, Microsoft recommend all nodes in Windows Failover Cluster should be have the same patch level which cause a very serious problem, your scheduled/planned downtime will increased significantly. Maybe from 10 minutes to 30 minutes or more, and if you add high-end hardware reboot time(cold start), it takes you another 15 minutes.

  All this are not acceptable. We decide to patch one node first and patch the second after one week later. Would this cause any negative malfunction on Windows Server Cluster. Sorry, This question is off topic, it is not a windows updates issue any more, it is a cluster issue related. I will post this question in Windows Server Failover Clsuter. Sorry for any inconvenience."


Viewing all articles
Browse latest Browse all 2783

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>