Hans-Peter,

Look at Microsoft Knowledge Base article Q186184.

Are you sure a DEFRAG of the Exchange DB didn't get
run in between the Exchange Agent backup and the
NTBACKUP backup?

Run a DEFRAG and retry the Exchange Agent backup
and NTBACKUP as close together (in time) as possible.

Del

-------------------------
Del Hoobler
Del Hoobler
IBM ADSM Agent Development
hoobler AT us.ibm DOT com

=========================================================
>
> Hi all out there !
>
> I have a problem with ADSM and MSExchange. We are running ADSM Server V3 on
> a WinNT 4.0 Server. The Exchange Server ist WinNT 4.0 (ServicePack 3) with
> MSExchange 5.5 (ServicePack 1). We are using the Connect Agent for Exchange
> Server V1.
>
> The first Exchange Backup we took results in:
>
> "source ESE97 (or ESE92 ?? couldn't remember)  msexchangeDS ((175)) direct
> read found corrupted page (162) with error 1018. Please restore the database
> from a previous backup."
>
> This error confused us a little because the new NTBACKUP utility (which also
> uses the Exchange API) didn't return this error.
>
> Is our Exchange DB really corrupted (hopefully not) or is there a bug in the
> ADSM Connect Agent ??
>
> Anyone there who can help me ?
>
> Thanx a lot !!
>
> Hans-Peter H?lscher
> DaimlerChrysler Aerospace -DASA- Raumfahrt Infrastruktur
> Tel.     +49 421 539 5151
> FAX      +49 421 539 5698
> email  hans-peter.hoelscher AT ri.dasa DOT de