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.

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.

Stellar Information Systems Limited, 22-Jan-2010, Gurgaon, the pioneer data recovery company providing advanced EDB recovery solutions and services, today announced the launch of a new, updated version of its Exchange server repair solution- Stellar Phoenix Mailbox Exchange Recovery v3.0. With various end-user innovations, the upgraded Version 3.0 now repairs MS Exchange Server 2007 databases and also provides full native support for repairing Unicode EDB files. This release introduces a new deleted mailbox recovery feature and added capabilities that reduce costs and enhance the overall user experience.

Stellar Phoenix Mailbox Exchange Recovery v3.0 recovers STM data in e-mail body itself, which is a considerable improvement over its previous releases that used to recover it as an e-mail attachment. Also, the exchange recovery software now allows users to manually select the root Exchange Server version at ‘Select EDB File’ dialog-box with the added ‘Select Server Type’ option. The free demo version of the exchange server recovery product is available for download from company’s website that lists the mailbox(es) it can recover.

“Stellar Phoenix Mailbox Exchange Recovery v3.0 is the unified package that delivers full versions’ compatibility, accidental deleted mailbox recovery, and multilingual data recovery support . Together with several conforming features, the update helps administrators to achieve long-term database control.”said Sunil Chandna, CEO of Stellar Information Systems Limited. “This release provides organizations a way to lessen the operational losses while Exchange database corruption. With several reworked features, Exchange Recovery v3.0 is designed as a cost-effective and time-saving solution”

New Features of Mailbox Exchange Server Recovery v3.0:

1. Supports MS Exchange Server 2007

2. Recovers deleted mailboxes

3. Supports Unicode-formatted EDB files

4. Recovers STM data as e-mail body for Exchange Server 2003, 2000, and 5.5

5. Allows to select Exchange Server type- a new ‘Select Server Type’ option

Pricing

Stellar Phoenix Mailbox Exchange Recovery v3.0 is an affordable edb recovery solution, available in three different license options- Administrator, Technician, and Academic. The product range starts at $499 for Academic License.

Stellar Information Systems

Stellar Information Systems Limited is industry’s leader in providing data recovery software, e-mail recovery tools, database repair solutions, file repair utilities, data safety products, and data recovery services. Certified with ISO 9001:2000 standard, Stellar has more than 1,100, 000 satisfied customers worldwide.

Contact Information

For more information and product purchase options:

Call : +1-866-554-2512 (TOLL FREE)
Mailto: orders[at]stellarinfo.com.
Web Address- http://www.ms-exchange-server-recovery.com/

Exchange Server database corruption can occur for several reasons and if backup is present that is stable, you can use it to restore the database conveniently. A database backup alone is not sufficient to bring the database back to consistent state. It is because after restoration, database and log files are not in perfect sync with each other. So, you need to replay the transaction files in order to make the database consistent. This process is termed as ‘Hard Recovery’. The hard restore requires all backup sets to be in clean state or otherwise, this procedure may fail. In such instances, you left with no alternatives other than using an Exchange Server Recovery utility that can repair the original database.

As example, consider an instance when you experience dirty shutdown with Microsoft Exchange Server. The next time, when you try to mount the Information Store database(s), it fails and you receive errors suggesting that one or more database(s) are corrupt. You try to perform hard restore, but cannot do so and receive the below error message:

“JET_errLogCorruptDuringHardRestore -573”

The database recovery method fails and data remains inaccessible.

Cause

Error -573 indicates that Exchange Server has detected some corruption in a backup set and cannot proceed.

Solution

You can try applying these solutions to solve such problems:

1. Check for some other backup set that may be used to restore the database and carry out hard restore

2. Run ‘ESEUTIL /P database_filename.edb’ command to repair the database, where ‘database_filename’ is the name of the corrupted database file. But during repair, the command can discard table rows and even complete tables. So, it is suggested to backup the database and later, opt for safe third-party Exchange Server Recovery solutions if you find the important data missing after repair or the repair process fails.

Exchange Recovery software are result-oriented tools to that repair EDB files using safe and effective scanning algorithms. These products are applicable in each case of database corruption. You can install these products easily and then operate them using simple steps as described by the software itself.

Microsoft Exchange Recovery is a powerful EDB Recovery utility that repairs corrupted Exchange database files and restores the mailboxes in individual *.pst files. The Exchange Recovery tool supports MS Exchange Server 5.5, 2000, 2003, and 2007. The tool can also recover deleted mailboxes. The software is compatible with Windows 7, Vista, XP, 2003, and 2000.

Transaction logging is a disaster recovery procedure of Microsoft Exchange Server that helps the database to get restored in consistent state after any unexpected stop. When the database stops suddenly, it goes to inconsistent state. On next restart, Exchange Server locates and then scans the log files to apply them from the database file. But for any reason if it fails to locate those log files, the recovery attempts fail. This forces you to locate the missing log files manually. However, if it cannot be accomplished, you need to restore the database from a suitable backup or perform Exchange Server Recovery using appropriate database repair procedures.

For each event in Exchange Server, the application logs the associated entry in Windows Application log. So, you might encounter the following error message displaying in this application log, usually after unexpected stop:

“Database requires log files that could not be located. The database requires log files to continue. Make sure the log files exist. Check Event logs for more information.”

The event ID of this error in 453 and can cause database to become unmountable.

Cause

Exchange database needs some log files that it could not locate to continue. For further information on which log files could not be located, you can see the event description which mentions the sequence of log files that it could not locate. It also includes the log file number, up to which recovery has been possible.

Some prime reasons that might prevent log files from being located are:

1. The temporary folder doesn’t contain the log files. The transaction logs are missing.

2. An anti virus software is running that has quarantined the log file

3. A hardware failure that has caused log files to lose.

Solution

You need to apply these measures to solve the existing problem:

1. Check if the required log files have been moved. If yes, move them back to the correct folder. But if they have been deleted, you need to restore from the backup.

2. You need to stop the antivirus scanning if any and examine its registry settings to put back the current log files to correct folder.

3. If none of the above measures work, you should restore the database from the backup or apply eseutil repair (hard recovery) utilities to repair the database.

Eseutil hard recovery is not safe to use as it deletes the corrupted pages. Thus, you are suggested to use commercial Exchange Recovery utilities as a better option. The Exchange Recovery software are suitable choice to repair corrupted Exchange database using safe, yet effective, scanning algorithms.

Exchange Recovery Software is a powerful EDB Recovery tool that repairs corrupted Exchange database and restores the mailboxes in *.pst files. The Microsoft Exchange Recovery tool supports MS Exchange Server 5.5, 2000, and 2003. The software is easy to install and operable using simple steps that even a non-tech user can understand.

Exchange data fragmentation occurs within the database. To reduce its effect, Exchange Server includes a default defragmentation process (called online defragmentation) on daily basis as a part of regular maintenance process. Also, the application provides an offline defrafgmentation technique, which is accomplished by eseutil /d command. Both of these methods discard the unused space, but occasionally introduce some database errors that cause database to corrupt. To repair such corrupted databases, you need to apply eseutil repair commands or restore from the last available backup. However, if these measures don’t help, you should repair the corrupted database using an Exchange Recovery Tool.

For instance, consider the following practical scenario. You try to defragment the Exchange database (*.edb) with eseutil /d command, but the process fails while it is defragmenting the database. After this, you observe that the file in effect is named as *.edb.edb. You rename it to *.edb, but Exchange Server refuses to mount it further.

When you try to perform soft database recovery, you get an error message, as below:

“Checking database integrity.Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non-database file or corrupted db) after n seconds”

The database is inaccessible .

Cause

The EDB file is severely corrupted and cannot be mounted.

Solution

You can try to implement the following suggestions to solve the described issue:

1. Restore from the last backup you have.
2. If the soft recovery has failed, you can use hard recovery command- eseutil /r. Make sure you backup the file first. It is the hard command and usually deletes the corrupted pages that it cannot understand.
3. If the above solutions are not valid, you should use a third-party database repair utility. Such software can easily repair a corrupted EDB file without harming the original integrity of the file.

Microsoft Exchange Recovery tools are specifically designed products with high competency to repair a corrupted Exchange database. An Exchange Server Recovery utility has a self-explaining interface and suitable documentation. They can repair a database corrupted due to any logical instance. For this, the software apply a powerful set of scanning procedures, which are also safe for the database originality.

Stellar Phoenix Mailbox Exchange Recovery is a powerful solution that repairs and restores damaged Exchange databases in each case. The Exchange Recovery Software supports Exchange Server 5.5, 2000 and 2003. It is a safe database repair tool with various user-end graphic features. The tool recovers all user mailboxes in individual *.pst files, which can be imported in Outlook.

Soft Recovery is an automatic process in Exchange Server that replays the transaction log files on a database that is remounted after an unexpected shutdown. The process replays only those log files that have been specified for the storage group containing the inconsistent databases. It makes the databases complete with the recorded transactions. At times, the log files get damaged and unusable and this corruption is detected when Exchange performs soft recovery. In such situations, the databases remain inconsistent and lose the ability to mount. To restore them, you should use your latest available backup or use eseutil repair commands to bring the databases to consistent state. If these measures fail, this compels you to repair the databases using Exchange Recovery solutions.

For instance, suppose you try to mount a mailbox store or public store of Exchange Server. The operation may fail with an error described below:

“Corruption was detected during soft recovery in the log file”

The error further describes that the log file has been damaged and cannot be used. The error prevents the Exchange databases from mounting. The application event log marks the error with event 465.

Cause

The error indicates that the databases are in dirty shutdown state and the transaction log file is corrupted. Generally, it occurs due to corruption in Edb00000E8.log file.

Solution

To resolve the described error, you should apply the steps mentioned underneath:

• Backup Exchange databases related with corrupted log files in offline mode

• Run eseutil /mh command to check the databases for consistency

• If the databases are consistent, you can safely remove all the log files from the folder

• If the databases are not consistent, you should perform soft recovery using eseutil /r command

• If running soft recovery doesn’t work, you can restore from backup or perform hard recovery using eseutil /p command

Exchange hard command is called forcible-sate recovery command and can cause data loss. Thus, to repair the databases safely, you should use more reliable alternatives of Exchange Recovery. There are several Exchange Server Recovery products available that can repair a corrupted databases and extract all mailboxes from them.

Stellar Phoenix Mailbox Exchange Recovery is an advanced and safe solution for repairing a corrupted Exchange database. The Exchange Server Recovery tool incorporates powerful scanning algorithms to result repair. It supports Exchange Server 5.5, 2000 and 2003. The software is competent at extracting mailboxes in individual .pst files.

Microsoft Exchange Server is designed to write all the database transactions to certain log files and commit them later whenever the system allows. The transactions also exist in system memory, but get lost in the event of crash. If the Exchange Server undergoes unexpected crash, these transaction logs serve as the crucial recovery method. For this reason, the transaction lof files should be kept on a reliable system. The log file header contains information like file signature, base name, creation time, checkpoint etc. At times, your Exchange Server indicates as it is unable to read this information. These are critical situations that may compel you to restore the data from an online backup or perform hard recovery for your databases. However, it is highly recommended that you try to move Exchange mailboxes on another server or use an Exchange Recovery product to repair the database.

To exemplify, consider a situation when you receive the below error with your Exchange Server database:

“Unable to read the log file header.”

The error is logged as event 412 in application event log. The ESE error code that displays in Description section of this event gives detailed information of the root cause.

Cause

As the error suggests, it occurs when Exchange database engine cannot read the log file header. This indicates that log file has a mismatching signature, has corrupted header information or is corrupt. You can deduce the exact cause by the ESE error code the event shows:

1. Jet_errLog fileCorrupt or error -501: The header of the log file is corrupt

2. Jet_errBadLogSignature or error -530: The log files signature mismatch. The log file signature ensures the correct replaying of log files set and is included in each database header. The error occurs when they mismatch.

3. Jet_errDiskIO or error -1022: A disk I/O issue for requested page in transaction log or database. Generally, -1022 error occurs because of severe database corruption. For a log file, the cause is corruption of log file header.

Solution

You need to use any of the below procedures:

1. Check for the last online backup and restore

2. In case of valid backup unavailability, you can run eseutil /p command and later isinteg -fix command. It is a hard command and data loss is likely as will delete database pages. Thus, for your production database, it is recommended to use another Microsoft Exchange Recovery method like moving the mailboxes to other database or using an Exchange Recovery software.

Stellar Phoenix Mailbox Exchange Recovery is a reliable and efficient solution for repairing corrupted Exchange databases created using Exchange Server 5.5, 2000 and 2003. The advanced Exchange Server Recovery tool can extract all mailboxes and store them in individual .pst files. The software uses intensive scanning algorithms for database corrupted due to any reason.

Exchange Server databases’ transactions are temporarily stored in transaction log files. At times, you need to remove these files manually, usually when the disk runs out of space or the circular logging is disabled. If you come to such situations, it is recommended to determine that the logs have been committed to database or otherwise will cause problems. The database usually shows Dirty Shutdown state in such cases. However, the other reason for this is that database is corrupt. If it is, you should look for Exchange Recovery solutions.

You can take the following situation when you try to mount an Exchange Server database. In an attempt of mounting the database, you might receive an error as below:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.

ID no: c1041724
Exchange System Manager”

The mount operation fails after you receive this error message.

Cause

Error c1041724 can be encountered if you have run eseutil /p repair utility on the affected database. At this point if Eseutil log files remain intact and are not removed, the database can fail to start with the above error.

Solution

To isolate the issue, you need to proceed as follows:

1. You need to first check if eseutil /p command was run. To do so, you should run eseutil /mh command for pub1.edb and priv1.edb and check the repair count value. If it is other than ‘0′, this shows that the command was run.

2. From the previous step, you also need to check for the database consistency. If it exists in Clean Shutdown state, which shows that the log files have been committed, you can safely remove the log files from Exchange Server folder, Mdbdata folder to a backup folder and mount the database.

3. If the database shows ‘Dirty Shutdown’ state, it may be because either all the log files have not been committed yet or the database is corrupt. You can wait for sometime to determine if uncommitted transactions is the case. If not, the database is corrupt that you need to restore from backup or by performing soft recovery.

In cases when database remains corrupted with no access to a suitable backup, you can use third-party Exchange Server Recovery utilities. These special applications allow safe extraction of user mailboxes without any modification to the original content. Exchange Recovery utilities provide you interactive design plus impressive features to experience.

Stellar Phoenix Mailbox Exchange Recovery is a complete tool that repairs Exchange database repair systematically. It is a safe and powerful Exchange Server Recovery tool that supports Exchange Server 5.5, 2000 and 2003. The tool can restore mailboxes in individual .pst files, which can be directly accessed in Outlook. The software is enriched with a realistic approach to repair corrupted EDB file in each instance.