RE: How to Fix Corrupted EBD

  • From: "Fares Rihani (Personal)" <Fares@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 2 Nov 2004 08:42:10 -0500

Hi gautam,

I ran this search

and came up with a few tips:

If the edb file is in a "clean shutdown" state then you can run eseutil
/createstm to generate a new stm file.
If the edb file is in a "dirty shutdown" state then you will have to
repair the database as well.
To check the state of the database you will need to run eseutil /mh
<path to the database>

edbutil /mh c:\exchsrvr\mdbdata\priv.edb >c:\edbdump.txt
Also monitoring the event log for any events from source EDB and
MSExchangeIS are also a good indicator as to the health of your database


First of all you have to recreate the STM file using the following
command (eseutil.exe should be in the exchsrvr\bin directory. Before
doing anything, make a backup copy of all your databases and log files:

eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb" /createstm

NOTE: This path to the database file assumes the default location for
the database file, Priv1.edb. You may have to modify the path to include
the correct path to the Exchange database files.

After recreating the STM now a repair can be performed on the database
to recover the data:

eseutil /P "c:\program files\exchsrvr\mdbdata\priv1.edb" runs through
about 3-5 GB per hour.

Next you'll need to run a offline defrag:

eseutil /D "c:\program files\exchsrvr\mdbdata\priv1.edb" - 3-5 GB per
hour and you'll need 110% free disk space based on the size of your EDB.
So if the Priv1.edb is 10 GB then you'll need 11 GB of free disk space.

Next you need check the integrity of the database:

isinteg -s <servername> -fix -test alltests (run this at least twice)

At this point your database should be repaired and you no longer need
the log files so you can remove them and start your information store.
Any time you run a hard repair expect "some" data loss.

328841 Exchange and antivirus software

313184 How to recover the information store on Exchange 2000 in a single

272570 How to recover from information store corruption (Exchange 5.5)

259851 Ramifications of running the eseutil /p or edbutil /d /r command

Technically, if you restore a valid, older database, you should be able
to replay all the log files coming forward by removing the log
checkpoint file. when the database comes online on the recovery server,
it should then play through all the available log files.  at that point
you should be able to use exmerge to extract the last two weeks of data
from each mailbox into a PST which can be exmerged back into the
production server.


Let us know what you've tried.  Good luck repairing.


-----Original Message-----
From: Gautam [mailto:jkakkar@xxxxxxxxx] 
Sent: Tuesday, November 02, 2004 3:00 AM
To: [ExchangeList]
Subject: [exchangelist] How to Fix Corrupted EBD

HI All,
We were using Exchange 2000 Enterprise. yesterday my exchange server
crashed and when i am trying to repair my edb using eseutil it is saying
that the database is corrupted. Can someone please help me as i have no
other option left to try than to seek help.

An urgent help is required in this concern as my job is at stake. 


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: