Networker

Re: [Networker] determining what was backed up

2009-11-12 17:37:33
Subject: Re: [Networker] determining what was backed up
From: Frank Swasey <Frank.Swasey AT UVM DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 12 Nov 2009 17:33:09 -0500
Today at 8:30pm, A Darren Dunham wrote:

On Thu, Nov 12, 2009 at 02:48:40PM -0500, Francis Swasey wrote:
I have a windows system that we have been backing up and it may have
index corruption or it may have such a convoluted series of mounted
directories that the data is just not being backed up.

I am able to use nsrinfo to see that the directory (empty) was backed up
on the last full save -- and that another directory that the system
admin originally said was not available is completely there.  I am able
to use "recover -t <nsavetime of last full> -c <client>" and browse into
the D:\users directory -- as nsrinfo says I should, and not into
D:\BHCommon as nsrinfo also says I should not.

Not sure I understand.  You're saying something appears in the index,
but when you try to recover it, it fails?  Or that something is in the
index, but it shouldn't have been backed up in the first place?

I mean I have a directory that the sysadmin says should be in the backups, but that isn't and because we've been dealing with index corruption caused by a bug in 7.4.5 -- I'm not sure if the problem is in NetWorker or my sysadmin...


Question:  Is there a way to see what was really backed up (short of
doing a full recover of the ssid)?  If the answer is scanner -- help my
feeble brain figure out what options to pass to it.

Why do you suspect the indexes are incorrect?  A full ssid recover is
the *best* way to know what's recoverable, but takes a lot of space.

See the 'scanner' page for a command line of how to do it.  Add -n to
uasm to not actually recover the files.  Something like:

scanner -S <SSID> <tapedev> -x uasm -rnv

I think the -v argument to uasm will cause it to display all files.
Because it's reading the entire filesystem, this may not be
significantly faster than actually doing a ssid recovery.  But it
doesn't consume disk space.

Wonderful! Thanks -- I should have realized that -- just fighting too much today to realize that.




--
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)

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

<Prev in Thread] Current Thread [Next in Thread>