Azure appliance deployment does not work with v13

[sumeet]

Case# 07968803

Unable to deploy Azure appliance with v13 VBR.

At step #5 - https://helpcenter.veeam.com/docs/vbazu ... ml?ver=8.1
The option to select VM size is empty (the drop down is empty).

We had a test env with v12 VBR, checked for the same Entra App, subscription, resource group, vnet, nsg and the VM size option worked.
What we observed is that the VM size options for v13 and v12 are different.

Informed support about this -- no real help.

Since we work with clients to provide backup service, we do not have access to Azure subscription - have to get our client in the support call for them to share the screen. Hence cannot have calls with EMEA support which is usually late evenings for me.

We ended up uninstalling v13 and installed v12 and completed the deployment.

Not a good experience to have while onboarding a client.
I hope the case gets looked in and resolved.
Putting this msg her, in case anyone else wants to deploy Azure backup appliance.

[nielsengelen]

Hi Sumeet,

I noticed that the case is still under investigation and it could be a specific issue to your setup. Please continue working with support for a solution.

[sumeet]

Hi Niel,

As mentioned in my last post, we uninstalled v13 and deployed v12 and completed the Azure Backup appliance.
There is nothing more to debug, as there is no setup available.
This is for your team to test and check if this works with v13

[nielsengelen]

Hi,

Understood, we will check what could cause these deployment issues.

[nielsengelen]

Hi Sumeet,

The only potential reason we can see is that quotas are not properly configured and in v13, the check is adjusted according to standards.

The first step for diagnosis would be to go to the target subscription in Azure, go to Settings->Usage + Quotas and confirm the state of the quotas for the default deployment sizes:
-Standard BS Family vCPUs
-Standard FSv2 Family vCPUs

If these are set to 0, it explains why the drop down is empty. If there are quotas, a support case would be needed again for deeper insight and troubleshooting.

[sumeet]

Thanks for the update. I have requested my client to check the default deployment sizes.

[sumeet]

Hi Niel,

Checked and these two deployment sizes:
-Standard BS Family vCPUs
-Standard FSv2 Family vCPUs

Are listed as unavailable for this region - our region is Australia southeast.

And v12 VBR uses different sizes, which are available and hence the deployment worked with this version.

[nielsengelen]

Hi Sumeet,

If you increase the quotas for those, it should work for v13 as well.

[sumeet]

Hi Niel,
Not sure what you mean by increase the quotas for those. I would expect VBR to not hardcode the sizes or allow us to select a size or specify the size if a particular size is not available in a region.

[nielsengelen]

We’ll see what can be done to enhance this in a future release but for now, you can change the quotas at Microsoft for those types in the regions using a Microsoft case to get it resolved.

[jensinghelbr]

This still does not solve the issue. Seeing as we have a max quota on the family of 50. these vm's are announced to get retired and no longer reservable. They are marked in our new subscription as sku as not available. For the westeurope region.
This is quite a severe problem.

[nielsengelen]

Hi Jens,

We are looking into this as we had more reports and looking on how to address this.

[nielsengelen]

Hi @jensinghelbr @sumeet,

If you have deployed VBR v13, please open a support case. There is a configuration/reg key that can be used to apply similar behavior for v12 and give all types of profiles. We'll also revert this change in an upcoming release.