Azure Site Recovery, Between an on-premises with Enhanced VMWare to Azure PartII

This blogpost continues configuration of ASR Enhanced VMWare to Azure protection. First blogpost can be found from HERE. In this second post I´m going configure Prosess Server to Azure (which is needed for failback to on-premises) and also show failover to Azure and Failback to on-premises.

Overview of failback process is documented in online document.
I will first create all the needed components before fail over to Azure and back to on-premises. You can do the failover to Azure without Azure Process Server, but it´s needed if you want to failback back to on-premises. In our example we are using Management Server Master Master Target role, but if you are replicating lot of data you might need to setup additional Master Target server.

In this example I´m using vCenter server and failback is done to orginal location. There are some dependencies which you need to take care, check them from section Failback to the original or alternate location.

In our example we need to ensure following:
“VM is managed by a vCenter server then the VM in the on-premises site must use the same datastore as the VM that’s running the on-premises master target server. If it isn’t you’ll need to migrate it in order to fail back to the same VM.”
ASRMGMT01 is our Management server which have following roles:
Process Server
Configuration Server
Master Target Server
ASR01 is our demo VM for testing the solution
ASREnhPartII001

Let´s start from installing Process Server to Azure.
Browse to you ASR Vault -> Servers -> Configuration servers tab ->add Process Server
ASREnhPartII002

Add name of the VM and select Network which is used for ASR (VPN exists).
Assign IP address.
ASREnhPartII003
After the process server is deployed in Azure login to VM.
Type your on-premises management server IP address and passphrase.
You can use default ports.
ASREnhPartII004

ASREnhPartII005

After installing Process server you have new Protection Group:
ASREnhPartII006

Next we are going to do the failover to Azure.
Browse to your recovery plan and start unplanned failover:
ASREnhPartII007
ASREnhPartII008

Browse to Jobs tab and you can check the status:
ASREnhPartII009

Wait until job is done.
After it´s finished browse to failovered VM and check that it´s up and running.
Test VM from your on-prem network (for example via RDP) and ensure that everything is running as expected.
ASREnhPartII010

Next we are going to reprotect VM. Browse to Protection Group and Mahines Tab.
Select Re-protect:
ASREnhPartII011

Select on-premises Master target (if you haven´t deployed new) and earlier deployed Azure Process Server.
As we want to recover the replica Azure VM to same on-premises VM, VM should be in the same datastore as the Master Targer server (as described earlier in this post).
Refer online documentation section Run the Failback.
ASREnhPartII012

Check from Jobs tab that reprotection is don successfully:
ASREnhPartII013

You can check the synchronization status from Failover replication group
(wait until it´s replicated):
ASREnhPartII014

ASREnhPartII015

After reprotection the VM is moved to the failback version of its protection group and is automatically added to the recovery plan you used for the failover to Azure.
ASREnhPartII016

Next we will do the failover back to the on-premises site.
In the Recovery Plans page select the recovery plan and click
Failover > Unplanned Failover.
ASREnhPartII017
ASREnhPartII018

Browse to Jobs tab and wait until it´s successfully processed.
ASREnhPartII019

Check that VM is up and running.
Last we need to Reprotect the on-premises Site.

In the ASR portal > Machines tab select the VMs that have failed back and click Re-Protect.
After you verify that replication to Azure is working as expected, in Azure you can delete the Azure VMs (currently not running) that were failed back.
ASREnhPartII020
ASREnhPartII021

Check Jobs tab:
ASREnhPartII022

And notice that your VM is applied to protection group.
ASREnhPartII023

That´s it.

Leave a Reply

Your email address will not be published. Required fields are marked *