Resolve Event id 217 and 478 in Exchange server

While working with Exchange server database, you may face problems related to backup failure that leads to the inaccessibility of database records. In most of the cases, the reason behind backup failure is database corruption but to know about the exact cause, you can refer to the application log where the event ID 217 or 478 and related description states you about the main reason for the error.

Consider a situation where you are trying to perform an online backup of Exchange Storage Group (ESG), but instead of you get the following events logged in the application log:

"Event ID:217
Event Type: Error
Event Source:ESE
Event Category:Logging/Recovery
Event ID: 217
Date:11/23/2006
Time:10:21:32 PM
User:N/A
Computer:EXCHANGE
Description:
Information Store (5484) First Storage Group: Error (-613) during backup of a database (file drive:\Program Files\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore. "

"Event ID: 478
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 478
Date:11/23/2006
Time:10:21:32 PM
User: N/A
Computer: EXCHANGE
Description:
Information Store (5484) The streaming page read from the file "drive:\Program Files\Exchsrvr\mdbdata\priv1.stm" at offset 7250493440 (0x00000001b029c000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2914298788 (0x00000000adb4aba4) and the actual checksum was 4278044063 (0x00000000fefdc59f). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup."

Cause:

The above encountered Event id 217 indicates the backup failure and event id 478 occurs due to database corruption.

Solution:

You can go through the following steps in order to fix up the exchange server database corruption issues:

By making use of recent online backup, restore the Information Store database

In case you are using Enterprise edition of Exchange server 2000 or 2003 then try to transfer the entire user mailboxes to another store

Next is to repair the database using Eseutil/p command following Eseutil/d command so as to defragment the database. But these command line utilities delete the records marked as corrupted so for safe corrupted edb repair, the best is to use Edb repair tool which is highly capable to repair as well as restore Exchange database.