In this series of articles, I would show how to make Azure Site Recovery work with Hyper-V- step by step.
This is part 4 of the series.
Now, it’s time to create the azure storage. Click on link “Create Storage account”.
On the window that slides out from bottom, provide the storage name i.e. “proddrstorage” and also location and redundancy. The location is “east asia” to maintain location consistency. This is shown below. Click on “create storage account” button. This would create a new storage account for our disaster recovery VHD and VM configuration.
Details of the storage account can be viewed by navigated to storage account as shown below.
Now, it’s time to create a protection group. Click on “Create Protection Group” from the dashboard.
This will take you to “Protected items” tab. Click on “Protected Groups” sub tab and “Create Protection Group” link as shown on below screen.
In the resultant popup window, provide Protection group name i.e. “proddrprotectiongroup” and also select the previously created hyper-v site “ProductionDRsite”.
Additional dropdown boxes would appear for selecting appropriate subscription and storage account. We should choose the same storage account that we created earlier.
Click on the complete arrow to go to next wizard window.
Select the values as shown in below screen.
Click on the complete button and the result should look like below.
The above screenshot shows that proddrprotectiongroup has been created and configured with 0 protected items. This is because we have not yet added any virtual machine to this protection group. In next step, we will be adding virtual machine to the protection group.
Also, if we navigate to Servers | Hyper-V sites, we should see below “productionDRSite” that the server on which we installed the provider and agent is visible with connected state.
Now, it’s time to add virtual machines to protection group and protect them during times of disaster.
I already have a virtual machine on my on-premise server name DRVM. It is shown below here.
It is this Virtual machine that would be used for disaster recovery. In this Virtual machine I have install IIS and have modified the start.htm page to reflect my name on it. When I browse the start.htm file, it looks like below. Notice that is shows my name.
Goto Recovery services | Protected Items | Protected Groups | proddrproductiongroup and click on it
On the resultant page, within “virtual machines” tab click on “Add virtual machines” link
On the resultant Popup window, names of all virtual machines on the on-premise server would be shown. We have just one VM DRVM and that should be visible as shown below.
Selecting the name of the virtual machine should bring more controls on the screen including the operating system type and operating system disk as shown below.
Since, DRVM is based on Windows operating system, Windows is chosen and there is only one disk so by default it is assumed as operating system disk. If there are multiple disk attached to the virtual machine, we should choose appropriate disk containing the operating system. Click on the complete button. This will start the process of protecting the DRVM virtual machine.
This is a time consuming job and consists of multiple steps as shown below.
Also, a quick look into Hyper-v manager would show that the replication has been initiated.
A new container is created within the storage account created earlier to store all the relevant virtual machine information.
Navigating to this storage container will show all the files needed to provision a virtual machine during a disaster at on-premise datacenter.
Once all the above steps are complete the protection is enabled. Starting initial replication takes a long time and is dependent on the size of your Virtual machine.
When you add a virtual machine to protection group, a lot of activities take place behind the scene. The entire configuration from protection group is sent to the Azure site recovery agent on the on-premise server and are applied to the virtual machine. The virtual machine is enabled for replication. It is provided configuration details of the replica server which in this case is Azure. All the other relevant details like copy frequency, retain recovery points, re-synchronization and more are set. The details that are set can be viewed by navigating to Virtual machine replication properties.
This completes the configuration of Azure Site recovery and our VM would still be available at the time of disaster.
In next part (part-5), we will continue with the step by step guide and test the failover.