AWS Plug-In for VBR for v11

[pirx]

I'm looking for the lastest versions of the AWS and Azure Plugins. I need to check which version uses .Net 3.1 and if possible replace if with a new plugin version that does not require 3.1.x. VBR is still v11.

Currently installed/used:

Veeam Backup for AWS 5.1.1.8
AWS Plug-In for VBR 11.0.5.553

Veeam Backup for Microsoft Azure 3.0.1.34
Azure Plug-In for VBR 11.0.3.209

On the Veeam download page I only see the plugins for v12, I don't see any link for an older version.

The documentation on https://helpcenter.veeam.com/archive/vb ... lugin.html links to
https://www.veeam.com/backup-replicatio ... nload.html but there is no v11 download anymore.

In general, until VBR is update to v12, I can't update to Veeam Backup for AWS/Azure 12.0.6.956 / 12.0.5.740?

[nielsengelen]

Correct, you will need to update VBR first to update the appliances.

If you need older plugins, you can open a support case and obtain the files this way.

[pirx]

Can you tell me if there are v11 plugin updates available that remove the requirement for .NET 3.1,or that are newer that what is currently installed?

I thought that I always got a notice when starting console if an update is available, but maybe this was not for the plugin. In general it would nice to keep other versions available to download than the current one.

[nielsengelen]

There are no updated plugins for v11. The latest version requires v12 of VBR.

We’ll look into keeping the previous version available somewhere.

[pirx]

I just found those 2 pages:

AWS: https://helpcenter.veeam.com/docs/vbaws ... tml?ver=60
--> 12.0.6.x, 11.0.5.x...

I guess with 11.0.5.553 we have the lastet v11 AWS plugin.


Azure: https://helpcenter.veeam.com/docs/vbazu ... tml?ver=50
--> 12.0.5.x, 11.0.4.x...

It looks like we are not on latest plugin version with 11.0.3.209. Where do I get the Azure version 11.0.4.x?

A few weeks ago .NET 3.1 was removed from all servers because its EOS and therefor a security risk. Veeam One and at least one VBR plugin stopped working. I'm having a hard time now to find out which of the plugins requires .NET 3.1 and if there is an update to make it work with newer .NET version. If not this plugin will stop working once I will remove 3.1, which will be on Monday. Would be good to know this before.

On the new documentation page the requirements are clearly stated:

https://helpcenter.veeam.com/docs/vbaws ... tml?ver=60
https://helpcenter.veeam.com/docs/vbazu ... tml?ver=50

Microsoft .NET Core Runtime 6.0 or later
Microsoft ASP.NET Core Shared Framework 6.0 or later

Nothing on the old page:
https://helpcenter.veeam.com/archive/vb ... ments.html
https://helpcenter.veeam.com/archive/vb ... ments.html

[doktornotor]

VBR 11 plugins are not updated for .NET 6.

[pirx]

Okay, then its the same as with Veeam One and its time to say good bye to those plugins until we are ready to migrate to v12.

[pirx]

I updated the AWS appliance on the weekend and since then configuration backup is failing (#05992253). I checked the logs on the appliance and found the following:

Code: Select all

Could not load file or assembly 'Microsoft.AspNetCore.WebUtilities, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

I'm sure support will help. But does this mean that on the appliance .NET 3.1 is also used? Maybe I was just too blind to see that if the plugin requires 3.1, the appliance does too. If this is the case then we have a bigger issue as we are then not allowed to operate this version of the appliance anymore.

[doktornotor]

Once again, the plugins are NOT updated in VBR11.

[nielsengelen]

If you are running VBR v11, this is normal. The latest plugins are only supported with VBR v12. Please update VBR first to continue using the integration.

[pirx]

Once again, the plugins are NOT updated in VBR11.

My issue here is maybe not the plugin. I've the task to remove everything .Net 3.1 related, the plugins on VBR server I can uninstall, then the VBR v11 instance should be fine. But now I noticed that the AWS _appliance_ is also having .Net 3.1 installed (that might be because of the Plugin) and I now need somehow take care of this. So I can uninstall the ubuntu packages related to this on cli, but I don't know if this will break anything or is only relevant for the plugin.

I know that Veeam is totaly relaxed regarding .Net 3.1 EOS and customers should just upgrade to v12. But it is simply not that easy for everybody. And the only thing that is currently certain is, that 3.1 has to be wiped ASAP and I've our security in my neck. All systems are usually activity scanned for those kind of software. But as this is an appliance it was just missed.

[nielsengelen]

VB for AWS v6 does not use .NET 3.1. You could decouple the appliance from VBR, upgrade it via the built-in updater and then later add it back to VBR v12.

[nielsengelen]

@pirx can u let us know if you are still running VBR v11 or VBR v11a in which you've tried to deploy the plugin? Or was this in a v12 deployment?

[pirx]

VBR is still on latest v11

[nielsengelen]

Then it is most likely related to the Azure plugin that you still see 3.1. VB for AWS v5a already used .NET 6.

Please continue working with support to get it clarified why you have that file alert even after removing the plugins.

[pirx]

Not sure if this is going into the right direction. I wrote that I uninstalled the plugins. So either the plugin and the integration is really mandatory for update or it was a misunderstanding.

Me:

Code: Select all

But today I uninstalled the AWS and Azure plugins on VBR server as they still use .Net 3.1 which is EOS (security policy doesn't allow this).
I then wanted to upgrade AWS appliance to version 6 but it shows...

"April 5, 2023 at 12:13 AM Managed appliances must be updated using the backup console UI."

Support:

Code: Select all

You cannot update to v6 without upgrading VBR to v12.
https://helpcenter.veeam.com/docs/vbaws/vbr_integration/system_requirements.html?ver=60

The plugin I sent is required to integrate VBR11 with VBAWS v5.
Without this the integration will fail.

[nielsengelen]

Yes, we are aware that you uninstalled them however it looks like something was missed or went wrong and as a result, the configuration backup still tries something related to them (hence the error).

We just wanted to confirm which versions you had since the AWS v5a plugin already used .NET 6.

[pirx]

Still fighting with this, as you mentioned latest AWS plugin already uses .Net 6, so I could reinstall this. I got the permission to install .Net 3.1.32 temporary to fix the issue with Azure plugin, I uninstalled both plugins without first removing the appliances in VBR console.

So I installed .Net 3 and Azure plugin from latest ISO which installed version 11.0.3.208, which is strange because I'm pretty sure it was 11.0.3.209 before (see top of my post). But there is no trace of the plugin in Console, no option to add Azure appliance in Managed Servers. But I already see Azure jobs in console

I've created #06006192 to clean this mess up.

My goal: properly remove v11 plugin from VBR, next update appliance to latest version. We are now running 3.0.1.34, on appliance update page it shows...

Veeam Backup for Microsoft Azure (5.0.0.579)
File level recovery for Veeam backup (6.0.0.682)

...not sure where version 4.x is gone, or if it ever existed. But until VBR is properly disconnected I can't update anyway.

[nielsengelen]

v5 has surpassed v4 hence why you see the latest version.