Hyper-V Failover Cluster 2016 Inplace Upgrade to 2019

Question

Hyper-V Failover Cluster 2016 Inplace Upgrade to 2019

SDS 221

Hello Community,

"Upgrading the operating system on an existing failover cluster is only supported when going from Windows Server 2016 to Windows 2019." as mentioned in https://learn.microsoft.com/en-us/windows-server/failover-clustering/upgrade-option-same-hardware

Does that mean I can Pause+Drain the node and perform an InPlace Upgrade from 2016 to 2019 without evicting the node from the cluster? Any additional steps needed?

Thank you!

Fernando Gomes 1 Reputation point

2021-11-16T16:51:22.963+00:00

It worked for me. Upgraded from 201 to 2022.

Pause and drain the first node.
[optional] - backup the host (I used VEEAM agent)
Run setup.exe from the server 2022 ISO. Make sure the ISO is of the same language as the server you're upgrading. Select "keep files and apps" [something like that].
Wait and wait and wait...
Severeal reboots later, the Server 2022 loaded up and automatically joined the cluster. Live Migration works. Quick migration does not, however. You'll get warnings saying that a compatible but different version of hypervisor is running, and stating that you should upgrade the remaining cluster nodes and then raise the cluster functional level.
Fernando Gomes 1 Reputation point

2021-11-16T16:51:43.097+00:00

*from 2016 to 2022

3 answers

Your answer

Fernando Gomes 1 Reputation point

2021-11-16T16:51:22.963+00:00

It worked for me. Upgraded from 201 to 2022.

Pause and drain the first node.
[optional] - backup the host (I used VEEAM agent)
Run setup.exe from the server 2022 ISO. Make sure the ISO is of the same language as the server you're upgrading. Select "keep files and apps" [something like that].
Wait and wait and wait...
Severeal reboots later, the Server 2022 loaded up and automatically joined the cluster. Live Migration works. Quick migration does not, however. You'll get warnings saying that a compatible but different version of hypervisor is running, and stating that you should upgrade the remaining cluster nodes and then raise the cluster functional level.
Fernando Gomes 1 Reputation point

2021-11-16T16:51:43.097+00:00

*from 2016 to 2022

Answer 1

Alex Bykovskyi 2,241

Hey,

You will still need to Pause+Draing roles on node1, evict it from the cluster rebuild it with Windows Server 2019, install all roles and features and then add it back to the cluster. Might help:
https://www.starwindsoftware.com/blog/cluster-rolling-upgrade-from-windows-server-2012-r2-to-windows-server-2016

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose

SDS 221 Reputation points

2021-09-07T07:03:13.347+00:00

How do you know?

It is written that "Upgrading the operating system on an existing failover cluster is only supported when going from Windows Server 2016 to Windows 2019."
What am I getting wrong?

Answer 2

Raed M. Mary 51

Delete the comment since it was placed in the wrong question.

Answer 3

Raed M. Mary 51

One more thing I want to add to the discussion, Hyper-V server 2022 no longer support NIC Teaming. The new technology called "Switch Embedded Teaming (SET)"

Share via

Hyper-V Failover Cluster 2016 Inplace Upgrade to 2019

3 answers

Your answer