Networker

Re: [Networker] two clients with same name

2006-04-27 18:47:28
Subject: Re: [Networker] two clients with same name
From: Tim Nicholson <tim AT MAIL.USYD.EDU DOT AU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 28 Apr 2006 08:43:12 +1000
This was a big problem for us.  It stopped us using clients >7.1.
The server still worked (provided there was no client with the
unqualified hostname as the server).

Until 7.3, which fixed that problem, but introduced many more.

We do two things to avoid the problem.

1.  When adding a client to the server, ensure you only have
fully qualified names in the "aliases" attribute of the client
(echo -e 'show name;aliases\nprint type: NSR client' | nsradmin -i -)

2.  Ensure the client believes it is the fully qualified name.  This
can be a little tricky.  For Solaris and Linux the trick was to ensure
that in the /etc/hosts field, the fully qualified name was before the
short name on the line for its ip-address.  There is a way in windows
to do it, but I leave that to my windows experts.  If the client has got
this wrong, then you see that error about a misconfigured server.  To me
it is a misconfigured client!


On 28/04/2006, at 1:36 AM, Tim Mooney wrote:

In regard to: [Networker] two clients with same name, Jim Thorsley said (at...:

I have two clients with the same hostname on different subnets. They are 'mirror.admin.csd.uwo.ca' and 'mirror.syslab.csd.uwo.ca'. mirror.admin has been around for a long time and works fine. When I added mirror.syslab
I get this error on the next backup session:

mirror.admin.csd.uwo.ca:L:\ save: SYSTEM error: client `mirror' is not
properly configured on the Sun StorEdge(TM) Enterprise Backup Server

Neither entry in nwadmin has 'mirror' as an alias. They are both named with their full name. mirror.admin is a Windows XP box while mirror.syslab
is running Fedora Core 4.

Is this telling me I can't have two clients with the same hostname even
when they're on different subnets?

Yes, and this is something Legato broke in the 7.x series. They, however, view the new behavior as an enhancement. This was discussed a while back,
search the archives for more detail.

To get around it, use the "save -c full.client.name" in the "Backup
command" field for each of the clients that have short names that conflict
with other short names.

Tim
--
Tim Mooney mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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 wit 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
wit 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