Article ID: 329021
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange 2000 Enterprise Server
This article was previously published under Q329021
SYMPTOMS
When you try to mount the Exchange 2000 information store databases after you use Windows NT Backup to back up and restore the databases, the following event ID messages are logged in the Application event log:
Event Type: Information
Event Source: ESE
Event Category: General
Event ID: 102
Description:
Information Store (2308) d0fe865b-91a6-435d-89a1-19fa586d5e33: The database engine started a new instance (0).
-and-
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 619
Description:
Information Store (2308) Attempted to attach database 'E:\MDBDATA\SG-A-MDB\priv1.edb' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.
-and-
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description:
Error 0xfffffde0 starting database "Storage Group\Mailbox Store" on the Microsoft Exchange Information Store. Failed to attach to Jet DB.
-and-
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description:
Error 0xfffffde0 starting Storage Group /DC=COM/DC=DOMAIN DC=ORGANIZATION/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=ORGANIZATION/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=SERVERNAME/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. MDB failed to start.
Additionally, when you run eseutil /cc to perform a hard recovery, you receive the following error message:
CAUSE
This issue occurs because there are one or more instances of logical page corruption present in the information store databases before the backup and restore procedure. The backup and restore process detects physical page corruption, but it does not detect instances of logical page corruption.
RESOLUTION
To work around this issue, use the Eseutil.exe utility in repair mode (eseutil /p) to repair the backup databases, or restore from another backup, if one is available.
For additional information about how to use the Eseutil.exe utility, click the following article number to view the article in the Microsoft Knowledge Base:
317014 XADM: Exchange 2000 Server Eseutil Command Line Switches
Microsoft recommends that you periodically test and perform integrity checks of your backup and production databases. To verify the integrity of databases, use the Eseutil.exe utility in integrity mode (eseutil /g). The Eseutil /g command runs in read-only mode and is a safe way to verify database integrity.
MORE INFORMATION
For additional information about the Eseutil.exe utility, click the following article numbers to view the articles in the Microsoft Knowledge Base:
232734 XADM: In Exchange 2000 Server Eseutil in Repair/Integrity Mode Incorporates /X and /V Options
183888 XADM: Free Disk Space Requirements for Eseutil.exe
For additional information about hard recovery of databases in Exchange 2000, click the following article number to view the article in the Microsoft Knowledge Base:
232938 XADM: The "Last Backup Set" Check Box and Hard Recovery in Exchange 2000
Keywords: kbnofix kbbug KB329021
