Seeing errors on our Exchnage 2010 SP1 server related to one of our databases. Looking to find the best solution to correct the errors and clean any corruption.

We have multiple database on our Exchange 2010 SP1 server (Ver. 14.01.0438.000) One database in particular has started to through errors leading us to believe that the database is corrupt. The database only has 2 mailboxes in it, but these mailboxes are both about 15 GB in size. We have tried to move the 2 mailboxes to another database, but they fail each time.

Our Exchange server is running on Windows Server 2008 R2 and is a virtual machine configured through VMware.

We are looking to see what might be the best way to resolve this issue and correct the errors seen. Please let me know if any more information is needed.

The errors we are seeing with the database are as follows:
Event ID: 233- Database Recovery - At '7/24/2015 5:09:38 AM', database copy 'XXX' on this server encountered an error. For more information, consult the Event log for "ExchangeStoreDb" or "MSExchangeRepl" events.

Event ID: 474 - ESE - Information Store (3860) XXX: The database page read from the file "E:\mdbdata\Mailbox\VIP\XXX.edb" at offset 29928882176 (0x00000006f7e68000) (database page 913356 (0xDEFCC)) for 32768 (0x00008000) bytes failed verification due to a page checksum mismatch.  The expected checksum was [da2b25d4b6fe068f:a2c8a2c80d692cc3:74e374e33eb21e4a:0899f76628ced59e] and the actual checksum was [da3e25c1c817f35a:930c930c99913cc8:7d427d42ecc6c3f1:0899f76628ced59e].  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.

Event ID: 203 - Database Recovery - At '7/24/2015 5:10:05 AM' database copy 'XXX' on this server appears to have an I/O error that it may be able to repair.  To help identify the failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events. Service recovery was attempted by failover to another copy. The failover was unsuccessful in restoring the service because of the following error: 'There is only one copy of this mailbox database (VIP). Automatic recovery is not available..

Thank you in advance for any help given.
Jason RingholzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
First - Exchange 2010 SP1 is no longer supported.
You need to upgrade your server to Exchange 2010 SP3.

When you attempt to move the mailboxes, what happens?
When was the last successful backup of the database?

The errors usually mean that little can be done without significant data loss. You could attempt a repair of the database, but there may well be data loss.
If you have a good backup, then I would look at restoring that backup to a recovery database, check the data to see if it is good then restoring for real.

Usually a move mailbox would resolve the issue, as it would allow you to drop the original database file, but the it looks the corruption has gone too far.

Database corruption on Exchange 2010 is rare, so I would be looking to see if there is an issue with the storage - as that is the most common cause.

Simon.
0
Ben HartCommented:
Maybe eseutil?
0
Will SzymkowskiSenior Solution ArchitectCommented:
From my experience and testing a great product that does a low level repair on the EDB database is Exchange Recovery by Kernel Data Recovery. You can do this offline and either re-mount the database or export all of the mailboxes to PST files.

http://www.nucleustechnologies.com/Exchange-Server-Data-Recovery.html

Will.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Jason RingholzAuthor Commented:
Thanks for the good information Simon,

We are in the process of upgrading to SP3 for Exchange. I actually just started working for this company and this issue is what I walked into. I would like to get the corrupt database issue resolved first before we go any further with upgrading Exchange.

We do have a good backup of the Exchange server and of the databases, but it's possible that the corruption is also in the backups that we have. If we have a good successful backup of this database, it may be a few months old.
0
Jason RingholzAuthor Commented:
Ben,

Thanks for the suggestion. I have looked into using that, but wanted to gather more information before trying to use that utility.

Seems like eseutil can help take care of similar issues, it might be worth trying, if all else fails we could restore from a backup, just not sure if the corruption is in the backups as well.
0
Jason RingholzAuthor Commented:
Thanks for your help Will,

I'll look into that utility and see if it will work for our situation.
0
Simon Butler (Sembee)ConsultantCommented:
Are the transaction logs in place for the suspect database?
If you have a complete set going back to the last backup then you could consider restoring the last backup then replaying the logs.

Therefore test the restore to a recovery database and see if you are getting the same problems. If not - suggesting the backup is good, then you could look at doing a full restore and log replay to get you back to the point you are at now, but with the restore.
Then finally move the mailboxes to a new database - it is best practise to replace a recovered database.

This might be something worth getting Microsoft involved with. If you explain that you cannot update to SP3 until the backup/restore is complete, they should be able to assist. It depends on how valuable the data is.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.