Hi,
Can anyone confirm if .NET 4.8 can safely be used with Veeam B&R 11?
I need to install an agent on the host server and .NET 4.8 is a requirement. I cannot get a definitive answer from our 3rd party vendor who just refer me back to the System Requirements.
Thank you
Best answer by coolsport00
As the vendor should. The requirement noted in the req’s is .NET 4.7.2 (see here). But, newer versions should be fine. That being said, if your VBR server is running in a VM, it’s easy to test/verify. I would take a snapshot of the VBR server VM, upgrade/install .NET 4.8, then create a test backup job to see if it works as normal. After the upgrade, I’d also see if browsing other items - Repl jobs, job history, storage integration, anything else you’ve configured initially, looks ok. If all seems fine, delete & commit the VBR server VM snapshot. If this process isn’t something you’re willing to do, contact Veeam Support to verify .NET is supported.
Hope that helps.
Cheers!
+12It was supported for V10, so it is for Veeam V11.
+21As the vendor should. The requirement noted in the req’s is .NET 4.7.2 (see here). But, newer versions should be fine. That being said, if your VBR server is running in a VM, it’s easy to test/verify. I would take a snapshot of the VBR server VM, upgrade/install .NET 4.8, then create a test backup job to see if it works as normal. After the upgrade, I’d also see if browsing other items - Repl jobs, job history, storage integration, anything else you’ve configured initially, looks ok. If all seems fine, delete & commit the VBR server VM snapshot. If this process isn’t something you’re willing to do, contact Veeam Support to verify .NET is supported.
Hope that helps.
Cheers!
+21As the vendor should. The requirement noted in the req’s is .NET 4.7.2 (see here). But, newer versions should be fine. That being said, if your VBR server is running in a VM, it’s easy to test/verify. I would take a snapshot of the VBR server VM, upgrade/install .NET 4.8, then create a test backup job to see if it works as normal. After the upgrade, I’d also see if browsing other items - Repl jobs, job history, storage integration, anything else you’ve configured initially, looks ok. If all seems fine, delete & commit the VBR server VM snapshot. If this process isn’t something you’re willing to do, contact Veeam Support to verify .NET is supported.
Hope that helps.
Cheers!
This is the best advice as noted by Shane. It should support it but test to be sure. 😀
+21Well, though I think the answer should really be my comment, at least Chris’s response included my comment :)
Cheers!
Well, though I think the answer should really be my comment, at least Chris’s response included my comment :)
Cheers!
Sorry! Yes - Premature clicker! Will test with snapshots in place, just to be safe.
Thank you for the concise reply - appreciate it! :)
+3Well, though I think the answer should really be my comment, at least Chris’s response included my comment :)
Cheers!
It’s fixed, 
+21Thanks
Cheers!
+7As the vendor should. The requirement noted in the req’s is .NET 4.7.2 (see here). But, newer versions should be fine. That being said, if your VBR server is running in a VM, it’s easy to test/verify. I would take a snapshot of the VBR server VM, upgrade/install .NET 4.8, then create a test backup job to see if it works as normal. After the upgrade, I’d also see if browsing other items - Repl jobs, job history, storage integration, anything else you’ve configured initially, looks ok. If all seems fine, delete & commit the VBR server VM snapshot. If this process isn’t something you’re willing to do, contact Veeam Support to verify .NET is supported.
Hope that helps.
Cheers!
I learnt something new today. I was always under the impression that snapshotting and reverting a Veeam server was not recommended due to CBT tracking in VMware being lost. So I am assuming it is fine to snapshot and revert if no jobs have been run?
+21As the vendor should. The requirement noted in the req’s is .NET 4.7.2 (see here). But, newer versions should be fine. That being said, if your VBR server is running in a VM, it’s easy to test/verify. I would take a snapshot of the VBR server VM, upgrade/install .NET 4.8, then create a test backup job to see if it works as normal. After the upgrade, I’d also see if browsing other items - Repl jobs, job history, storage integration, anything else you’ve configured initially, looks ok. If all seems fine, delete & commit the VBR server VM snapshot. If this process isn’t something you’re willing to do, contact Veeam Support to verify .NET is supported.
Hope that helps.
Cheers!
I learnt something new today. I was always under the impression that snapshotting and reverting a Veeam server was not recommended due to CBT tracking in VMware being lost. So I am assuming it is fine to snapshot and revert if no jobs have been run?
Yep you should be good. There are a few ways to handle upgrades.
+7As the vendor should. The requirement noted in the req’s is .NET 4.7.2 (see here). But, newer versions should be fine. That being said, if your VBR server is running in a VM, it’s easy to test/verify. I would take a snapshot of the VBR server VM, upgrade/install .NET 4.8, then create a test backup job to see if it works as normal. After the upgrade, I’d also see if browsing other items - Repl jobs, job history, storage integration, anything else you’ve configured initially, looks ok. If all seems fine, delete & commit the VBR server VM snapshot. If this process isn’t something you’re willing to do, contact Veeam Support to verify .NET is supported.
Hope that helps.
Cheers!
I learnt something new today. I was always under the impression that snapshotting and reverting a Veeam server was not recommended due to CBT tracking in VMware being lost. So I am assuming it is fine to snapshot and revert if no jobs have been run?
Yep you should be good. There are a few ways to handle upgrades.
Thank you!
+21I wouldn’t run each and every job either. I only mentioned just to create 1 after the snap, with 1 VM..just to test. I’m pretty sure I’ve done similar testing without issue. Thanks for chiming in on this
+21I wouldn’t run each and every job either. I only mentioned just to create 1 after the snap, with 1 VM..just to test. I’m pretty sure I’ve done similar testing without issue. Thanks for chiming in on this
No trouble at all Shane as I have tested this stuff lots of times. Been burned in the past with a few upgrades.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
