With virtual network mappings, you map protected site networks to networks on the recovery SDDC.

Virtual network mappings allow you to use separate networks on the recovery SDDC, so you can use one network for disaster recovery testing and ransomware recovery. Then, you can use one network for disaster recovery and another network for recovering production VMs.

Before you map virtual networks in a recovery plan, we strongly recommend that you add a custom VMware Cloud Gateway to the recovery SDDC on the recovery SDDC, and then create different network segments on each gateway. Creating separate gateways ensures that your recovery, testing, and ransomware operations do not interfere with production workloads you might be running on the recovery SDDC.
Note: Individual network segment names within a gateway must be unique.

If running a ransomware recovery plan, make sure that the recovery network has internet access to connect to Carbon Black Cloud. For more information, see Network Isolation Levels.

Failover Mappings Tab for Disaster Recovery and Recovering Clean VMs to Recovery SDDC

For disaster recovery operations, and for recovering cleansed VMs to the recovery SDDC, use the Failover mappings tab.

In this example, the plan is configured for Failover mapping with Gateway A selected.

Recovery plan with Gateway A being used for regular failover.

Network segments mapping to unique network segment on Gateway A.

Test Mappings Tab for Ransomware and Test Recovery Operations

For ransomware recovery and for failover testing, use the Test mapping tab

In this example, the plan is configured for Test mappings using Gateway B.
Note: By default, networks not in the selected Gateway are hidden from view. You can choose to show all other network segments, but they are not selectable.

Recovery plan with Gateway B chosen for failover test and for ransomware recovery.

Networks segments mapping to unique network segment on Gateway B.