I have an Exchange EDB database file from a dead server and need to get mailboxes out of it, but I have no working Exchange server to mount it on.
How do I open or extract from an EDB without Exchange?
I have an Exchange EDB database file from a dead server and need to get mailboxes out of it, but I have no working Exchange server to mount it on.
How do I open or extract from an EDB without Exchange?
An orphaned EDB with no server is a common disaster recovery situation, and the routes split by whether you can stand up an Exchange to mount it or need to read it directly, so both:
The native route if feasible, mounting on Exchange: the officially supported way to read an EDB is to mount it on a matching Exchange server, so a recovery database on a working Exchange of the same version, restoring the EDB into a recovery database and extracting mailboxes with New-MailboxRestoreRequest, is the Microsoft path. The catch is needing that matching Exchange, which the dead server scenario often lacks, plus the EDB usually needs to be in a clean shutdown state, checked with eseutil /mh and repaired with eseutil if it is in a dirty shutdown, itself a delicate step.
The direct read route, third party EDB tools, the practical answer for no Exchange: dedicated EDB reader and converter tools open the EDB file directly without any Exchange server, browsing mailboxes and exporting them to PST, EML or importing to a live Office 365 or Exchange, exactly the standalone reading the dead server scenario needs. SysTools EDB Converter and similar tools handle the EDB structure directly, which is why they exist, for the orphaned database no longer has a server. This is usually the realistic route when there is no matching Exchange to mount on.
The dirty shutdown consideration either way: an EDB from a crashed server may be in a dirty shutdown state, meaning it has uncommitted transactions in logs and clean handling matters, eseutil /mh reports the state, a soft recovery with eseutil /r replaying logs brings it clean if the logs are present and only a hard repair with eseutil /p as a last resort when logs are lost, since /p can lose data. Good EDB tools handle dirty shutdown states during reading, part of what you pay them for.
The route by circumstance: a matching Exchange available makes the recovery database the supported path, no Exchange makes a direct EDB tool the practical one and a dirty shutdown adds a recovery step either way. For the typical dead server with no replacement Exchange handy, the direct EDB reader tool extracting mailboxes to PST is the route that actually gets the mail out, mounting being unavailable by the nature of the situation.
No matching Exchange available so the direct EDB tool route was the only practical one, it opened the file standalone and exported the mailboxes to PST despite a dirty shutdown state it handled itself. The eseutil state explanation helped me understand what the tool was dealing with. Mail extracted from a truly dead server.