Exchange Server Recovery
Exchange database recovery starts at the drive level. When the server's storage has failed, tools like eseutil cannot access the EDB file. We image the drive using PC-3000, mount the recovered EDB, and extract individual mailboxes to PST files. Exchange 2003 through 2019. No data, no fee.
EDB File Structure and Corruption Patterns
Exchange Server stores all mailbox data in EDB files using the Extensible Storage Engine (ESE), the same database engine that powers Active Directory (NTDS.DIT). Each EDB contains a B-tree structure of mailbox tables, attachment tables, and folder hierarchies. Transaction logs (E00, E01, etc.) record every write before it reaches the EDB, providing crash recovery.
The ESE engine uses a page-based architecture. Exchange 2007 and later use 32KB pages; Exchange 2003 uses 4KB pages. Each page has a checksum computed at write time. During read operations, ESE validates the checksum and reports -1018 (JET_errReadVerifyFailure) if it does not match. A single -1018 error on a critical page can prevent the entire information store from mounting.
Common failure scenarios:
- Dirty shutdown: The Exchange services stopped without flushing in-memory pages to the EDB. The database is in an inconsistent state. Normal recovery replays transaction logs, but if the logs are missing or the drive is failing, soft recovery (
eseutil /r) fails. - -1018 checksum errors: Physical drive degradation caused incorrect data to be read back. The ESE engine rejects the page. If the errors are concentrated in mailbox table pages, specific users lose access to their email. If the errors hit the database header or space tree, the entire store will not mount.
- JET_errLogFileCorrupt: Transaction logs are damaged or missing. Soft recovery cannot bring the database to a clean shutdown state. Mounting fails with error -501 or -528.
- Oversized EDB on degraded storage: Exchange databases grow over years and eventually exceed the performance envelope of aging drives. Heavy fragmentation plus marginal sectors leads to intermittent failures that escalate to full store dismount.
When eseutil /p Makes Things Worse
The eseutil utility ships with Exchange Server and has several modes. The dangerous one is eseutil /p (hard repair). This mode walks every page in the EDB and discards any page that fails checksum validation. It then rebuilds the database metadata without the discarded pages. The result is a structurally valid EDB with missing data.
Microsoft positions eseutil /p as a last resort: "Data loss is almost guaranteed. You should seriously consider alternative solutions prior to using the /p switch." The typical recommendation sequence is: restore from backup first, try soft recovery (eseutil /r) second, and only use /p if both fail.
The problem: when the EDB corruption originates from a physically failing drive, eseutil /p reads the same damaged sectors that caused the corruption in the first place. It discards pages that a proper drive recovery (with PC-3000 adaptive read parameters) would have recovered cleanly. Running /p on the original drive also writes the "repaired" database back to the same failing media, compounding the risk.
Before running eseutil /p: Power down the server. Do not run soft recovery, do not attempt to mount the store, do not run New-MailboxRepairRequest. Each operation writes to the transaction logs and modifies the database state. Contact us for a free evaluation of the drive's physical condition.
Post-Migration Recovery: Exchange Online to On-Prem Archive
A common scenario: an organization migrated from on-premises Exchange to Microsoft 365, decommissioned the old servers, and retained the drives in storage. Months or years later, someone needs data from an old mailbox that was not fully migrated, or compliance requires access to historical email.
The drives from the decommissioned server may have degraded in storage (head stiction from prolonged inactivity, lubricant redistribution on older drives, firmware clock issues). We image the drives, mount the recovered EDB in an offline Exchange instance, and extract the specific mailboxes to PST. The PSTs can be imported into Outlook or uploaded to Microsoft 365 archive mailboxes.
We do not need the server hardware, Active Directory, or Exchange configuration. The EDB is a self-contained database file. Given a clean copy of the EDB, mailbox extraction is a direct operation.
Our Exchange Recovery Workflow
Drive assessment and imaging
Evaluate the server drive's physical condition. Image with PC-3000 using write-blocking and conservative retry settings. If the drive requires mechanical repair (head swap, motor repair), that is performed first in the clean bench.
EDB extraction and integrity assessment
Extract the EDB and transaction log files from the cloned image. Run a page-level integrity scan to quantify damage: how many pages have checksum failures, which mailboxes are affected, and what percentage of data is recoverable.
Database repair and mounting
Repair damaged page headers and checksums. If transaction logs are intact, apply soft recovery to bring the database to a clean shutdown state. If logs are missing, rebuild the minimum required log stubs. Mount the EDB in an isolated Exchange instance.
Mailbox extraction and PST export
Enumerate the mailbox store and extract individual mailboxes to PST files. Each PST preserves the user's folder structure, email messages, calendar items, contacts, and tasks. Provide a manifest listing each recovered mailbox and item count.
Pricing
Exchange recovery pricing is based on the physical condition of the drive. Mailbox extraction and PST export are included at no additional charge. For RAID or SAN configurations, each member drive is priced separately.
| Service Tier | Price | Description |
|---|---|---|
| Simple CopyLow complexity | $100 | Your drive works, you just need the data moved off it Functional drive; data transfer to new media Rush available: +$100 |
| File System RecoveryLow complexity | From $250 | Your drive isn't recognized by your computer, but it's not making unusual sounds File system corruption. Accessible with professional recovery software but not by the OS Starting price; final depends on complexity |
| Firmware RepairMedium complexity – PC-3000 required | $600–$900 | Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access Standard drives at lower end; high-density drives at higher end |
| Head SwapHigh complexity – clean bench surgery50% deposit | $1,200–$1,500 | Your drive is clicking, beeping, or won't spin. The internal read/write heads have failed Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench 50% deposit required. Donor parts are consumed in the repair |
| Surface / Platter DamageHigh complexity – clean bench surgery50% deposit | $2,000 | Your drive was dropped, has visible damage, or a head crash scraped the platters Platter scoring or contamination. Requires platter cleaning and head swap 50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type. |
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
All tiers: Free evaluation and firm quote before any paid work. No data, no fee on simple copy, file system, and firmware tiers. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. For ultra-high-capacity drives (20TB and above), the target drive costs approximately $400+ due to the large media required. All prices are plus applicable tax.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.
Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
See our clean bench validation data and particle test videoExchange Recovery FAQ
Can you recover individual mailboxes from a corrupted EDB?
Should I run eseutil /p on my corrupted Exchange database?
Can you recover Exchange data after migrating to Microsoft 365?
What Exchange versions do you support?
How long does Exchange recovery take?
How is Exchange recovery priced?
Related Recovery Services
All supported database engines
MDF/NDF recovery, suspect mode, Error 5171
RAID 0, 1, 5, 6, 10 arrays
Dell, HP, IBM enterprise servers
Mechanical HDD recovery
NVMe, M.2, SATA solid state drives
Recover Your Exchange Mailboxes
Call Mon-Fri 10am-6pm CT or email for a free drive evaluation.