Re: [Networker] determining what was backed up
2009-11-17 10:40:00
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.
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.
Not sure if this is what you are looking for, but you can view all the
files in a saveset via this method:
mminfo -q ssid=3145699585 -r sscreate,client,name,nsavetime
created client name save time
10/18/09 hostname.uwo.ca /data01 1219101438
nsrinfo -t 1219101438 hostname.uwo.ca
Mark
--
Mark Davis
University of Western Ontario - ITS
email: davism AT uwo DOT ca
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
|
|
|