How to configure NB to use a backup network connection?

[Wayne_Maranduik]

Hi,

I am setting up a seperate backup network connection from my Master Server to my other physical servers through a seperate switch just for running backups...how do I tell NetBackup to utilize the backup network and not use the data network on the other NIC?

Backup Network NIC#2 ip address 10.54.249.0/24

Data Network NIC#1 ip address 10.54.1.0/24

Thanks

[Dyneshia]

This is specific to Exchange http://www.symantec.com/docs/TECH49883  but the principal are the same.

Normally, you would setup a backup network that is not routable and is dedicated to backups. If you have a DNS, use it. You need a NIC dedicated to the backup network. Use your hostname/servername and add a suffix to identify it. eg. Your server name is server1. Your backup network name is server1-bn or some suffix you prefer. If DNS not available, use your host files with same configuration. Your Netbackup client names will be hostname-nb with the IP for that network/NIC. Your master neeeds to be configured with hstname-nb or you can specify to use a specific NIC or use a route for your backup network so master and media servers use that network only. I have used it in previous jobs and it worked great.

[Dyneshia · Accepted solution]

Here is a great forumn

https://www-secure.symantec.com/connect/forums/dedicated-backup-lan-configurations

Yes, you first of all need to config backup network at OS level.

Each backup interface will need a new hostname associated with the IP address. e.g.

# Public network
192.168.10.1  master
192.168.10.2  media1
192.168.10.3  client1
192.168.10.4  client2

# Backup network
10.10.10.1 master-bk
10.10.10.2 media-bk
10.10.10.3 client1-bk
10.10.10.4 client2-bk

Update hosts entries on all servers and clients.
Add bp.conf to add SERVER entries for -bk servers on all server and clients. 
If master server was installed with Public network address, you need to keep that name as 1st entry.

Change CLIENT_NAME in bp.conf on all clients to -bk name.

If you have already done backups for clients with Public Network hostnames, before you change all policies to -bk client names, create symbolic links in image folder to -bk names. e.g:
# cd /usr/openv/netbackup/db/images
# ln -s client1 client1-db
This will ensure that images are stored in same folder and that restores will work using both names.

See these sections in NBU Troubleshooting Guide for detailed info:

Example of host name and service entries on UNIX clients in multiple networks

Example of host name and service entries on UNIX server that connects to multiple networks

Please ignore all references to 'service entries' as this is no longer used in NBU 7.x and should have been removed from the manual...

More reading matter: 

DOCUMENTATION: How network interfaces are selected in NetBackup 6.x/7.x when there are multiple NICs on a NetBackup host. 
http://www.symantec.com/docs/TECH54733

How to verify name resolution for Veritas NetBackup (tm) systems, using the "bpclntcmd" command
http://www.symantec.com/docs/TECH27430
 
DOCUMENTATION: When and how to clear the NetBackup host cache
http://www.symantec.com/docs/TECH136792