PowerProtect Data Manager can separate management and backup traffic onto different virtual networks (VLANs). Virtual networks help to improve data traffic routing, security, and organization.
The default configuration routes the management traffic over the same network as backup traffic. All assets are part of the same network.
Figure 1. Flat network
You can also configure virtual networks to separate management traffic from backup traffic. This configuration can also separate traffic that originates from different networks. In that case, you can use the same virtual network for management and backup traffic, or separate virtual networks for each.
Figure 2. Virtual networks
To use virtual networks with
PowerProtect Data Manager, you must configure the
DD and network infrastructure before you configure the
PowerProtect Data Manager or assign networks to assets.
Configuration follows a multistep workflow:
Configure the virtual network on the
DD.
Add the
DD as storage and name the network interface.
Add the virtual network to the
PowerProtect Data Manager.
Register the assets with the
PowerProtect Data Manager.
Create a protection policy (or edit an existing policy) and assign the preferred virtual network.
Optionally, assign the virtual network to individual assets. This action overrides any preferred virtual network that you may have specified through a protection policy.
The initial steps to configure and add each virtual network are one-time events. The subsequent steps to assign virtual networks to protection policies or assets happen as required.
Configuration is nondisruptive. You can add, edit, or delete virtual networks without affecting background activities, disconnecting network interfaces, or affecting the
PowerProtect Data Manager user interface.
PowerProtect Data Manager logs network changes in the audit log. Failed network changes appear in the
System alerts.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\