VMware VM with EFI Migration to Microsoft Azure (BAW16)

This information has been around for a little while and therefore I apologise if you have seen it already.

I have been investigating the different ways to migrate virtual machines from a local VMware vSphere environment to Microsoft Azure.  The main concern that I have had is around virtual machines configured with EFI in VMware and being able to get them fully functional in Azure.  I have basically decided on two methods that seem to work quite well.

 

Option 1 – Microsoft Azure Site Recovery

From a Microsoft Azure point of view, this is the simplest solution.  You can deploy an agent directly from Azure to the machine that you wish to be protected.  Once everything is synchronised, you can then perform a test failover and then a final failover to the Azure environment.  Previously, I would have discounted this option as there wasn’t support for EFI and Windows Server 2016 but Microsoft have corrected both of these issues now and the process works well.  From the EFI point of view during the failover, it converts the virtual machine back to normal BIOS.

 

Option 2 – Veeam Restore to Microsoft Azure

The second option utilises Veeam Backup and Replication.  This is a great addition to an already good product and gives you the capability of restoring an existing backup to a Microsoft Azure subscription.  Although this is not a live synchronised function like the Site Recovery product, you could configure Veeam to backup the virtual machines to Microsoft Azure (with a relatively short space between backups) to provide a similar function.  With the data already residing in Azure, it would be quicker to perform a restore to Microsoft Azure and have the VM working.  Veeam had the functionality to convert EFI to BIOS during the restore process before Microsoft added it to ASR.  One downside with the Veeam solution is that you need to have a local Microsoft account to perform a restore to a subscription using the preferred Resource Manager portal… this means that you cannot utilise federated AD accounts for the backup process, which could be seen as a security risk in a larger corporation.  I’m sure that Veeam will iron out this issue in future releases and then both products will be pretty much on a par again.

 

As you can see, migrating to Cloud solutions is getting easier and easier… just remember to weigh up all of the costs involved with Cloud hosted solutions compared to locally or data centre hosted solutions (such as power, cooling, hardware costs etc.) to gain a true understanding of the costs.

 

Blog-a-Week 2018 Posting (BAW):

In previous years, I have had periods throughout the year where I have been unable to post an entry to my blog.  During 2018, my aim is to post a blog entry each week of the year.  I’m hoping that the blog entries will all be useful bits of information or items that I’ve been working on recently but if the standard of the entries drops, I apologise now, as this could have been a busy week and I wasn’t able to put in as much time as I would have liked into the post

About the Author

Dinger

I'm a technical person who has held many IT related jobs for the past 20+ years. I am now working for VMware helping customers to maximise their investment in VMware technologies.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.