Networker

Re: [Networker] Backup via second NIC on client?

2011-04-01 18:25:12
Subject: Re: [Networker] Backup via second NIC on client?
From: "Albert, Eddie - JACKSONVIL FL" <eddie.albert AT BANKOFAMERICA DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 1 Apr 2011 18:23:06 -0400
I use this same setup 99% of the time anywhere I consult... Create your
backup server with multiple nics as well one on Public Highway one on
Alternate Highway (for backup).. Create Serial interface on backup
highway only. Define the client name with the NIC that is on
ALThighway... viola zoom-zoom...

Your backup server?

Do you have multiple NICs (6?) trunked together to give you an aggregate
of say 6GB over the ALThighway...? This works and is an awesome setup.

Semper fidelis, /ALE

-----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 message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments, and be advised that any review or dissemination of, or the taking 
of any action in reliance on, the information contained in or attached to this 
message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a 
solicitation of any investment products or other financial product or service, 
an official confirmation of any transaction, or an official statement of 
Sender. Subject to applicable law, Sender may intercept, monitor, review and 
retain e-communications (EC) traveling through its networks/systems and may 
produce any such EC to regulators, law enforcement, in litigation and as 
required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, 
and EC may be archived, supervised and produced in countries other than the 
country in which you are located. This message cannot be guaranteed to be 
secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this EC may have additional 
important disclosures and disclaimers, which you should read. This message is 
subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
consent to the foregoing.

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