Export (0) Print
Expand All

Deploy Azure Site Recovery: On-Premises to On-Premises Protection

Updated: June 20, 2014

Microsoft Azure Site Recovery can protect virtual machines running on Hyper-V host servers located in System Center Virtual Machine Manager (VMM) clouds. Using Azure Site Recovery you can set up replication and failover from one on-premises VMM server to another, or from an on-premises VMM server to Microsoft Azure.

This deployment guide helps you to deploy Azure Site Recovery for on-premises to on-premises protection. After you complete the walkthrough, your virtual machines will be configured for failover and recovery. You can verify the configuration by running a test failover.

The walkthrough consists of the following steps:

  1. Deployment prerequisites: On-premises to on-premises. Check deployment requirements, and complete the planning steps before you begin deployment.

  2. Step 1: Create and configure an Azure Site Recovery vault: On-premises to on-premises—Create a vault and specify a vault key. Upload a management certificate (.cer) to the vault.

  3. Step 2: Install the Azure Site Recovery Provider: On-premises to on-premises—Install the Hyper-V Recovery Manager agent on the VMM servers you want to register in the vault.

  4. Step 3: Configure protection settings for VMM clouds—Specify protection settings for the cloud, including source and target settings, recovery points and snapshots, and initial replication settings.

  5. Step 4: Configure network mapping: On-premises to on-premises—Create mappings between VM networks on source and destination VMM servers.

  6. Step 5: Configure storage mapping: On-premises to on-premises—Create mappings between storage classifications on source and target VMM servers.

  7. Step 6: Enable protection for Hyper-V virtual machines: On-premises to on-premises—Enable protection for virtual machines.

  8. Step 7: Create and customize recovery plans: On-premises to on-premises—Create and customize recovery plans that specify how virtual machines should be grouped and failed over.

See Also

Show:
© 2014 Microsoft