Information Store is one ost vital components of Microsoft Exchange Server that stores transaction logs and database files. Unlike any other database corruption, Information Store databases can also get corrupted due to dirty database shutdown, anti-virus scanning, and log file corruption. In most of these situations, you encounter an error message that suggests database corruption. To easily overcome such database corruption scenarios, you need to restore the data from an online backup. But in case of online backup unavailability, you will need to opt for advanced Exchange Server Repair solutions.
To illustrate the above case, consider a scenario where you attempt to take a backup from Veritas software and you encounter the below error message:
“Access Denied to Database Mailbox Store (Server Name) – Warning mailbox Store (Server Name) is a corrupt file. This file cannot verify”
After the above error message pops up, the database backup process stops. On viewing the application error log, you view event id 217. The description section for the same event is mentioned underneath:
“Information Store (2320) 8d59bacd-96a8-4d3a-b1cd-0f31dc7be0b8: Error (-613)
during backup of a database (file D:\ProgramFiles\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore. Information Store (3272) The streaming page read from the file “D:\ProgramFiles\Exchsrvr\mdbdata\priv1.stm” at offset 5598494720 (0×000000014db24000) for 4096 (0×00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3969232578 (0xec95aec2) and the actual checksum was 4119053255 (0xf583c3c7). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.”
Cause:
The fundamental cause for the above error message is corruption of database.
Resolution:
To resolve the above error message, you need to:
-
Restore the data from an updated backup, as suggested in the error log.
-
Run Eseutil/d (offline defragmentation) to resolve minor corruptions in Microsoft Exchange database.
-
Run Eseutil /p and then run Isinteg -fix to fix corruption on a database backup.
However, if the problem still persists, then you need to go for an advanced Exchange Repair to extract user mailboxes from the corrupted database. Such Exchange Server Repair solutions can be easily downloaded from the Internet and used even by a novice user.
Stellar Phoenix Mailbox Exchange Recovery is a advanced repair application that repairs corrupt Exchange EDB file, irrespective of its cause of corruption. The repaired mailboxes can be saved in separate *.pst files. With recovery of deleted mailboxes, the Exchange Repair software supports Exchange Server 5.5, 2000, 2003, and 2007.
