locked
Corrupt Exchange Database RRS feed

  • Question

  • Hello, we are running a small business server 2003 with one exchange store. Exchange has been operating properly - however a few nights ago we were no longer able to backup the database via NT backup or BEX. From what everyone is telling me, it seems that there is some corruption is the store. Some people have told me to run repairts on the database - others have told me to create a new database and move the users to the new database. Still, another person told me to run CHKDSK. What is the best way to proceed? It is a failrly small database - only about 10gb.
    Friday, February 18, 2011 2:07 PM

Answers

  • On SBS 2003 your options are very limited. You cannot create a new database because you have a limit of one on that version.
    Chkdsk is unlikely to do anything for you.

    What I would suggest is that you stop all of the Exchange services, then take a copy of the Exchange database files.
    At that point do a repair of the database, which is documented in the MS KB. Confirm everything works correctly. If it does, the copy can be discarded.

    Do you get errors from the backup job? What are those. It might be something that doesn't require a database repair, with the associated risks that brings.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    • Marked as answer by Gavin-Zhang Saturday, February 26, 2011 1:35 AM
    Friday, February 18, 2011 3:31 PM
    1. Great advice from Simon on all counts
    2. However if you find that its unrepairable then check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp since you can use it to open an offline copy of the DB and recover data directly into a new database.
    3. Just to reiterate be sure to make an offline copy of your database files (EDB & STM) before you run any MS utilities against it so that you have the ability to do a rollback if something goes terribly wrong.

    Troy Werelius
    www.Lucid8.com
    • Marked as answer by Gavin-Zhang Saturday, February 26, 2011 1:35 AM
    Friday, February 18, 2011 6:02 PM

All replies

  • On SBS 2003 your options are very limited. You cannot create a new database because you have a limit of one on that version.
    Chkdsk is unlikely to do anything for you.

    What I would suggest is that you stop all of the Exchange services, then take a copy of the Exchange database files.
    At that point do a repair of the database, which is documented in the MS KB. Confirm everything works correctly. If it does, the copy can be discarded.

    Do you get errors from the backup job? What are those. It might be something that doesn't require a database repair, with the associated risks that brings.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    • Marked as answer by Gavin-Zhang Saturday, February 26, 2011 1:35 AM
    Friday, February 18, 2011 3:31 PM
    1. Great advice from Simon on all counts
    2. However if you find that its unrepairable then check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp since you can use it to open an offline copy of the DB and recover data directly into a new database.
    3. Just to reiterate be sure to make an offline copy of your database files (EDB & STM) before you run any MS utilities against it so that you have the ability to do a rollback if something goes terribly wrong.

    Troy Werelius
    www.Lucid8.com
    • Marked as answer by Gavin-Zhang Saturday, February 26, 2011 1:35 AM
    Friday, February 18, 2011 6:02 PM
  • Hi calibertech99,

    Any update for your issue?
    Above gave some good suggestions.
    Hope it works now!

    Regards!
    Gavin
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, February 23, 2011 8:11 AM