MS Exchange Server 2007 is integrated with improved data security and database improvement features that make the application become a reasonably secured platform to work on. The chief improvements that this version has to offer are increased database size limitation of about 16 TB, more than before number of storage groups per server, improved antivirus, anti-spam protection and more.
In-spite of the improvements so made, Exchange database corruption might hit the user big time. Corruption may strike the EDB database any time and with no such exception. Exchange Server 2007 database prone to corruption due to number of common Exchange Server corruption reasons that include Dirty Shutdown, Application issues etc. The main solution to deal with these issues must be use of isinteg Exchange 2007 utility. Isinteg stands for Information Store Integrity Checker tool that lets the administrator eliminate the errors resulting in issues during the start-up of Information Store.
Isinteg is a command line utility that uses isinteg syntax to resolve the Exchange database errors that restrict a user to login to their accounts and to view delete and receive emails. This can also be used to investigate mailboxes, folders, items etc to confirm the existence of any sort of problem.
Isinteg Exchange 2003 utility repairs the errors so discovered at the application level that are higher than the page level. The ideal way to resolve Exchange database corruption issues is with the use of Exchange repair tools or restore database from available backup. In case none of these measures work, then you require a third party Exchange recovery utility. Suppose in a real time working scenario, you use Exchange Server 2007 and come across database corruption. You realize than when you try copying the database, the copy operation fails and you come across an I/O error in system log, mentioned below:
The driver detected a controller error on DeviceHarddisk0DR0.
– 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 GroupMailbox Database
As suggested by the above error message, you can run ISINTEG utility to check the consistency of your EDB database. When you run the ISINTEG utility to check the database consistency, you receive the following error message:
MSExchangeIS (3932) First Storage Group: Data inconsistency detected in table table_num of database database_path
Also, the ESEUTIL /p utility fails to fix the EDB database corruption. Such situations indicate the database corruption to an extent that it cannot be repaired using Microsoft utilities. In order to extract the data from mailboxes, you can rely on the following solutions:
1.Database backups- so that you can restore in cases of EDB corruption
2.Third party Exchange repair utility can repair and restore database contents. Exchange Recovery utility can use effective and save scanning algorithms to recover the lost data.
Use professional Exchange Recovery tool that has the ability to recover mailboxes from corrupt Exchange database in individual *.pst files. The Exchange Server Recovery application supports data recovery from Exchange Server 2007, 2003, 2000, and 5.5. Exchange Recovery tool supports recovering deleted mailboxes and STM file data in an email body.
The author of this article is a technical expert and has a decade long experience of working on isinteg Exchange 2003 processes. Through this article the author wishes to throw light on why a user restrict use of isinteg utility and must stick to Kernel for Exchange repair tool when corruption strikes.