What we used to do is just look at the file spaces - which
used to pretty accurate (Days since last backup completed
successfully 1) and pull out any machine that is greater
than 1 - now with the TDP for exchange 2.2 client it reports
the filespace as successfully completed even if a storage
group in exchange failed it's backup.
Have not bothered opening a call for this because as Del says,
all the actual messages are logged to the server - we pull it
out of there including other info like the throughput for
the session. This way of reporting seems the most accurate.

Cheers
Christo
================================================================


> I'm currently testing TDP for Exchange for possible deployment
> in a very large enterprise environment.  Is anyone aware of
> tools/scripts that I can use to monitor the backups/restores.
> I'm aware that
> I can look at the past history of backups/restores and
> determine approximately how long it will take, however,
> this can be quite time consuming.  Also, does anyone
> know how most people are monitoring
> the success/failure of their respective backups.  I
> was going to scrape data out of the excfull.log or
> excincr.log.  This seems kind of primitive.

Joe,

Just one thought...
Also, keep in mind that all backup (and restore) events
for TDP for Exchange are logged in the TSM server
activity log... including their success or failure.
That way you can go to one central location
to find out the status of the backups, i.e. you
would not have to go to each Exchange server
to find out the status.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

"Celebrate we will. Life is short but sweet for certain..."  -- Dave
______________________________________________
"The information contained in this communication is confidential and
may be legally privileged.  It is intended solely for the use of the
individual or entity to whom it is addressed and others authorised to
receive it.  If you are not the intended recipient you are hereby
notified that any disclosure, copying, distribution or taking action
in reliance of the contents of this information is strictly prohibited
and may be unlawful.  Absa is neither liable for the proper, complete
transmission of the information contained in this communication, any
delay in its receipt or that the mail is virus-free."