Thanks for the help... I have a unique situation. I am fairly confident
that the file in question is on the tape; I just can't locate it.
I am a victim of a couple of situations... The night in question, my
filesystem that contained the index got full, so I have no index.
I think that the backup ran successfully that night, but I need to try to
extract a particular file.
How can I find out if the file is on this tape since I have no index?
Thanks again for all the help... the below steps are something I was not
aware of (and this is very usefule!), but it didn't find the file.
Thanks again,
Diane
> -----Original Message-----
> From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
> EDU]
> On Behalf Of Tim Mooney
> Sent: Thursday, December 15, 2005 6:15 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: quick file recover help please
>
> In regard to: [Networker] quick file recover help please, Diane
> Rolland...:
>
> > I have a single file that I need to recover that is not on any browsable
> > index.
> >
> > I have the file name, the path that I want to restore to and the ssid.
> I
> > also know the tape that the file should be located on.
>
> There are (possibly) two easy ways to do this:
>
> - The file isn't browseable anymore, but do you have a tape that contains
> a backup of the index data for that client that would have contained
> the
> the file information?
>
> For example, say your client name is foo.bar.com. You want to recover
> a file from July 4th 2005, but the file isn't browseable. You do,
> however, know that one of your tapes contains an "index:foo.bar.com"
> saveset from August 3rd 2005, and your browse policy is such that that
> index would have contained the file information.
>
> In that case, you can quickly recover the index for foo.bar.com using
> `-L7' option to nsrck:
>
> nsrck -L7 -t 08/04/05 foo.bar.com
>
>
> Once you have that, you can browse from the client, use changetime to
> browse back to 07/04, and add and recover the file.
>
> - Since you know the exact path, you can use a saveset recover and specify
> which path it is you want to recover. This will be slower than
> recovering the index of the client and browsing, but it will work even
> if you don't have a suitable index for the client.
>
> You will need to run the `networker' GUI on the client in question, as
> root. From the GUI, choose "Save Set->Recover". From the window that
> comes up, choose the client in question. Next, select what filesystem
> it is that would contain the file.
>
> Next, choose the saveset in question that has the file you want to
> recover. For example, if you know it's in an incremental saveset that
> was done on 07/04/05, you would choose that one from the list.
>
> Once you have that selected, you can click "Details" to verify that
> the one you selected matches the ssid and tape volume you're expecting.
>
> Next, click "Recover". Select the one saveset that should show up
> in the "Savesets" window, so that it's highlighted (this step *may*
> not be necessary anymore, though it does no harm).
>
> Then, in the "Paths to Recover" box, type in the exact path to the
> file you want to recover. Be sure you hit "Enter", so that the path
> appears in the area below the text entry box.
>
> You can use the "Options" button to change what happens on file
> conflicts or to relocate the recovered file(s) to a different location,
> but if you want it to be recovered to the spot it was backed up from
> and there isn't already something there by the same name, you don't
> need
> to do anything with the "Options" button.
>
> Next, click "Recover", and wait. NetWorker will read the saveset in
> question, on the tape in question, record by record, looking for the
> file data for the file in question. When it finds it, it will recover
> it and continue reading the saveset.
>
> Hope this helps,
>
> 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
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
|
