On Thu, Mar 20, 2008 at 02:28:09PM -0400, MIchael Leone wrote:
> (I need to recover some files created by a NW server at one of my remote 
> sites, and I don't feel like going out there with the tapes and doing the 
> restore. I have a NW server here at the data center. I'd like to read the 
> index off the tapes here, do a directed recover from here)
> 
> How would I go about doing that? Is that also "scanner -m"?

Since this is a foreign server, you'll always need the scanner -m so
that the volume is known by the media DB.  That part isn't usually
necessary on the original server.

> Or is the command different, since these tapes have the index file
> saved on the tape? Is it "scanner -i"?

Think of it this way: the indexes are on disk as a way to point to
individual data within the saveset.  They are necessary if you don't
want to do a full saveset recover (but want to recover individual
files).

There are (at least?) 3 ways of putting that information on a server
that doesn't currently have it:

1) scanner -i (builds index info from the actual saveset and merges)
2) nsrck -L7 (merges index backup on tape with indexes on disk)
3) recover /nsr/index/<client> from tape (okay if no client index exists)

#2 and #3 work from an index backup.  #1 only requires the actual saveset
data.  If the saveset is huge and you only need a bit of the data, then
#1 will take a much longer time to complete the task than the others.

-- 
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. >

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