Hmmm... Clever. So all you need to do is just figure out which tape has
the client's index from the date that you wish to recover the file(s)
from and then run that command, and then you can browse back using
nwrecover? When did this command become available?

I seem to recall a way to recover a file using some kind of two-step
method where one command is piped to another. I want to say one of the
commands was uasm where you give it the starting record and/or file
number to get it to the desired location on the tape? Not sure what
those commands were and how youfigure out the parameters to pass it,
though.

George

Robert Maiello wrote:
>
> George,
>
> Perhaps your referring to the nsrck -L7 -c clientname -t date   command?
> This will ask for the tapes with the index backups on them and merge the
> old index into to the new one.  Then you can browse the files as usual and
> do your restore.   We certainly have had to run scanner or restore a whole
> saveset for one file since this command became available.
>
> Robert Maiello
> Thomson Healthcare
>
> On Tue, 25 Mar 2003 11:36:29 -0500, George Sinclair
> <George.Sinclair AT NOAA DOT GOV> wrote:
>
> >I did specify the ssid as follows:
> >
> >recover -d relocation_directory -S ssid path
> >
> >This worked like a champ, and I have my data, but I was just curious if
> >there was any way to speed up the process and make it run as fast as
> >nwrecover. In my case, the files are too old to browse.
> >
> >George
> >
> >Stan Horwitz wrote:
> >>
> >> On Tue, 25 Mar 2003, George Sinclair wrote:
> >>
> >> >Hi,
> >> >
> >> >Is there a way to speed up a saveset recover other than specifying the
> >> >specific pathname and date (instance) or ssid when running from the
> >> >command line?
> >>
> >> If you did not specify a ssid on the -S option on the recover
> >> utility, you probably are not doing a saveset recover. Try using
> >> the -S option. There are other options such as -i and -q that
> >> often come into play when doing a saveset recover so you might
> >> want to review the documentation to see which options are best
> >> for your situation.
> >
> >--
> >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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=