This was a client that was being migrated from another backup solution
(Harbor), so I stopped that backup client software on one of the 3 clients that
was having this problem. FYI, this service hasn't been a problem on several
other clients that I've migrated.
I think I might look into using the hostname and then adding aliases. That
would be a pain to change the current 120 clients.
Brings up something I'd like to check with the list on...
What is the preferred naming convention that you all use when adding clients?
Create a new domain? Use hostname? Other?
We use the FQDN for all clients.
Thanks,
Joel
-----Original Message-----
From: Carston Locher [mailto:clocher AT LEGATO DOT COM]
Sent: Thursday, March 06, 2003 5:02 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] SUMMARY...Kinda [Networker] aliases not working
Joel,
I agree with the individual that recommended using the hostname for
the client name and then putting all other potential names in the
aliases field.
Just remember if you do rename the client you will probably have to
fix the index location as NetWorker stores the client index in
/nsr/index/<clientname>. If you need help in doing this I'd open
a case with Tech Support on how to do it.
NetWorker simply does a gethostbyname() and gethostbyaddr(). It uses
whatever the return value is to communicate with.
What service did you stop? Was that box a NetWorker client or the
NetWorker server?
Thanks,
Carston
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Joel Fisher
Sent: Thursday, March 06, 2003 1:48 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] SUMMARY...Kinda [Networker] aliases not working
Well, I'd like to say I figured out what the problem was. But it just went
way.
The main suggestions were to check DNS... as I noted in the original query I
had already triple checked them, because I know this is typically the
problem.
I came in this morning and ran the test group containing the clients I was
having problems with and they failed... a few _minutes_ later I ran the same
group and they succeeded. I didn't change anything in DNS or within Legato.
Only thing I did do was stop a service(not networker) on one of the servers
just to rule that out... and magically it worked. Stopping one service on
one machine "fixed" a problem on 3 completely unrelated machines. Yeah
Right!!!
Man this really sounds like a stupid user(admin) induced problem... I
wouldn't believe me either.
I was just hoping someone had seen the problem before... maybe I'll head
down to the nearest psych ward.
Thanks for the responses...
Joel
-----Original Message-----
From: Matts Nilsson [mailto:matts_nilsson AT yahoo DOT com]
Sent: Thursday, March 06, 2003 4:24 PM
To: Legato NetWorker discussion; Joel Fisher
Subject: Re: [Networker] aliases not working
Joel,
I'd guess You have a different DNS name compared to
the FQDN on Your W2k client. It seems Your DNS name is
clienta.wfubmc.edu. Still You define the client as
clienta.nt.wfubmc.edu in NetWorker. We usually define
all clients using their short name, especially NT/W2k
clients, mainly to avoid problems when moving clients
from one domain to another.
In Your case we would have the following names in the
Alias field:
clienta
clienta.wfubmc.edu
clienta.nt.wfubmc.edu
>From what I understand from Your original posting, You
have these names listed under Aliases. I still believe
there's a name resolution problem. Check Your Network
ID on the client. Also check if there are any hosts
files messing things up. Do a ping using the short
name, then do a ping -a on the returned address. This
should return the actual FQDN, which can differ from
the DNS name.
HTH!
// Matts
--- Joel Fisher <jfisher AT WFUBMC DOT EDU> skrev: > Hey
Robert,
>
> That(extra characters) is what I figured was
> happening also. But I
> don't see anything via nsradmin or in the nsr.res
> file. I was hoping
> someone had run into this before. Thanks for the
> guess though.
>
> Joel
>
> -----Original Message-----
> From: Robert Maiello
> [mailto:robert.maiello AT MEDEC DOT COM]
> Sent: Wednesday, March 05, 2003 4:49 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU; Joel Fisher
> Subject: Re: aliases not working
>
> I'll take a guess..
> Perhaps there's are some extra control characters or
> something in your
> alias list?? I'm not familar with windows but
> perhaps look at the
> entries via nsradmin or the nsr.res file on the
> server.
>
> If that's not it, then perhaps the dns or reverse
> lookups are failing at
> the
> time of the backup for some reason?
>
> Robert Maiello
> Thomson Healthcare
>
>
> On Wed, 5 Mar 2003 11:40:29 -0500, Joel Fisher
> <jfisher AT WFUBMC DOT EDU>
> wrote:
>
> >Hey All,
> >
> >
> >
> >Since upgrading to 6.1.2, I occasionally run in to
> the below problem.
> >
> >
> >
> >I'll create a client named clienta.nt.wfubmc.edu
> but get the below
> >error.
> >
> >
> >
> >* clienta.wfubmc.edu:C: 1 retry attempted
> >
> >* clienta.wfubmc.edu:C: save: SYSTEM error:
> `clienta.wfubmc.edu' is not
> >a registered client
> >
> >* clienta.wfubmc.edu:C: save: Cannot open save
> session with
> backupserver
> >
> >
> >
> >No big deal right... either change the client DNS
> suffix, or add
> >clienta.wfubmc.edu to aliases field of
> clienta.nt.wfubmc.edu. In some
> >cases it doesn't help to do either. After some
> fiddling with the alias
> >field sometimes it'll eventually work, but it seems
> a little silly to
> >have to delete and reenter that same alias 3 or
> more times before it
> >works correctly. BTW I typically use the W2K Admin
> GUI to manage my
> >server which resides on Solaris 2.6. My thinking
> was that the W2K GUI
> >was adding or leaving out some hidden characters,
> so I tried to use
> both
> >nsradmin and nwadmin on my SUN box to create these
> clients with the
> same
> >results.
> >
> >
> >
> >I have one client that is named
> clientb.nt.wfubmc.edu. But I still get
> >the below error:
> >
> >
> >
> >* clientb.nt.wfubmc.edu:C: 1 retry attempted
> >
> >* clientb.nt.wfubmc.edu:C: save: SYSTEM error:
> `clientb.nt.wfubmc.edu'
> >is not a registered client
> >
> >* clientb.nt.wfubmc.edu:C: save: Cannot open save
> session with
> >backupserver
> >
> >
> >
> >Strange that it gives me this error and includes
> the name I have
> >configured in Legato as not registered.
> >
> >
> >
> >I now have 3 clients that I can't get backed up
> because of this
> >problem... Is there something else that could
> cause the 'not a
> >registered client' error? I've triple checked my
> DNS forward and
> >reverse entries and they are correct.
> >
> >
> >
> >SUN E450/Solaris 2.6
> >
> >Solstice 6.1.2
> >
> >
> >
> >TIY,
> >
> >
> >
> >
> >
> >Joel
> >
> >
> >--
> >Note: To sign off this list, send a "signoff
> networker" command via
> email
> >to listserv AT listmail.temple DOT edu or visit the list's
> Web site at
> >http://listmail.temple.edu/archives/networker.html
> where you can
> >also view and post messages to the list.
>
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff
> networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's
> Web site at
> http://listmail.temple.edu/archives/networker.html
> where you can
> also view and post messages to the list.
>
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
_____________________________________________________
Gå före i kön och få din sajt värderad på nolltid med Yahoo! Express
Se mer på: http://se.docs.yahoo.com/info/express/help/index.html
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
