Exchange-EDB-To-PSTHistory of Exchange Server backs to April 1993 when it was introduced as a XENIX-based messaging system by Microsoft. Apart from being a server it is also serves the purpose of a mail client and a calendaring tool. Similar toother databases, Exchange server also stores its data in file called Exchange Databaseand records its transactions and activities in a corresponding Log file.

Exchange Database Files (EDB Files)

The EDB files comprisesof the complete data of Exchange Server. The EDB files are divided into two folders – Private and Public Folders.In earlier versions of Exchange such as Exchange 5.0 and Exchange 5.5 there were only two databases – priv.edb and pub.edb. But from Exchange 2000, additional files with extension.stm were being accompanied with the .edb files till Exchange 2007.

  1. Private Folder

The private folders consists of two files- priv1.edb and priv1.stm

  • priv1.edb

This file contains the personal and private emails that are associated with a particular user account. It contains messages in the form of Rich Text Formatted (RTF) messages.

  • Priv1.stm

This file contains non-RTF messages. It contains streaming data like audio and video. The extension .stm implies to streaming data for utilization as MIME (Multipurpose Internet Mail Extension) data.

  1. Public Folder

The public folder is also comprised of two files-pub1.edb and pub1.stm.

  • pub1.edb

It contains public data which is secured by the administrator. It can be accessed by any user that exists on the Exchange server.

  • pub1.stm

Similar to priv.stm file pub.stm also contains non-RTF messages.It contains streaming data like audio and video which is available to all users.

Data Loss Issues In Exchange

Exchange server has gained wide popularity in the corporate world owing to its efficiency in providing communication services and DR server. But if the Exchange server gets disrupted due to some issues it can make the users helpless. Issues or errors in Exchange server leads to corruption in the database files. Some common issues which cause data loss in Exchange files are:

  1. Jet Engine Errors

Exchange users experience data loss in EDB files due to Jet Engine errors. Few errors are:

  • JET_errRecordNotFound
  • JET_errKeyDuplicate Illegal duplicate key

The above mentioned errors lead to database corruption of Exchange server. The reason for Jet Engine errors can be the presence of bad sectors in the hard drive.Also if some data has been written incorrectly in the database file, it may lead to database corruption.

  1. Dirty Shutdown

Dirty shutdown is the stage when the system is shutdown in an improper manner. Some errors which are caused due to dirty shutdown are:

  • Database was not shutdown cleanly (Dirty Shutdown)
  • Unable to mount database (hr=0×80004005, ec=-528) 

Improper shutdown can happen either due to power failure or power surge.Transaction files keep track of all the major and minor changes in the database. In dirty shutdown state the transaction files have not yet being written to the database, therefore leading to corruption of EDB files.

  1. Database Hampering

At times malicious users may also deliberately hamper the Exchange database in order to make the database inaccessible. These users may do so by deleting some EDB files or full database so that it cannot be accessed in future.

  1. Server Outages

It is often possible that the Exchange server is down for maintenance. This leads to temporary inaccessibility of the database. Also it may happen that due to certain hardware or software issues may crash the Exchange server. Hence server outages lead to database corruption.

  1. Human Errors

Exchange Server users may sometimes hard delete (Shift+Delete) their data unknowingly. The hard deleted items get permanently deleted from the database and cannot be recovered manually.

Fix Exchange Issues ByExchange EDB to PST Conversion

The above mentioned errors make the EDB files of Exchange server corrupted and inaccessible. Therefore, in order to fix the corruption issues it is advised to implement Exchange EDB to PST conversion. The EDB files after conversion to PST format can be viewed in Outlook. Since EDB to PST conversion is not possible manually especially in the case of corruption, hence deploying a third party tool would be the only choice feasible. An external tool like Exchange EDB to PST Converter efficiently recovers EDB files if they have been deleted/corrupted. The tool converts the recovered EDB file to PST format which can be easily accessed in Outlook.

Conclusion

The corrupted or deleted EDB files render Exchange Server in an inoperable state. To overcome the database issues in Exchange server it is advised to convert Exchange EDB files to PST files. The conversion process will maintain the data integrity of the Exchange database files intact and the users will be able to continue working with their data files.