In regard to: [Networker] Backup via second NIC on client?, Stu Duncan said...:

I'm trying to get my clients to back up on their second NIC.  However,
they seem to respond with DNS on their first NIC and thus the backup
server won't recognize them.

Primary NIC: 10.234.1.220, cfc.win.int.unavco.org (via DNS)
Secondary NIC: 10.255.1.220 cfc-backup.unavco.org (via hosts file)

Networker server: 10.255.1.5 networker.unavco.org

I can't see any way to get the client to use the secondary NIC/backup
name.  Both the client & server can see each other (on the 10.255
network), but when I go to back it up, or request backup on client I get
this:

39078:winworkr: SYSTEM error: client `cfc.win.int.unavco.org' is not properly 
configured on the NetWorker Server
or `cfc.win.int.unavco.org'(if not a virtual host) is not in the aliases list 
for client `cfc-backup.unavco.org'

The client does think it's named cfc.win.int.unavco.org.
Should I put an alias in the hosts file like this:

10.255.1.220 cfc-backup.unavco.org cfc.win.int

No, you only need to add cfc.win.int.unavco.org to the "Aliases" field
for the client within NetWorker.  If you're using the GUI, it's in the
"Globals (1 of 2)" tab of the client properties.

Tim

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER