Assume that you have Exchange server 2003 , and you have lost the operating system but you still have the EDB and STM files for the databases, what can you to be up and running as fast as you can, below is the steps that can be used to rescue the exchange in our case
1. Have a windows server installed and patched to match existing Exchange server
You will want to have the OS already installed and patched to match the existing Exchange server’s patch level.
2. Reset Exchange Server AD account
When you make the decision to bring up the DR server you will need to reset the Exchange server’s AD account (in ADUC right click the server and choose reset account). Then rename the standby server to match the old Exchange server and join it to the domain. Change the IP address of the standby server to what the old production server was. This way you do not need to make any DNS or firewall changes
3. Install Exchange 2003
Use setup.exe /disasterrecovery to install Exchange without creating any databases. Make sure your installation matches your old configuration (database and logs on same drives as they were in before).
Make sure that you click Action-Disaster Recovery for the Messaging and Collaboration services and for Exchange System Management Tools
Install Exchange 2003 SP2 using the /disasterrecovery switch
a. Check the following registry subkey for ServicePackBuild
b. If the key does not exist add the following
i. Reg_Dword : ServicePackBuild
1. Hexadecimal value : 1DD6
Install all post SP2 exchange hotfixes that were installed on prior server
4. Run Eseutil /mh
Run Eseutil /mh to check if the database is shutdown in a dirty state. If the database is in a dirty state it will not mount.
If the database is shutdown in a clean state attempt to mount the Store. If successful then mail should start flowing.
Install SSL certificates on new server.
5. If the mount attempt fails or if the Eseutil /mh shows the database is in a dirty state we will need to look at the store
If ESEUtil /mh shows the database in a dirty state proceed with step one.
If ESEutil /mh shows the database as clean but the mount fails, skip step one.
1. Attempt a Soft Recovery (A transaction log replay process that occurs when a database is re-mounted after an unexpected stop)
a. Run ESEUtil /r ENN
i. ESEUTIL /r enn /L[path to log files] /s[path to checkpoint file] /d[path to database file]
2. Verify the integrity of the database
a. Run ESEUtil / g
3. Further steps to recover would be dictated by the results of the ESEUtil /g
a. Error id’s located in this technet article