> > If so, do I need to
> > delete "admnlts003", and remake it, using that client ID?
> 
> Yup.  Or, create it with a different name.  If NetWorker can resolve
> the name, it should be fine creating the client as something like
> 
>     admnlts003-old
> 
> That way, you can have both the old data and the data you've backed
> up since converting to the new server.


AH HA! I sense salvation. I can live with that - I could make up fake IPs 
for all the "-old" names (to be honest, it's probably only 2 or 3 hosts 
that I woulod *probably* restore from, based on my experience in the last 
year). I could make them up in the hosts file, so NW would find it, and 
then I should just do a redirected restore, from the "-old" to the new.

As long as NetWorker doesn't mind that the name used to be "admnlts003", 
and now is "admnlts003-old" (but has the same client ID, and links the 
"scanner -i" info to "admnlts003-old".

Have you tried that? Does it work?

> > *OR* can I just
> > enter that client ID, directly into the existing "admnlts003" client,
> > overwriting it's current client ID?
> 
> I don't think that's going to do what you want.  I would be very 
hesitant
> to do that.
> 
> Tim

Tim, if that works, remind me that I owe you a keg or two ....

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