Update to 5.0.0.579

[jhellermann]

After update to 5.0.0.579 I got the error by excuting Backupjob >> Failed to create a backup plan (Cannot connect to the storage account ....
It works until Update to 5.0.0.579. Repository is reachable in the Job Configuration. If i want to add a new Respository, the Storage Account is visibale, but the choice of Folders is not possible.
Somebody there with the same error ?

[Vitaliy S.]

Have you modified this account by any chance in Azure before? Can you please go through this account edit wizard and see if this fixes the issue or not?

[jhellermann]

No, i didn't change anything. I connect with my Azure Subscription. Should i do "Renew application" under Azure Accounts ?

[Vitaliy S.]

I would give it a try and if this doesn't help, let's open a support case and share your case ID for tracking.

[johnnyts]

I am facing exactly the same issue after Veeam Backup for Azure is updated to 5.0.0.579 automatically.

When manually triggering the backup policy, it displayed an error saying "Failed to create a backup plan (Cannot connect to the storage account xxxxxxxx. Make sure that virtual network xxxxxxxxxx has access to it.) (TraceId : 011bd9f8-decf-4d27-8074-249ec69f2093)". I logged in to the VM and spun up a new VM in the same subnet to test connectivity to the storage account. In both VMs I can send HTTP requests to both storage account successfully.

In the Configuration menu, the repository can be shown but I couldn't scan for any containers inside the repository. I even created a new storage account & a new container inside it, the same issue still happened.

[jhellermann]

Yes, exactly same as me.

I solved it like this

1. delete all BackupJobs
2. remove repositorys
3. remove the AzureAccount
4. Go to Azure AppRegistration and select your App
5. there select Certificates & Secrets and create new ClientSecrets
Save Value and Secret ID. Only visable at this point.
Later need for registration
6. Select Subcription,IAM,RoleAssingment,AddRoleAssignment
there select Contributer,next to members and there select your app, review+assign
7. Login to VeeamBackupForAzure
8. Add Azure Account, select Specify existing service account
9. Enter AppID, Secret it th Value from 5. and enter TenantID
10. When Succesfull add the repository again. I have to do a Rescan to get all StorageAccounts
If all works fine, the Import starts after finish.
11. Create new BackupJob

Maybe it works for you.
I had previously connected with an Azure account and the Contributer role.
However, this does not seem to work anymore after the update.
Conditional Access seams for me to be a problem or somthing changed in the Access configuration.
That's why I connected it via the service account.

[Vitaliy S.]

I wouldn't recommend re-creating all policies as it looks like really a last resort. @johnnyts, can you please open a support case and let me know your case ID?

[jhellermann]

It would be nice and useful if you can post the solution made by veeam

[Vitaliy S.]

Happy to share it, once we have data from opened support cases.

[dr1992]

I'm experiencing the same issue. Does anyone have any updates on the solution or is it best to log with VEEAM?

[Vitaliy S.]

The best move is to contact the technical support team, share the case ID, and get assistance, as currently this issue is not seen in our labs.

[Vitaliy S.]

Looks like we were able to confirm this behavior. The issue can happen in two cases:

1. After the upgrade we show a message in the Notification Bell that new permissions should be granted to the service account. If this is ignored, then this issue will occur
2. If a custom role was used and new permissions are not added upon the upgrade

To resolve it, you can do the following:

1. Renew the service account in the VB UI
2. Or assign the permissions mentioned below to the custom account:

Code: Select all

 "Microsoft.Storage/storageAccounts/blobServices/containers/read",
 "Microsoft.Storage/storageAccounts/blobServices/containers/write",

Hope it helps!

[merku]

Hello,
I currently have Veeam for Azure connected to a VBR version 11.0.1.1261 and I am not offered the update to version 5.0.0.579 on the UI.
Do you know if it's a compatibility issue between VBR and Veeam for Azure?

Greetings

[Vitaliy S.]

Hi Mercurio,

Veeam B&R v11 does not support VB for Azure v5. To get this version, you need to upgrade to Veeam B&R v12.

Thanks!