Azure Site Recovery Planning Considerations – Part 4 – For VMware Virtual Machines and physical server

On these post series, I want to cover some of the planning considerations that I usually use, when I’m designing/planning with my costumers, an ASR deployment/infrastructure. I broke down in several posts so I can cover and make easy to find the considerations that you are looking for. In this post, I will cover additional considerations when you need to configure Azure-based protection of VMware virtual machines and physical servers. The general considerations you can find here.

When configuring Azure-based protection of VMware virtual machines and physical servers, the following additional considerations apply:

  • Use VMware vSphere v5.1, vSphere v 5.5 or vSphere v6.0.
  • Microsoft recommends the use of VMware vCenter 5.5 or VMware vCenter 6.0 to manage vSphere hosts.
  • If you decide to use an Azure premium storage account to store replicated data, you must designate another storage account to store replication logs.
  • To use push installation of the Mobility service on the Windows virtual machine that you intend to protect, ensure that the Windows Firewall allows inbound File and Printer Sharing and Windows Management Instrumentation traffic. For Linux virtual machines, you should enable the Secure File Transfer Protocol subsystem and password authentication in the sshd_config
  • You have the option of excluding individual disks from replication.
  • The computer hosting the configuration server component must have outbound connectivity to Azure via TCP port 443. The computer hosting the process server component should have outbound connectivity to Azure via TCP port 9443. You can use a different port for this purpose if needed. Because both the process server and the configuration server components reside by default on the configuration server, you should make sure that this server can access the following URLs over ports 443 and 9443:
    • *
    • *
    • *
    • *
    • *
  • The configuration server should also be able to reach over TCP port 80.
  • Depending on the outcome of your capacity planning, you have the option of adjusting the bandwidth available to the replication traffic. In this scenario, the process server handles replication. Therefore, you can configure its Microsoft Azure Backup throttling settings or adjust the number of upload and download threads per virtual machine by modifying its registry. For details regarding this option, refer to the Azure Site Recovery Planning Considerations – Part 2 – For Hyper-V Virtual Machines.


Marcos Nogueira
Twitter: @mdnoga

Marcos Nogueira

With more than 18 years experience in Datacenter Architectures, Marcos Nogueira is currently working as a Principal Cloud Solution Architect. He is an expert in Private and Hybrid Cloud, with a focus on Microsoft Azure, Virtualization and System Center. He has worked in several industries, including Aerospace, Transportation, Energy, Manufacturing, Financial Services, Government, Health Care, Telecoms, IT Services, and Gas & Oil in different countries and continents. Marcos was a Canadian MVP in System Center Cloud & Datacenter Managenment and he has +14 years as Microsoft Certified, with more than 100+ certifications (MCT, MCSE, and MCITP, among others). Marcos is also certified in VMware, CompTIA and ITIL v3. He assisted Microsoft in the development of workshops and special events on Private & Hybrid Cloud, Azure, System Center, Windows Server, Hyper-V and as a speaker at several Microsoft TechEd/Ignite and communities events around the world.

One Reply to “Azure Site Recovery Planning Considerations – Part 4 – For VMware Virtual Machines and physical server”

Leave a Reply

Your email address will not be published. Required fields are marked *