Microsoft Exchange Recovery Tool

An Exchange Server backup software issues a backup routine that calls the operating system to read 4 KB database pages (that are saved on the hard disk), and then to write data on the backup tape. This routine also includes a process to read the checksum value of each database page header, before writing data to tape. This checksum value is then compared with the corresponding value returned while reading the page. If for some reasons, like database corruption, these values do not match each other, Microsoft Jet Database Engine reports backup failure and prompts some error message. Such situations require that the administrator applies Exchange Server Recovery measures.

Such problems will be more clear with the further scenario. An Exchange administrator runs a backup process for its Exchange Server Information Store database. It observes that the backup could not be completed. Further, when it views the application log, it encounters the below error written in the description section of event logged:

“Information Store (3732) 23aca049-4dfa-4e45-b2f8-64c5414a947a: The backup has been stopped because it was halted by the client or the connection with the client failed.”

The associated event ID can be 215 or 447.

Cause

Some possible reasons for the above error to occur are:

• You have installed a third-party event sink that is incompatible or being problematic
• You are using a backup application that is incompatible or being problematic
• The hard disk or hard disk controller is faulty
• You are trying to backup a corrupted Exchange database

Solution

The suggested measures to solve the above problem are:

• Uninstall the third-party event sink.
• Try to use a different backup application, preferably suggested by Microsoft like, NTBackup or try to reinstall the existing backup program.
• Check the system log for probable hard disk and hard disk controller issues. Based on the issue, perform operations like repairing hard disk by running chkdsk and installing the recent driver and firmware updates.
• Repair the corrupted database using ‘Eseutil’ hard repair commands on a backup of database. If the resultant database has some important data missing, use a third-party, safe Exchange Recovery utility. A Microsoft Exchange Recovery software can scan and repair corrupted Exchange database using effective scanning algorithms.

Exchange Mailbox Recovery is a professional utility that repairs corrupted Exchange database and extracts the mailboxes as separate *.pst files. Incorporated with deleted mailbox recovery feature, this Microsoft Exchange Recovery utility supports MS Exchange Server 2007, 2003, 2000, and 5.5.

An Exchange Server database is susceptible to different corruption problems, such as dirty database shutdown, antivirus scanning, log file issues, and others. Thus an administrator might require different Microsoft Exchange Recovery tools to solve such problems and to continue working the e-mailing environment.

Further is a scenario that depicts a similar situation of Exchange Server database corruption. As an Exchange Server administrator, you may observe one or more of the below symptoms:

1. You cannot start and/or Information Store service
2. Exchange clients lose the ability to send or receive e-mails. You cannot solve this issue by restarting the server
3. You restore the database from an offline backup but the database is still inconsistent. On running Isinteg utility (database integrity check), it gives the below error message on screen:

“Error 4294966746: JET_errDatabaseInconsistent”

Cause

Information Store is corrupt. Either both or one of public store and private store is corrupted.

Solution

Before trying the below steps, you are recommended to take the backup of the entire Information Store to prevent any post-crash consequences. Use the below steps in order to solve the above problem:

1. Analyze all the error message and events of application event log that Exchange reports on attempting to start the Information Store

2. Run eseutil /mh command to check the integrity of Exchange databases (Priv.edb and Pub.edb). An inconsistent database shows ‘Dirty Shutdown’ state but is not always corrupt. This state can also occur if all the transaction logs have not been committed yet.

3. Replay all the transaction log by performing soft database recovery. For this, execute eseutil /r command for the affected database(s).

4. Run hard database repair in case soft recovery doesn’t work. Run eseutil/ p command and delete all the .chk and .log files

5. Check if the previously occurring symptoms go away. If you can successfully work with the database(s), they are repaired. Next, run eseutil /d and isinteg -pri -fix -test alltests commands in sequence to defragment and fix database issues respectively.

6. In case, the problem remains the same, use a third-party Exchange Server Recovery tool to diagnose and repair the database more effectively. A Microsoft Exchange Recovery utility uses safe, yet powerful, scanning procedures and allows for easy database repair.

Exchange Server Recovery Tool is a professional utility that repairs corrupted Exchange database and extracts the mailboxes in individual *.pst files for Exchange Server 2007, 2003, 2000, and 5.5. The tool provides advanced Exchange Server Recovery features and is easy to use. It can also recover deleted mailboxes and inaccessible STM data.

New Features of Exchange Server Recovery Software:

Exchange 2007 Recovery

Exchange 2003 Recovery

In Microsoft Exchange Server, you can check and fix the integrity and consistency of Information Store database using Isinteg.exe utility. This built-in command-line tool works on all information store databases such as public information store, Pub.edb, and private information stored, Priv.edb. However, in some cases, you encounter errors while trying to resolving information stored database issues in Exchange Server, and the process fails. The problem persists and you can not access data from Exchange Server database. This behavior leads to data loss and need Exchange Server Recovery to be sorted out.

In a practical scenario, you may come across the below error message when you run the Isinteg -patch on MS Exchange Server that is running on Microsoft Cluster Server:

“The private store could not be updated
Reason: JET_errKeyDuplicate”

Before running the Isinteg -patch tool on Microsoft Exchange Server computer, which is running on the Microsoft Cluster Server, it is essential to set environment variable _CLUSTER_NETWORK_NAME_ to ERG (Exchange Resource Group) name. For instance, when the ERG network is named as EXCLUSTER, type the below as command prompt:

SET_CLUSTER_NETWORK_NAME_=IP ADDRESS NAME

• Here IP ADDRESS NAME is name assigned to IP ADDRESS resource in Exchange Resource Group. It is essentially NetBIOS name of exchange Server computer.

In such circumstances, the Isinteg utility fails after restore the database, which was forklifted from the stand-alone Exchange Server computer to the clustered Exchange Server computer.

The failure occurs if the value of _CLUSTER_NETWORK_NAME_ environment variable is incorrect. It can be due to typographical errors. After the environment variable is set, you can not change it.

If you have incorrectly set the environment variable on your Exchange Server database, the database corruption or inaccessibility situations may occur. In such circumstances, you must perform complete restore of the database as you can not change cluster name in information.

Inaccessibility of the Exchange Server Database (EDB) file leads to data loss situations and need Exchange Recovery to be sorted out. Recovery is best possible with the help of powerful and advanced third-party EDB Recovery Software.

These applications are particularly designed to carry out in-depth scan of entire EDB file and extract all damaged, inaccessible, and corrupted mailboxes. The Exchange Recovery tools have read-only and non-destructive conduct to retrieve your data safely.

Microsoft Exchange Recovery is a comprehensive edb recovery tool and ensure absolute recovery of all EDB file objects including emails, notes, contacts, tasks, journal, and more. The software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Microsoft Exchange Server 2007 includes several data security and database improvements that give an appearance of a relatively safer application. The prime enhancements that this version provides are extended database size limitation up to 16 TB, increased number of storage groups per server, improved antivirus, anti-spam protection, and more. Despite of these improvements, Exchange database corruption is not an exception. An Exchange Server 2007 database is vulnerable to get corrupt because of Dirty shutdown, application issues, and the like common causes. The prime solution to deal with such problems should be use Exchange repair utilities or to restore from backup. But if none of these measures works, you require an Exchange Recovery utility.

Consider the following practical example of such problems. You use Exchange Server 2007 and observe database corruption with the following symptoms:

• You try to copy the database, but the copy operation fails reporting an I/O error in system log, such as below:

The driver detected a controller error on \Device\Harddisk0\DR0.

• When you try to move a mailbox from the corrupted store to a new one, it cannot be accomplished with an error similar to below:

Unable to move mailbox mailbox_name.
A problem occurred while getting the properties for a message.
Parent folder name: Inbox; Message subject: RE: SND253P1 ; Error code: 0xfffffa0a.
Run ISINTEG to check for any problem in the database “First Storage Group\Mailbox Database

• As suggested by the above error, when you run ISINTEG utility to check the database consistency, you receive the below error:

MSExchangeIS (3932) First Storage Group: Data inconsistency detected in table table_num of database database_path

Also, the ESEUTIL /p repair operation fails to fix the database corruption.

Such situations indicate database corruption to an extent that it cannot be repaired and dealt using MS Exchange utilities. To extract the mailboxes, you need solutions like:

1. A database backup that can be used to restore.
2. A third-party repair Exchange Server Recovery utility that can repair and restore the database contents. An Exchange Recovery utility can use effective, yet safe, scanning algorithms to recover the lost data in intact form.

Exchange Recovery Tool is a professional utility with ability to recover mailboxes from a corrupted Exchange database in individual *.pst files. The Exchange Server Recovery application supports Exchange Server 2007, 2003, 2000, and 5.5. The tool also supports recovering deleted mailboxes and STM file data in an e-mail body.