Data Interface Pairs: Overview

A Data Interface Pair (DIP) defines an exclusive network route between two host computers. You can use DIPs to improve performance by routing high-volume backup traffic through a network interface different from the default interface (the one specified during installation).

Clients belonging to a client group can have an interface pair defined to another client, such as a MediaAgent, by defining a DIP from the group to that MediaAgent. This can save you time and effort if a group of logically related clients all use the same MediaAgent.

A DIP requires that both host computers in the pair have a network interface name that was not used during the software installation process. 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 from the Job Configuration tab of the computer's Properties dialog box.

Sample Scenarios for Data Interface Pair Usage

This section presents examples of data interface pair use.

Scenario 1

In this case, data traffic can be conducted through the backup.com domain to reduce the network traffic on the production domains. These data interface pairs are required for it:

  • ma1.backup.com and client.backup.com

    This interface pair is for transmitting data through the backup.com domain. The default interface for the client is client.prod1.com, and for MediaAgent1 it 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

Scenario 2

This diagram shows the CommServe computer located in a different city from where the Client and MediaAgent computers are located. In this case, communication can be made more efficient by adding a third domain (backup.com), and defining an interface pair between the Client (client.backup.com) and the MediaAgent (ma.backup.com).

The default network interface for the client is client.prod.com. The default network interface for the MediaAgent is ma.prod2.com

Scenario 3

This diagram shows all the components in the same domain. Adding an interface pair between Client2 and MediaAgent1 (ma2.prod.com and client2.prod.com) results in more efficient network communication.

Sample Scenario for Default Interface Name Usage

This diagram shows all client computers in the production domain ( prod.com), and the MediaAgent and CommServe computers attached to the backup.com domain.

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 can be performed through the backup.com domain. Communication is more efficient when the clients use interface names that are on the same domain as the CommServe and MediaAgent computers.

Sample Scenario for CommServe Hostname Usage

In this case, the CommServe is installed with cs.net1.com as its default network interface, but Client2 and MediaAgent2 use cs.net2.com to reach the CommServe host, to keep their data traffic off of the net1.com domain.