Hello, I have an SBS2003 which started showing failure with tape backup (Backup Exec) due to Exchange database corruption. I have run eseutil and was able to correct the corruption. However, 3 weeks later the corruption returned. I have run a read-only check disk after the second corruption and found some file system corruption. What is the best way to address this? I do not want to keep running eseutil just to find it come back. Below are the errors I see. Backup Exec error: \\Main\Microsoft Information Store\First Storage Group\Mailbox Store (MAIN)" is a corrupt file. Windows event log (ID 217): Information Store (6644) First Storage Group: Error (-613) during backup of a database (file C:\Program Files\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore. Windows event log (ID 478): The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup. Thanks in advance. Akira

Most Exchange database corruptions are caused outside of Exchange - often with storage issues. Bad hard disk, bad storage controller, something like that. Depending on the age of the machine, you may well be looking at a system that is getting close to end of life. Hard disks will fail, it is just a matter of when. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thanks. We found several ASR reboots. That is likely the culprit for corruption.

On Wed, 18 May 2011 21:25:00 +0000, Akira Kato wrote: >Thanks. We found several ASR reboots. That is likely the culprit for corruption. Since ASR power-cycles the machine the shutdown is anything but graceful. If you don't have a disk controller with a battery backup to keep cache active you can be pretty sure that ASR is the casue of your problem. Disable it in the BIOS. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP