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

We have a fix written and tested for the problem identified
in my 12/28/1999 append attached below.

You can download the FIXTEST (1.1.1.01) from the IBM FTP site at
ftp.software.ibm.com (this has replaced index.storsys.ibm.com).

*************************************************************************

FIXTEST 1.1.1.01 Details
------------------------
  FTP Site:    ftp.software.ibm.com
  FTP Site:    ftp.software.ibm.com

  Directory:
/storage/tivoli-storage-management/patches/agents/ntexch/1.1.1/

  The parts:

    IC25816_01.EXE          - Self extracting install file.
                              Download binary and run the EXE
                              file to install FIXTEST 1.1.1.01.
                              File Size = 3,205,532 bytes

    IC25816_01.README.FTP   - README file.


  *  You WILL be able to restore backups made by earlier versions
     of the TDP for Exchange (aka ADSMConnect Exchange Agent) with
     this FIXTEST version.

  *  You WILL NOT be able to restore backups made by the FIXTEST
     version with a prior version.  So, any backups that you make
     with this FIXTEST will need to be restored with this FIXTEST
     version (or anything we release after this FIXTEST version.)

  *  We recommend all customers install this FIXTEST to avoid
     possible restoration problems in the future.

  *  Microsoft has agreed that their API is returning incorrect
     data in this specific situation that is causing the problem.
     The API in question is HrBackupGetBackupLogs().
     However, they are not sure how they will handle it.
     They have agreed to put out KB articles describing this
     scenario but have not committed how they will handle it.

*************************************************************************

Thanks,

Del

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



Del Hoobler/Endicott/IBM@IBMUS AT VM.MARIST DOT EDU> on 12/28/99 03:48:11 PM

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:  FLASH: Exchange Agent/TDP for Exchange Customers--PLEASE READ!



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