We have B&R 12.3 running on a physical Windows 10 Pro system. Does anyone have experience with an inplace upgrade to Windows 11 in relation to B&R. Should B&R be uninstalled beforehand?
Solved
Windows 11 Inplace Upgrade on B&R System
Best answer by Dynamic
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.
+4I 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.
Wesley Martins @ Senior Enginner at Veeam Technical Support - Public Cloud | My blog: https://itproland.com.br (PT-BR)
+9Clean install is preferred, but in-place upgrade should work. Just keep the PC-name the same, otherwise you have manual work with DB configuration
Fan since FastSCP | VMCA-1 | VMCE9 | VMCE2022 | VMCE2024 | VMCA2024
+21As 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.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
+10Don’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.
LK | Veeam Vanguard | VUG Leader - Cyber Security Space | Security Specialist
+11Hi
[Microsoft MVP | Veeam Legend (2021 -2025) | VMware vExpert 5x | Cisco Champion 3x | Object First Ace 2x]
+21Iams3le wrote:
Hi
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.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
+9I 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.
Markus Hartmann | Veeam Vanguard | Veeam Legend 2024 | VMCA 2024 & VMCE 2024 | VMware Certified Implementation Expert - DCV 2024 | https://markushartmann.blog/
+11lukas.k wrote:
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.
I am currently about to do this today. Could you deep dive into the known risks, thank you.
[Microsoft MVP | Veeam Legend (2021 -2025) | VMware vExpert 5x | Cisco Champion 3x | Object First Ace 2x]
+11Chris.Childerhose wrote:
Iams3le wrote:
Hi
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 agree! Same steps apply.
[Microsoft MVP | Veeam Legend (2021 -2025) | VMware vExpert 5x | Cisco Champion 3x | Object First Ace 2x]
+10Iams3le wrote:
lukas.k wrote:
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.
I am currently about to do this today. Could you deep dive into the known risks, thank you.
Absolutely, there you go:
- compatibility issues in case an older Veeam version is used (please check the Veeam OS support matrix)
- SQL servers may fail and schema changes may occure (I saw both PostgreSQL and MSSQL instances not coming up after an inplace upgrade)
- 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)
- driver issues might occure (in case of hardware)
- HBA and iSCSI configurations might be wiped or can fail
- third-party integrations might break depending on the software that is used (check OS compatibility matrix on that as well)
- failed upgrades might corrupt Veeam installations
- 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
LK | Veeam Vanguard | VUG Leader - Cyber Security Space | Security Specialist
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.