How To: Install & Configure Azure Site Recovery: Part 4

In the previous blog post we configured our on-premises Process Server and the communication between vCenter and the Configuration Server via the Process Server.  In this blog post we are going to protect some virtual machines.

Start by logging into the Azure Portal selecting Recovery Services > VMFocusVault > Protected Items > Protection Groups > Create New Protection Group

Azure 35

Specify a Protection Group name, as I’m original I’m going with VMF-PG01

Azure 36

Next we need to select the Replication Settings for the Protection Group, choices are:

  • Multi VM Consistency – Each VM within the Protection Group will be consistent with each over
  • RPO Threshold – How much data can we afford to loose, bandwidth needs to be able to cope with this setting
  • Recovery Point Retention – How many recovery points do we want to have available?
  • Application Consistent Snapshot Frequency – Calls VSS to quiescence memory

Select your chosen settings and Click the Tick

Azure 37

Once the Protection Group has finished being created.  Click on the Protection Group and select ‘Add Virtual Machines’

Azure 38

Select the virtual machines you want to protect (in my case VMF-AZ01) and Click the Tick

Azure 39

Next select your Process Server, Master Target Server and Storage Account and Click the Tick

Azure 40

Finally specify the credentials for the Mobility Service to use to perform installation.  Then Click the Tick

Azure 41

Naturally, it will take sometime for the initial replication to complete.  However this can be monitored by selecting the Protection Group.

Azure 42


Quite a few cups of tea later and my on-premises vSphere virtual machines are now protected within Azure Site Recovery.  Now I want to configure the virtual machines so that they use the correct virtual networks within Azure.

Select your Protection Group then click on your VM

Azure 43

Select Configure from the top bar

Azure 44

This is the heart of the configuration of where our protected on-premises VM will sit in Azure.  The items we can configure are:

  • Name – These can be altered on-premises to Azure.  Not entirely sure of the use case for this, but it’s an option
  • Properties – The target VM in Azure when it is hydrated.  Note that you cannot change between VM’s between series once failed over to Azure so make sure you choose the right one.
  • Network – The target Azure Network and IP address for virtual machine

Azure 45

Now we have configured the protection for our virtual machines, in the next post we are going to failover to Azure.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s