Exchange Backup Repair

How to restore Exchange database when Exchange BKF file gets damaged or not available?

Exchange Information Store or database holds user mailboxes mounted on an Exchange Server. It comprises of three files i.e., EDB or primary database, Transaction Log and STM or Live Streaming Media File. Live Streaming media content has been assembled in EDB database with MS Exchange Server 2007 and higher versions. EDB file is main constituent of an Exchange Information Store and may become corrupt or inaccessible due to several reasons such as faults in networking cable and others. Network administrator can store all EDB files of an Exchange Database Directory List in a Windows Backup or BKF file. The Exchange Backup or BKF file is used by the network administrator to retrieve original EDB files in extreme situations such as Exchange Server disaster.

However, Exchange BKF files too are not free from corruption threats. NTBackup utility of MS Windows cannot restore EDB files from a corrupt or damaged Exchange BKF file. If your Exchange BKF file is damaged due to CRC errors or virus codes, then you can use inbuilt database repair tool of MS Exchange Server. You can restore original Exchange database with inbuilt tool in following steps:

  • Click>Start>Run
  • In the command box, type "cmd" and press Enter to open DOS command prompt
  • Open Program Files\Excsrvr\bin directory at command prompt and type Esseutil
  • The command line will look like this C:\ Program Files\Exchsrvr\bin> Esseutil

Esseutil utility supports only offline defragmentation, integrity check and hard repair of corrupt Exchange databases. Therefore, before running Esseutil command, ensure that selected Exchange databases are dismounted from Exchange Server. You can use any repair switch /p or /r with Esseutil to perform hard database recovery. The command line will appear like this:

  • Esseutil/p EDB or log file name
  • Esseutil/r EDB or Log file name

After recovering Exchange Information Store with Esseutil.exe utility, you are also required to perform complete database integrity check with Isinteg.exe utility of MS Exchange Server. Isinteg utility fixes some unresolved corruption errors of Exchange Database files. Isinteg.exe is also located in same directory path i.e., Program Files\Exchsrvr\Bin. Command line to perform complete integrity check on all un-mounted EDB and Transaction Log files is:

  • Isinteg -s Servername [-fix]

It will detect and list all errors of Exchange Database files. You must use Isinteg command till no error is reported or shown on Exchange Server. Both Esseutil and Isinteg commands help network administrator to retrieve EDB or Log files when Exchange BKF file is damaged or not available. However, if you're unable to retrieve original Exchange database file with inbuilt options, then we advise you to choose a proficient Exchange BKF File Repair tool. A smart Exchnage BKF recovery tool can quickly fix CRC errors, Page checksum errors and other corruption issues of EDB backup folder. It quickly restores user profiles or mailboxes on Exchange Server from corrupt BKF files. Exchange BKF recovery tool completely supports backup archives created with any version of MS Windows.