Networker

Re: [Networker] Index retention and Browse times

2006-07-10 18:24:41
Subject: Re: [Networker] Index retention and Browse times
From: Tim Mooney <mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 10 Jul 2006 17:23:23 -0500
In regard to: [Networker] Index retention and Browse times, Sid Martin said...:

Does the tape (ssid) have to be brows to be able to user the GUI recover
process to selectively restore imbedded folders.

Yes.

If so what Do I have to do to return to brows able.

The list of what files are contained in a particular saveset (and what
parts of the saveset they're in) is part of the client index.  Generally,
when you back up a client, after all the filesystems on that client get
backed up, then a differential backup of the index for that client (which
is on the server) gets backed up.

If you still have the index backup that was done (i.e. it's still on a
tape that hasn't yet been overwritten), you can just merge that into the
current client index contents, and your client data will again be
browseable.  That merge is performed using `nsrck -L7' with a particular
time and client name.  See the man page for nsrck.

If that index backup is no longer available but the client savesets
are still available, you can use scanner with the `-i' option to rebuild
the client index data from the actual tape contents.  That's pretty slow,
but it should always work.

If this can't be done what do  I need to do to recover imbedded folders if
I know the SSID???

If you know the exact path and filenames for every one of the folders you
need to recover, you can do a saveset recover and limit which
files/folders are recovered via the "Paths to recover" part of the saveset
recover dialog in the GUI.  It will be slow, but it will recover only
the bits you need.

Alternately, you can do the same thing using the '-S ssid' and multiple
paths specified on the command line for `recover'.

As Darren already replied, you could also use `uasm' to accomplish this,
but he's correct that it's a fairly advanced techique and probably not one
you want to try at this point.

If you don't know the exact paths for all of the data you need to recover,
then you'll need to get to the point where things are browseable, which
means one of the two options I pointed out above (nsrck or scanner).

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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