Recovering a Corrupt Exchange Database with Stellar Repair — Real-World Lab Test

Why Stellar Repair for Exchange Caught My Eye#

I’ve spent enough years in the trenches with Exchange to know one thing for certain. When a database goes dirty, your weekend is already over.

Microsoft hands you eseutil and a few other tools. Fine for tidy problems. In a real disaster, though, it’s a butterknife at a gunfight.

That’s the gap Stellar Repair for Exchange tries to fill. One job, nothing fancy: take a corrupt EDB file and make it readable again.

A 4.9/5 Trustpilot rating told me I wasn’t the only one wondering whether it delivers.

The Test Lab: Building a Realistic Disaster#

You don’t trust recovery software on a hunch. So before anything else I stood up a lab that looked like a real environment. Two boxes:

• HQ-DC01 - Windows Server 2019, Active Directory Domain Controller
• HQ-EXCH01 - Windows Server 2019, Exchange 2019 CU15

Three demo users. A handful of emails going back and forth, a few calendar invites thrown in. The goal was to make the database feel lived-in, like an ordinary Tuesday at the office rather than an empty test rig.

Making a Mess: Dirty Shutdown on Purpose#

Now the fun part.

Exchange logs hold the database together. They keep it consistent. So I deleted half of them. Then I killed the “Microsoft Exchange Information Store” service. That was enough to shove the database straight into a dirty shutdown.

To confirm:

1
eseutil /mh '.\DB01-Mailbox.edb'

Dirty. Exactly what I was after.

Exchange now flatly refuses to mount the thing. Disaster achieved, on schedule.

Recovery with Stellar Repair for Exchange#

Recovery Options That Matter#

From here, your choices open up. You can:

• Export to PST
• Export to MSG, EML, HTML, RTF, PDF (single items)
• Export back to Exchange Server
• Export directly to Office 365
• Even push data into a Public Folder

For the lab I chose Export back to Exchange. One catch worth knowing about: Outlook has to be installed on the same machine as Stellar. In production you’d run this on a separate VM. Trust me on that one.

The recovery scope is wide. Stellar pulls back nearly everything a mailbox holds: emails and their attachments, contacts, calendars, tasks, notes, journals, even Public Folder content.

It covers Exchange Server versions all the way from 5.5 up through 2019.

WARNING

As of this test (July 2025), Exchange 2019 CU15 was used. Support for newer versions, if released, should be verified with Stellar.

Rebuilding the Mailboxes#

Over in the Exchange Admin Center:

1. Disabled the broken mailboxes (so user accounts remain in AD)
2. Created fresh mailboxes with _restored suffix
3. Logged in to confirm: clean, empty

Back in Stellar:

• Right-click mailbox → Export to Exchange Server
• Provide Exchange server and credentials
• Click OK

Then repeat for every mailbox and let it sync.

Key Takeaways#

• Ease of use: Zero PowerShell gymnastics, just point and click
• Compatibility: Works with Exchange 5.5 up to 2019
• Recovery options: PST, Office 365, Public Folders - take your pick
• Safety net: When eseutil leaves you stranded, this saves your bacon

Final Thoughts#

This isn’t an ad. It’s the sober readout after I broke Exchange on purpose and watched what happened: Stellar Repair for Exchange works.

If you run Exchange servers and don’t keep something like this in your back pocket, you’re betting against downtime. That’s a bet you lose eventually.

My advice?

Build a lab. Break your own database. Run the recovery yourself and watch it come back. Far better to learn this on a quiet afternoon than at 3 AM on a Sunday.

Learn more about Stellar Repair for Exchange