NV Version: all
OS Version: Windows 2000/2003
Application version: Microsoft Exchange 5.5/2000/2003
Plugin version: Microsoft Exchange plugin, all versions
A problem in an Exchange store database will prevent the database from being mounted after a restore.
After attempting to restore an Exchange store.edb using the Exchange APM, the restore completes successfully however the store is un-mountable. A Windows event log error indicates:
'Information Store (7576) First Storage Group: Attempted to attach database '[path to database file]' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.'
Also, subsequent attempts to restore the store fail, with the error "database not found".
Reason of problem/issue:
There is a corruption in the store that existed at the time of the backup. After the restore the database must be mounted, however, due to the corruption, the mount is unsuccessful.
To confirm this, run eseutil /mh to check the consistency of the public and private information stores. If this indicates that the store you restored is not consistent, you must run a hard repair operation against ONLY the databases that are inconsistent.
You need to run a hard repair by running eseutil /p. The repair goes through the database and checks and repairs critical structures inside the database (such as system tables, attachment tables, and so on) and checks for damaged pages in the databases.
Use extreme caution with this command, because if there are damaged pages in the database, this data will be lost following a hard repair.
Please note that, if you must run a hard repair (eseutil /p) on your production database, Microsoft recommends that you perform an offline defragmentation (eseutil /d) and an integrity check (isinteg -fix) to make sure that the database is stable after the repair procedure.
There is significant information about recovering an Exchange public or private store on the Microsoft website. Please make sure you are familiar this information before attempting a recovery. It is recommended that Microsoft support is contacted if guidance is required.