Product Documentation

Adding a network group

Using Resiliency Platform console, you can add network group for a data center. Unlike the subnets, port groups or VLANs, vSwitches, network groups cannot be discovered and can only be added. You can create network groups using subnets and port group / VLAN.

You have to first set the purpose of the subnet to Production and then add the subnet to the network group. You cannot add the purpose directly to the network group.

Similarly, for port group/VLAN, set the purpose to Production and then add the port group/VLAN to the network group.

After adding network groups, you can pair them across the data centers like other individual network objects. If you have created and paired network groups across data center, and you perform a disaster recovery operation, the virtual machines are mapped to the required subnets, port groups or VLANs, vSwitches, or cloud networks in the target data center.

For rehearsal operations, within a same data center you can map the subnets or port groups which are part of a network group with other subnets or port groups whose purpose is set as Rehearsal.

If your target data center is AWS, then ensure that the production subnet and the rehearsal subnet are in the same virtual private cloud (VPC).

Creating network groups using subnets and using them for pairing the network objects across data centers is enabled only if your target data center is Amazon Web Services (AWS) cloud.

From version 3.2 onwards, you can now create network group using port group/VLAN. This network group is specific to VMware environment in source data center or target data center or VMware environment in both data centers. The port group/VLANs which belong to this network group must be from same cluster and must have same VLAN ID. Similar to network group of subnets, the purpose of this network group should be Production.