Classic VM (ASM) to ARM Using Azure Site Recovery (ASR) V2 – Part 1: Vault Deployment

About two weeks ago, Azure Site Recovery (ASR) V2 was released to preview. Using the “Unplanned Failover” we can perform ASM (Classic / V1) VM to Azure Resource Manager (ARM) VM conversion.

In this multipart blog post series, I’m going to walk you through the process of deploying a full ASR infrastructure in Azure and while doing so I will also show you how this can be leveraged to perform the VM conversion.

As an extra bonus, I’m not going just to convert a Classic VM to an ARM VM, I’m also going to move the VM between two physical Azure regions, from north Europe to west Europe. WOOT!

Deploying the Process Server VM

For the purpose of this series, I’ve deployed my Process as a “D2_V2 Standard” VM in a Resource Group located in West Europe. This VM will connect to my Management subnet configured in the same RG and will be located on my Management storage account blob – fairly straight forward.


After the deployment is done, change the VM Private IP and restart the VM. The last part is one of the installation perquisites.


In order to get the Process server installation file, we need to deploy Recovery Services Vault from the Azure Marketplace. The Vault is where all our Azure DR and data protection infra and policies are being managed.

Notice that I’ve selected the “Recovery Services” and not “Azure Site Recovery” which represent the previous version. For the purpose of this post we will only do what’s necessary in order for us to get the ASR installation and the vault registration key.


In my case, the Vault is created in the same Resource Group where the Process is – “LKRG-WE” in West Europe.


Once the Vault deployment is done, the management interface will open automatically. For those of you who are familiar with the previous version in the Classic portal, you can already see a big interface improvement here!


To download the ASR Process server installation file and vault registration key, go to the Site Recovery servers and choose to add a new Configuration Server. “Configuration server” represent one of the components in the Process server itself – don’t worry about not understanding where this name is coming from.

Bullets 2 & 3 will point you what you are looking for at this point. My recommendation is for you to do this part from the Process server itself so you won’t have to upload the 500MB installation file to the Process server – can save you some time.


If you didn’t follow my advice, just upload those two files to the Process server so in the next post for this series you will be ready to start the installation.


In the next part for this series, we will walk through the Process server installation wizard.

Be the first to comment

Leave a Reply