02-25-2016 06:56 PM
Hi All,
We have two NIC's on client one for production and another one for backup.
We use backup interface for backup. but when I issued command bpclntcmd -pn on client host, It is pointing to production interface of client.
Master server is reachable to production interface of client not for backup interface.
I have asked SA Team to check DNS entries for both the NIC's and if routing is corrrect or not.
Asked them to clear host cache.
What are other troubleshooting steps which I can follow to resolve this issue.
Thanks in advance.
02-25-2016 07:58 PM
Try to ping client from master server through both IP's.If both are communicating u can do a entry with backup ip on hosts file of master server.If backup ip is not communicating please check with OS team to resolve it
02-25-2016 09:54 PM
02-25-2016 10:54 PM
Yes Marianne, Backup interface has different hostname than production.
Client host(backup interface) is not reachable from Master server and bpclntcmd -pn is resolving for production not for backup interface.
I think there should be problem with DNS entries.
Will post you the result once SA team checks it.
Thanks,
02-26-2016 12:07 AM
If Client and master cannot communicate on backup interface at TCP/IP level, then this is not a NetBackup issue.
Why is client -> master comms via public network a problem?
No backup data is flowing through this path.
The idea with a backup interface is for data transfer between client and media server.
If this working correctly, then this should not be a problem.
02-26-2016 06:22 AM
Hello,
In addition I would suggest to look at these 2 technotes
https://www.veritas.com/support/en_US/article.TECH171040
https://www.veritas.com/support/en_US/article.TECH54733
02-26-2016 08:38 AM
Can you not just add a route to the backup servers via their backup interface?
If you do a route print you will see the interface number for each NIC, right near the top of the list.
You can then delete the current route and add it back in like this example where the interface number is 12 .. then all traffic to that address range will go over that interface:
route add -p 10.123.123.22 mask 255.255.255.240 mask 10.1223.123.1 IF 12
Hope that helps