Microsoft Exchange Server Recovery — Email, Mailbox & EDB Database Recovery

Last Updated: 5 June 2026

Microsoft Exchange Server is the heartbeat of organisational communications — and when it fails, every email, calendar, contact and task in your organisation goes offline. The Original PC Doctor provides emergency Exchange Server recovery services for Australian businesses, recovering corrupted databases, deleted mailboxes, failed Exchange servers, and ransomware-encrypted Exchange environments with 24/7 emergency response.

We work with Exchange 2007 through Exchange 2019 and Exchange Online hybrid deployments, recovering at the EDB database level to extract individual mailboxes, entire stores, or specific items — regardless of whether the Exchange server itself is still running.

📧Exchange down? Call 1300 723 628 — emergency response 24/7.

Exchange Versions We Support

Exchange Failure Scenarios We Handle

• Exchange database (EDB) won’t mount — “dirty shutdown” state — the most common Exchange failure. An unclean server shutdown leaves the EDB in an inconsistent state. If transaction logs are available, we run a soft recovery. If logs are missing or corrupted, we extract directly from the EDB using low-level database tools.
• Exchange EDB file corrupted — ESEUTIL /mh shows corrupted state — database pages corrupted by a hardware fault, bad sectors on the underlying drive, or a partial write during a power failure. We repair at the page level and extract all accessible mailboxes.
• Exchange database hard drive failed — the physical drive hosting the EDB and/or transaction logs has failed. We perform physical drive recovery first, then Exchange database recovery from the recovered image.
• Exchange RAID array failed — the underlying storage array for the Exchange mailbox database has gone offline. Full RAID reconstruction followed by EDB recovery.
• Accidentally deleted mailbox — retention period expired — Exchange Dumpster (deleted item and mailbox retention) has a configurable retention window. If a mailbox was deleted and the retention expired, we recover directly from the EDB file at the database level.
• Exchange transaction logs missing or corrupted — logs required for a clean database mount were deleted, corrupted, or ran out of disk space. We use database-level extraction to bypass the log replay requirement.
• Ransomware encrypted Exchange databases and logs — EDB and log files encrypted by ransomware. We assess for VSS shadow copies, undamaged backup sets, and Exchange-specific recovery options. With a decryption key we perform decryption and database repair together.
• Exchange database size limit exceeded — store dismounted — legacy Exchange 2003 and 2007 databases hit the 75GB or 18GB store size limit and automatically dismount. We extract mailboxes from the full database and migrate to a new environment.
• Failed Exchange migration or upgrade — migration from Exchange 2010/2013 to Exchange 2016/2019 or Exchange Online that failed mid-process, leaving mailboxes in an inaccessible state.
• Exchange server hardware replaced — database won’t import — moved EDB files to new hardware but Exchange won’t mount due to mismatched Exchange organisation or server name. We mount externally and extract.

Exchange EDB Recovery — How It Works

The Exchange database (EDB file) is a JET database that stores all mailbox data — messages, attachments, calendar items, contacts, tasks and notes — in a single database file (or multiple in DAG configurations). Our Exchange recovery process works at this database layer, independently of the Exchange server software:

• We mount the EDB directly using professional Exchange recovery tools, bypassing the need for a running Exchange server or Windows Active Directory environment
• We can extract individual mailboxes as PST files for import into any Exchange, Office 365 or Outlook client
• We can extract specific date ranges, specific folders, or complete mailbox exports
• We work with corrupted, oversized, dirty-shutdown and partially damaged EDB files that Exchange itself cannot mount
• For large enterprise environments, we can restore directly to a new Exchange server or import directly into Exchange Online

Our Exchange Recovery Process

1. Emergency phone assessment — call 1300 723 628 and describe the Exchange version, the failure mode (dismounted database, physical drive failure, ransomware, etc.) and the urgency. We’ll advise immediate safe steps.
2. Secure collection of EDB files — if the Exchange server is accessible, we can copy the EDB and log files for remote analysis. If the server or storage has physically failed, we recover the storage device first.
3. Database integrity analysis — we analyse the EDB file header, page-level integrity, and transaction log sequence to determine the best extraction approach.
4. Mailbox extraction — we extract all accessible mailboxes to PST format with a full inventory. You see exactly what’s recoverable before any work is charged.
5. Delivery or direct import — PSTs are delivered for import by your IT team, or we perform direct import into your new Exchange environment or Exchange Online tenant on request.

Free Resources

Independent, non-commercial references:

• Standard RAID levels (Wikipedia)
• Network-attached storage (Wikipedia)

FAQs — Exchange Server Recovery

How much does Exchange recovery cost?

Exchange recovery from a corrupted or dismounted EDB (where the database is accessible) typically starts at $1,200–$2,500 AUD. Cases involving physical drive failure or RAID failure underneath Exchange add the physical recovery cost. Large enterprise environments or DAG recovery are quoted on a project basis. Call 1300 723 628 for an immediate assessment.

Can you recover a mailbox that was deleted from Exchange?

Yes — even after the Exchange retention period (Dumpster 1.0 / 2.0) has expired. We work directly at the EDB database level, where deleted mailbox data is often present in the database free pages long after Exchange’s own retention mechanisms have purged the reference. The recoverability depends on how long ago the deletion occurred and how much new email activity has occurred to overwrite those pages.

The Exchange database is in dirty shutdown and won’t mount — can you fix it?

Yes. Dirty shutdown is the most common Exchange recovery scenario we handle. If the required transaction logs are present, we perform an offline soft recovery (ESEUTIL /r) to bring the database to a clean shutdown state. If logs are missing or corrupted, we use low-level database extraction tools to extract mailboxes directly from the dirty database without needing to mount it at all.

Can you recover Exchange after a ransomware attack?

We assess several recovery vectors: VSS shadow copies of the Exchange database volume (often deleted by ransomware but worth checking), Exchange Online Hybrid sync copies if any mailboxes are dual-homed, unaffected backup copies on separate storage, and partial plaintext recovery from un-overwritten disk sectors. If you have the decryption key, we perform both decryption and database repair. Call us immediately after a ransomware event — the sooner we assess the more recovery options are available.

Do you need the Exchange server itself, or just the EDB file?

Just the EDB file (and transaction logs if available). We don’t need a working Exchange server, Active Directory, or any Windows Server environment to perform Exchange recovery. If you can copy the EDB file to an external drive or network share, we can begin remote analysis immediately.

📞Call 1300 723 628 for free expert advice — or book online now.