Networker

Re: [Networker] DNS lookups on virtual interfaces breaking backups

2008-05-14 16:37:54
Subject: Re: [Networker] DNS lookups on virtual interfaces breaking backups
From: Fazil Saiyed <Fazil.Saiyed AT ANIXTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 14 May 2008 15:33:31 -0500
Hello,
There is a better way, perhaps more then one, i don't have exact 
specifics, but by adding a route entry to TCP settings on 
solaris\linux\windows you should be able to tell where should the backup 
go ( which interface to talk to on the backup server).
Perhaps a firewall rule ?
Perhaps not depending on the DNS server for such an server may be 
better,you may be able to accomplish this by adding host entries and 
configuring networker client in certain way.
Last question, why do you need so many address on one server ?
HTH



Valdis Kletnieks <Valdis.Kletnieks AT VT DOT EDU> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
05/14/2008 03:02 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Valdis.Kletnieks AT VT DOT EDU


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: [Networker] DNS lookups on virtual interfaces breaking backups






On Wed, 14 May 2008 19:36:51 -0000, Thomas S Pinard said:
> I have a Solaris client that has 188 VIFs.  These VIFs are on a seperate
> network than the primary interface, but statically routed to the primary
> interface.
> 
> I recently moved this client from an old (5.1.103) Networker server to a
> newer (7.3.2) server.  Backups worked just fine on the old server, but 
are
> failing on the new one.  It appears to be failing because it is trying 
to
> nslookup all of the VIFs:
> 
> * my.client.net:All savefs: Reverse DNS lookup failed for
> address 1.2.3.1

The solution that worked for our 7.2 server was to add an entry on the 
*client*
in the /etc/hosts that looked like:

hostname-1-2-3-1.whatever.tld            1.2.3.1
hostname-1-2-3-2.whatever.tld 1.2.3.2

(one for each interface).  The name can be made up - all it cares is that
there *is* an entry in /etc/hosts for that IP address.

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



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