I'm in a bind here. Our mail server (exchange 2003) crashed last weekend due to our SAN going down. After we restarted, exchange would not mount our main mailbox store because it was corrupted. We were down for two days while I ran eseutil /p, then eseutil /d, then isinteg -fix -test alltests - until it came up as clean as possible. After running isinteg, I could not get any lower than 30 errors in the folder test. We mounted the mail store, gave a quick check of some mailboxes, then dumped the mail queue. Everything to the clients was working fine but backup exec 12.5 could not backup the mail store because it failed a consistency check. NTBACKUP gave us similar errors.
Since you don't want to trust a repaired database, we created two new mailbox stores (one for "large" users, and one for "regular" users) and I began to migrate users from the old mailbox store into the two new mailbox stores. The plan was to migrate everyone over the weekend, delete the old mail store and finally get a good information store backup. But nothing ever goes as planned, and while everything appears to be moving fine, I see errors in event viewer for BOTH of the new databases I created! It looks like there are two of these checksum errors in both of my newly created databases. Here is a sample of the event log:
Event Type: Error
Event Source: ESE
Event Category: Database Page Cache
Event ID: 474
Time: 2:31:48 AM
Information Store (2164) First Storage Group: The database page read from the file "D:\Program Files\Exchsrvr\mdbdata\Pro
at offset 13690195968 (0x000000032fffd000) (database page 3342332 (0x32FFFC)) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was -3010982791536671029 (0xd636d71a9da486cb) and the actual checksum was 14355210566124788 (0x0032fffcea7844f4). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
For more information, click http://www.microsoft.com/contentredirect.asp
I haven't had a good backup in over a week now, getting worried that bad things are going to happen. I did a flat file backup this morning by dismounting the mail stores then copying the .edb, .stm and transaction log files to another system.
Any suggestions on what to do?
Also- I am actually running out of disk space with this migration too. (ugh!) I am running eseutil /d on the old mail store to shrink it since I have a good number of space hogs moved to the new database. Is this wise, or should I temporarily put the mail store on a mapped drive to another system with more disk space?
Thanks for any help!