Our company is running Exchange 2010 on Windows 2008 Server.
The hardware in this server is:
2x Intel E5520 Xeons
16GB RAM
RAID:
2x 600GB SAS (RAID 1 for OS)
8x 300GB SAS (RAID 5 for DB)
We recently had a problem where the default edb became corrupt, I used ESEUTIL to fix the problem but also created a new edb and moved all mailboxes to it (81 total mailboxes).
In the last 2 days the new edb has become corrupt.
How is this possible? There has been no power cuts or anything that I can see that would have caused this.
What are the possible causes of an edb becoming corrupt over night?
Thanks, for the link; I am aware of how to repair the edb, but what I want to know is how it's possible that a brand new edb can become corrupt in less than a week.
DJMohr
ASKER
will have to schedule a disk check. I need to add that the drives in the server are a week old, installed them last friday.
Have you confirmed about disk checking ?
Also please note : Usage of Eseutil tool is probably not good enough as this tool never ensure about the security of exchange database. Even, My personnel experience is not good with this tool. This tool is failed in several crucial circumstances. Also, It's a bit complex and take a lot of time to restore the database . Especially, It works by discarding the severely corrupted database pages that it cannot be fixed. However, it is capable to fix the individual database tables but can not maintain the relationships among them. My recommendation is to go with any good third party tool if you face EDB corruption problem further.
DJMohr
ASKER
I have run the chkdsk and run a repair on the edb, monitoring the event logs for any further issues.
http://community.spiceworks.com/how_to/show/2217-repairing-a-corrupt-or-dirty-exchange-database