Not all error messages for TDP For Exchange (1.1.1.01 anyways) are logged on
the server.

We just ran into this on one of our test servers, messages in client log:
ACN3002E --
The Directory service is not running. A backup was attempted
but the necessary Exchange Services were not running.
01/29/2002 20:59:31,ACN3025E -- Backup error encountered.

On the server, all you see is
01/28/2002 21:00:02      ANR2561I Schedule prompter contacting EX-CSDSVTEMB

                          (session 2400) to start a scheduled operation.

01/28/2002 21:00:03      ANR0406I Session 2403 started for node EX-CSDSVTEMB

                          (WinNT) (Tcp/Ip 192.168.176.45(4083)).

01/28/2002 21:00:16      ANR0403I Session 2403 ended for node EX-CSDSVTEMB
(WinNT).

Now this may be a bad example because if it is a production system you would
know pretty quick that the directory service was not running on Exchange!

We monitor all backups via q event to look for failed schedules (this does
not catch all Exchange Failures)

We do a daily check for filespaces that have not been backed up (this will
catch Exchange failures).

We also run a report using the accounting file as input which will show you
how much data is backed up by each node and the throughput.

Tim Rushforth
City of Winnipeg