Hi,
case #07709816.
Support can't figure it out atm, so posting here.
Scenario:
- VBR server running latest 12.3.1
- VBA in Azure running latest 8 (upgraded from VBR)
VBA is mapped without issues in on-prem VBR. I can take backups of Azure VMs in VBA no issues.
In the VBA wizard in VBR, when you add the VBA to VBR, at the end it finds the storage accounts currently in VBA and ask to add credentials so they can be added as external repos in VBR.
And this is where the issues is - if i try to add the storage account VBR throws a "Failed to connect to repository backups: user authentication failed".
But the credentials are correct as in the same server I have installed azure storage explorer, and from there i can add and browse the same storage account without issues, so it is definitely VBR.
Time on the server is correct.
Connection to VBA is direct via VPN to Azure.
Thanks
case #07709816.
Support can't figure it out atm, so posting here.
Scenario:
- VBR server running latest 12.3.1
- VBA in Azure running latest 8 (upgraded from VBR)
VBA is mapped without issues in on-prem VBR. I can take backups of Azure VMs in VBA no issues.
In the VBA wizard in VBR, when you add the VBA to VBR, at the end it finds the storage accounts currently in VBA and ask to add credentials so they can be added as external repos in VBR.
And this is where the issues is - if i try to add the storage account VBR throws a "Failed to connect to repository backups: user authentication failed".
But the credentials are correct as in the same server I have installed azure storage explorer, and from there i can add and browse the same storage account without issues, so it is definitely VBR.
Time on the server is correct.
Connection to VBA is direct via VPN to Azure.
Thanks
Statistics: Posted by lolcathost — May 26, 2025 7:13 am






