Eseutil /p hard repair discards the pages, rows and tables it cannot fix, so the mail stored there is gone.
Microsoft says repair loses some data. Exchange 2007 guidance adds Eseutil /D, Isinteg and a full backup as the steps that finish a repair.
Before you run eseutil /p, know what the command removes from your database. Eseutil /p hard repair fixes a file at page and table level and discards what it cannot fix.
Below you find what Eseutil discards, which fixes to try first and which steps Microsoft adds after a repair in Exchange 2007.
What does Eseutil /p Delete From a Database?
Eseutil /p discards the data it cannot repair. Microsoft's Exchange 2007 page, Eseutil /P Repair Mode, says a repair can discard rows from tables or even entire tables.
Repair mode checks all pages and tables for consistency and does not correct problems at the application level. Isinteg handles that level.
| Level | What eseutil /p does | Result for your mail |
|---|---|---|
| Page | Discards a database page it cannot repair | Data on that page is gone |
| Table | Discards rows or entire tables when needed | Data in those rows is gone |
| Application | Does not correct problems here | Isinteg handles this level |
ESE event 500 flags eseutil /p data loss during the repair. Microsoft says the event means the repair found a bad page, failed to fix it and discarded it, per The database engine lost one page of corrupted data. Exchange Jet Error -1018 explains the error behind many bad pages.
What should You Try Before Eseutil /p?
Eseutil /p hard repair comes last. Microsoft's Exchange 2003 page, Repairing Exchange Databases, calls repair the final option and recommends restoring a backup set instead when you can.
Work down this list and stop at the first step that works.
Exchange Database Dirty Shutdown covers soft recovery in depth. Step 3 protects your mail before the hard repair starts.
| Fix | Source file | What it needs |
|---|---|---|
| Log replay with eseutil /r | Replays logs into the database | Logs in place, none moved or deleted |
| Backup restore | Replaces the damaged file | Good backup plus newer logs |
| Copy-out from a duplicate | Source file unchanged | Duplicate .edb and its logs |
| Hard repair with eseutil /p | Discards what it cannot fix | Free space, downtime and a saved copy |
“Treat eseutil /p as the last step, not the fix. Get the mail out of a copy first, then let the repair do what it has to do.”
How do You Use Eseutil /p Step by Step?
Eseutil /p hard repair works on a dismounted database, so dismount it and save a copy of the files before you start.
For Exchange 2007, Microsoft suggests free space of 20 percent of the database size on the local drive for the temporary repair file. Use an account that is a delegated member of the local Administrators group.
Then start the repair on the database file.
eseutil /p "E:\ExchangeData\DB02\DB02.edb"
Check the header afterwards with eseutil /mh, which makes no changes to files, per Eseutil /M File Dump Mode.
eseutil /mh "E:\ExchangeData\DB02\DB02.edb"
Microsoft's Exchange 2007 sample output shows a repair count and date when a repair has happened.
Repair Count: 2
Repair Date: 08/10/2006 09:19:57
Which Steps Follow a Hard Repair in Exchange 2007?
After an eseutil /p hard repair, Exchange 2007 guidance says you must use Eseutil /D and Isinteg with the fix option to finish the repair. Then take a full backup.
| Step | What Microsoft says |
|---|---|
| Eseutil /P | Repairs the database at page and table level |
| Eseutil /D | Rebuilds indexes and defragments the database |
| Isinteg with the fix option | Repairs at application level and checks relationships between tables |
| Full backup | Repair invalidates previous backups |
Microsoft's Exchange 2003 page, Repairing Exchange Databases, lists the same order. You can leave out /D when the repaired file only serves to salvage mail before you delete it.
Skipping both can mean less salvaged data and several hours saved, per How to Run Eseutil /P (Repair).
Eseutil /D builds a new database with all data of the original and then deletes the original or saves it where you say. Reserve free disk space of 110 percent for that defragmentation, per Eseutil /D Defragmentation Mode.
In Exchange 2010 RTM and earlier, Isinteg repaired a mailbox only with the database dismounted. Exchange 2010 SP1 added New-MailboxRepairRequest, which repairs a mailbox while the database stays online, per New Exchange Core Store Functionality in Exchange 2010 SP1.
New-MailboxRepairRequest -Database DB01 -CorruptionType AggregateCounts
Microsoft allows one active database repair request at a time. AggregateCounts and FolderView work only by themselves.
Why does a Repair Invalidate Your Backups?
Microsoft's Exchange 2007 page says eseutil /p hard repair invalidates previous backups, because you can no longer roll the database forward from them.
You can still restore an older backup. Log replay then ends at the point of the repair. Changes made after the repair cannot be put back.
Microsoft calls a full backup as soon as possible after a repair critical, per How to Run Eseutil /P (Repair).
What does Microsoft Say About Repaired Databases?
Repaired databases that still show errors do not belong in production. Microsoft's Exchange 2003 page, Repairing Exchange Databases, says so when you cannot get the error count to zero. Salvage data by moving mailboxes into another database, Microsoft adds.
In 2015, the Exchange Team announced a support change for repaired databases (New Support Policy for Repaired Exchange Databases). Microsoft's policy requires you to evacuate a database that keeps a repair count or old repair count of 1 or higher. Moving mailboxes and public folders into new databases does that.
Repair Count shows the repairs made during the last repair operation. Microsoft's Exchange Server Analyzer page for Exchange 2003 SP2 and later, The database has been repaired <N> times, says a Repair Count above Old Repair Count means the database was repaired since its last offline defragmentation.
What can You Do When Eseutil /p Fails or Loses Too Much?
When an eseutil /p hard repair fails, restore a backup or open the database offline and export whatever mail survives.
Microsoft's Exchange 2007 advice for a database beyond repair is to restore from an online backup. With no valid backup, it says to create a blank database and recover what you can from PST files on client computers, per The database engine lost one page of corrupted data.
Exchange EDB Converter from Univik adds a path that leaves your source file unmodified. Univik Software replays logs saved beside your .edb into a working copy. With no logs, the app repairs that copy and finishes with a direct scan of raw data when repair fails.
Recovered items collects mail from a damaged Exchange 2010 file when its folder is lost. Sender, subject and date stay visible.

| Point | Eseutil /p | Univik Software |
|---|---|---|
| Source file | Repaired in place | Copy used, source unchanged |
| Damaged data | Discarded | Broken sections skipped, rest exported |
| Message preview | None | Preview before export |
| Free space | 20 percent of database size suggested | 256 MB above database size for dirty or locked files |
| Price | No charge | Starts at $99 for 2 PCs |
For PST export after a failed eseutil /p, How to Convert EDB to PST shows the numbered steps. Eseutil Commands Reference lists the other eseutil switches.
- Eseutil /p hard repair discards the pages, rows and tables it cannot fix. You cannot undo it.
- Try soft recovery and a backup restore before a hard repair.
- Save your database files elsewhere and export your mailboxes first.
- After eseutil /p in Exchange 2007, follow with Eseutil /D, Isinteg and a full backup.
- Empty a repaired database that shows a repair count of 1 or higher.
Univik Software opens a duplicate of your damaged database and exports the mailboxes you cannot lose. Trial edition saves 10 messages per folder. Licences start at $99 for 2 PCs.
Free Download See all featuresQuestions About Eseutil /p Hard Repair
Does eseutil /p cause data loss?
Yes. Microsoft's Exchange 2007 page says eseutil /p hard repair loses some of your data and can discard rows from tables or even entire tables, per Eseutil /P Repair Mode for Exchange 2007.
Can you undo eseutil /p?
No. Microsoft says you cannot undo the changes a repair makes to a database, per Repairing Exchange Databases for Exchange 2003. Only a copy saved before the repair still has the original data.
Do you need eseutil /d after eseutil /p?
Yes, in Exchange 2007, unless the repaired file only serves as a mail source before you delete it. Microsoft says offline defragmentation should follow a repair, per Eseutil /D Defragmentation Mode.
Do you still need Isinteg after eseutil /p?
Yes, in Exchange 2007, where Microsoft says Isinteg with the fix option finishes a repair. Exchange 2010 SP1 added New-MailboxRepairRequest, which repairs a mailbox while the database stays online.
Does eseutil /p invalidate your backups?
Yes, in Exchange 2007. Microsoft says you can still restore an older backup, but log replay ends at the point of the repair. Take a full backup soon after the repair.
How much time does eseutil /p need?
Microsoft gives no figure. Its Exchange 2003 page says a repair takes much longer than a restore from backup, per Repairing Exchange Databases.
Where do you see the repair count?
Use eseutil /mh to see the Repair Count and Repair Date lines, as Microsoft shows for Exchange 2007. In Exchange 2010 and 2013, add the /vss switch to check a VSS copy while the database stays online, per Exchange 2010 / Exchange 2013 – Determining the repair count of a database.
Can you get mail out when eseutil /p fails?
Yes. When eseutil /p fails, Univik Software reaches the mail in your damaged .edb on a Windows 11 or 10 PC. Installing Exchange Server or Outlook on your PC is not required.