How about occasional random restores of files? Your backups, after
all, are only as good as your restores.

(most of the time i use bpimagelist -- sometimes bperror -backstat )

Of course, if there's only 2 important files on a box and an admin
puts them on an exclude list - I would never know if they were missed
or not - backup was successful, but doesn't do much good if the
important data is missing.

-Charlie

On 8/25/05, Wayne T Smith <wtsmith AT maine DOT edu> wrote:
> How about:
> 
>    bpimagelist -U -hoursago 99999 -client <clientname>|head -3|tail -1
> 
> That is, bpimagelist outputs images ("successful" backups) with most
> recent first.  "head" takes 1st 3 lines of output and "tail" throws away
> the 1st two (header) lines, leaving the most recent backup line, that
> might look like this:
> 
>    08/24/2005 21:49  09/21/2005    13496   809836  N  Cumulative I
> SomePolicy
> 
> Of course, that doesn't say all the files of interest were backed up,
> nor is it of much usefulness if a client is covered by more than one
> policy, or if files are excluded/selected according to schedule.
> 
> cheers, wayne
> 
> Piszcz, Justin wrote, in part,  on 8/25/2005 8:55 AM:
> 
> > I know I can utilize various bp* commands as well as a bpreport.pl
> > script I found in the archive mailing lists.
> >
> > But on a per-client basis, what is the best way to determine **when**
> > the last successful (full or incremental) backup occurred?
> >
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>