.Net Core 3.1 will reach EOL

[jorgedlcruz]

Last time I tried VBR v12, it didn't install .net core 3.1.x. From what I have seen, it was some of the VB Plugins installing it.

If you still see it on a new installation, please open a support ticket, and let us know on the appropriate subforum.

I would say if you see, on a VBR environment, 3.1.x .net you could remove it, but please verify it with Support.

For VONE, you can update to the latest VONE v12 Patch which will install .net 6.x, and you can remove .net 3.1.x after.

Thank you

[karsten123]

Hi Jorge,

it is v11, fresh install. I will try.
Thx
I love your blog

[Mildur]

Our plug-ins for backup appliances (AWS, Azure, GCP, Nutanix) are using .Net Core on the VBR server.
- Plug-ins for Veeam Backup & Replication v12 require .Net Core 6.x.
- Plug-ins in v11a require with .Net Core 3.1.x. These plugins can be uninstalled if you don‘t use these backup appliances.

If you are on Veeam Backup & Replication v12 you can just uninstall .Net Core 3.1 (if no other third party product requires it).

Best,
Fabian

[RubinCompServ]

@Mgamerz VBR does not use .NET Core 3.1 in V11 or V12, the whole issue is with Veeam ONE only.

Yes it does. Uninstalling .NET Core 3.1 on my v12 VBR broke the Veeam AWS service and the Veeam Azure service. Ticket #05960818

[Gostev]

Seems you don't have the latest versions of these two plug-ins installed.

[RubinCompServ]

V12 only came out a month ago and I installed the P20230227 patch, so I don't understand how those would be out of date already.

[Gostev]

Plug-ins are on their own dev cycle. They are also separate downloads, so not a part of core VBR patches. The latest VBR ISO version will always have the latest plug-ins though, as it includes all optional components for convenience.

[RubinCompServ]

To be honest, it would be nice if that was listed somewhere. I didn't install these components separately so they must have come from the initial VBR install; it seems counterintuitive to expect customers to know that components installed with a "standard" installation won't get updated when performing a "standard" update (especially when the update is done from the ISO).

[lando_uk]

Can we have a proper KB article about this .Net Core 3.1 issue please, as its just been flagged in our environment and just reading from this thread isn't the best.

We are running the latest V11a on both VBR and Veeam One. So your saying we can safely uninstall both .Net Core and ASP.net core from the VBR, but not from the Veeam One Until we update to V12?

[jorgedlcruz]

Hello Mark,
Sure, we have the next article for you - https://www.veeam.com/kb4410

It is very easy to follow, with the links to the newest .NET 3.x released by Microsoft in December 2022, that fixes some issues including some vulnerabilities.

For Veeam Backup & Replication, the .NET is used for the Veeam Backup for Azure/AWS components, if not in use in VBR, you can remove them.

Best option will be to upgrade to VBR v12 with latest patch, and do the same for VONE. I saw your question on the other thread regarding RAM, but I would upgrade nevertheless.

I hope you can make an informed decision with this information.

Thank you!

[lando_uk]

> For Veeam Backup & Replication, the .NET is used for the Veeam Backup for Azure/AWS components, if not in use in VBR, you can remove them.

When you say AWS components, we use AWS S3 object storage for the SOBR, would that still be ok?

[jorgedlcruz]

Yes, I am talking about the plugins for the Veeam Backup for AWS/Veeam Backup for Azure. Your SOBR and S3 backups are fine.