Step 11. Configure Network Mapping

When you recover a machine from a Veeam agent backup or a VM from a vSphere backup to a cloud environment, Orchestrator is not able to connect the recovered VM to the same networks as the source machine — that is why you must create at least one network mapping rule for the location 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. The Add Network Mapping Rule window will open.

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

• To recover machines from Veeam agent backups, specify a range of IP addresses that contains the IP addresses of the source agent machines. Alternatively, create a separate network mapping rule to map each individual IP address.
• To recover VMs from vSphere backups, from the vCenter Server list, select a vCenter Server that manages source VMs. Then, from the list of available networks, select a network to which the source VMs are connected.

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.

2. In the Target network section, select a virtual network and a subnet to which you want to connect the recovered VMs. For a virtual network to be displayed in the Cloud network list, it must be created in the Microsoft Azure portal for the region selected at step 8, as described in Microsoft Docs. For a subnet to be displayed in the Subnets list, it must be created in the Microsoft Azure portal for the specified virtual network, as described in Microsoft Docs.

You can also specify a security group (virtual firewall) that will be associated with the recovered VMs. For a network security group to be displayed in the Security Groups list, it must be created and associated to the necessary subnet in the Microsoft Azure portal as described in Microsoft Docs.