I did inplace upgrade a few years ago on Windows Server running Veeam and it worked, but it's always recommended a clean install if possible. 

You can use the configuration backup to restore Veeam database after a clean installation. 

Clean install is preferred, but in-place upgrade should work. Just keep the PC-name the same, otherwise you have manual work with DB configuration

As noted it will work but migration to a server OS is the better way forward here as it is supported on Win10/11 but not recommended.  As noted have a configuration backup and if you can remove/reinstall it would be better.

Don’t in-place upgrade at all, there are risks and you might run into OS issues before even deepdiving into Veeam.

I agree with Chris, VBR should be running on a Windows Server OS.

Hi ​@ropi-ask, it depends! If you are using VBR solely on the server, I recommend a clean installation. But you may want to take a look at a this response from Veeam Support for more information: https://community.spiceworks.com/t/server-2022-inplace-upgrade-w-veeam-b-r-installed/963970/4

Keep in mind they are doing Win10 to Win11 not a Server OS but this would still pertain to any upgrade.  Switching to Server OS is still the better option.

I do agree in all points from my colleagues mentioned above 

But one additional point: It’s also an option, to check if your Inplace Upgrade (even if i wouldn’t recommend it) will work - and this is more regards to a general Option you have with VBR:

• do a Sure Backup from your physical VBR server (so you need an Agent Backup.. and also with a DNS server in this isolated Virtual Lab environment).
• if your VBR is running fine in this Virtual Lab, do your Inplace Upgrade there, check if it’s working, without any issues. If yes, you should be good to go for production.
• keep in mind, you wouldn’t have connections to physical other Repositories, Proxy and stuff like that - but it’s an indicator, if your Upgrade will work.

I am currently about to do this today. Could you deep dive into the known risks, thank you.

I agree! Same steps apply. 

Absolutely, there you go:

1. compatibility issues in case an older Veeam version is used (please check the Veeam OS support matrix)
2. SQL servers may fail and schema changes may occure (I saw both PostgreSQL and MSSQL instances not coming up after an inplace upgrade)
3. Network configuration issues might occure (keep in mind: the Win Server 2022 doesn’t longer support the teaming multiplexor driver e.g. in Hyper-V)
4. driver issues might occure (in case of hardware)
5. HBA and iSCSI configurations might be wiped or can fail
6. third-party integrations might break depending on the software that is used (check OS compatibility matrix on that as well)
7. failed upgrades might corrupt Veeam installations
8. no official rollback support (at least from Veeam)

As for VMs (I always try to get my customer to install VBR on a VM) I see a massively lowered risk in just getting up a new VM, installing OS, drivers etc. and just restoring the config backup after installing VBR as per best practices.

Let me know if you have further questions!

Lukas