02-13-2017 08:32 AM - edited 02-13-2017 08:38 AM
02-13-2017 11:42 PM
For evening to work master must be able to talk with both client and media servers.
You don't need to configure VLAN if master server can reach client via its default interface.
All interfaces must have separate DNS names.
I am not aware of any documentation about Netbackup and multihomed installations.
02-14-2017 10:16 AM - edited 02-14-2017 10:17 AM
02-14-2017 10:24 AM
NetBackup is very sensitive to names and addresses. For example, if your client is system-backup and it connects back as system, NetBackup will have issues.
I have had issues with Linux and multi-nic where I had to specifically configure the system to respond via the NIC that was addressed. You may find you have issues having the master communicate via prod network and data coming over backup network.
Also, NetBackup does a tremendous amount of logging, and you may need to allow a path to send to the master with verbose logging turned on. I know I have seen a positive impact even on getting faster disks to log on, even at minimal logging. Not sure what impact the network would have.
Simpler will generally be better.
02-14-2017 10:26 AM
Having said that, I can confirm the using the hosts file will work.
I have done DR where I took DRmaster and confgured all the clients to point master to DRmaster, and "faked" out netbackup to use the DRmaster as the master server -- of course this was a while ago, not sure if it will work with new security in place.
02-15-2017 11:58 PM
Can't recommend host files. Going large scale it will be a nightmare (been there, done that).