Search
StarWind is a hyperconverged (HCI) vendor with focus on Enterprise ROBO, SMB & Edge

[Azure] Use Azure Site Recovery to migrate to Azure from your VMWare environment

  • September 6, 2018
  • 9 min read
Cloud and Virtualization Architect. Florent is specializing in public, hybrid, and private cloud technologies. He is a Microsoft MVP in Cloud and Datacenter Management and an MCSE in Private Cloud.
Cloud and Virtualization Architect. Florent is specializing in public, hybrid, and private cloud technologies. He is a Microsoft MVP in Cloud and Datacenter Management and an MCSE in Private Cloud.

https://i1.wp.com/cloudyjourney.fr/wp-content/uploads/2018/01/ASRLogo.png?ssl=1

You’re on VMWare ESX 5.5, 6 or 6.5 and you want to migrate to Azure? Don’t worry, it’s pretty simple now, just follow this article.

To start, you must run one of the following VMWare version, supported by Microsoft, 5.5, 6.0 or 6.5. After that, you need an Azure subscription to be able to migrate to Azure.

More information about the ASR pricing is available here : https://azure.microsoft.com/en-us/pricing/details/site-recovery/

NOTE : It’s free for 31 days, to help you in you migration to Azure… or to try the product.

The full documentation is available here : https://docs.microsoft.com/en-us/azure/site-recovery/vmware-azure-tutorial

To start, create a new Recovery Services Vault in your Azure Subscription :

wp-image-9867

Click on Site Recovery on the left part, under Getting Started and choose Prepare Infrastructure.

Choose from where you want to synchronize (OnPrem) to where (Azure) and the type of the hypervisor, VMWare :

wp-image-9868

Do the deployment planning and continue :

wp-image-9869

Click on Configure Server to start the wizard to configure the server. Download the VM that you will import in your VMWare environment :

wp-image-9870

Import it in your VMWare infrastructure and start it. Complete the Windows server installation and the ASR setup that start automatically after the login. Choose a server name and connect to your Azure subscription:

wp-image-9871

wp-image-9872

wp-image-9873

The VM will restart and after that, you can install the VMWare vSphere PowerCLI :

wp-image-9874

When it’s done, launch the shortcut on the desktop, Microsoft Azure Site Recovery Configuration Manager :

wp-image-9875

It’ll open a new IE session, where you can start the configuration of the configuration server. Choose the NIC from where you want to receive the traffic to send it to Azure :

wp-image-9876

And validate :

wp-image-9877

After that, connect to your Azure account and select the vault that you created :

wp-image-9878

Install MySQL to be able to use ASR :

wp-image-9879

Installation completed successfully :

wp-image-9880

Some checks will be done before continuing. Be sure that you don’t have failed. In my case, the only warning that I’ve is that I don’t provide a static IP :

wp-image-9881

When it’s done, add your vCenter/ESXi details and an account that has the rights to connect to :

wp-image-9882

You can continue :

wp-image-9883

Finally, add credentials to connect to OS (Linux and/or Windows) :

wp-image-9884

You can finalize the configuration :

wp-image-9885

After some minutes, the appliance is configured :

wp-image-9886

Go back to the Azure interface, and now, you should be able to see your configuration server as a source :

wp-image-9887

Select the connection to the vCenter that you want to use :

wp-image-9888

Be sure to have a storage account and a network available to continue :

wp-image-9889

Create new replication policy, by providing the RPO threshold, the number of recovery points, etc. :

wp-image-9890

Finalize the adding of this configuration server :

wp-image-9891

Replicate your first VM

I’ve a VM a Debian VM, OnPrem, with a website :

wp-image-9892

Go on Azure, and choose Step 1 to replicate a VM. Choose the configuration server and the vCenter where the VM is located :

wp-image-9893

Provides some information like the storage account and the network :

wp-image-9894

Select the VM in the list :

wp-image-9895

Associate credentials to connect to the VM and install the replication agent :

wp-image-9896

Assign the replication policy that you created before. And validate :

wp-image-9897

The protection is starting. After 5 minutes, the agent is installed and the initial replication can start.

wp-image-9898

wp-image-9899

wp-image-9900

The replication starts the synchronization :

wp-image-9901

Depending on the size of the VM and your network, after sometimes, you’ll be able to see the VM as protected :

wp-image-9902

Before doing the failover, you can, if you want, customize the VM size, the VM name, the static IP address, etc. in the Compute and Network tab of the protected VM.

Failover to Azure

Before going to Azure, you can do a test failover if you want, to try the migration for example. In my case, I want to migrate my VM to Azure, so just click on Failover :

wp-image-9903

Use the recovery point of your choice, shut down the VM OnPrem or not, and click OK :

wp-image-9904

You can check the status of the job in Site Recovery jobs tab :

wp-image-9905

It works fine after few minutes :

wp-image-9906

And I can see it as VM :

wp-image-9907

I’ll just add a public IP to my NIC to be able to access the website from outside :

wp-image-9908

And I can access it through SSH :

wp-image-9909

And I have done some modifications on my website :

wp-image-9910

If you don’t want to go back OnPrem, you just need to go back in your vault, on the VM, and click on Complete Migration. Don’t do this if you want to go back OnPrem and use the Re-protect option :

wp-image-9911

It will do the commit and will remove your instance from the vault :

wp-image-9912

After few minutes, the migration is completed :

wp-image-9913

And I’ve nothing anymore in my vault :

wp-image-9914

As you can see, it’s pretty easy to migrate from VMware to Azure, and this is for free 😊

Found Florent’s article helpful? Looking for a reliable, high-performance, and cost-effective shared storage solution for your production cluster?
Dmytro Malynka
Dmytro Malynka StarWind Virtual SAN Product Manager
We’ve got you covered! StarWind Virtual SAN (VSAN) is specifically designed to provide highly-available shared storage for Hyper-V, vSphere, and KVM clusters. With StarWind VSAN, simplicity is key: utilize the local disks of your hypervisor hosts and create shared HA storage for your VMs. Interested in learning more? Book a short StarWind VSAN demo now and see it in action!