The cheapest way to do this is to get yourself familiar with SQL queries,
all the information you need is in the tables.




"Mark Bertrand" <Mark.Bertrand AT USUNWIRED DOT COM>@VM.MARIST.EDU> on 
04/16/2002
03:56:30 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  Re: Daily Backup Report


So, if I follow your message correctly and the point I have been trying to
make... There is no easy (one button) method of reporting, which should be
the basis of the software, the very basic core of any backup software, that
I don't have.

To answer the other question posted by Mr. Joseph Dawes, How do I track
failures?, I do it the long way. I start with the q events ex=yes as a
first
level then we start going through the activity logs starting with a search
for ANE4959i reporting missed files. Next we go through individual error
logs on the clients if necessary.