SALES: 1-800-867-1380

Prerequisites and support

Updated: February 18, 2015

Get information about Azure Site Recovery prerequisites and supported scenarios.

 

Supported VMM version Supported Azure Site Recovery deployment Supported operating system on source Hyper-V host Supported operating system on target Hyper-V host Supported Provider/Agent version

VMM on System Center 2012 R2 with VMM update rollup 5.0 preview

On-premises to on-premises protection with SAN replication

At least Windows Server 2012 with latest updates

At least Windows Server 2012 with latest updates

Latest version of Azure Site Recovery Provider for installation on VMM servers

VMM on System Center 2012 R2 (recommended)

On-premises to on-premises protection with Hyper-V replication

At least Windows Server 2012 with latest updates

At least Windows Server 2012 with latest updates

Latest version of Azure Site Recovery Provider for installation on VMM servers

On-premises to Azure protection with Hyper-V replication

Windows Server 2012 R2

Not applicable

Latest version of Azure Site Recovery Provider for installation on VMM servers

Latest version of Azure Recovery Services Agent for installation on Hyper-V host servers. Required for on-premises to Azure deployment only

VMM on System Center 2012 SP1 with latest cumulative update

On-premises to on-premises protection

Windows Server 2012 with latest updates

Windows Server 2012 with latest updates

Latest version of Azure Site Recovery Provider

 

VMM configuration On-premises to on-premises On-premises to Azure

On-site VMM server (physical or virtual)

Y

Replicate with Hyper-V replication from on-site VMM server to another VMM server in same site or different location

Replicate with SAN replication from on-site VMM server to another VMM server in same site or different location

Replicate with Hyper-V replication between two clouds on the same on-site VMM server.

Y

Replicate from on-site VMM server to Azure storage with Hyper-V replication

On-site VMM in cluster deployment (virtual)

Y

Replicate from on-site VMM cluster to VMM cluster in same site or different location with Hyper-V or SAN replication

Y

Replicate from on-site VMM cluster to Azure with Hyper-V replication

The table summarizes the type of virtual machines that can be supported when replicating from an on-premises VMM server to Azure storage.

 

Virtual Machine Feature Azure Site Recovery Support Details

Host operating system

Windows Server 2012 R2

Prerequisites check fails for non-supported configuration.

Guest operating system

Windows Server 2008 R2 or later

Linux: Centos, openSUSE, SUSE, Ubuntu

Prerequisites check fails for non-supported configuration.

Update the value in the VMM console.

Guest operating system architecture

64-bit

Prerequisites check fails for non-supported configuration.

Operating system disk size

Between 20 MB and 127 GB

Prerequisites check fails for non-supported configuration.

Operating system disk count

1

Prerequisites check fails for non-supported configuration.

Update the value in the VMM console.

Data disk count

16 or less (the maximum is a function of the size of the virtual machine being created. 16 = XL)

Prerequisites check fails for non-supported configuration.

Data disk VHD size

Between 20 MB and 1023 GB

Prerequisites check fails for non-supported configuration.

Network adapters

One adapter and one IP address

Azure Site Recovery doesn’t fail but an error is issued to indicate that the virtual machine has multiple adapters. One of the adapters will be chosen as the default. Select a different adapter in the virtual machine properties in Azure Site Recovery.

Static IP address

Not supported

Azure Site Recovery doesn’t fail but an error is issued to indicate the virtual machine has a static IP address and will use DHCP after failover.

iSCSI disk

Not supported

Prerequisites check fails for non-supported configuration.

Shared VHD

Not supported

Prerequisites check fails for non-supported configuration.

FC disk

Not supported

Prerequisites check fails for non-supported configuration.

Hard disk format

VHD

VHDX (supported on generation 1 only)

Prerequisites check fails for non-supported configuration.

Virtual machine name

Should contain between 1 and 63 characters. Restricted to letters, numbers, and hyphens. The name must start with a letter or number and end with a letter or number.

Update the value in the virtual machine properties in Azure Site Recovery.

Virtual machine type

Generation 1

Prerequisites check fails for non-supported configuration.

 

Prerequisite Details

Microsoft Azure requirements

An Azure account with Azure Site Recovery enabled. If you don’t have an account or the feature isn’t enabled, see Azure free trial and Azure Site Recovery Pricing Details.

If you want to deployment Azure Site Recovery for on-premises to Azure replication, you’ll need an Azure storage account. For more information, see Introduction to Microsoft Azure storage.

VMM server and cloud requirements

The VMM server should be running System Center 2012 R2 for protection with Hyper-V replication. For SAN replication the VMM server should have VMM update rollup 5.0 installed.

At least one VMM server.

Any VMM server containing virtual machines you want to protect must be running the Azure Site Recovery Provider. This is installed during the Azure Site Recovery deployment.

In an on-premises to Azure deployment, any Hyper-V host server you want to protect must have the Azure Recovery Services agent installed. This is installed during the Azure Site Recovery deployment.

If you are running only one VMM server and you want to deploy on-premises to on-premises protection, it must have two clouds configured.

Any Hyper-V host server or cluster for which you want to manage protection must be included in a VMM cloud.

For on-premises to on-premises protection with two VMM servers each server must have at least one cloud configured on the primary VMM server you want to protect and one cloud configured on the secondary VMM server you want to use for protection and recovery.

For on-premises to Azure protection the source VMM server must have an least one cloud configured.

All VMM clouds must have the Hyper-V Capacity profile set.

The source cloud that you want to protect must contain the following:

  • One or more VMM host groups.

  • One or more Hyper-V host servers in each host group .

  • One or more virtual machines on the host server. For failover to Azure the virtual machines must comply with the requirements listed in the section above.

Hyper-V server or cluster requirements (on-premises to Azure)

Cluster broker isn’t created automatically if you have a static IP address-based cluster. If you use DHCP this is done automatically by Azure Site Recovery.

If you’re deploying on-premises to Azure protection with a source cloud that uses a failover cluster, you can either install the broker manually - Configure Hyper-V Replica Broker, or install Windows Server 2012 R2 update roll: June 2012 on each cluster node. For more information, see KB 2961977: “Hyper-V Replica Cluster Broker is not installed”2962409. After you install this update, you don’t need Hyper-V Replica Broker for replication to Azure. Instead Azure Site Recovery and VMM handle the replication.

Hyper-V server or cluster requirements (on-premises to on-premises)

Cluster broker isn’t created automatically if you have a static IP address-based cluster. If you use DHCP this is done automatically by Azure Site Recovery.

If you’re deploying on-premises to on-premises protection, you’ll need to configure the cluster broker manually. For instructions see Configure Hyper-V Replica Broker.

Network mapping requirements for on-premises to on-premises protection

In order to deploy network mapping so that virtual machines are connected to a VM network after failover, the following is required:

  • The virtual machines you want to protect on the source VMM server should be connected to a VM network. That network should be linked to a logical network that is associated with the cloud.

  • The target cloud on the secondary VMM server that you use for recovery should have a corresponding VM network configured, and it in turn should be linked to a corresponding logical network that is associated with the target cloud.

SAN replication requirements

  • You’ll need two SAN arrays set up, one in the primary site and one in the secondary.

  • Network infrastructure should be set up between the arrays. Peering and replication should be configured. Replication licenses should be set up in accordance with the storage array requirements.

  • Networking should be set up between the Hyper-V host servers and the storage array so that hosts can communicate with storage LUNs using iSCSI or fibre channel.

  • View a list of supported arrays at Deploying Azure Site Recovery with VMM and SAN - supported storage arrays.

  • SMI-S Providers, provided by the storage array manufacturers should be installed and the SAN arrays should be managed by the Provider. Set up the Provider in accordance with their documentation.

  • Ensure that the SMI-S provider for the array is on a server that the VMM server can access over the network by IP address or FQDN.

  • Each SAN array should have one or more storage pools available to use in this deployment.The VMM server at the primary site will need to manage the primary array and the secondary VMM server will manage the secondary array.

  • The VMM server at the primary site will need to manage the primary array and the secondary VMM server will manage the secondary array.

Network mapping requirements for on-premises to Azure protection

In order to deploy network mapping so that virtual machines in source VM networks are connected to a specific Azure network after failover, ensure the following:

  • The virtual machine you want to protect on the source VMM server should be connected to a VM network. That network should be linked to a logical network that is associated with the cloud.

  • You should have Azure networks configured before you start the deployment.

  • To automatically map the VM network to an Azure subnet, the name of the subnet in Azure should match the name of the VM network in VMM. If this doesn’t happen, the virtual machine will be mapped to the first Azure subnet based on alphabetical order.

Storage mapping requirements for on-premises to on-premises protection

You should have storage classifications set up on the source and target VMM servers before you begin deployment.

Provider requirements

The same version of the Azure Site Recovery Provider should be installed on all VMM servers registered in a vault. Using different versions of the Provider is not supported.

We recommend you install the latest version of the Provider.

Agent requirements: on-premises to Azure

The same version of the Azure Recovery Services Agent should be installed on Hyper-V host servers located in a VMM cloud. Using different versions of the Agent is not supported.

We recommend you install the latest version of the Agent.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft