SALES: 1-800-867-1380

Step 4: Configure network mapping: On-premises to on-premises

Updated: July 18, 2014

After configuring protection settings for Virtual Machine Manager (VMM) clouds, you can map VM networks on source servers to VM networks on target servers. Network mapping ensures the following:

  • Replica virtual machines are connected to appropriate networks after failover.

  • Replica virtual machines are optimally placed on Hyper-V host servers. Replica virtual machines will be placed on hosts that can access the mapped VM networks.

In order to set up network mapping, do the following:

  1. Configure networks in VMM—Configure VM networks properly before you start network mapping. For more information, see Step 3: Prepare for network mapping in the Planning Guide.

  2. Learn about network mapping—Read the Network mapping below, and look through the examples to make sure you understand how the network mapping mechanism works.

    To understand how VM network settings influence how replica virtual machines will be connected failover, read the section “Connection settings after failover” in the Administer and Monitor Azure Site Recovery.

  3. Configure network mapping—After you have VM networks set up in VMM perform the steps in Configure network mapping. We recommend that you configure network mapping before you enable protection so that network mapping can be used during placement of replica virtual machines. If you do it afterwards you might need to migrate some replica virtual machines to more suitable Hyper-V hosts.

Network mapping can be configured between VM networks on two VMM servers, or on a single VMM server if two sites are managed by the same server. When mapping is configured correctly and replication is enabled, a virtual machine at the primary location will be connected to a network, and its replica at the target location will be connected to its mapped network. Mapping is illustrated in the following table.

Mapping is illustrated in the following table.

 

Location VMM server VM Networks Mapped to

New York

VMM-NewYork

VMNetwork1-NewYork

Mapped to VMNetwork1-Chicago.

VMNetwork2-NewYork

Not mapped to any network

Chicago

VMM-Chicago

VMNetwork1-Chicago

Mapped to VMNetwork1-NewYork.

VMNetwork2-Chicago

Not mapped to any network

Using the settings in the table, when a replica virtual machine is created for any virtual machine that is connected to VMNetwork1-NewYork, it will be connected to VMNetwork1-Chicago. When a replica virtual machine is created for VMNetwork2-NewYork or VMNetwork2-Chicago, it will not be connected to any network.

Note that if the target network has multiple subnets and one of those subnets has the same name as subnet on which the source virtual machine is located, then the replica virtual machine will be connected to that target subnet after failover. If there’s no target subnet with a matching name, the virtual machine will be connected to the first subnet in the network. 

If networks have been set up correctly in VMM, when you select a target VM network during network mapping, the VMM source clouds that use the source VM network will be displayed, along with the available target VM networks on the target clouds that are used for protection. Here’s an example to illustrate this mechanism. Let’s take an organization with two locations in New York and Chicago, and define the settings for cloud protection, logical and VM networks, and network availability for clouds. Based on these settings, let’s see the choices that will be available when you set up network mapping for Hyper-V Recovery Manager.

The following tables show how VMM clouds and networks are set up in our example organization.

Cloud protection settings

Protected cloud Protecting cloud New York logical network associated with cloud VM network associated with logical network

GoldCloud1

GoldCloud2

SilverCloud1

SilverCloud2

GoldCloud2

NA

LogicalNetwork1-NewYork

LogicalNetwork1-Chicago

SilverCloud2

NA

LogicalNetwork1-NewYork

LogicalNetwork1-Chicage

Logical and VM network settings

Location Logical network Associated VM network

New York

LogicalNetwork1-New York

VMNetwork1-NewYork

Chicago

LogicalNetwork1-Chicago

VMNetwork1-Chicago

LogicalNetwork2-Chicago

VMNetwork2-Chicago

Cloud and logical network settings

Logical network Cloud

LogicalNetwork1-NewYork

GoldCloud2

SilverCloud2

LogicalNetwork1-Chicago

GoldCloud2

SilverCloud2

LogicalNetwork2-Chicago

GoldCloud2

Based on these settings, when you select the target VM network, the following table shows the choices that will be available.

 

Selection Source cloud Protecting cloud Availability of target VM network

Select VMNetwork1-Chicago

SilverCloud1

SilverCloud2

Available

GoldCloud1

GoldCloud2

Available

Select VMNetwork2-Chicago

SilverCloud1

SilverCloud2

Not available

GoldCloud1

GoldCloud2

Available

To see what happens in the case of failback (reverse replication), let’s assume the following:

VMNetwork1-NewYork is mapped to VMNetwork1-Chicago, with the following settings.

 

Virtual machine Connected to VM network

VM-1

VMNetwork1-NewYork

VM-2 (replica of VM1)

VMNetwork1-Chicago

With these settings, let’s review what happens in a couple of scenarios.

 

Scenario  

No change in the network properties of VM-2 after failover.

VM-1 remains connected to the source network.

Network properties of VM-2 are changed after failover and is disconnected.

VM-1 is disconnected

Network properties of VM-2 are changed after failover and is connected to VMNetwork2-Chicago.

If VMNetwork2-Chicago isn’t mapped, VM-1 will be disconnected.

If VMNetwork2-Chicago is mapped, say to VMNetwork2-NewYork, VM-1 will be connected to VMNetwork2-NewYork.

Network mapping of VMNetwork1-Chicago is changed.

VM-1 will be connected to the network now mapped to VMNetwork1-Chicago.

  1. On the Quick Start page, click Map networks.

  2. Select the source VMM server from which you want to map networks, and then the target VMM server to which the networks will be mapped. The list of source networks and their associated target networks are displayed. A blank value is shown for networks that are not currently mapped. Click the information icon next to the source and target network names to view the subnets for each network.

  3. Select a network in Network on source, and then click Map. The service detects the VM networks on the target server and displays them.

    Networks
  4. In the dialog box that is displayed, select one of the VM networks from the target VMM server.

    Target Network
  5. When you select a target network, the protected clouds that use the source network are displayed. Available target networks that are associated with the clouds used for protection are also displayed. We recommend that you select a target network that is available to all the clouds you are using for protection.

  6. Click the check mark to complete the mapping process. A job starts to track the mapping progress. You can view it on the Jobs tab.

See Also

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