Attention Tivoli Data Protection for Microsoft Exchange Server users!
          ====================================================
          (formerly: ADSMConnect Agent for Microsoft Exchange Server)

PROBLEM:
========
We have identified a situation where it is possible that when
running a full backup of the Exchange Information Store,
not all of the necessary transaction logs are included
in the backup.  This can result in an Information Store
database corruption problem when restoring a single full
Exchange Server backup from the Tivoli Storage Manager server.

This problem can occur when your Exchange server is very
active during the full backup, i.e. it is creating multiple
transaction log files during backup of the database file itself.


CIRCUMVENTION:
==============
The circumvention for this is to run an incremental backup
following the full backup to ensure the necessary transaction
log files are backed up.  We recommend that those doing
automated backups add an incremental backup immediately
following your full backup.  For example, in your script
or batch file doing the automated backups:

   OLD:
      excdsmc /backup:is,full

   NEW:
      excdsmc /backup:is,full
      excdsmc /backup:is,incr

The incremental backup will ensure that the necessary
transaction log files are backed up.

If you have to restore, make sure that you restore the
incremental backup with the full backup before
restarting your Information Store service.


FURTHER ACTION:
===============
We have identified a specific situation where one of the
Microsoft API calls is returning invalid data causing
this problem.

We are actively pursuing the problem with Microsoft now.
We will update you when we know the official resolution.


A special thanks goes out to Bob Fenstermaker for helping
identify and pinpoint this unique problem!


Thanks,

Del

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