Microsoft Exchange Recovery Tool

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.

Microsoft Exchange Server first passes data to the operating system and then, depends on the installed device drivers and hardware to keep this data securely. In case, these lower layers fail to provide required protection to data, your Exchange database might become corrupt. This form of database corruption is counted as the most severe one since it lacks the ability of get repaired and compel you to restore the database from backup or delete the corrupted data using Eseutil hard recovery techniques. Another alternative can be to use an Exchange Server Recovery utility that provides mailbox extraction from the corrupted database.

Most of the physical database corruption errors are detected by Exchange Server while operations like taking an online backup or performing database maintenance. This is because during these operations, the database engine undergoes page-wise testing of database. As a result, it logs similar errors, as mentioned below, in application event log:

1. “-510 JET_errLogWriteFail”

2. “-1022 (JET_errDiskIO)”

Cause

Each Exchange database has a 40-byte header information that stores a page number a CRC (Cyclic Redundancy Check). The database engine first determines the page number to ensure the requested one and then, checks the CRC value when reading the database page. If either of these checks fails, an error is returned, as above.

Before declaring the corrupt page, the database engine attempts to read it up to 16 times. These error indicate that either the page is bad or the database engine has failed in its trials without any success. You cannot backup the database in such cases and the operation is aborted.
Solution

You can avoid such problems by configuring a suitable hardware, device drivers, and firmware. Possible solutions to these problems are:

1. Restore from a backup, if is available and valid

2. Run eseutil /r command to find and remove bad pages from the database

The lost database pages might contain data that is important. For example, if the deleted page contains a B-tree index, it can render a considerable database part to become useless. To prevent from such situations, it is however, recommended to opt for safer Exchange Recovery solutions. The Microsoft Exchange Recovery software use intensive, yet safe, scanning algorithms to repair and restore the corrupted Exchange database.

This Exchange Recovery Software is a reliable tool that repairs corrupted Exchange database and restores the mailboxes in *.pst files. The Exchange Recovery utility supports MS Exchange 5.5, 2000, and 2003. The tool has an interactive interface that makes the software easy to operate. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

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.