Del,
Thanks, we had overlooked the "ERASEEXISTING" option. That cleared all the
log files, and allowed the ISINTEG -PATCH to run.
Thanks again,
Barry
> -----Original Message-----
> From: Del Hoobler [SMTP:hoobler AT US.IBM DOT COM]
> Sent: Friday, September 10, 1999 12:33 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Exchange 5.5 Restore Problems
>
> Barry,
>
> We do have many customers running Exchange 5.5 on NT 4
> backing up and restoring their IS database without problems.
>
> A few things to consider before calling IBM service...
>
> Are you sure the Exchange IS database was OK
> BEFORE the backup was taken? Had you run the integrity
> checker before the backup to verify it was OK?
> Normally, if there is an integrity problem, you
> get an error during backup (checksum). But there
> was a Microsoft bug (X5: 102736) that had to
> deal with Exchange Server not catching this problem
> during backup. The associated knowledge base
> article is Q230215. Please take a look.
>
> ...and I assume you are specifying the "ERASEEXISTING" option
> during the restore process (default is no).
>
> Is this happening on ALL of your Exchange 5.5 servers?
> If not, then you may have taken a bad backup and
> it could be related to the Microsoft bug mentioned above.
>
> If you are still seeing problems, please contact IBM service.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> Del Hoobler
> IBM ADSM Agent Development
> hoobler AT us.ibm DOT com
>
> >
> > My apologies for posting this again, but I fear that the original post
> did
> > not make the list. I could not find it on the "adsm.org" archives.
> >
> > We have just finished upgrading MS-Exchange 5.0 to 5.5. Today we
> > attempted
> > to restore a 5.5 backup. The restore finished without error, but the
> > Exchange Information Store would not start. The Exchange repair utility
> > ESEUTIL, reports a very large number of errors, and it has been unable
> to
> > successfully complete a repair. ISINTEG -PATCH reports problems with
> > logfile signatures.
> >
> > The restore process is the same process we have used many times in the
> > past
> > with the Exchange 5.0 Server. In fact, to test, we setup and restored a
> > 5.0
> > backup successfully.
> >
> > Our Environment:
> >
> > ADSM Server: RS/6000
> > AIX 4.3.2.0
> > ADSM for AIX 3.1.2.20
> >
> > Client: NT 4.0 SP5
> > Exchange 5.5 SP2
> > ADSMConnect Agent for Exchange 1.1.0.0B
> >
> > Has anyone had similar experience? Any suggestions would be
> appreciated.
> >
> > Thanks
> > > Barry T. Hill
|
