Support matrix for disaster recovery of VMware VMs and physical servers to a secondary site
This article summarizes what's supported when you use the Azure Site Recovery service for disaster recovery of VMware VMs or Windows/Linux physical servers to a secondary VMware site.
- If you want to replicate VMware VMs or physical servers to Azure, review this support matrix.
- If you want to replicate Hyper-V VMs to a secondary site, review this support matrix.
Replication of on-premises VMware VMs and physical servers is provided by InMage Scout. InMage Scout is included in Azure Site Recovery service subscription.
The Site Recovery scenario for replication between on-premises VMware or physical datacenters is reaching end-of-support.
From August 2018, the scenario can’t be configured in the Recovery Services vault, and the InMage Scout software can’t be downloaded from the vault. Existing deployments will be supported.
- From December 31 2020, the scenario won’t be supported. Existing partners can onboard new customers to the scenario until support ends.
During 2018 and 2019, two updates will be released:
- Update 7: Fixes network configuration and compliance issues, and provides TLS 1.2 support.
- Update 8: Adds support for Linux operating systems RHEL/CentOS 7.3/7.4/7.5, and for SUSE 12
- After Update 8, no further updates will be released. There will be limited hotfix support for the operating systems added in Update 8, and bug fixes based on best effort.
|vCenter server||vCenter 5.5, 6.0 and 6.5
If you run 6.0 or 6.5, note that only 5.5 features are supported.
Replicated VM support
The following table summarizes operating system support for machines replicated with Site Recovery. Any workload can be running on the supported operating system.
|Windows Server||64-bit Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 with at least SP1.|
|Linux||Red Hat Enterprise Linux 6.7, 6.8, 6.9, 7.1, 7.2
Centos 6.5, 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2
Oracle Enterprise Linux 6.4, 6.5, 6.8 running the Red Hat compatible kernel, or Unbreakable Enterprise Kernel Release 3 (UEK3)
SUSE Linux Enterprise Server 11 SP3, 11 SP4
Linux machine storage
Only Linux machines with the following storage can be replicated:
- File system (EXT3, ETX4, ReiserFS, XFS).
- Multipath software-device Mapper.
- Volume manager (LVM2).
- Physical servers with HP CCISS controller storage are not supported.
- The ReiserFS file system is supported only on SUSE Linux Enterprise Server 11 SP3.
Network configuration - Host/Guest VM
|Host - NIC teaming||Yes|
|Host - VLAN||Yes|
|Host - IPv4||Yes|
|Host - IPv6||No|
|Guest VM - NIC teaming||No|
|Guest VM - IPv4||Yes|
|Guest VM - IPv6||No|
|Guest VM - Windows/Linux - Static IP address||Yes|
|Guest VM - Multi-NIC||Yes|
Guest or physical server storage
|Gen 2 VM||N/A|
|Shared cluster disk||Yes|
|Disk > 1 TB||Yes|
|Volume with striped disk > 1 TB
|Hot add/remove disk||Yes|
|Move vaults across resource groups (within or across subscriptions)||No|
|Move storage, network, Azure VMs across resource groups (within or across subscriptions)||No|
Mobility service and updates
The Mobility service coordinates replication between on-premises VMware servers or physical servers, and the secondary site. When you set up replication, you should make sure you have the latest version of the Mobility service, and of other components.
|Scout updates||Scout updates are cumulative.
Learn about and download the latest Scout updates
|Component updates||Scout updates include updates for all components, including the RX server, configuration server, process and master target servers, vContinuum servers, and source servers you want to protect.
Download the InMage Scout user guide