Configure protection for virtual machines

Atualizada: Fevereiro de 2015

You can protect your virtual machines with Azure Site Recovery in two deployment scenarios:

  • Protect on-premises virtual machines to Azure—Virtual machines on an on-premises Hyper-V host server located in a VMM cloud replicate and failover to Azure virtual machines. Replication and failover is orchestrated by Azure Site Recovery. Data is stored in an Azure Storage account.

  • Protect on-premises virtual machines to an on-premises datacenter—Virtual machines on an on-premises Hyper-V host server located in a VMM cloud replicate to a Hyper-V host server located in a VMM cloud in the target datacenter. Replication and failover is orchestrated by Azure Site Recovery. Data is stored on the target Hyper-V server.

  • A datacenter that contains a VMM server running System Center 2012 R2.

  • The datacenter should be running Azure Pack with Update Rollup 4 or later.

  • The datacenter should have SMA installed and configured in the Azure pack deployment.

  • A Hyper-V host server located in the datacenter, running Windows Server 2012, 2012 with SP1, or 2012 R2. The Hyper-V host server must belong to a VMM private cloud.

  • An Azure account with Azure Site Recovery enabled. If you don’t have an account or the service isn’t enabled, see Azure free trial and Azure Site Recovery Pricing Details. You can set up a storage account before you start, or when you’re configure Azure Site Recovery settings.

  • An Azure storage account. The account needs geo-replication enabled. It should be in the same region as the Azure Site Recovery service, and be associated with the same subscription.

  • The VMM server must have Internet access. In the browser on the server open http://manage.windowazure.com to confirm access.

  • Each VMM cloud needs:

    • At least one VMM host group with at least one Hyper-V host server in each group.

    • One or more virtual machines on the host server.

  • If you want to set up network mapping you’ll need to set up logical networks on the VMM servers. In the self-service Azure Pack portal tenants set up virtual networks based on those logical VMM networks. When a tenant configures a virtual network a matching VM network is created in the VMM console. You then select and map these VM networks in the Azure Site Recovery portal using the network mapping feature.

  • Two datacenters in the same Active Directory forest if you’re using Active Directory user subscription accounts.

  • Each datacenter should have a VMM server running System Center 2012 R2.

  • Each datacenter should be running Azure Pack with Update Rollup 4 or later.

  • Each datacenter should have SMA installed and configured in the Azure pack deployment



  • A Hyper-V host server located in each site, running Windows Server 2012, 2012 with SP1, or 2012 R2. The Hyper-V hosts must belong to VMM private clouds.

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

  • VMM servers must have Internet access. In the browser on the server open http://manage.windowazure.com to confirm access.

  • Check that Hyper-V host servers in both sites can connect. Ping using FQDNs to confirm. A primary Hyper-V host server should be able to connect to a secondary Hyper-V host server using port 8084.

  • Each VMM cloud needs:

    • At least one VMM host group with at least one Hyper-V host server in each group.

    • One or more virtual machines on the host server.

  • If you want to configure two-way protection you need at least two clouds on each VMM server.

  • If you want to set up network mapping you’ll need to set up logical networks on the VMM servers. In the self-service Azure Pack portal tenants set up virtual networks based on those logical VMM networks. When a tenant configures a virtual network a matching VM network is created in the VMM console. You then select and map these VM networks in the Azure Site Recovery portal using the network mapping feature.

 
Mostrar: