EDB to PST Tutorial

Exchange Server Recovery

Microsoft Exchange Server is an email server application which is often used by companies to handle their email, contact and calendar data from a centralized location. The entire Exchange server data gets stored in the form of EDB files that can be many GB’s in size. Any unfavorable event can cause corruption of these Exchange server data (.EDB). When power failure or any other abnormal server failure takes place, the Exchange Server mailboxes become inaccessible. Thus, a severe data disaster situation arises.

Components of Exchange Database (EDB) file –

Exchange EDB file is made up of server component which is based on the standard database technique. This email server system has embedded database engine, which lays out structure of disk of the Exchange Server. Major components of EDB file are as give below:

Information Store:This is the key component of server; it has two separate databases - private information store and public information store. It works with MAPI and database engine to make sure that all operations are stored on server hard drive.
JET Database Engine:Exchange databases are based upon JET format that uses log files to maintain and track information. It collects information and store them in systematic way.
Corruption in Exchange Database –

Like other database files, Exchange server EDB database is also very susceptible to any unfavorable events occurring to your system. Exchange server administrators often come across such issues which usually occur due to virus infection, improper system shutdown, application malfunction, user errors and missing database objects. There are two main types of database corruption, which require Exchange Repair to be resolved:

Internal or Logical Corruption: Such errors occur due to damaged or missing database objects such as database engine failure and information store corruption. This type of corruption could also occur at application level in folders, mailboxes, messages and attachments.
External or Physical Corruption: This type of corruption errors occur when entire database gets damaged on the hard drive.

To overcome such Exchange server corruption situations, Exchange provides two repair tools - Eseutil and Isinteg. These utilities help you to repair, recover and restore corrupt database in minor situations. Before applying these utilities you must create a backup of existing EDB database if it is possible as it may harm your database. In case of severe EDB corruption issues, these utilities get fail.

You are recommended to look for the best available alternative, Exchange Server Recovery tool. It is much powerful and advanced tool and capable to provide you the best possible result. There are two modes of Exchange EDB recovery: Standard Scan & Advanced Scan. Standard scan is fastest mode and extracts the user mailboxes from a corrupt EDB database, recover mailboxes, and then save it to MS Outlook .PST files. Advanced scan mode is slower than the first mode, but scans the severely corrupt EDB database thoroughly, recover it and then save it in Outlook .PST file or to a Live Exchange Server. This mode is more effective than the first mode.

Significant features of Exchange Server Recovery tool–
  • Repairs EDB errors and recovers Exchange mailbox data
  • Fixes all minor and severe Exchange server corruption issues
  • Provides "Ask for EDB Version" option to make selection of Exchange Server to proceed proper recovery of affected files
  • Recovers data from Database.edb, Public Folder Database.edb, Priv1.edb, Pub.edb databases
  • Export the recovered EDB database to the Productive Exchange Server or Office 365
  • Recovers deleted mailboxes, folders and items. Supports recovery of all attachments and allows you to save them in various formats like PST, MSG (Unicode/ ANSI), EML, HTML, TXT and RTF files
  • Embedded with two Exchange EDB recovery modes - Standard Scan & Advanced Scan.
  • Empowered with advanced settings that optimize and improve restoration of EDB files
  • Executes the simultaneous recovery of multiple corrupt EDB mailboxes and produces the output files in either Outlook PST or stores directly to the Live Exchange Server.
  • Provides the facility to filter duplicate items to avoid confusion.
  • Use duplicate items filter to remove similar entries while exporting data.
  • Supports all versions of MS Exchange server and MS Outlook
  • Compatible with all Windows OS, including Windows 10
  • Available with free trial version
  • Quickly send your Exchange database files to Public folders (pub1.edb) and Archive Mailboxes
  • Improved search performance to find specific items and save them in the shortest time period.
  • Move specific items of particular dates with total accuracy by filtering calendar settings in date-range filter.
  • Extended recovery of user mailboxes from EDB file supporting Exchange Server version 2013 and 2016.
  • Conversion of Unicode characters with total precision, without concerning about the data in foreign languages like Chinese, Japanese, French etc.
Download free trial version –

Free trial version of Exchange Server Recovery tool is available which can be easily downloaded and installed on your system. It helps you to get a fair idea about the tool’s functionality and performance. This version allows you to move 25 EDB file items per folder to live Exchange Server/ PST file/ Office 36 platform.

Download Software Demo
Software Related Topics

No need to panic for this, you can simply use EDB Recovery software to restore your crashed or damaged Exchange Server Database. With the help of this tool you can easily  extract mailbox items such as emails, contacts, distribution lists, calendars, meetings, events, journal, task draft, notes, etc.

Reham Pastra . 4th Aug 2016
How to resolve Exchange Server Error 0x80004005 Harrison Broad . 29th Apr 2016 . 1 Reply

Reason behind generation of Exchange Server error “0x80004005”

  • Accidental deletion of log files which are under writing process
  • Failure in mounting database or mailbox database
  • Abrupt system shutdown affecting log files
  • Corruption of database due to logical or physical error

How to detect Exchange Server error “0x80004005”?

This error is generally received while mounting mailbox database or while mounting public folder database on Exchange Server.

Mailbox Database Error Exchange is unable to mount the database that you speciefied. Specied database:
d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed:
Unable to mount database. (hr=0x80004005,ec=-2147467259

How to check and repair root cause of Exchange Server error “0x80004005”?

1.Run following command to repair the corrupted database:

Mailbox Database Error, Error: eseutil/p “C:Program FilesMicrosoftExchange
ServerV14MailboxMailbox DatabaseMailbox Database.edb”

2.If the issue still exists, then check Database Log files:
eseutil/ml”C:Program FilesMicrosoft Exchange
ServerV14MailboxMailbox DatabaseE00

A list of log files will appear after running the command. You will receive an error if they are in bad state. However if the log files do not show any sign of error, then you need to follow any of the three further mentioned methods to resolve this error.

A. Preparing AD:

  1. Get the Exchange Server CD run Setup AD command to prepare the Active Directory service for the corrupted Exchange Server. Running this command you will be able to restores Exchange Server configuration in Active Directories.
  2. Start the Exchange Server Help
  3. Go to the Contents tab and click Deployment
  4. Choose New Installation and then click Preparing to Deploy Exchange Server
  5. Select how to prepare active directory and domains


B. Addition to manage auditing and security log:

  1. Open domain controller and mention the account credentials
  2. Go to Start menu and choose Administrative tools
  3. Select and open Domain Controller Security Policy and click Settings MMC
  4. Open Local Policies and select User rights Assignment
  5. Select Manage auditing and security log form the right pane menu
  6. A new dialog box will appear. Select Add user or group and mention the required information, then click OK
  7. Close all the windows and open MS Exchange information store service to check the status of Exchange Server.


C. Using third party application:

Here we are explaining quick retrieval procedure of Exchange Server by utilizing Exchange Server recovery software, as this software has been considered as the most reliable and potential software by far. User can easily download its free version from the website directly and run its setup within seconds. Follow the below mentioned steps after installing the setup.

  1. Launch the software exe, a window will appear asking you to choose the source Exchange database
  2. Select STM or EDB files which you need to recover. You can either use the search option to find the required files if location is unknown or can use browse option in case the location is known. Then click Next and select Repair option
  3. The software will start repairing the files and within seconds, it will enlist all the files with their components in hierarchal order
  4. Select and preview the files for verification purpose
  5. Click Save button after getting satisfactory results
  6. Choose any of the enlisted formats to restore the files. You can also choose any cloud based destination to relocate the file

Out of the three-mentioned methods, third one is most reliable and quickest one to resolve the error. It completely depends on user to choose any of them, considering the situation and requirements and resources. See more info at: http://www.edbtopst.com/

Colinen Rich . 29th Apr 2016
How I can get my deleted EDB Files? Victor Valdes . 2nd Sep 2014 . 1 Reply

No problem you can simply download Exchange Recovery software. It is easy to use and recover your all Exchange Server Data without any error. Before purchasing this software you can try free trial version of the software.

Carlos Nunez . 5th Sep 2014

Some time it will happen. First of all close the Exchange Recovery software and reopen it. Select the Corrupted EDB file and click next. On the Select Recovery Mode step select the option "Use Disk Space" and click finish to run the process. Your problem will be solved.

Sophia Loren . 20th Aug 2014