Solved

.Net core version compatilibity for Veeam backup and replication 12.2

3 months ago
November 29, 2024
3 comments
438 views

+1

Nikks
Influencer
79 comments

We have upgraded VBR and EM to version 12.2. According to our discussion with the OS team, due to a vulnerability, they need to remove the older version 3.1.32.31915. We can only see the highlighted .NET version required for version 12.2

NET Framework and ASP.NET Core Shared Framework 8.0

We observed .NET Core runtime 3.1.32 and .NET Runtime 7.0.20 in VBR server

We would like to know if we can remove .NET Core runtime 3.1.32 and .NET Runtime 7.0.20, as it is not mentioned in the article

Please advise.

Best answer by Chris.Childerhose

You can remove that .NET Core Runtime and not affect Veeam. I don’t even have that version on my Veeam server in my lab and everything works fine. To be safe if you prefer verify with support like Markus mentioned.

View original

Did this topic help you find an answer to your question?

+9

Dynamic
Veeam Vanguard
361 comments
3 months ago
November 29, 2024

Hi Nikks,
hard to tell, i would suggest it’s working. But keep in mind, maybe it will be redeployed by another Windows or Component Update.

But to be sure, i would suggest, let’s verify by Support Team.

Also a valid option: if your VBR is running in a VM, you could test it within a SureBackup/Virtual Lab - remove the .Net components within the Virtual Lab - and check if within the deinstallation process anything drops errors. Also after a reboot within the Virtual Lab, check if Veeam itself is running without issues (for sure, you will have no connection to your productive Repositories and other Proxies in this scenario).

+21

Chris.Childerhose
Veeam Legend, Veeam Vanguard
8414 comments
Answer
3 months ago
November 29, 2024

You can remove that .NET Core Runtime and not affect Veeam. I don’t even have that version on my Veeam server in my lab and everything works fine. To be safe if you prefer verify with support like Markus mentioned.

N

+6

AndrePulia
Veeam Legend, Veeam Vanguard
319 comments
3 months ago
November 29, 2024

Dynamic wrote:

Hi Nikks,
hard to tell, i would suggest it’s working. But keep in mind, maybe it will be redeployed by another Windows or Component Update.

But to be sure, i would suggest, let’s verify by Support Team.

Also a valid option: if your VBR is running in a VM, you could test it within a SureBackup/Virtual Lab - remove the .Net components within the Virtual Lab - and check if within the deinstallation process anything drops errors. Also after a reboot within the Virtual Lab, check if Veeam itself is running without issues (for sure, you will have no connection to your producitve Repositories and other Proxies in this scenario).

I really liked the recommendation, use of the sureback functions for us too (as an IT professional) :-)

Comment

Rich Text Editor, editor1

Comment

Related topics

extra kosten terwijl mijn 4g al uit was gezeticon

Extra kosten een maand later betalenicon

Extra kosten van 0,86 centicon

extra kosten door minimum plafond!icon

extra kosten?icon

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded