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
-----Original Message-----
From: Del Hoobler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 3:42 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP monitoring
> 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
IBM Corporation
[EMAIL PROTECTED]
"Celebrate we will. Life is short but sweet for certain..." -- Dave
