ASR Bug - Unable to support Hyper-V Gen 2 Guest Linux

[Josephus]

Looking to utilize Veeam B&R v10 as a work-around to the Microsoft confirmed bug in Azure Site Recovery.

Hyper-V Guest VMs running .VHDx disk and Gen 2 Linux are unable to replicate and boot into ASR. In fact the ASR wizard won't even let you select the VM within Hyper-V.

Yes I acknowledge Microsoft says it's supported, but if you dig in to the details there are exceptions.
https://docs.microsoft.com/en-us/azure/ ... neration-2

And so we find ourselves looking to Veeam to do what Microsoft cannot.

In speaking with Veeam staff, they are able to support this scenario with the helper appliance in Azure, and restore out of blob. Provided these reg keys are used:
https://www.veeam.com/kb4100

Would very much like to stay on track with finding the Veeam solution to this, and not re-hashing the conflicting Microsoft supported/unsupported documents.
I really appreciate the insights and brilliant folks here in the Veeam forums. Hopefully this can help someone else as this thread evolves.

-Cheers!

[HannesK]

Hello,
and welcome to the forums.

What is your question? Or are you just pointing out that Veeam "Restore to Azure" is working fine for you? If yes, which Linux distribution did you use?

Second question: I read VBR V10 in your first sentence... Gen2 support was introduced with V11. Which version of VBR are you using?

If you like to test whether it works, I recommend downloading the trial version of Backup & Replication and use the quick start guide for the first backups https://helpcenter.veeam.com/docs/backup/qsg_hyperv/

In general: restoring Linux to Azure (or AWS) has to be planned carefully as both clouds have many limitations around that. I recommend testing.

Best regards,
Hannes

[soncscy]

Yes I acknowledge Microsoft says it's supported, but if you dig in to the details there are exceptions.
https://docs.microsoft.com/en-us/azure/ ... neration-2

...

https://www.veeam.com/kb4100

I can't help but notice some concerning statements here

"exceptions" and "experimental" make me itchy -- I've read through the Azure docs you linked (and their child links), but I'm maybe not finding the exceptions you are concerned on.

Similarly, "experiment" seems like not a great idea for what I understand as a DR solution/migration solution.

Like, if you're not getting full support for a function, is it really worth pursuing this when it comes to anything besides a few test servers? Just my $.02, since it kind of sounds like you're really digging in deep on this when there are Microsoft Bugs and exceptions that are worrying you.