Let's Chat

03 9430 1788


Disaster Recovery: How to Configure Azure Site Recovery for DR

IT Networks How-To Logo

Azure Disaster Recovery (DR)

Microsoft Azure offers a Disaster Recovery option in the cloud called “Azure Site Recovery”.  If you have not read the previous article “Backup your On-Premises Servers to Microsoft Azure“, please do so as it contains some prerequisites.

Azure Site Recovery

Azure Site Recovery is a quick and relativity inexpensive way to have Disaster Recovery for your on-premises VMware environment.  It also supports Hyper-V, however this article will focus on VMware because it’s better!


  • Azure Recovery Services Vault (read our Backup your On-Premises Servers to Microsoft Azure article)
  • Azure Virtual Network for machines replicated to Azure
  • 1.2 TB of local data-store storage to hold the Configuration Server
  • A Windows 2016 License
  • A fast internet link (at least 100 Mbps+)

Okay, let’s go and setup Azure Site Recovery.

  1. Login into https://portal.azure.com
  2. Do a search for “Recovery”, click the “Recovery Services vaults”, then open your Vaultrecovery service vault
  3. Under Getting Started, click Site Recoverygetting started Site Recovery
  4. Click “Prepare infrastructure”, then choose the replication source and destinationprotection goals 1

    When prompted if you have completed deployment planning, choose Yes.

  5. Click +Configuration Server and download the *.ova 
    ** This file is a complete VMware VM deployment template ~20GB **

    Tip: Download the file to a computer  that has VMware Client installed.

  6. Once the *.ova has finished downloading, open VMware Client and click File > Deploy from OVF
  7. Go through the steps to deploy the template, give it a name, resources & network mappings as required.deploy ova file
    For this example we have left all the default settings.
  8. Power up the VM, then accept all the T&Cs and supply a password
  9. The server will reboot, be patient after login as you will be presented with a prompt to provide a Computer name, obviously provide one.provide a computer name
  10. Configure an IP address if prompted, you will also be asked to sign-in. For this sign-in use your Azure Tenant account. Finish the setup process as required and the Server will once again reboot.
  11. After the server reboots, IE will open and you will be required to register the VM with Azure Site Recovery. Follow the prompts as required, you will need to provide:
    • Vmware ESXi credentials
    • Windows domain credentialsconfigure appliance for comms
  12. Head back to the Azure Portal, open the Recovery Service Vault > Getting Started > Site Recovery in order to complete the Wizard.  Create a Replication Policy as required with RPOs as needed for your DR requirements.Azure RPO replication settings
  13. Finally we are now ready to replicate our machines to Azure, to do so head back to the Recovery Services Vault > Protected items > Replicated items
  14. Click +Replicate and complete the Source details as follows;enable replication step1
  15. Complete the wizard as required, choose your source VMs, the type of Azure VM you want (HDD type etc) and the Replication policy created earlier.
  16. The Replicated items blade will show the progress of the VM being replicated, this process will take a very long time (hours) depending on the size of the VM.enabling replication status
  17. Once replication is done, its status will say ‘Protected’.

If you followed this article this far, then you have just made yourself a DR environment in Azure.  Have a play around with the Site Recovery blade, there are some options you can tweak for the fail-over.  I recommend a test fail-over be done at least once a quarter to test your DR strategy.

As always, please reach out if you need assistance with this.

Want to stay up to date with useful tech-tips?  

Follow us on LinkedIn, Facebook or Twitter to be notified when we post new content. Or, even better, scroll down to the very bottom of this page to sign up for our Newsletter. We only send them once a month and you can always unsubscribe.