Converting a virtual computer (VMware) to Azure

%3CLINGO-SUB%20id%3D%22lingo-sub-2378470%22%20slang%3D%22en-US%22%3EConverting%20a%20virtual%20computer%20(VMware)%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2378470%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20to%20migrate%20a%20Windows%202008%20R2%20server%20with%20a%20web%20application%20and%20some%20systems%20to%20Azure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20currently%20have%20some%20virtual%20machines%20created%20using%20Windows%20images%20with%20managed%20disks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20this%20server%20to%20be%20converted%20to%20Azure%20just%20like%20my%20others%20are%20currently.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20simplest%20option%20and%20with%20little%20effort%20to%20make%20this%20migration%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20two%20procedures%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOption%201%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1%20-%20Create%20a%20VHD%3CBR%20%2F%3E2%20-%20Allocate%20to%20a%20storage%20account%3CBR%20%2F%3E3%20-%20Create%20an%20image%20of%20this%20VHD%3CBR%20%2F%3E4%20-%20Deploy%20a%20new%20VM%20using%20this%20image%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOption%202%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fmigrate-tutorial-windows-server-2008%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fmigrate-tutorial-windows-server-2008%3C%2FA%3E%3C%2FP%3E%3CP%3EBut%20this%20one%20is%20a%20lot%20of%20work!%20I%20wanted%20something%20simpler.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2378470%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EVirtual%20Machine%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2438296%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20a%20virtual%20computer%20(VMware)%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2438296%22%20slang%3D%22en-US%22%3ESoo..%20many%20ways%20to%20do%20this%2C%20as%20you%20mentioned%20there%20is%20Azure%20Site%20Recovery%20and%20the%20image%20method.%3CBR%20%2F%3E%3CBR%20%2F%3EAnother%20option%20I've%20used%20in%20the%20past%20is%20Veeam%20Backup%20and%20restore%20into%20Azure%20(maybe%20see%20if%20your%20backup%20solution%20you%20are%20using%20for%20on-premises%20workloads%20has%20an%20Azure%20endpoint%20that%20can%20help%20restore%20to)%20.%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%2C%20you%20could%20look%20into%20turning%20your%20web%20applications%20into%20Azure%20WebApps%20through%20the%20migration%20assistance%3A%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-gb%2Fservices%2Fapp-service%2Fmigration-assistant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fazure.microsoft.com%2Fen-gb%2Fservices%2Fapp-service%2Fmigration-assistant%3C%2FA%3E.%3CBR%20%2F%3E%3CBR%20%2F%3E*%20If%20it%20is%20only%20a%20few%20and%20you%20can%20leverage%20downtime%2C%20then%20creating%20the%20images%20and%20then%20virtual%20machines%20is%20an%20option.%3CBR%20%2F%3E*%20If%20you%20have%20have%20more%20than%204%2B%20virtual%20machines%2C%20I%20would%20look%20at%20Azure%20Site%20Recovery%2FAzure%20Migrate%20to%20reduce%20downtime%20and%20data%20loss%2C%20especially%20if%20you%20have%20access%20to%20the%20hypervisor%20then%20you%20can%20do%20multiple%20workloads%20at%20once.%3CBR%20%2F%3E%3CBR%20%2F%3EInstalling%20Windows%20Server%202019%20on%20new%20fresh%20Virtual%20Machines%20in%20Azure%20and%20migrating%2Fupgrading%20the%20workloads%20would%20be%20preferred%2C%20if%20you%20can't%20go%20the%20PaaS%20route%2C%20then%20you%20are%20running%20the%20latest%20supported%20operating%20systems%2C%20which%20doesn't%20have%20any%20legacy%20drivers%20or%20old%20software%20and%20is%20a%20good%20opportunity%20to%20upgrade%20legacy%20software%20and%20potentially%20do%20a%20seamless%20swap%20over%2C%20between%20old%20and%20new.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20may%20be%20of%20some%20interest%20as%20well%20for%20Cloud%20Adoption%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcloud-adoption-framework%2Fdigital-estate%2F5-rs-of-rationalization%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcloud-adoption-framework%2Fdigital-estate%2F5-rs-of-rationalization%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ERehost%2C%20Refactor%2C%20Rearchitect%2C%20Rebuild%2C%20Replace%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

I need to migrate a Windows 2008 R2 server with a web application and some systems to Azure.

 

I currently have some virtual machines created using Windows images with managed disks.

 

I want this server to be converted to Azure just like my others are currently.

 

What is the simplest option and with little effort to make this migration?

 

I found two procedures:

 

Option 1

 

1 - Create a VHD
2 - Allocate to a storage account
3 - Create an image of this VHD
4 - Deploy a new VM using this image

 

Option 2

 

https://docs.microsoft.com/en-us/azure/site-recovery/migrate-tutorial-windows-server-2008

But this one is a lot of work! I wanted something simpler.

 

Thanks.

2 Replies
Soo.. many ways to do this, as you mentioned there is Azure Site Recovery and the image method.

Another option I've used in the past is Veeam Backup and restore into Azure (maybe see if your backup solution you are using for on-premises workloads has an Azure endpoint that can help restore to) .

Also, you could look into turning your web applications into Azure WebApps through the migration assistance: https://azure.microsoft.com/en-gb/services/app-service/migration-assistant.

* If it is only a few and you can leverage downtime, then creating the images and then virtual machines is an option.
* If you have have more than 4+ virtual machines, I would look at Azure Site Recovery/Azure Migrate to reduce downtime and data loss, especially if you have access to the hypervisor then you can do multiple workloads at once.

Installing Windows Server 2019 on new fresh Virtual Machines in Azure and migrating/upgrading the workloads would be preferred, if you can't go the PaaS route, then you are running the latest supported operating systems, which doesn't have any legacy drivers or old software and is a good opportunity to upgrade legacy software and potentially do a seamless swap over, between old and new.

This may be of some interest as well for Cloud Adoption:
https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/digital-estate/5-rs-of-rationalizati...

Rehost, Refactor, Rearchitect, Rebuild, Replace
Hi,
As you running currently a non supported OS version and even that OS 2008R2 with a new product key is supported I would not do this, build a new fresh server 2019 in Azure an move the application over. that way you can test and sideload the application, In basic there is no good reason to run server 2008r2, Take the time and move the application to a new system, you will thank me later as all runs smoothly and easy to handle. stay current and stay secure, ping me if you need more help or visit my blog