Access for VBA Account on new Subscriptions

[agrob]

Good Day

I wonder what is the correct way to grant access to an existing Veeam Account when new Subscriptions are added to a tenant.
I configured VBA some time ago and i discovered on each Subscription in the Prod Tenant, Veeam created a Custom Role on and configured the required permissions.
Now I added a new Subscription. What do i have to do in Veeam that the Custom Role is configured on this new Subscription as well? I could go and configure it manually but i don't think this is the way to go?
The Microsoft.ManagedServices Resource provider is registered on this new subscription

Thanks

[nielsengelen]

Hi Andre,

You can find the permissions in the user guide. If you configure these, you can setup a new account.

[agrob]

Hi

Thanks for your reply. I'm aware of those permissions. the question is, ho does veeam set those on the new created subscriptions.
so if i add new subscriptions i have to create a new account each time and then the permissions are added automaticly?

Thanks

[nielsengelen]

If you add a subscription, you can configure the account automatically. This should create everything for you from VBA to Azure.

[Vitaliy S.]

Andre,

What version of VBA are you using now?

If it's version 3, you would need to copy Veeam custom role to a new subscription, find out Veeam application ID (can be done by editing the Azure account in the VB UI), then assign this application to the copied role, and finally hit the rescan in the policy wizard to locate new resources.

If you're using version 4, then the process is simpler, you just need to go the Azure account tab in the VB UI, then select to edit the account and choose the renew option. This will discover the newly added subscription and assign the necessary permissions as a part of the application renewal process.

Let me know if that helps!

[agrob]

Hi Vitaly
I'm still on Version 3
I did exactely as you described, manually add a custom role to the new subscription with the subscription id in the name. That worked so far.
Thanks anyway

About Version 4, the update does not show me Version 4. I also had this issue last year when i did want to update from Version 2 to Version 3. The action plan then was:

***************

1. Please check the versions of the packages:

sudo dpkg -l | grep veeam

Output example:

ii veeam-updater 4.0.0.565 amd64 Veeam Updater Utility
ii veeamazurebackup 2.0.0.303 all Veeam Backup for Microsoft Azure
ii veeamflr-netdep 2.0.0.340 amd64 File level recovery for Veeam backup

The veeam-updater may be on the version 4 but the rest of it will be on the 1st version.

2. Check the the gpg key is good now:

sudo apt update

Output:

...
Hit:4 https://repository.veeam.com/vbazure/2/public stable InRelease
...

There should be no errors for the repository and it should the same address as shown above.


3. Update packages by the following command:


sudo apt-get --only-upgrade install veeamazurebackup veeamflr-netdep

4. There will be several dependencies installed as well. Once the installation is over, reboot the appliance by a command in the shell

sudo reboot

5. Several minutes after the VM is started it should be ready to go and the version should be a new one.

******

I guess it would be fine to try this here as well, right?

Thanks

[Mildur]

Hi Andre

Any chance you have connected the appliance to a VBR?
In that case, first update the plugin on the VBR server and then start the upgrade within the VBR console.

[agrob]

Hi Fabian
Oh what a beginner failure totaly forgot about the plugin (should have better read the release notes further down ) Thanks for the hint, i'll update the plugin and try again.

Update: Plugin is updated but still not able to update the appliance. Not in VBR (option is greyed-out) and also if i search for upates in the appliance... I guess i'll open a case to check this.

[Mildur]

No worries. You're welcome
One of the next version will have a notification in the web updater if it's connected to a VBR server.

[Vitaliy S.]

Update: Plugin is updated but still not able to update the appliance. Not in VBR (option is greyed-out) and also if i search for upates in the appliance... I guess i'll open a case to check this.

Appliance will not display any available updates if it is managed by a backup server. Let us know your case ID, once you open a ticket.

[agrob]

Hi Vitaliy

Thanks for your reply. the issue is solved in the meantime. the problem was the azure account used to connect from vbr to vba. when i tried to upgrade vba via vbr, the gui hung for about 15 minutes then the message "Failed to upgrade host component. One or more errors occurred". Also if i did try to popen properties of the vba appliance in vbr, the guy hung for about 15 minutes and a api failure was displayed.

in the logs the error was that the user account password was expired... well stupid error. it would be usefull if veeam gui would display this error as well not only the "failed to upgrade host componentes...."

anyway, it is solved now. upgrade worked after setting a new pw for the account

Best regards

[Vitaliy S.]

Veeam Backup appliance does send notifications about expired accounts, or are you referring to Veeam B&R? If that's later, I will pass this feedback to the appropriate teams.

[agrob]

Hi Vitaly
It is in VBR. The Account which is used to connect VBR to VBA. The error messages i sent in my last message here was from vbr, not vba.
Yes please pass the Feedback to the appropriate team. it would be a nice enhancement it the correct message is displayed in the vbr gui. (as the message about account expiration is already present in the vbr logs). Output from the vbr log:

[11.08.2022 12:55:26] 3 (1) Warning: Request to Microsoft Azure failed with error: AADSTS50055: The password is expired.

Thanks!
Best Regards

[Vitaliy S.]

Andre,

Do you have a case ID opened for this or you fixed it yourself? If you did it yourself, then can you please share the log files from this folder on the VBR server via a private message with me so that I could forward them to the QA team?

Code: Select all

C:\ProgramData\Veeam\Backup\Plugins\Microsoft Azure\Logs

Thanks!

[agrob]

Hi Vitaliy

The Veeam Case ID is 05574517. Logs are uploaded to this case.

Thanks

[Vitaliy S.]

Perfect, thanks!