Export (0) Print
Expand All

Site Recovery

Updated: November 11, 2014

Deploy Microsoft Azure Site Recovery to protect virtual machines and assure business continuity with replication and failover. You can deploy Azure Site Recovery in a number of

The following table summarizes and compares the VMM on-premises and Azure deployment options.

 

Feature

On-Premises to Azure

On-Premises to On-Premises (Hyper-V replication)

On-Premises to On-Premises (SAN replication)

Data to Azure Site Recovery

Cloud metadata is sent to Azure Site Recovery.

Replicated data is stored in Azure storage.

Cloud metadata is sent to Azure Site Recovery.

Replicated data is stored in location specified on target Hyper-V server.

Cloud metadata is sent to Azure Site Recovery.

Replicated data is stored in the target storage array.

Vault requirements

You'll need an Azure account to set up an Azure Site Recovery vault. See Azure free trial and get pricing information at Azure Site Recovery Manager Pricing Details.

Azure account with Azure Site Recovery enabled.

Azure account with Azure Site Recovery enabled.

Replication

Virtual machines replicate from source on-premises Hyper-V server to target Azure storage. You can set up reverse replication to replicate back to the source location.

Virtual machines replicate from source on-premises Hyper-V server to another. You can set up reverse replication to replicate back to the source location.

Virtual machines replicate from source SAN storage device to target SAN device. You can set up reverse replication to replicate back to the source location.

Virtual machine storage

Virtual machine hard disk stored in Azure storage

Virtual machine hard disk stored on Hyper-V host.

Virtual machine hard disk stored on SAN storage array.

Azure storage

Azure storage account required.

The account should have geo-replication enabled, be located in the the same region as the Azure Site Recovery service, and be associated with the same subscription.

Not applicable

Not applicable

SAN storage array

Not applicable

Not applicable

SAN storage array must be available in both the source and target sites and managed by VMM. See Deployment prerequisites for more information. 

VMM server

Requires a VMM server only in the source site only. The VMM server must have at least one cloud that contains at least one Hyper-V host server or cluster.

Requires source and target VMM servers with at least one cloud on each, or a single VMM server with two clouds. Clouds must contain at least one Hyper-V host server or cluster.

Requires source and target VMM servers with at least one cloud on each. Clouds must contain at least one Hyper-V cluster.

VMM System Center version

System Center 2012 R2

System Center 2012 with SP1

System Center 2012 R2

System Center 2012 R2 with VMM Update Rollup 5.0

VMM configuration

Set up clouds in source and target sites

Set up VM networks in source and target site

Set up storage classifications in source and target sites

Install the Provider on source and target VMM servers

Set up clouds in source site

Set up SAN storage

Set up VM networks in source site

Install the Provider on source VMM server

Enable virtual machine protection

Set up clouds in source and target sites

Set up VM networks in source and target sites

Install the Provider on source and target VMM server

Enable virtual machine protection

Azure Site Recovery Provider

Install on source VMM server

Install on source and target VMM servers

Install on source and target VMM servers

Azure Recovery Services Agent

Install on Hyper-V host servers located in VMM clouds

Not required

Not required

Virtual machine recovery points

Set recovery points by time.

Specifies how long a recovery point should be kept (0-24 hours). A recovery point is created using the formula 90/copy_frequency during the first hour,and then once an hour.

Set recovery points by amount.

Specifies how many additional recovery points should be kept (0-15). By default a recovery point is created every hour. When set to zero only the latest recovery point is stored on the replica Hyper-V host server.

Configured in array storage settings.

Network mapping

Map VM networks to Azure networks.

Network mapping ensures that all virtual machines that fail over in the same source VM network can connect after failover. In addition if there's a network gateway on the target Azure network then virtual machines can connect to on-premises virtual machines.

If mapping isn't enabled only virtual machines that fail over in the same recovery plan can connect to each other after failover to Azure.

Map source VM networks to target VM networks.

Network mapping is used to place replicated virtual machines on optimal Hyper-V host servers, and ensures that virtual machines associated with the source VM network are associated with the mapped target network after failover.

If mapping isn't enabled replicated virtual machines won't be connected to a network.

Map source VM networks to target VM networks.

Network mapping ensures that virtual machines associated with the source VM network are associated with the mapped target network after failover.

If mapping isn't enabled replicated virtual machines won't be connected to a network.

Storage mapping

Not applicable

Maps storage classifications on source VMM servers to storage classifications on target VMM servers.

With mapping enable virtual machine hard disks in the source storage classification will be located in the target storage classification after failover.

If storage mapping isn't enabled replicated virtual hard disks will be stored in the default location on the target Hyper-V host server.

Maps between storage arrays and pools in the primary and secondary sites.

Show:
© 2014 Microsoft