So if it's only stored in one place then there must be some other reason
that NetWorker would barf if the current client id does not match the
client id associated with the saveset you're trying to recover that had
the same client name. It must look at the current value and think: "It
doesn't match the value from the saveset you're specifying so I'm not
gonna do it". Or, maybe it wouldn't care and it would do it anyway?
Seems like there is some disagreement about this, and I've never
actually tried it myself or had to yet so it's all just theory to me,
but it's more comforting to know what tricks to try if I ever need to do
this.

Tim Mooney's suggestion (see reply to my other posting: "Client id --
final question and 2 observations") about creating a fake client name in
server's /etc/hosts file (assuming DNS resolution is done via files
first) and then creating client with that same name, and then changing
its client id to match old one, seems like an innocent enough course of
action that could not hurt anything. I mean, it seems like using the
same id could only help and doing it via the fake client method at least
would not disrupt anything else.

George

Byron Servies wrote:
>
> On May 19, 2004, at 11:26 AM, Davina Treiber wrote:
>
> > Darren Dunham wrote:
> >
> >>
> >> The other copy is associated with the client, and is in the resource
> >> files for the client (visible/modifyable with nsradmin).
> >>
> >
> > Sorry to disagree, but the client ID is NOT in the res files. It is
> > accessible with nsradmin, but I guess nsradmin is just getting it from
> > the media database. And I'm not sure that it's modifiable in any
> > circumstance.
> >
>
> Correct on both counts.  Client id is stored in the media database and
> is only settable at client creation time.   The nsr rap server does not
> store all of the attributes in the res files; some come from other
> locations or are purely dynamic.
>
> Byron
>
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=