Netbackup 5, how do you direct traffict to backup network ?

[dandan123]

I'm a Solaris admin trying to help our Netbackup admin troubleshoot network congestion problems.

All our servers have two nics, one for production and one for backup. Till recently the backups were being run over the production network but when it showed signs of choking we started looking at moving the backup traffic to the backup network.

We named the backup nics hostname-bkup on all the hosts and made appropriate dns entries. The production nics are on the 10.xxx.xxx.xxx network while the backup nics are on the 192.168.xxx.xxx network.

On all the clients we added the REQUIRED_INTERFACE = hostname-bkup line.

But the production network still seems to be choking.

We are backing a mix of Solaris and Windows clients.

Any suggestions ?

 

[cdpwin12]

Did the client names in NetBackup get changed to clientname-bkup?

 

[dandan123]

No the client names have not been changed as this would affect restores ?

 

[jdespres]

Does the Master have a 192.x.x.x address?

If so I would edit the hosts file on the clients to point at that..

192.x.x.x Master

Check and verify by running traceroute on the client. Checking of course that it's going out the 192 nic on the client!

bplclntcmd -pn is also handy way of checking...

Joe Despres

 

[RustyMajor]

Change your client names within netbackup to have the -bkup appended to the name. This is both in the policy and in the bp.conf/backup archive restore gui. This may effect restores, but only until the older backups without the -bkup in the name.

NetBackup is very DNS dependant, if you haven't found that out yet.