Skip to main content
Solved

.Net core version compatilibity for Veeam backup and replication 12.2

N
Forum|alt.badge.img+1
  • Nikks
  • Influencer
  • 77 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?

    3 comments

    Dynamic
    Forum|alt.badge.img+8
    • Dynamic
    • Influencer
    • 361 comments
    • 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).

     
     

     

     

    Markus Hartmann | Veeam Vanguard | Veeam Legend 2024 | VMCA 2024 & VMCE 2024 | VMware Certified Implementation Expert - DCV 2024 | https://markushartmann.blog/
    Chris.Childerhose
    AndrePulia
    dloseke
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • AndrePulia
      AndrePulia
    • dloseke
      dloseke
    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • 8401 comments
    • Answer
    • 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.

    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
    dloseke
    Dynamic
    N
    3 people like this
    • dloseke
      dloseke
    • Dynamic
      Dynamic
    • N
      Nikks
    AndrePulia
    Forum|alt.badge.img+5
    • AndrePulia
    • Veeam Legend
    • 318 comments
    • 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) :-)

    André Pulia - VMCA | VMCE | VMCT | HPECI | VCI | Nutanix Certified Instructor | Twitter: @andrepulia | Blog Site – https://pulia.com.br | https://www.credly.com/users/andre-pulia
    Chris.Childerhose
    AndrePulia
    dloseke
    4 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • AndrePulia
      AndrePulia
    • dloseke
      dloseke
    • Dynamic
      Dynamic

    Comment


    Terms & Conditions