In this article I will show how I configured a VM in my lab to be replicated to Azure. At least, I will start to.
First, you will need to create a recovery vault. I had this configured before, with the premises-to-premises configuration. You have to configure the certificates, just so VMM can be connected to your azure subscription.
You have detailed steps here.
Now you have an extra option there, for the Premises-to-Azure configuration:
Once you have the vault connected to your VMM server, you can configure the protection:
You will need an agent on your VMM server and also on each Hyper-V host that is part of the cloud in question:
See, that’s what I mean.
Once you have the agent:
Now you can select all the machine that are in a cloud:
Remember that they need to have:
- A supported server operating system
- Be in a cloud
- Have VHD disks
- Have the OS disk marked as such in the VMM configuration
- Have required patch level in your Hyper-V hosts (see below).
- If you are mapping the networks, both the vault and the networks in azure need to be on the same region
And now here’s a new one for the bag:
As per http://support.microsoft.com/kb/2961977, you must have the latest rollups in your Server. Let’s go for it!
After some patching/rebooting, then more patching and reboot, I finally got all the required bits in.
And guess what?
One the Hyper-V side:
My uplink is pretty slow, so it will take a while to finish.
Another interesting fact is that you have now a new option on your VM configuration in VMM:
Part II will include configuring the recovery plan and mapping the networks!