In general, only basic error messages should be written to the NT Eventlog,
detailed error information should be written to the TSM error log.

The 4.2 Journal Service incorrectly logs two messages which it shouldn't.

One is generated when access to an object which has changed but is excluded
via the
journal exclude list fails.

The other is generated when an object changes and is deleted before the
journal
service can process the first change notification (apparently this is
somewhat common
when applications create and remove temp files).

Both these problems (and many others) will be fixed in the 5.1.0 Journal
Service.

The next version of the Journal Service will also allow adding or removing
file systems without stopping
and restarting the service, and will have enhanced support for running in a
Cluster environment.


Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: tanenhau AT us.ibm DOT com
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"

---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on
12/21/2001 12:09 PM ---------------------------
12/21/2001 12:09 PM ---------------------------

"Malbrough, Demetrius" <DMalbrough AT TTIINC DOT COM>@VM.MARIST.EDU> on 
12/21/2001
10:25:37 AM

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:    4.2.1.15 NT Journal Service FILLING EventLog



Happy Holidays, *SMers!

Just a FYI! We have upgraded some of our NT 4.0 clients to 4.2.1.15 to take
advantage
of the Journal Based backups, but it seems to be more of a BURDEN! The
Journal Service
seems to be accessing the clients every second for files to process,
backup,
skip, etc...
(this is normal), but it is filling up the EventLog with a message EVERY
SECOND! That
is not acceptable because if there was ever a real problem on one of the NT
boxes then
the EventLog would be flooded with these Journal Messages! It would prevent
the CRITICAL
messages from revealing themselves!

Anyone else noticed this???????????

So, we have decided to just STOP all Journal Services & disable them until
Tivoli comes
up with a better solution!  The Journal Service needs more tweaking!!!!


Regards,

Demetrius Malbrough
UNIX/TSM Administrator