Unable to Enable RA-GRS or ASR on Recovery Services Vault

Hello Al Mokhlif Oud,

Based on that below is our investigation.

For queries

1.An estimated timeline for when Azure Site Recovery will officially support NVMe disk controllers?

We only know the ETA for Azure-to-Azure Site Recovery, which is Public Preview March 15 for Windows OS NVME, March End for Linux OS NVME and No ETA shared for other scenarios.

2.Recovery Services vault creation is failing in UAE North. When we try to create a new vault in resource group CDN, the deployment fails with ResourceDeploymentFailure error. This is blocking us from creating a new vault with RA-GRS/CRR enabled. Why vault creation is failing in UAE?

The issue is Recovery Services vault creation is failing in UAE North because of the regional restriction what we can do now we can request an exception to unlock it. To proceed, we will need to check with our Quota team and upon colloborating with them

We are glad to share that your request for BS Series, Esv6 Series, and Easv6 Series SKUs has been successfully fulfilled in the West Europe region. You should now be able to deploy them without issue.

We have granted region access for all these SKUs. If you encounter any problems, please let us know.

If everything is working fine, kindly confirm so we can proceed to close the collaborative case.

Below is the discussion summary.

For this our support engineer worked with our internal team on your request and are glad to share the following updates:

• BS Series in West Europe: Region enablement has been successfully completed. Please proceed with deployment. If you face any issues or errors, kindly provide us with a full-page screenshot so we can investigate further with our internal team.

• Esv6 Series in West Europe: You already have region access for this SKU. Please go ahead with deployment and let us know if you encounter any problems.

• Easv6 Series in West Europe: Due to high demand in this region, our internal team has asked if you can redirect your deployments to Intel SKU. Please confirm if this option works for you so we can share your response with them.

Note: This alternate guidance is subject to change based on availability, and recommendations may vary depending on customer demand for alternate regions/SKUs.

Out of the three requests under this ticket, two have been fulfilled (BS Series and Esv6 Series). For the Easv6 Series, we need your input on the guidance provided by our internal team.

For Easv6 Serie customer confirm that we are open to using an Intel SKU as an alternative. Please proceed with the Intel SKU recommendation for West Europe so we can complete the ASR replication setup for our database server.

We will proceed with the BS Series and Esv6 Series deployments and will share screenshots if any issues arise

For Issue 1, the behavior you describe when upgrading the Recovery Services vault from GRS to RA-GRS typically occurs when the vault has existing backup items configured with a storage redundancy setting that cannot be modified in place. In Recovery Services vaults, storage redundancy can only be changed before any backup items are protected. If backups already exist, the vault storage setting is locked even if no resource locks are present and you have Owner permissions. To confirm, check whether any backup items, soft-deleted items, or registered containers exist in the vault. Even soft-deleted items will block the change. You can verify this using:

Get-AzRecoveryServicesVault -ResourceGroupName "CDN" -Name "defaultVault625"
Get-AzRecoveryServicesBackupItem -VaultId <VaultID>

If backup items exist, the supported resolution would be to create a new Recovery Services vault in UAE North configured with RA-GRS at creation time, then reconfigure backup policies to use the new vault. Cross Region Restore requires RA-GRS to be enabled at the time protection begins - it cannot be retroactively applied to an active vault with protected items. If no items exist and the error persists immediately on save, this may indicate a backend vault provisioning issue specific to the region, in which case a Microsoft support ticket under Backup > Recovery Services Vault > Configuration is required so the platform team can review backend validation logs.

For more info, refer to https://learn.microsoft.com/en-us/azure/backup/backup-create-recovery-services-vault

For Issue 2, AFAIK, error 1400119 is expected. I'm not aware of any published ETA for NVMe support in ASR. The general guidance is to either redeploy the VM using a supported disk controller (SCSI-based VM sizes such as certain v5-series SKUs) and then enable replication, or implement database-level replication as an alternative disaster recovery mechanism. If ASR-based VM replication is mandatory, resizing to a supported VM size and ensuring the OS disk controller type is SCSI would be the path to follow.

If you require an official roadmap commitment for NVMe support, you could request it via a Microsoft support case or through your Microsoft account team.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin