exchange recovery

Like other databases, Microsoft Exchange Server database (EDB file) may also corrupt at some point of time and does not let you perform typical Exchange Server operations. The corruption can be of two types – Logical and Physical. Logical corruption is pretty common and occurs due to internal fault in the database. When it happens, Microsoft Exchange Server database becomes totally unusable and you encounter serious data loss. MS Exchange Server does not include any utility to detect and fix logical corruption. Thus, you are required to opt for Exchange Recovery to get your valuable data back.

You may encounter logical corruption of EDB file due to any of the following reasons:

1.If you incorrectly run the soft recovery using eseutil /r tool after restoring database from an online backup, it replays only log files and ignores the patch files. It may result in logical corruption. Extensible Storage Engine 98 does not let you run the soft recovery on an EDB file that needs hard recovery. In case you try this, the following Jet error appears in Application Event Log of Exchange Server:

“JET_errSoftRecoveryOnBackupDatabase (-544)”

2.If you initialize an inconsistent EDB file, the process checks whether that log range specified in database header is there in directory of log, and signatures of both log and database are correct. In case it does not find the specified values, it logs the below event:

“JET_errRequiredLogFilesMissing (-543)”

3.The database may also face logical corruption if you run eseutil /p utility. Jet-level Exchange Server database repairs result in some inefficient disk space uses and data loss, because it fixes the EDB file by deleting the corrupt data.

Resolution

To fix this problem and ensure effective Microsoft Exchange recovery, follow the underwritten steps:

1. Defragment the database using eseutil /d command and then run database integrity check using Isinteg -fix command.
2. Restore corrupt EDB file from the most recent backup. You should not run the soft recovery after restoring from backup as it may cause further damage.
3. Use third party Exchange recovery software to repair and restore the problem database.

The Exchange recovery tool is particularly designed to perform in-depth scan of entire EDB file and extract all inaccessible data from it. They offer simple and secure Exchange Server Recovery due to their rich graphical user interface and non-destructive nature.

Stellar Phoenix Exchange Mailbox Recovery is the most efficient and comprehensive exchange server recovery tool to offer exchange database recovery in all EDB corruption scenarios. It restores emails, contacts, tasks, notes, journal, attachments, appointments, and other EDB file objects. The exchange user profile recovery software works well with MS Exchange Server 2007, 2003, 2000, and 5.5.

In a practical scenario, the Information Store Service of Exchange Server may fail to start and you encounter the below errors in Application Event Log of Exchange Server, while read/writing data from/to EDB file:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 482
User: N/A
Description:
Information Store (4360) First Storage Group: An attempt to write to the file “D:\Program Files\Exchsrvr\mdbdata\res2.log” at offset 4194304 (0×0000000000400000) for 1048576 (0×00100000) bytes failed after 0 seconds with system error 112 (0×00000070): “There is not enough space on the disk.”. The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.”

You can not access the database after above error. To gain access of your valuable data in the EDB file, you need to identify the root of this issue and perform Microsoft Exchange recovery by resolving it.

Root of the problem:

You may face this behavior of Exchange Server due to any of the below reasons:

1. You do not have sufficient free space on the Exchange Server hard drive. The Error 0×00000070 entails ERROR_DISK_FULL and Error 0xfffff8f0 entails JET_errDiskFull.
2. EDB file is corrupt and Exchange Server can not recognize it.

Resolution:

You can try out any of the below methods to sort out this problem:
1.If problem is caused by low disk space, remove some files to free up disk space.
2.If database corruption is causing the issue, repair and restore the database using powerful and advanced commercial Exchange recovery software.

The Exchange recovery tool carry out in-depth scan of entire Exchange Server database and extract all inaccessible data from it. You need not to be technically sound to use these tools and repair the database as they have interactive graphical user interface.

Stellar Phoenix Exchange Mailbox Recovery is the most powerful, yet easy to use exchange database recovery application to ensure easy recovery in all EDB corruption scenarios. The Exchange 2007 recovery software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores inaccessible objects of EDB file, such as emails, notes, tasks, contacts, journal, calendar items, and more.

In a practical scenario, you cannot start the Exchange Server services after installing Microsoft Exchange Server 2007 on the global catalog server. But, other services can be started manually. Furthermore, you may see the below events in the Event Log of Exchange Server:

• Event ID: 2601
  Source: MSExchange ADAccess
  Category: General
  Type: Warning
  Description: Process MSEXCHANGEADTOPOLOGY (PID=1624). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…> – Error code=80040934. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
• Event ID: 5000
  Source: MSExchangeIS
  Category: General
  Type: Error
  Description: Unable to initialize the Microsoft Exchange Information Store service. – Error 0×96e.

Exchange Server is partially dependent upon Microsoft Exchange System Attendant. Exchange Server Information Store service is not dependent upon Microsoft Exchange System Attendant.

Cause

The problem may occur, if:

• Exchange Server domain controller and other services don’t start completely.
• Exchange Server database is corrupted.

Resolution

To perform Microsoft Exchange Recovery, follow the given steps:

• Manually start Exchange services.
• Change Exchange Server dependencies.
• Use Exchange Recovery Software to repair and restore damaged EDB file of Microsoft Exchange Server.

The Exchange Recovery tool are capable of methodically scanning the damaged Exchange Server database and extract all inaccessible data from it. The software are totally safe and easy to use with read-only nature and interactive user interface.

Stellar Phoenix Mailbox Exchange Recovery software repairs and restores damaged Exchange Server database in all cases of corruption. The software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all EDB file objects, such as emails, notes, contacts, tasks, attachments, appointments, and more.

To recover Microsoft Windows Store that doesn’t start, use the below methods:

• Check Application Event Log of Windows NT Event Viewer for MSExchangePub, MSExchangePriv, EDB, and MSExchangeIS messages. The messages may provide you information about actual cause of the problem.
• Shut down all the MS exchange Server services, and then restart Exchange Server. When information store service restarts, it attempts to recover automatically and return database to consistent state.
• Create an absolute backup of Microsoft Exchange Server Information Store. It must include all the EDB and Log files.
• Restore database from last complete online backup. Make sure that you don’t click to choose ‘Start Service after Restore’ option. Restore incremental backups of Information Store. Only click selecting ‘Start Service after Restore’ option while restoring current incremental backup. Do not select ‘Erase all existing data’ option.
• If the above method can not help you start information store, check Event Log and review logged messages for EDB.
• If the above method doesn’t work, restore online backup of information store. Select ‘Start Service after Restore’ and ‘Erase all existing data’ options.
• Remove all the Log and EDB files from Mdbdata folder and then restore copies of Pub.edb and Priv.edb databases from backup.
• If none of the above methods work, you need to wipe the information store as last resort.
• If wiping does not work, you need to remove the Information store. However, it causes data loss. The easiest and safest way to retrieve data in such situations is Microsoft Exchange Recovery.

Recovery is possible using powerful and advanced third-party applications, known as Exchange Recovery Software. The applications are able to handle all EDB corruption situations, irrespective of the cause of corruption.

The Exchange Recovery Tool employ efficient database scanning techniques to methodically scan whole EDB file and extract damaged objects from it. With simple graphical user interface and read-only conduct, the applications are easy and totally safe to use.

Exchange Recovery software is the most advanced utility to recover your Exchange Server database from corruption. It works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. The software restores all EDB file objects such as emails, notes, contacts, tasks, appointments, attachments, and more.

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.

“Error -1216 (JET_errAttachedDatabaseMismatch)”

This error can also be symbolized in the hexadecimal format as ‘0xfffffb40’. When you encounter this error, Microsoft Exchange Server aborts the soft recovery process on EDB file, prior to make some changes in the database that might prevent you to re-integrate the missing database files with data set.

When this error occurs, you should try restoring the missing database files. When such files are not available, use Eseutil tool to override the error and continue with Exchange Server Repair. When this error occurs, you might find the following entries in the application event log of Exchange Server:

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 4/24/2001
Time: 6:20:18 PM
User: N/A
Computer: EXCHANGE1
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘D:\exchsrvr\mdbdata\PRIV2.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed).

The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.”

This behavior of Exchange Server generally occurs when the assessment of header information in database and log files indicates that the replacement or deletion of some vital files has been done. If you run soft recovery, entire database might get damaged.

No matter what the cause of this issue is, the ultimate result would be the loss of your mission critical data. In such situations, Exchange Server Recovery is required to repair and restore damaged database. This is best possible using powerful and advanced third party tools, known as Exchange Server Repair software.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective tool to retrieve data from damaged Exchange Server. This software can repair and restore EDB files of Exchange Server 2003, 2000 and 5.5. It is compatible with Microsoft Windows 2003, XP and 2000.

Sometimes when you attempt to create backup of Microsoft Exchange Server database, which is damaged and inaccessible, you might come across the below given error message:

“Database or database element is corrupt”

Furthermore, with this error message, you might also get a statement, which states that this file can not be verified. Due to corruption, the Exchange Server can not recognize the database and thus can not access it. At this point, you need to identify the cause of data loss and carry out Exchange Server Repair by sorting it out.

Root of the issue

As stated in the above error message, this situation occurs due to corruption to the EDB file. The corruption could be the possible result to virus infection, accidental system shutdown, application errors, operating system malfunction and other similar reasons.

Resolution

In order to fix this issue, you should go for Eseutil/p utility. This is an inbuilt tool in Microsoft Exchange Server that is used to repair damaged EDB file. This tool scans the damaged database and can repair in a number of cases.

Although, this utility is helpful in resolving this error message, but it also has a downside. It deletes all of the database elements that are not recognized by this tool. This behavior of Eseutil tool cause critical data loss situations and make your data permanently inaccessible. To safely retrieve your critical data, go for advanced and powerful Exchange Server Recovery software.

These software are particularly designed to safely, smoothly and thoroughly scan entire database and retrieve all of the inaccessible database objects. These software use efficient and powerful scanning algorithms to achieve perfect Exchange Server Repair. With interactive and simple graphical user interface, such applications are easy to use and do not require sound and prior technical skills.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective software that can handle all EDB corruption scenarios. It can repair and restore damaged EDB file of Exchange Server 2003, 2000 and 5.5. This software is compatible with Windows 2003, XP and 2000.

Sometimes, when you attempt to mount the Exchange Server database (EDB file), you might come across any of the following events in the Application Event Log of Exchange Server:

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 505
Description: Information Store (2028) An attempt to open the compressed file “drive:\Exchsrvr\MDBDATA\priv1.edb” for read / write access failed because it could not be converted to a normal file. The open file operation will fail with error -4005 (0xfffff05b). To prevent this error in the future you can manually decompress the file and change the compression state of the containing folder to uncompressed. Writing to this file when it is compressed is not supported.

Or

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff05b starting database “First Storage Group\Mailbox Store (EXCHANGE)” on the Microsoft Exchange Information Store. Failed to attach to Jet DB.

This issue generally occurs when you upgrade to Exchange Server 2000 Service Pack 3 or later and the Information Store database is compressed using NTFS (New Technology File System) file system compression. Under some situations, NTFS compression may damage the Exchange Server database like when the EDB file exceeds 4 GB size. In such cases, Exchange Repair is required to work around the issue.

Exchange Server 2000 Service Pack 3 and later do not allow NTFS compressed information store to mount. The files are managed by Extensible Storage Engine (ESE) that needs sector independence for log-based recovery that is not allowed in compression.

This entire behavior of Exchange Server corrupts the EDB file and you are required to repair and restore is using Exchange Recovery software to access your critical data. These software can recover all of the Exchange Server database objects.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced Exchange Repair software that works in most of EDB corruption cases. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.