Here is part two of my VMM to Azure quick guide. In part one, the Hyper-V and VMM servers had the required agents installed and the VMM server was registered with the Azure Site Recovery Vault.
In this part I’m going to cover:
- Configuring cloud protection
- Managing virtual machine protection
- Changing the hardware sizing of virtual machines
Configuring cloud protection:
During the installation of the VMM agent, if the Sync cloud meta data to site recovery portal option is checked, there should be a list of your on-premises clouds appear in Azure. This is found under the Protected Items tab of the Site Recovery Vault that you have registered the VMM Server with.
If you didn’t or there where problems during the agent install, you will need to open SCVMM, select a cloud you wish to protect, right click and open the properties tab and finally check the box ‘Send configuration data about this cloud to the Windows Azure Hyper-V Recovery Manager’
Once the clouds appear, select the cloud you wish to protect, click on Configure Protection Settings, select Azure as the target, configure any other cloud settings then click SAVE on the bottom menu bar.
Setting that you may wish to adjust include
- Copy Frequency: 30 Seconds | 5 Minutes | 15 Minutes
- Retain Recovery Points For (Hours): 0 – 24
- Frequency of application consistent snapshots: Never – 12 Hours
Once the configuration setting have saved, the cloud is protected and this is shown in the Azure Portal.
Managing virtual machine protection
To protect virtual machines, they must reside in one of the protected clouds. Click on the protected cloud to open it, then either click on Enable Protection if you are adding the first virtual machine for protection or click on the + Add virtual Machine button on the bottom menu.
Select the virtual machine you wish to protect and if its running Windows or Linux and then click the tick to begin protection of the virtual machine.
There are multiple ways to enable protection on a virtual machine, another way is by setting it on a virtual machine within VMM. Browse in VMM to the virtual machine you wish to protect, select the virtual machine and then click the Manage Protection button on the top ribbon. As with most things Microsoft there are various ways to achieve the same thing and in VMM is no exception, with various locations available to enable protection.
Once the machine has been enabled for protection, the virtual machine will begin to sync with the Azure Site Recovery Vault.
Changing the hardware sizing of virtual machines
Once the the virtual machine has replicated to ASR, its possible to change some of the hardware details of the Azure clone. It maybe that in a DR scenario, as long as the resource is able to continue to run in the cloud, performance is not so much of a problem as that of the cost to do so. Azure offers the ability to select the size of Azure machine you wish it to run on, depending on processor and RAM requirements.
To do this, open the protected cloud which the protected virtual machine resides in, then click on the virtual machine to display the Source and target properties.
It is from here the machine size can be changed.
That’s the end of this part of the post, in part three I hope to cover:
- Mapping networks
- Recovery plans
- Failover options.
Microsoft Azure Site Recovery: Between an on-premises VMM site and Azure – Part One
Microsoft Azure Site Recovery: Between an on-premises VMM site and Azure – Part Two
Microsoft Azure Site Recovery: Between an on-premises VMM site and Azure – Part Three