Classic VM (ASM) to ARM Using Azure Site Recovery (ASR) V2 – Part 3: Mobility Service

In this post we will install the Mobility Service agent on our Classic VM and touch on the networking challenges we have with this design.

In the previous parts for this series:

Let’s review my North Europe Classic VM infrastructure. This VM will get replicated to a blob storage and Resource Group physically located in West Europe.

The challenge needs to be resolved prior to the replication is to make the Mobility Service communicate with the Process Server. The problem is that the Classic VM is connected to a Classic VNet in North Europe and the Process server is connected to an ARM VNet in West Europe.

In order to overcome this challenge, a Site to Site VPN IPSec tunnel needs to be established first between the two VNets. Let’s review the architecture:


Creating Site to Site VPN Tunnel Between Classic and ARM VNets

Now this is kind of long process which I’m not going to go through in details. In order to create the tunnel, use the following guidelines:

Once you have this connection established the Classic VM will be able to PING the Process Server.


Installing the Mobility Service on the Classic VM

The Mobility Service agent is the component responsible on registering the protected machine against the Process server which eventually will allow the VM to be protected by the Vault. It can be pushed and installed automatically by the Process server or installed manually. Since I want to show you what is going behind the scenes (not much really) let’s drive manually.

First thing first, you will need to copy the agent installation file from the Process server to the target Classic VM. The easiest way to go is to do this via the RDP session.

The Windows installation file located here:

C:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository


If you are using Windows FW, make sure you have ports 443 & 9443 open (I just disable it). Also, set Windows UAC to minimal protection.

The installation is very easy, all you need is the Process server private IP and the Connection Passphrase you saved in txt file.




You are done with installing the Mobility Service. In the next part for this series, we will configure the storage account and the network for the replicated Classic VM.

Be the first to comment

Leave a Reply