Exchange Information Store Corrupt With Database Not Found Error

In several exchange database operations, like (butMailbox Store."
not limited to) backup process, the operatingOn exploring the application event log, it shows
system is called to read database pages thaterror -1018.
have to be written on disk. During this operation,Cause
the checksum value placed in database pageThe root cause of the above behavior is
header is compared with that returned by thecorruption of Exchange mailbox store, most likely
READ operation. The backup operation fails ifdue to hardware issues. These errors cause
these values do not match. Such errors indicatechecksum errors in database pages.
corruption in database and need backup availabilitySolution
to restore lost data. But in cases when user findsTo resolve the problem:
it unfeasible to restore from backup (because it is1. You need to run system hardware diagnostics
corrupted or incomplete), a Microsoft Exchangeto find the root cause and then isolate the related
Recovery tool can help.issues.
To depict the probable events, let's take a related2. User can create a new mailbox store and
scenario of an Exchange Server 2003 user. Whenmove the mailboxes from the corrupted store, to
he runs a backup utility to copy the Exchangecorrect the database problems.
database, the operation halts with an error that3. You can also try repairing the corrupted
reads:database using Eseutil/p repair utility. However,
"Database was not found and could not bethis command is often unrecommended because
backed up. Please make sure database exists andit deletes the corrupted database pages and can
is mounted."cause important data to delete.
The logs also consist of errors such as:4. And, for safe database repair, use an Exchange
"Store_Name is a corrupt file. This file cannotRecovery Tool. Designed to run safe scanning
verify."procedures, these Microsoft Exchange Server
OrRecovery software can repair corrupted
"Access is denied. Access denied to databasedatabase and extract valuable data.