If that's true then it would appear that it *IS IN FACT* necessary to
first re-create the client if it does not exist. I mean, if I want to
recover data from fred, using saveset recover or 'recover -S ssid', and
I don't have a machine named fred anymore then I can't very well grant
permission to some other machine if I don't first create a client named
fred. This seems to be a major problem with NetWorker.

Will NetWorker care that this is a new fred? Will it check the client id
value against the old value somewhere and then complain? How do you get
around this problem? What is the correct way to handle this situation?

George

Darren Dunham wrote:
>
> > Of course! Thanks.
> >
> > I assume if the client does still exist, that it would not be necessary
> > to give permission to the client you're running the recover command on,
> > correct? I mean, 'recover -S ssid' should bypass that since you're not
> > using the GUI to do a browse recovery?
>
> No, the permissions affect any recovery, gui or command line.
>
> You need to either run the recover from the machine that Networker
> believes is the client, or from a machine or account that has remote
> access permission for that client.
>
> --
> Darren Dunham                                           ddunham AT taos DOT 
> com
> Senior Technical Consultant         TAOS            http://www.taos.com/
> Got some Dr Pepper?                           San Francisco, CA bay area
>          < This line left intentionally blank to confuse you. >

--
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. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=