> It would be nice if you could use bpflist to grab the initial mount
> point of the backup (can you?), then script it to show the mount points
> that were backed up that day.  That still doesn't solve the first
> problem that one of the backups could be partial, etc.

Yup, that's what I do (sort of) for one of my daily reports.  There are
some gotchas.

If you do incrementals of filesystems that have *no* updates (in my
case, I saw this on some /boot filesystems), then there may be no new
data, and nothing to pull from bpflist.  If you're working only from the
catalog, then there's no record that a backup was done on that date of
the filesystem (because no data was sent to tape).

However without that nit, and assuming standard or NDMP backups of
normal filesystems (no agents, no catalog backups), then the first file
from bpflist is the backup selection that was passed to it.

Sometimes the "index" on the first line is not '1'.  I'm not sure why
that is, but all my reports run well assuming that the first FILES line
is the selection.

> The true audit test, of course, would be to do an alternate restore of
> the thing.  To hell with logs, baby, give me a restore!

Absolutely.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu