FYI: VBR & Azure NVMe Servers

[Gene-MN]

Good morning,
this is just a FYI for those who may be unaware of the current limitation with v6/v7 (NVMe) SKU's in Azure. They will backup with no issues but cannot currently be restored. We encountered a similar issue with our Veeam Backup for Microsoft Azure servers months ago and it was fixed. From other posts it appears we are waiting on a new feature/update in VBR 13 to support this.

Case #08026861

Mentioned in limitations documentation:
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

Thanks!

[CarlosEsteves]

I have same issue.

Disks premium v2 with logical sector size 4096, restore not supported.

Now we have backup , but can´t restore

[CarlosEsteves]

Hello,

Is there any plan from Veeam to follow Azure improvements and new features?

They are deploy new sizes like v6 and v7, where the controller of the disks are NVMe.

Restore a server from VBR to Azure is not possible if the size uses only NVMe, because all restores are SCSI.

That is very bad.

[nielsengelen]

Hi,

We will look what can be done to resolve this in a short manner of time.

[nielsengelen]

Hi Carlos,

Are you restoring full VM or specific disks only?

[CarlosEsteves]

Full VM

[nielsengelen]

Thank you for the information. We'll have to see what can be done for this aspect within VBR.

Additionally, can you clarify the source of the backups? Are these protected from VMware or another hypervisor? Or are we talking about backups made by VB for Azure that you try to restore using VBR?

[CarlosEsteves]

My VMs are running on Azure, but we do backup using Veeam Windows Agent as we need to have Tlog backups