Windows Server Hyper-V version update - Veeam component redeploy?

[mkeating44]

Hi,

We are planning out an upgrade for our Hyper-V clustered hosts to go from Windows Server 2019 to Windows Server 2022. We have tested using the overall steps from Microsoft at https://learn.microsoft.com/en-us/windo ... de-process using a clean install of Windows Server 2022. The process itself works well and we have had no issues, but I had a question about how Veeam will behave as we didn't do it with Veeam on-host components deployed. If we keep the same machine name, IP addressing etc is it just a case of going through the Hyper-V Cluster properties wizard and re-deploying the components again, or is anything else needed?

I haven't opened a support case yet as we are a way off doing it in production, but I had the thought after realising we hadn't tested this.

[david.domask]

Hi Michael,

In general the process should be transparent. My experience from my Support days was you indeed will need to go through the properties of the cluster in the Backup Infrastructure tab, but typically it should be transparent. I would advise check this topic for a few of the considerations that you may need to review from the HyperV side (internal testing showed in some cases there were issues on the HyperV side with the virtual machine versions and connectivity, but that was a 2012R2 => 2019 upgrade so I'm not confident you'll see the same with 2019 => 2022)

But in general, it should be transparent for Veeam.