> In the past, I played around with a script to check this, but it relied
> on a hard coded listing of savesets, and this was a pain to keep updated
> as clients were added, deleted and savesets moved around. Using a script
> to possibly keep this information in sync would make it much easier.

100% agree.  I've done this with a couple of different frameworks.

I've had someone do a whole database setup, so that a web display could
show all filesystems backed up, and easy graphs for success/failure/no
attempt on any day.

It was easy to scan the page looking for isolated red blocks (simple
failure) and also lines of gray (in the DB, but no recent backups).

Another method was just a quickie.  Use 'mminfo' to grab all successful
full backups over the past 2 weeks (allows one failure to occur).  Sort
and dump to a file.  Every week run a 'diff' against the previous week
and resolve differences.  This is easy, but you have to not let anything
fall through by missing a week.

--
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. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=