---
title: "Step 7. Configure Network Mapping"
description: "When you recover a VM from a Hyper-V backup, the recovered VM is connected to the same Hyper-V networks as the source VM; if the same networks are not available in the recovery location, you can create a network mapping table for the location so..."
canonical: "https://helpcenter.veeam.com/docs/vro/userguide/hyperv_location_network_mapping.html"
breadcrumb: "User Guide > Configuring Veeam Recovery Orchestrator > Managing Recovery Locations > Adding Recovery Locations > Adding Microsoft Hyper-V Recovery Locations > Step 7. Configure Network Mapping"
dateModified: "2026-08-26"
---

# Step 7. Configure Network Mapping

When you recover a VM from a Hyper-V backup, the recovered VM is connected to the same Hyper-V networks as the source VM; if the same networks are not available in the recovery location, you can create a network mapping table for the location so that the recovered VM is connected to the correct network. However, when you recover a VM from a vSphere backup, there are no Hyper-V networks that can be used. Therefore, to recover a vSphere VM, you must create at least one network mapping rule so that the recovered VM is connected to the correct network.

To configure network mapping, at the **Network Mapping** step of the wizard, click **Add** > **VMware Mapping** to recover VMs from vSphere backups or **Add** > **Hyper-V Mapping** to recover VMs from Hyper-V backups. Then, do the following in the **Add Network Mapping Rule** window:

 1. Depending on whether you plan to recover machines from vSphere or Hyper-V backups, do the following in the **Source network** section:

    -   To recover VMs from vSphere backups, select a vCenter Server that manages source VMs, a network to which the source VMs are connected, and a datacenter or a cluster where the source VMs reside.

        For a vCenter Server to be displayed in the **vCenter Server** list, it must be connected to Orchestrator as described in section [Connecting VMware vSphere Servers](connecting_vsphere_servers.md).

        ::: note

        Orchestrator supports IP addresses in the IPv4 format only. If a machine that you want to recover has a single IPv6 address, you must create a mapping rule *0.0.0.0/0* (this will map all networks). Otherwise, Orchestrator may halt the recovery process.

        :::

    -   To recover machines from Hyper-V backups, select either an SCVMM server that manages source VMs and a cluster where these VMs reside (in case the necessary cluster is part of the SCVMM fabric), or a standalone cluster or host (in case of a direct connection) — and also choose a network to which the source VMs are connected.

        For an SCVMM server, cluster or host to be displayed in the list of available Microsoft Hyper-V servers, it must be connected to Orchestrator as described in section [Connecting Microsoft Hyper-V Servers](connecting_scvmm_servers.md).

 2. In the **Target Hyper-V network** section, select a network to which the recovered VMs will be connected. 

    For a network to be displayed in the **Network** list, it must be configured on all the hosts of the cluster selected at [step 5](hyperv_location_server.md) of the wizard. For more information on how to configure network for Hyper-V hosts, see [Microsoft Docs](https://learn.microsoft.com/en-us/system-center/vmm/hyper-v-network?view=sc-vmm-2025).

::: tip

If you have only one target network, you can select the **Match any source network** check box to instruct Orchestrator to connect all the recovered VMs to the same target network.

:::

[![Adding Recovery Location](images/add_hyperv_location_network_mapping.png "Adding Recovery Location")](images/add_hyperv_location_network_mapping.png){.toggle scale=65}