Troubleshooting Steps:
1. Copy the .edb and .stm files from the location you selected to extract them to on the drive. You may have to do a search on the Recovery Manager for Exchange drive to find them but they should still exist if you didn't cancel out of the Direct Tape restore.
2. Once copied to a new location, use the Offline EDB file restore option in Recovery Manager for Exchange and select to use the Hard Repair during the restore. If this doesn't work, you will have to confirm that the edb file is not corrupted by using the Eseutil instructions below.
Using Eseutil:
Run Eseutil with the /g and /mh switches, which can be found in Microsoft KB Article ID 317014 "XADM: Exchange 2000 Server Eseutil Command Line Switches":
http://support.microsoft.com/default.aspx?scid=kb;en-us;317014
Also, the commands are below:
replace the path to the edb file with the actual path to the information store.
c:\exchsrvr\bin> eseutil /mh c:\path to edb file\priv1.edb >c:\header.txt
c:\exchsrvr\bin> eseutil /g c:\path to edb file\priv1.edb >c:\integ.txt
This is what you want to look for in the Eseutil outputs:
Header.txt
Microsoft(R) Exchange Server(TM) Database Utilities
Version 6.0
Copyright (C) Microsoft Corporation 1991-2000. All Rights Reserved.
Initiating FILE DUMP mode...
Database: D:\original db\priv1.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,9
Engine ulVersion: 0x620,9
Created ulVersion: 0x620,9
DB Signature: Create time:04/07/2005 19:28:02 Rand:4105571532 Computer:
cbDbPage: 4096
dbtime: 140435284 (0-140435284)
State: Dirty Shutdown
Integ.txt
Microsoft(R) Exchange Server(TM) Database Utilities
Version 6.0
Copyright (C) Microsoft Corporation 1991-2000. All Rights Reserved.
Initiating INTEGRITY mode...
Database: D:\original db\priv1.edb
Streaming File: D:\original db\priv1.STM
Temp. Database: TEMPINTEG2896.EDB
Checking database integrity.
The database is not up-to-date. This operation may find that this database is corrupt because data from the log files has yet to be placed in the database.
To ensure the database is up-to-date please use the 'Recovery' operation.
Operation terminated with error -550 (JET_errDatabaseDirtyShutdown, Database was not shutdown cleanly. Recovery must first be run to properly complete database operations or the previous shutdown.) after 2.281 seconds.
If the outcome is a Database Dirty Shutdown, search Microsoft's knowledgebase to find best practices for repairing a corrupted edb file: http://search.support.microsoft.com/search/?adv=1
