SALES: 1-800-867-1380

Plan for Azure Site Recovery Deployment with VMM Sites

Updated: December 11, 2014

Deploy Microsoft Azure Site Recovery Manager to replicate and failover virtual machines on Hyper-V host servers that are located in System Center Virtual Machine Manager (VMM) clouds. You can set up replication and failover from a source on-premises VMM server to a target on-premises VMM server, or from a source on-premises VMM server to Azure storage. Azure Site Recovery orchestrates the replication, and VMM uses Hyper-V Replica to perform the replication. Hyper-V Replica is a replication mechanism built into Hyper-V from Windows Server 2012 onwards.

On-premises to on-premises replication.

Hyper-V Recovery Manager Architecture

On-premises to Azure replication.

Azure Site Recovery - on-premises to Azure

Azure Site Recovery offers a number of business benefits, including:

  • A cost-effective method of providing protection and recovery services for multiple Hyper-V virtual machines managed by VMM.

  • A single and simplified management interface for protection and recovery across multiple VMM data centers.

  • The ability to scale and automate protection and recovery of virtual machines, including the ability to create recovery plans to automate failover and recovery of specific applications and VMM clouds.

  • The ability to easily scale storage by replicating to Azure.

  • Automated configuration of replication settings across multiple Hyper-V hosts and clusters.

  • Automated configuration and protection for data center changes, including adding or removing Hyper-V hosts from VMM clouds.

  • A simplified testing infrastructure to validate protection and recovery plans without affecting production.

  • Comprehensive reporting of cloud, host, and virtual machine status.

Prerequisites and support—Verify VMM support, virtual machine requirements, and deployment prerequisites.

Step 1: Sign up for Azure—Get signed up for Azure Site Recovery.

Step 2: Plan the VMM infrastructure—Make sure your VMM infrastructure is configured correctly.

Step 3: Prepare for network mapping—Network mapping ensures that replica virtual machines are optimally connected to networks after failover.

Step 4: Prepare storage—Storage mapping provides granular control over where replica virtual machine hard disks are stored after failover to a secondary VMM site.

Step 5: Prepare for Provider deployment—Prepare prerequisites for Provider installation on VMM servers.

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