Tim,

Normally this means that there was an incremental
backup (or even a full) that contains logs that
you may also need to restore.

When you restore just the public or private part of the
Information Store, we can't erase existing log files
since the non-restored part of the Information Store
requires those other logs for integrity.
Clear as mud, right?  How about an example.

Say for example, the current log files are:

edb00010.log
edb00011.log
edb00012.log

And you restored the private part of the IS
and the associated logs, say:

edb00004.log
edb00005.log
edb00006.log

The Exchange Server DEMANDS logs:

edb00007.log
edb00008.log
edb00009.log

or it won't start up correctly.

If those logs are in an incremental, then just restore them.
But, if you are trying to "backlevel" only that part of
the store, and you have taken more full backups in between,
then you will have to try another procedure, like restore
to an alternate server and copy out what you want.

Thanks,

Del

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


> Running TDP for Exchange version 1.1 on Exchange Server 5.5 Service Pack
3.
> NT 4.0 SP 6a. ADSM Server - NT 3.1.2.40.
>
> After restoring only the Public Information store, the Information Store
> service fails to start with the messages below.  Restoring both Public
and
> Private IS works fine.
>
> System Log
> Event ID 7024
> Source Server Control Manager
> The Microsoft Exchange Information Store service terminated with
> service-specific error 3355443757.
>
> Application Log
> Event ID 5000
> Source MSExchangeIS
> Unable to initialize the Microsoft Exchange Information Store service.
Error
> 0xc8000713.
>
> Event ID 1080
> Source MSExchangeIS
> Unable to recover the database because error 0xc800022d occurred after a
> restore operation. The data is not fully restored because some log files
are
> missing.
>
> Event ID 153
> Source ESE97
> MSExchangeIS (245) The restore log file 0xa4d is missing.
>
> If anyone has any information or suggestions on this it would be
> appreciated.
>
> Thanks,
>
> Tim Rushforth
> City of Winnipeg
> trushfor AT city.winnipeg.mb DOT ca