Data Interface Pairs - Overview
A Data Interface Pair (DIP) allows you to create an exclusive network route between two host computers, for faster data transfer. DIPs also reduce network traffic on the default network interface by routing the high-volume traffic required for backup through a different interface. (The "default network interface" is the interface specified during installation.)
A DIP requires that each host computer have a network interface name that was not used during software installation. A host computer can have multiple network interfaces when it has multiple Network Interface Cards (NICs). If you have more than one client with multiple interfaces, you can create data interface pairs using the CommCell Console. You do this from the Control Panel or the Job Configuration tab of the computer's Properties.
Sample Scenarios for Data Interface Pair Usage
The following diagrams illustrate a few sample scenarios in which data interface pairs can be used:
This diagram shows that the data can be conducted through the backup.com domain to reduce the network traffic on the production domains. To accomplish this goal, the following data interface pairs have to be defined:
- ma1.backup.com and client.backup.com
This interface pair can be used to conduct data over the backup domain. The default interface for the client is client.prod1.com, while the default network interface for MediaAgent1 is ma1.prod1.com.
- ma1.backup.com and ma2.backup.com
This interface pair can be used to conduct auxiliary copy operations over the backup.com domain. The default network interface for MediaAgent2 is ma2.prod2.com
This diagram shows the CommServe located in one geographic domain, while the Client and MediaAgent are located in a different geographic domain. In this situation, adding a third domain and defining the following interface pair between the Client and MediaAgent would result in efficient communication:
client.backup.com and ma.backup.com
This interface pair can be used to conduct data over the backup domain. The default network interface for the client is client.prod.com and the default network interface for the MediaAgent is ma.prod2.com
This diagram shows all the components in the same domain. Adding the following interface pair between Client2 and MediaAgent would result in better network communication:
ma2.prod.com and client2.prod.com
Sample Scenario for Default Interface Name Usage
By using the client1.backup.com and client2.backup.com as the default interface names for the clients, data transfer and communication with the CommServe will be performed on the backup.com domain. It is important for the clients to use interface names that are on the same domain as the CommServe and MediaAgent to enable faster communication.
Sample Scenario for CommServe Hostname Usage
This diagram shows that, although the CommServe is installed with cs.net1.com as its default network interface, Client2 and MediaAgent2 must use cs.net2.com as the CommServe hostname to avoid a possible network traffic on net1.com domain.