logo
search
Email Recovery

How to Recover an Exchange 2013 Database from an Inaccessible Drive

Emma BrownEmma Brown Oct 12, 2026 869 views

Question details

The user needs to recover a Microsoft Exchange 2013 database and its transaction logs located on a drive that has become inaccessible.

How to Recover an Exchange 2013 Database from an Inaccessible Drive
Product
Microsoft Exchange Server 2013
Device & OS
not provided
Scenario
The storage drive containing the critical Exchange database and transaction log files has failed or become inaccessible, preventing the database from mounting.
Observed behavior
The Exchange database cannot be accessed or mounted, leading to email service disruption and requiring safe data extraction or restoration without risking further corruption.
Before you start

Do not reinstall Exchange or run any disk repair operations (like CHKDSK) on the original inaccessible drive before preserving the data, as this can cause irreversible data loss.

Solution 1Recommended

Restore the Database from a Backup Using a Recovery Database

The safest and recommended approach is to restore your Exchange database and log files from a known good backup to an alternative drive.

By restoring your backup to an Exchange Recovery Database (RDB), you can extract mailbox data using the Exchange Management Shell without affecting your live production environment.

1
Restore files from backup

Use your backup solution to restore the Exchange 2013 database (.edb) and transaction log files to a healthy, accessible drive on your server.

2
Create a Recovery Database

Open the Exchange Management Shell and run the 'New-MailboxDatabase' cmdlet with the '-Recovery' switch, pointing the EDBFilePath and LogFolderPath to the restored files.

3
Mount the database

Mount the newly created recovery database by executing the 'Mount-Database' cmdlet in the Exchange Management Shell.

4
Extract mailbox data

Use the 'New-MailboxRestoreRequest' cmdlet to extract mailboxes from the recovery database and merge them directly into your production mailboxes.

Restore the Database from a Backup Using a Recovery Database
Administrator Validation: Always have an Exchange administrator validate the health of the restored database and log files using the Eseutil tool before attempting a production restore.
Free Microsoft Office alternative

Need a Reliable Office Suite? Try WPS Office

While server administrators handle complex tasks like Exchange database recovery, ensure your team stays productive with WPS Office. It is a lightweight, free alternative to Microsoft Office that offers full compatibility with Word, Excel, and PowerPoint documents.

  1. 1. Download the installer: Visit the official WPS Office website and click on the 'Download WPS Office Free' button.
  2. 2. Install the software: Run the downloaded installer and follow the straightforward on-screen instructions.
  3. 3. Open your documents: Instantly open, edit, and save your existing Microsoft Office files without losing any formatting.
Free and lightweight Office suite for everyday productivityFully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Familiar user interface ensuring a seamless migration for teamsBuilt-in PDF editing and format conversion tools
microsoft office alternative - wps office

Frequently Asked Questions

Should I try to repair the inaccessible drive first before recovering the database?

No. Running repair operations on a failing or inaccessible drive can permanently overwrite or destroy remaining data. Always attempt to extract or copy the data to a new location first.

What is an Exchange Recovery Database (RDB)?

An Exchange Recovery Database is a special kind of mailbox database that allows you to mount a restored database offline and extract data from it without disturbing user access to current production databases.

How do I know if my recovered Exchange database is safe to mount?

You should use the Eseutil utility (specifically the command 'Eseutil /mh') to check the header information of the database. It is safe to mount if the state is listed as 'Clean Shutdown'.