Upgrade 3-Node 2016 Microsoft Failover Cluster to 2022 (Hyper-V)

Raed M. Mary 51 Reputation points
2023-01-09T18:32:48.887+00:00

Hello,

I am upgrading current 3-node 2016 cluster to 2022 by adding new windows server 2022 physical servers to the existing cluster. I'll update the cluster functional level afterward. I did upgrade another 2-node 2016 cluster to 2019 cluster successfully. Can windows server 2022 be added to existing 2016 cluster?

Note: this is a Hyper-V cluster.

Thank You
Raed

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
Windows for business | Windows Server | Storage high availability | Clustering and high availability
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Thameur-BOURBITA 36,261 Reputation points Moderator
    2023-01-09T20:15:16.673+00:00

    Hi,

    The answer is yes based on the Microsoft article below talking about Cluster upgrade from to Windows 2019 and 2022:

    cluster-operating-system-rolling-upgrade

    Please don't forget to mark helpful reply as answer

    1 person found this answer helpful.
    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Raed M. Mary 51 Reputation points
    2023-01-09T20:58:10.487+00:00

    Thank you Thameur-BOURBITA for the article!

    The article does not state skipping a version when upgrading from Microsoft (Hyper-V) failover cluster 2016 to 2022 (skipping 2019).
    I can not find articles on companies upgraded their Microsoft failover cluster from 2016 to 2022.

    I am asking because it's failing to add a new Windows server 2022 to the existing Microsoft failover cluster 2016.

    Errors I get is like:

    the computer is joined to a cluster.
    Unable to add cluster nodes - Cluster service did not reach the running state. The Error code is 0x5b4.

    277604-image1.png277560-image2.png

    1 person found this answer helpful.
    0 comments No comments

  2. Raed M. Mary 51 Reputation points
    2023-05-08T17:57:37.2433333+00:00

    Hi Thameur-BOURBITA,

    I ended up migrating the Failover cluster from version 2016 to version 2019.

    My goal was to upgrade to 2022. I will come back in the near future to try and upgrade from failover cluster version 2019 to 2022. In this case, I have to use the network configuration called "Switch Embedded Teaming (SET) instead of NIC Teaming, which is no longer supported by 2022 Hyper-V.

    Thank You for the help.

    Raed

    1 person found this answer helpful.
    0 comments No comments

  3. Thameur-BOURBITA 36,261 Reputation points Moderator
    2023-01-09T21:12:41.78+00:00

    Hi,

    I think that the Cluster OS rolling upgrade process allow up 1 version increase at a time such as from Server 2016 to Server 2019 or Server 2019 to Server 2022 like the process of upgrade in-place.
    You can upgrade from windows 2016 directly to Windows 2022 and mentioned in the article in my previous answer.
    Did you have the same error when you try to upgrade from Windows 2016 to windows 2019 ?

    Please don't forget to mark helpful reply as answer

    0 comments No comments

  4. Raed M. Mary 51 Reputation points
    2023-01-11T11:48:00.3766667+00:00

    Hello BOURBITA Thameur,

    I have not tried to upgrade this specific cluster from 2016 to 2019 yet. However, I upgraded another 2016 cluster to 2019 last year successfully.

    I might have just to go 2016 > 2019 > 2022.

    Note:

    Hyper-V server 2022 no longer support NIC Teaming. The new technology called "Switch Embedded Teaming (SET)". I am not sure yet to whether Hyper-V supports mixed NIC configuration (NIC Teaming and SET) in the same cluster.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.