Defining a Dedicated Backup Network with Commvault
Our recent posts regarding Data Listening, Implementation, and Operationalization have certainly made clear the importance of data to an organization. Data collected and utilized correctly can improve your customer journey and keep you a step ahead of your competitors. Your data is a critical resource to the success of your organization.
On the other end of this equation is protecting your data in the case of a disaster, or the occasional file restore. This is a critical part of your data management system and could cost you heavily should your backup system not be complete. However, producing the extra load on your network for backup purposes can cause delays in accessing real-time production data. In order to maximize your production network utilization, it is possible to offload backups to a separate backup network. This can easily be done within Commvault.
The first step is obviously to ensure that your clients and media agents are on the backup network. If possible, a separate network with a separate network adapter is recommended. Test connectivity with some ping tests before proceeding. It is also recommended to add a DNS entry to these backup interfaces, such as hostname-b to specify that it is a backup interface. That way, if a backup network needs to change, such as for a migration or a server replacement, a simple DNS entry change is all that is needed.
The 2nd step is to tell Commvault on what IP interfaces you wish for them to communicate with each other. This is done by creating a data interface pair.
To define a data interface pair for a client, follow these steps.
Navigate to the server in the CommServe browser.
Right click the server and select Properties.
From the General Tab, click the Advanced button.
Select the Job Configuration tab.
At the bottom of the screen, click Add to add a new interface pair.
In the Add Data Interface Pair Wizard, select the target machine, such as the media agent, that you wish to create the pair with.
Click Add again to tell Commvault which IP interfaces you wish for the two servers to communicate with. Using hostname is preferred here, since if there is an IP change, you only need to update the server and DNS entry and not every client in the CommVault environment.
Click Next, and then Next again. Verify that all of the data on this screen is accurate before clicking on Finish
At this point, you have created a Data Interface Pair. When this server needs to communicate with the remote server defined, it will use the IP interfaces defined. If there are multiple media agents that the server can use for its backups, you can create multiple data interface pairs for the server. Repeat this process for each server that you wish to use the backup network.
At this point, future backup jobs will then be executed over the backup network and not the production network, freeing up resources for your users to access production data.