exchange database corruption repair tips.

In this article, i will talk about how to restore an exchange database from one server to another. To get started, you have two computers one old one with the exchange database that you wish to move, and one new one with a brand new fresh os just waiting to go. You have already installed exchange server on both computers and copied the database (MDB Databases) over to the new computer.

The first step i had to do was rename and move all the default exchange stores. To do this, go into the system manager, under SERVERS-> FIRST STORAGE GROUP->MAIL BOX STORE. Rightclick on this and hit dismount. Do this for the public store as well. This will allow you to rename and move the store so you can put the backup store in its place.

Next move the default files somewhere where they will not be in the way. I moved all the log files, and everything so as not to confuse the server. I then copied the backup database in its place.

Now the next step is to run a "checkdisk" on the database. this is done with the eseutil.exe which is located under exchsrvr\bin directory. I found a great microsoft article that describes this in more detail, almost too much detail but here you go for your reference. http://support.microsoft.com/default.aspx?scid=kb;en-us;296788 If you want to have fun and play around with eseutil, just type it in with no parameters and you will get a list of the things you can do. Take a look at the first command i ran this was in order to clean the dirty shutdown status that the database will have. I say this like its a fact, but the truth of the matter is that i have done this now about 4 or 5 times and i have never seen it not have a dirty shutdown. Go figure.

Before running this, i had to go into the services section of the control panel and stop the exchange store. just click on the microsoft exchange information store and click stop.

C:\Program Files\Exchsrvr\MDBDATA>..\bin\eseutil /p priv1.edb

after runing this command and letting it chomp away for awhile, i get the output


Repairing damaged tables.

Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 494.344 seconds.


Now we want to run the same command on the public database. Same output and this one ran alot faster i guess they were not really using the public store that much.

Next we need to do another check of the database consistancy as if we were to try and mount the store at this point we would get an internal processing error (I tried it just for fun and got the error)