Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.12 Administration and User Guide

PDF

Virtual network planning

When you plan your virtual network configuration, observe the following requirements:

Table 1. Component traffic type requirementsComponent traffic type requirements
Component Compatible types Incompatible types
PowerProtect Data Manager Management, Data for Management Components Data
Protection engines Data for Management Components, Data Management
Search Engine nodes Data for Management Components Management, Data

While the table indicates compatible traffic types, protection engines can operate without virtual networks.

Separating the Data for Management Components traffic from the Management traffic requires you to name the virtual networks for protection storage. Change network settings for protection storage provides instructions. If you do not name the virtual networks for protection storage, this traffic defaults to the Management network.

Parallel virtual networks

Your environment may have more than one virtual network for each traffic type, such as different Data networks for different departments. Where parallel virtual networks exist, all protection engines require an interface to at least one virtual network of each required type. However, each protection engine does not require connections to all virtual networks of the required types.

For example:

  • Your environment has Finance and Engineering departments with their own assets.
  • Your environment has the following virtual networks: Management, Finance Data, and Engineering Data.

The following table describes the connections to each virtual network for scenarios where both departments share a protection engine and where departments have private protection engines.

Table 2. Example: virtual network interfacesExample: virtual network interfaces
Virtual network name Shared protection engine Private protection engines
Finance protection engine Engineering protection engine
Management Yes Yes Yes
Finance Data Yes Yes No
Engineering Data Yes No Yes

Even though protection engines require connections for Data traffic, the private protection engines maintain separation between the virtual networks for each department.

Several of the diagrams for supported virtual network topologies include parallel virtual networks.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  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: <>()\