Len Philpot wrote:
> Can someone give me a braincheck on this?
>
> If I do:
>
> # mminfo -ar 'nsavetime,sscreate(22)' -c jupiter -N /dir1 -q '!ssrecycle'
>
> I see a listing thus :
>
> save time ss created
> 1264829064 01/29/10 23:24:24
> 1265094026 02/02/10 01:02:54
> 1265180427 02/03/10 01:02:06
> 1265266822 02/04/10 01:02:07
> 1265353207 02/05/10 01:00:05
> 1265434114 02/05/10 23:28:35
>
> ...and so on, up to the last backup. These should be all the browseable /
> recoverable backups for "/dir1" on "jupiter" currently in the database (we
> keep our browse and recovery policies equal).
>
> Therefore, running nsrinfo with one of the 'nsavetime' values like this :
>
> # nsrinfo -t 1264829064 jupiter
>
> ...spews output thus :
>
> /dir1/lost+found/
> /dir1/.profile
> /dir1/subdir2/subdir3/more_subdirs/install
> /dir1/subdir2/subdir3/more_subdirs/installer
> /dir1/subdir2/subdir3/more_subdirs/locks/
> /dir1/subdir2/subdir3/more_subdirs/logs/2007-01-05_03-19-55PM.log
> /dir1/subdir2/subdir3/more_subdirs/logs/2007-01-05_03-59-39-PM.log
> /dir1/subdir2/subdir3/more_subdirs/logs/2007-01-05_03-59-39-PM.out
> /dir1/subdir2/subdir3/more_subdirs/logs/2007-01-05_03-59-39-PM.err
>
> ...for thousands of lines. This output should be a listing of every file
> backed up for that given savetime, right? And, therefore, if I go through
> all active savetimes and a given file never shows up, then it was never
> backed up. :-)
Yes, if the file was not in any of the save sets then it wasn't backed
up. Were all these save sets full backups? If some were incremental or
level backups you might not see the file you were looking for anyway in
some of them.
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
|