SALES: 1-800-867-1380

Prerequisites and support

Updated: July 11, 2014

Get information about Azure Site Recovery prerequisites and supported scenarios.

 

Supported MM version Supported Azure Site Recovery deployment Supported operating system on source Hyper-V host Supported operating system on target Hyper-V host On-premises to on-premises only Supported Provider/Agent version

VMM on System Center 2012 R2 (recommended)

On-premises to on-premises

On-premises to Azure

Windows Server 2012 R2

Windows Server 2012 with latest updates

Windows Server 2012 R2 RTM

Windows Server 2012 with latest updates

Azure Site Recovery Provider: Latest version

Azure Recovery Services Agent: Latest version - 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

Azure Site Recovery Provider: Latest version

 

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

On-site VMM server (physical or virtual)

Y

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

Replicate between two clouds on the same on-site VMM server.

Y

Replicate from on-site VMM server to Azure storage.

On-site VMM in cluster deployment (virtual)

Y

Replicate from on-site VMM cluster to VMM cluster in same site or different location

Y

Replicate from on-site VMM cluster to Azure.

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 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

Character restriction based on supported Regex

Supported: [a-zA-Z0-9_\-]{1,63}(?<!\-)$

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 on-premises to cloud deployment.

At least one VMM server.

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.

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.

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 host server in cluster (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 backup 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 host server in cluster (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 backup, you’ll need to configure the cluster broker manually. For instructions see Configure Hyper-V Replica Broker.

Network mapping requirements: on-premises to on-premises deployment

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

  • The virtual machine that is located in the cloud on the source VMM server should be connected to a VM network, and it in turn 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.

Network mapping requirements: on-premises to Azure deployment

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 that is located in the cloud on the source VMM server should be connected to a VM network, and it in turn should be linked to a logical network that is associated with the cloud.

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

Storage mapping requirements: on-premise to on-premise deployment

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

Certificate requirements

A management certificate (.cer and .pfx files) is required for upload to the Azure Site Recovery vault. The certificate requires the following:

  • The certificate can be any valid Secure Sockets Layer (SSL) certificate that is issued by a Microsoft Enterprise certification authority (CA) or by any CA that is trusted by Microsoft (and whose root certificates are distributed through the Microsoft Root Certificate Program). Alternatively, for test purposes you can use a self-signed certificate that you create using the Makecert.exe tool.

  • The certificate should be an x.509 v3 certificate.

  • The certificate must have a valid Client Authentication EKU.

  • The certificate should be currently valid with a validity period that does not exceed three years.

  • The certificate should reside in the Personal certificate store of your Local Computer.

  • To upload to the certificate to the vault, it must be in .cer format file and contain the public key.

  • The .cer certificate must be exported in .pfx format (with the private key). This .pfx certificate must be imported to each VMM server that you want to register with the vault. During installation of the Provider on a VMM server, you select the .pfx file.

  • Each Hyper-V Recovery vault only has a single .certificate associated with it at any one time. You can upload a certificate to overwrite the current certificate that is associated with the vault at any time.

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:
© 2014 Microsoft