Network pairs for recovering machines to on-premises data center (For NetBackup, third-party replication or Resiliency Platform Data Mover)
This topic mentions about the network pairs for recovering VMware or Hyper-V virtual machines to on-premises data centers if you are using NetBackup, third-party replication technologies or Resiliency Platform Data Mover.
You can map the networks in the source data center with networks in the DR data center. The Resiliency Platform uses this information to create appropriate VNICs in the recovered virtual machine and connect them to the appropriate networks according to the mappings.
Network pairs for VMware environment:
If on-premises data center is VMware, you can also create network group using port group/VLAN for VMware environment. When you pair network groups and perform a disaster recovery operation, virtual machines connected to different port groups can be migrated to same network on target data center.
For NSX-T type networks: Create NSX-T VLAN/Port Group to any of the standard, distributed, NSX -T type network or network group pair.
VMware vLAN/Port Group to vLAN/Port Group
With clustered ESX servers:
Distributed vLAN: Create vLAN/Port Group to vLAN/Port Group pair
Standard vLAN:
For each ESX standard vLAN, create vLAN/Port Group to vLAN/Port group pair
Create network group of vLAN/Port Group and create vLAN/Port Group network group to vLAN/Port Group network group pair
Without Cluster ESX servers: Create vLAN/Port Group to vLAN/Port Group pair
Subnet to Subnet (Optional, if no IP customization is done)
Network pairs for Hyper-V environment:
Hyper-V vSwitch to vSwitch
Hyper-V vLAN to vLAN (Optional)
Subnet to Subnet (Optional, if no IP customization is done)
To create network pairs, refer to the following topic
Creating network pairs between source and target data centers
Table: Network Mapping types for on-premise datacenters
Virtualization Technology | Network Mapping Type | Mandatory? | Purpose |
|---|---|---|---|
VMware | vLAN to vLAN | Yes | To connect the VNIC of the recovered virtual machine to the Port Group |
HyperV | vSwitch to vSwitch | Yes | To connect the VNIC of the recovered virtual machine to the Port Group |
HyperV | vLAN to vLAN | Optional | To connect the VNIC of the recovered virtual machine to the Port Group |
In addition, if IP customization of the virtual machines is required, following mapping is also required to be defined:
Table: IP customization of the virtual machines
Virtualization Technology | Network Mapping Type | Mandatory | Purpose |
|---|---|---|---|
VMware/HyperV | Subnet to Subnet | Yes | If IP customization is required |
If network mappings are not defined as per above table, the Resiliency Platform is unable to set the correct network configuration for the virtual machines after recovery. Following table identifies the effect of mappings on recovered virtual machines :
Table: Effect of mapping on recovered virtual machines
NIC configuration in source datacenter | Mapping done for NIC's vLAN/vSwitch | Mapping done for NIC's Subnet? | NIC status after recovery to remote datacenter | |
|---|---|---|---|---|
Connectivity status | IP status | |||
Connected with IP address | Yes | Yes | NIC is created with same MAC address and is connected to the vLAN/vSwitch | New IP address is plumbed |
Connected with IP address | Yes | No | NIC is created with same MAC address and is connected to the vLAN/vSwitch | IP configuration is untouched |
Connected with IP address | No | * | NIC is created with same MAC address and is disconnected from vLAN/vSwitch | IP configuration is untouched |
Disconnected | * | * | NIC is not created | N/A |
* denotes that mapping may be defined or not defined