Anybody updated their S2D cluster yet?

[Jaan]

Asking for a friend.........

[Warwick_Tech]

We're looking at S2D for a new project, either that or Clustering (Haven't decided yet) but these will all likely be on S2022

 

If it helps I would personally wait as it took S2019 around 6 months of release to support my RAID controllers natively...

[jslate1980]

Everything I have read, Microsoft have dropped support. As they are pushing companies to use Azure HCI stack instead. Which is a paid monthly solution. Which can only be ran on certified hardware.

[jslate1980]

Here is a link explaining https://4sysops.com/archives/microsoft-will-not-release-a-free-hyper-v-server-2022/

[Primus]

Here is a link explaining https://4sysops.com/archives/microsoft-will-not-release-a-free-hyper-v-server-2022/

 

That link is regarding the free version of Windows Server called Windows Hyper-V Server - the last release of it was 2019.

[Jaan]

Yeah i think its the GUI less version also.

 

We have a full fat S2D s2019 3 node cluster. Just wanted to know if anybody has upgraded their s2d cluster directly to s2022.

[jslate1980]

That link is regarding the free version of Windows Server called Windows Hyper-V Server - the last release of it was 2019.

My mistake, you are correct.

[KK20]

we went from 2016DC to 2019DC for our stretch cluster (4 nodes split over two buildings/2 sites). We did this last summer as I wasnt prepared to wait for 2022. I will wait for a while as 2019 had issues when it was first released (regarding clustering).

[Jaan]

Longest time for a reply goes to me......

 

Was this update done inplace onan active cluster?

 

Did you just drain the node. inplace OS update and re-add to the cluster? how did the cluster handle different OS versions?

 

cheers

[Aprice]

Had to rebuild a failed S2D not long ago. Just exported whatever was salvageable. Started a 2022 install from scratch and imported back.

[KK20]

Ive since gone to 2022 now. With the 2016 -> 2019 I evicted a node, upgraded (note, this was a fresh install, not an inplace upgrade), rejoined. Did this for all of them. It is a supported scenario https://learn.microsoft.com/en-us/windows-server/failover-clustering/upgrade-option-same-hardware Edited December 4, 2023 by KK20

[Jaan]

Ive since gone to 2022 now. With the 2016 -> 2019 I evicted a node, upgraded (note, this was a fresh install, not an inplace upgrade), rejoined. Did this for all of them. It is a supported scenario https://learn.microsoft.com/en-us/windows-server/failover-clustering/upgrade-option-same-hardware

 

Any reason you did fresh and not in place?

[KK20]

it was what MS recommended. Since this was my hypervisor I followed the instructions without cutting corners. The hypervisor wasnt hard to install, it only has storage and network drivers really.

[Jaan]

I finally did this update this week

 

https://www.edugeek.net/forums/windows-server-2022/236816-ive-inplace-updated-my-s2d-cluster-2019-2022-a.html#post2027267