Dirty Shutdown on Exchange 2003
Posted on 2008-06-24
I am suffering a dirty shutdown on exchange 2003. After reading and re-reading all the KB's and tips and tricks and every other tidbit of information out there I am a little reluctant on jumping in head first so I wanted to get some advice. Here is the cut from the trouble shooter that I ran.
MANUALLY RECOVER THE DATABASE IN-PLACE
You can use Eseutil.exe to manually recover a database. In-place manual recovery runs simultaneously for all databases in the storage group. To do an in-place recovery with Eseutil.exe:
1. Copy all existing transaction log files to a safe backup location. Manual recovery may alter the current transaction log in such a way that missing databases or previous backups cannot be restored. The backup copies of the log files may be required to fully recover backups or missing databases.
2. Open a Command Prompt window and change the default directory to the transaction log file directory (for example, CD /D C:\Logs).
3. Run this Eseutil.exe command from inside the transaction log folder:
C:\Exchsrvr\bin\eseutil.exe /R E00 /I
Now the steps:
Step 1 I want to make sure I copied the transaction log files to a "safe place" so I copied the whole EXCHSVR folder. Will that cover everything?
Step 2 Open a command prompt window and change the default directory to the transaction lof file directory. Change what default directory? From the command prompt?
Step 3 run the eseutil from inside the transaction folder? How do I get it there when it is located in the .bin file?
These directions are not very clear, can someone help please.