Azure Site Recovery support matrix for replicating from on-premises to Azure

This article summarizes supported configurations and components for Azure Site Recovery when replicating and recovering to Azure. For more about Azure Site Recovery requirements, see the prerequisites.

Note

Ensure that you update to the latest version of Site Recovery provider and agent to achieve compatability with the updates in the support matrix.

Support for deployment options

Deployment VMware/physical server Hyper-V (with/without Virtual Machine Manager)
Azure portal On-premises VMware VMs to Azure storage, with Azure Resource Manager or classic storage and networks.

Failover to Resource Manager-based or classic VMs.
On-premises Hyper-V VMs to Azure storage, with Resource Manager or classic storage and networks.

Failover to Resource Manager-based or classic VMs.
Classic portal Maintenance mode only. New vaults can't be created. Maintenance mode only.
PowerShell Not currently supported. Supported

Support for datacenter management servers

Virtualization management entities

Deployment Support
VMware VM/physical server vCenter 6.5, 6.0 or 5.5
Hyper-V (with Virtual Machine Manager) System Center Virtual Machine Manager 2016 and System Center Virtual Machine Manager 2012 R2

Note

A System Center Virtual Machine Manager 2016 cloud with a mixture of Windows Server 2016 and 2012 R2 hosts isn't currently supported. Configurations that include upgrade of an existing SCVMM 2012 R2 to 2016 is currently not supported.

Host servers

Deployment Support
VMware VM/physical server vSphere 6.5, 6.0, 5.5
Hyper-V (with/without Virtual Machine Manager) Windows Server 2016, Windows Server 2012 R2 with latest updates.
If SCVMM is used, Windows Server 2016 hosts should be managed by SCVMM 2016.

Note

A Hyper-V site that mixes hosts running Windows Server 2016 and 2012 R2 isn't currently supported. Recovery to an alternate location for VMs on a Windows Server 2016 host isn't currently supported.

Support for replicated machine OS versions

Virtual machines that are protected must meet Azure requirements when replicating to Azure. The following table summarizes replicated operating system support in various deployment scenarios while using Azure Site Recovery. This support is applicable for any workload running on the mentioned OS.

VMware/physical server Hyper-V (with/without VMM)
64-bit Windows Server 2016 (Server Core, Server with Desktop Experience)*, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 with at least SP1

Red Hat Enterprise Linux : 5.2 to 5.11, 6.1 to 6.9, 7.0 to 7.3

CentOS : 5.2 to 5.11, 6.1 to 6.9, 7.0 to 7.3

Ubuntu 14.04 LTS server (supported kernel versions)

Ubuntu 16.04 LTS server (supported kernel versions)

Debian 7

Debian 8

Oracle Enterprise Linux 6.4, 6.5 running either the Red Hat compatible kernel or Unbreakable Enterprise Kernel Release 3 (UEK3)

SUSE Linux Enterprise Server 11 SP3

SUSE Linux Enterprise Server 11 SP4
(Upgrade of replicating machines from SLES 11 SP3 to SLES 11 SP4 is not supported. If a replicated machine has been upgraded from SLES 11SP3 to SLES 11 SP4, you'll need to disable replication and protect the machine again post the upgrade.)
Any guest OS supported by Azure

Note

* Windows Server 2016 Nano Server is not supported.

Important

(Applicable to VMware/Physical servers replicating to Azure)

On Red Hat Enterprise Linux Server 7+ and CentOS 7+ servers, kernel version 3.10.0-514 is supported starting from version 9.8 of the Azure Site Recovery Mobility service.

Customers on the 3.10.0-514 kernel with a version of the Mobility service lower than version 9.8 are required to disable replication, update the version of the Mobility service to version 9.8 and then enable replication again.

Supported Ubuntu kernel versions for VMware/physical servers

Release Mobility service version Kernel version
14.04 LTS 9.9 3.13.0-24-generic to 3.13.0-117-generic,
3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic to 4.4.0-75-generic
14.04 LTS 9.10 3.13.0-24-generic to 3.13.0-121-generic,
3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic to 4.4.0-81-generic
14.04 LTS 9.11 3.13.0-24-generic to 3.13.0-128-generic,
3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic to 4.4.0-91-generic
14.04 LTS 9.12 3.13.0-24-generic to 3.13.0-132-generic,
3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic to 4.4.0-96-generic
16.04 LTS 9.10 4.4.0-21-generic to 4.4.0-81-generic,
4.8.0-34-generic to 4.8.0-56-generic,
4.10.0-14-generic to 4.10.0-24-generic
16.04 LTS 9.11 4.4.0-21-generic to 4.4.0-91-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-32-generic
16.04 LTS 9.12 4.4.0-21-generic to 4.4.0-96-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-35-generic

Supported file systems and guest storage configurations on Linux (VMware/Physical servers)

The following file systems and storage configuration software is supported on Linux servers running on VMware or Physical servers:

  • File systems: ext3, ext4, ReiserFS (Suse Linux Enterprise Server only), XFS
  • Volume manager : LVM2
  • Multipath software : Device Mapper

Paravirtualized storage devices (devices exported by paravirtualized drivers) are not supported.
Multi-queue block IO devices are not supported.
Physical servers with the HP CCISS storage controller aren't supported.

Note

On Linux servers the following directories (if set up as separate partitions/file-systems) must all be on the same disk (the OS disk) on the source server: / (root), /boot, /usr, /usr/local, /var, /etc

XFSv5 features on XFS filesystems such as metadata checksum are supported starting from version 9.10 of the Mobility service. If you are using XFSv5 features, ensure you are running Mobility Service version 9.10 or later. You can use the xfs_info utility to check the XFS superblock for the partition. If ftype is set to 1, then XFSv5 features are being used.

Support for network configuration

The following tables summarize network configuration support in various deployment scenarios that use Azure Site Recovery to replicate to Azure.

Host network configuration

Configuration VMware/physical server Hyper-V (with/without Virtual Machine Manager)
NIC teaming Yes

Not supported when physical machines are replicated
Yes
VLAN Yes Yes
IPv4 Yes Yes
IPv6 No No

Guest VM network configuration

Configuration VMware/physical server Hyper-V (with/without Virtual Machine Manager)
NIC teaming No No
IPv4 Yes Yes
IPv6 No No
Static IP (Windows) Yes Yes
Static IP (Linux) Yes

Virtual machines is configured to use DHCP on failback
No
Multi-NIC Yes Yes

Failed-over Azure VM network configuration

Azure networking VMware/physical server Hyper-V (with/without Virtual Machine Manager)
Express Route Yes Yes
ILB Yes Yes
ELB Yes Yes
Traffic Manager Yes Yes
Multi-NIC Yes Yes
Reserved IP Yes Yes
IPv4 Yes Yes
Retain source IP Yes Yes
Virtual Network Service Endpoints (Azure Storage firewalls and Virtual networks) No No

Support for storage

The following tables summarize storage configuration support in various deployment scenarios that use Azure Site Recovery to replicate to Azure.

Host storage configuration

Configuration VMware/physical server Hyper-V (with/without Virtual Machine Manager)
NFS Yes for VMware

No for physical servers
N/A
SMB 3.0 N/A Yes
SAN (ISCSI) Yes Yes
Multi-path (MPIO)
Tested with: Microsoft DSM, EMC PowerPath 5.7 SP4, EMC PowerPath DSM for CLARiiON
Yes Yes

Guest or physical server storage configuration

Configuration VMware/physical server Hyper-V (with/without Virtual Machine Manager)
VMDK Yes N/A
VHD/VHDX N/A Yes
Gen 2 VM N/A Yes
EFI/UEFI No Yes
Shared cluster disk No No
Encrypted disk No No
NFS No N/A
SMB 3.0 No No
RDM Yes

N/A for physical servers
N/A
Disk > 1 TB Yes

Upto 4095 GB
Yes

Upto 4095 GB
Disk with 4K logical and 4k physical sector size Yes Not supported for Generation 1 VMs

Not supported for Generation 2 VMs.
Disk with 4K logical and 512 bytes physical sector size Yes Yes
Volume with striped disk > 1 TB

LVM-Logical Volume Management
Yes Yes
Storage Spaces No Yes
Hot add/remove disk No No
Exclude disk Yes Yes
Multi-path (MPIO) N/A Yes
Azure storage VMware/physical server Hyper-V (with/without Virtual Machine Manager)
LRS Yes Yes
GRS Yes Yes
RA-GRS Yes Yes
Cool storage No No
Hot storage No No
Block Blobs No No
Encryption at rest(SSE) Yes Yes
Premium storage Yes Yes
Import/export service No No
Virtual Network Service Endpoints (Azure Storage firewalls and Virtual networks) configured on target storage account or cache storage account used for storing replication data No No

Support for Azure compute configuration

Compute feature VMware/physical server Hyper-V (with/without Virtual Machine Manager)
Availability sets Yes Yes
HUB Yes Yes
Managed disks Yes Yes

Failback to on-premises from Azure VM with managed disks is not currently supported.

Failed-over Azure VM requirements

You can deploy Site Recovery to replicate virtual machines and physical servers running any operating system supported by Azure. This includes most versions of Windows and Linux. On-premises VMs that you want to replicate must conform with the following Azure requirements while replicating to Azure.

Entity Requirements Details
Guest operating system Hyper-V to Azure replication: Site Recovery supports all operating systems that are supported by Azure.

For VMware and physical server replication: Check the Windows and Linux prerequisites
Prerequisites check will fail if unsupported.
Guest operating system architecture 64-bit Prerequisites check will fail if unsupported
Operating system disk size Up to 2048 GB if you are replicating VMware VMs or physical servers to Azure.

Upto 2048 GB for Hyper-V Generation 1 VMs.

Upto 300 GB for Hyper-V Generation 2 VMs.
Prerequisites check will fail if unsupported
Operating system disk count 1 Prerequisites check will fail if unsupported.
Data disk count 64 or less if you are replicating VMware VMs to Azure; 16 or less if you are replicating Hyper-V VMs to Azure Prerequisites check will fail if unsupported
Data disk VHD size Up to 4095 GB Prerequisites check will fail if unsupported
Network adapters Multiple adapters are supported
Shared VHD Not supported Prerequisites check will fail if unsupported
FC disk Not supported Prerequisites check will fail if unsupported
Hard disk format VHD

VHDX
Although VHDX isn't currently supported in Azure, Site Recovery automatically converts VHDX to VHD when you fail over to Azure. When you fail back to on-premises the virtual machines continue to use the VHDX format.
Bitlocker Not supported Bitlocker must be disabled before protecting a virtual machine.
VM name Between 1 and 63 characters. Restricted to letters, numbers, and hyphens. The VM name must start and end with a letter or number. Update the value in the virtual machine properties in Site Recovery.
VM type Generation 1

Generation 2 -- Windows
Generation 2 VMs with an OS disk type of basic (which includes one or two data volumes formatted as VHDX) and less than 300 GB of disk space are supported.
Linux Generation 2 VMs aren't supported. Learn more

Support for Recovery Services vault actions

Action VMware/physical server Hyper-V (no Virtual Machine Manager) Hyper-V (with Virtual Machine Manager)
Move vault across resource groups

Within and across subscriptions
No No No
Move storage, network, Azure VMs across resource groups

Within and across subscriptions
No No No

Support for Provider and Agent

Name Description Latest version Details
Azure Site Recovery Provider Coordinates communications between on-premises servers and Azure

Installed on on-premises Virtual Machine Manager servers, or on Hyper-V servers if there's no Virtual Machine Manager server
5.1.2700.1 (available from portal) Latest features and fixes
Azure Site Recovery Unified Setup (VMware to Azure) Coordinates communications between on-premises VMware servers and Azure

Installed on on-premises VMware servers
9.12.4653.1 (available from portal) Latest features and fixes
Mobility service Coordinates replication between on-premises VMware servers/physical servers and Azure/secondary site

Installed on VMware VM or physical servers you want to replicate
9.12.4653.1 (available from portal) Latest features and fixes
Microsoft Azure Recovery Services (MARS) agent Coordinates replication between Hyper-V VMs and Azure

Installed on on-premises Hyper-V servers (with or without a Virtual Machine Manager server)
Latest agent (available from portal)

Next steps

Check prerequisites