On Apr 1, 2011, at 10:37 AM, Morton, Jeffrey wrote:

> In the client properties for cfc-backup.unavco.org within the NMC, enter
> cfc.win.int.unavco.org within the Aliases section under the "Globals (1
> of 2)" tab.

Thanks for the info.  One question: Can you explain to me how/why that won't 
use the primary interface on the client?


> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Stu Duncan
> Sent: Friday, April 01, 2011 11:58 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Backup via second NIC on client?
> 
> 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
> 
> I've seen reference to a client attribute of server network interface,
> but can't find any documentation on it.
> 
> So how do I properly get the client software to connect to the backup
> server on the secondary NIC or backup name, which should be the same
> thing.
> 
> Thanks,
> 
> Stu Duncan
> Facility Systems Administrator
> UNAVCO, Inc.
> o: (303) 381-7473
> c: (970) 214-9276
> 
> 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
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
> 
> 
> NOTICE OF CONFIDENTIALITY: This message and any attachments contains 
> confidential information belonging to the sender intended only for the use of 
> the individual or entity named above. If you are not the intended recipient, 
> be advised that copying, disclosure or reliance upon the contents is strictly 
> prohibited. If you have received this message in error please notify the 
> sender immediately.
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> 
> 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
> 


Thanks,

Stu Duncan
Facility Systems Administrator
UNAVCO, Inc.
o: (303) 381-7473
c: (970) 214-9276

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