If it were me, I wouldn't waste the time doing isinteg, and just restore the database from the last backup and replay the log files. I think I read it here that once a DB has corrupted once, it's suddenly a lot more prone to corruption in the future, and you may very well find yourself doing a restore anyway. From: Matthew McComas [mailto:[EMAIL PROTECTED] Sent: 06 March 2008 15:31 To: MS-Exchange Admin Issues Subject: dreaded Event ID 447 We had a power outage yesterday and due to our inadequate back up power, we were forced to power all of our servers off. Our Exchange server was gracefully shut down, however, ever since the outage we started getting this event: Event Type: Error Event Source: ESE Event Category: Database Corruption Event ID: 447 Date: 3/6/2008 Time: 9:13:29 AM User: N/A Computer: WAMEXCH03 Description: Information Store (2760) First Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 2353, PgnoRoot: 28516) of database D:\Exchsrvr\mdbdata\Corp\Corp Mailbox Store.edb (10214338 => 2781183, 10221014). Looking at articles and such, it's obvious we will have to run an integrity check with ISinteg as soon as possible. I saw a further example of the issue with a single mailbox which would not receive any new email...you could send email from it but it wouldn't receive...so the question is: How long can we go with the database in question? Can it wait a day or two until we have a maintenance window? Is there a risk of corruption spreading? Thanks, MM
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
