Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Leveraging Microsoft Azure as your disaster recovery/failover data center

Rand Morimoto | June 24, 2014
Using Azure Site Recovery (ASR) to replicate VMs to Azure.

So my step by steps:

Have a working Microsoft System Center Virtual Machine Manager (VMM) 2012R2 server and a HyperV host connected to Active Directory thatll be the basis of your on-premise virtual machine environment.

Within VMM, create a cloud and assign the HyperV host to that cloud

Right click the cloud and create a VM and place that VM on the HyperV host. Make sure the Property on the VM Operating System says it is Win2008 or higher that is supported by Azure. By default, VMs take on the OS property of undefined and thatll cause a failover later when you try to replicate the VM to Azure as Azure only wants replicas of Azure supported OSs. Also, when you create the VM, if you have the option, make sure it is a Generation 1 VM. Azure currently does not support Gen2 VMs and thatll trip you up.

Use an existing Azure Subscription account and login, or sign up for a free trial by going to this site and selecting try it now.

Within the Azure Portal screen, scroll down to Recovery Services (on the left menu), and click on Create a New Vault (this is where your VMs will be replicated to) which will bring up a Data Services / Recovery Services / Site Recovery Vault option, select Quick

Create

For the name of the Vault, give it something youd remember, in my case, Ill call it RandsVault, and Ill choose the Region West US since Im in the Western United States, then click Create Vault

Once the Vault has been created, click on the Right Arrow next to the name of your vault. Under Setup Recovery, choose Between an on-premise site and Microsoft Azure so that you are telling the configuration settings that you are going to be replicating between your on-premise datacenter and Azure in the cloud.

You will now see a list of things you need to do which the first thing is to create a key exchange of certificates between Microsoft Azure and your VMM server.

From a Command Prompt, run: makecert.exe -r -pe -n CN=CertificateName -ss my -sr localmachine -eku 1.3.6.1.5.5.7.3.2 -len 2048 -e 01/01/2016 CertificateName.cer that will create a self-signed certificate for your VMM host (the makecert.exe program can be found from a Visual Studio installation in the c:\Program Files\Windows Kits\?.?\bin\x64\ You can download a free copy of Visual Studio Express for Windows Desktops here. Note: Visual Studio is not used for anything else on this process, so you could install VS on a separate system, all you are looking to do is get a copy of the makecert.exe utility)

Export a PFX copy of the cert you just created by running MMC from a Command Prompt, doing a File Add/Remote Snap-in, choose Certificates for the Local Computer, and then browsing the Certificates Tree to Personal \ Certificates. Youll see the name of the certificate you just created. Right click the Certificate and choose Export, click Next, then choose Yes, export the private key, select Personal Information Exchange (PFX) and choose to include all certificates in the certification path if possible and choose Export all extended properties, the click Next. Click Password and choose a password, could be something simple like 123456, Click Next. Then select a name that you want to name this PFX file (in my case, Ill call it RandVaultExport, then click Finish to export the cert.

 

Previous Page  1  2  3  4  5  Next Page 

Sign up for CIO Asia eNewsletters.