In regard to: Re: [Networker] Backup - Log / Checklist, Howard, Patrick...:

From the responses I have seen, it seems that there is really no "good"

method in a large environment to "easily" verify that all of the backups
that should have ran, actually ran.  It also seems that everyone fears
the same thing I do...(a group is set to not auto start and it doesn't
get documented or communicated that it was done, and it gets
"forgotten")  I guess it's nice to know that others are fearful of the
same thing.

You should ponder Darren's response more.  Several people gave good tips
for seeing what failed *if* the backup group or machine ran at all, but
that wasn't really what you were asking.  You could use any of their
suggestions, if you save every filesystem line from the savegrp reports
and then compare them day by day (i.e. "Yesterday the machine foo.bar.com
had a C: and a D: in our report, but it doesn't appear at all today, it
must have been missed").

Alternately, you can use Darren's suggestion of working against the media
database.  It's what we've done for years, mainly because I think it's
much easier and much more straightforward.

The basic idea is simple.  Run an mminfo query that generates a list of
all (client, filesystem) tuples that have ever (or in the last 3 months,
or whatever) had a successful full backup.  That's your baseline.  Sort
that output and save it to a file.

Now run an mminfo report that generates a list of (client, filesystem)
tuples that have backed up since some point in time N (e.g.
"savetime>yesterday", or whatever).  Sort and save to a different file.

Diff the two lists, and you have the complete list of clients and volumes
that haven't successfully had anything added to the media database since
your time N.

You can make all sorts of improvements on the basic idea by getting more
adventurous with your mminfo command and the post-processing you do, but
the basic idea is simple and it does what you're looking for.

4. But I still don't know if all of my backups that should have kicked
off, actually did.

Darren's answer gave you the tip you needed, but he didn't go into a lot
of detail.

Tim
--
Tim Mooney                                        Tim.Mooney AT ndsu DOT edu
Information Technology Services                   (701) 231-1076 (Voice)
Room 242-J6, IACC Building                        (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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