Unable to configure Azure in VBR

[johannesk]

Hi,

This problem is being worked on with ticket #05287030.

We are following this documentation:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110
But we are not able to add a managed server for Azure (or GCP or AWS). It does not appear in the list, only the first 4 appear on the list of servers to add.

We have Enterprise plus license with 8 instances unused. VBR is 11.0.1.1261. In services we hae Veeam Azure Service running. The Azure plugin is installed version Veeam azure plugin 11.0.3.209. Since installation of the plugin the whole system has been rebooted several times.

Any ideas?

Regards,
Jóhannes

[HannesK]

Hello,
I can only recommend to continue with support. It should look like with with the current version. My guess is, that something is not up-to-date



Best regards,
Hannes

[HannesK]

guess from my side: are all Veeam services running with the default settings as LOCAL SYSTEM or did you change the service accounts to something else? I remember that this can cause issues.

[johannesk]

This has been resolved. We now get the option to add Veeam cloud native backup appliance. The trick was to configure the 'Veeam Azure Service' to use the same 'Log on as' in services as the 'Veeam backup service'. By default it's configured as local system. This makes sense now that we've done it, but it was not so obvious this needed to be done.

This put Veeam support on the right track:

[22.02.2022 09:39:03] 4 (1) Starting authorization utility. Directory: C:\Program Files\Veeam\Plugins\Microsoft Azure\Service\VeeamAuth.exe. Arguments: /purpose:DATA /clientCertificateThumbprint:E42C3E477CCB37ACF1454CC568C999DD2DDF7DB6 /platformId:89622f35-9e48-424b-9d52-a74dc03b65c2
[22.02.2022 09:39:09] 4 (1) Error: VBR REST API service is unavailable: Failed to authenticate Veeam Backup for Microsoft Azure server. System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:9392
...
[24.02.2022 14:42:54] 160 (1) Starting authorization utility. Directory: C:\Program Files\Veeam\Plugins\Microsoft Azure\Service\VeeamAuth.exe. Arguments: /purpose:DATA /clientCertificateThumbprint:E42C3E477CCB37ACF1454CC568C999DD2DDF7DB6 /platformId:89622f35-9e48-424b-9d52-a74dc03b65c2
[24.02.2022 14:42:55] 160 (1) Error: VBR REST API service is unavailable: Failed to authenticate Veeam Backup for Microsoft Azure server. Access denied.

So this is working for us now.

Regards,
Jóhannes

[HannesK]

Hello,
thanks for confirming my guess

yes, I remember discussions about the same issue for the Nutanix plugin...

Just curious... what's the goal of changing the account? I mean, that means management of an additional account, management of an additional password and maybe even regular password changes. I also cannot see how an account that has local admin permissions is somehow "more secure" than LOCAL SYSTEM, because a local admin can always elevate to LOCAL SYSTEM

Best regards,
Hannes

[johannesk]

Regarding the goal of changing the account - we did it just to get the Azure backup working from VBR. As of now we use same account on the Veeam Azure service as for the Veeam Backup service (not local system).

[HannesK]

yes, my question was why the account of the Veeam Backup Service was changed. LOCAL SYSTEM is the default and I see no reason to change it. out of the box everything would have worked