I having some major Exchange 2007 DB problems. Firstly, I have no backup as the backups that I thought were OK I can't recover from. Somehow the DB has been corrupted to the point that I can't even take a copy of the edb file so i can safely run ISINTEG and ESEUTIL. It starts to copy (for quite a while as it's a 60 GB file) and then towards the end i get an I/O error and the copy bombs out. When I look in the system log of the server there are all kinds of disk errors just before the copy fails. I have therefore had to run ESEUTIL /p and ISINTEG alltests on the actual DB file. ESEUTIL took a few hours and the report showed a ____ of a lot of warnings and maybe 50 errors which it succesfully dealt with (by deleting the bad sectors I presume). ISINTEG just stopped the first time at the message test but during that run i noticed it had fixed 960 errors in the folder test, which seemed a lot. I rerun ISINTEG alltests it and it completed fine the second time but the DB is still screwed. When I attempt to move a mailbox from the corrupt DB to a new one it goes through the motions and then errors out saying it met the corrupt message limit (150). When I look at the application log on the server during the mailbox copy process i get hundreds of errors relating the disk errors and corrupt messages. Below are some examples; -------------------------------------------------------------------------------------------------------------------- Unable to move mailbox Brown, Craig. A problem occurred while getting the properties for a message. Parent folder name: Inbox; Message subject: RE: SND253P1 ; Error code: 0xfffffa0a. Run ISINTEG to check for any problem in the database "First Storage Group\Mailbox Database". ---------------------------------------------------------------------------------------------------------------- MSExchangeIS (3932) First Storage Group: Data inconsistency detected in table 1-24 of database E:\EXCHANGEDATABASE\First Storage Group\Mailbox Database.edb (5578,5772946). --------------------------------------------------------------------------------------------------------------- Also, here are examples of the system event log when attempting to copy the file. ---------------------------------------------------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk0\DR0. ------------------------------------------------------------------------------------------------------------- Logical drive 1 configured on array controller P400 located in server slot 1 returned a fatal error during a read/write request from/to the volume. Logical block address 24e9d106, block count 128 and command 20 were taken from the failed I/O request. Array controller P400 located in server slot 1 is also reporting that the last physical drive to report a fatal condition (associated with this logical request), is located on bus 0 and ID 4.

I would call Microsoft support and see if they can help you salvage anything.

What's the best way to contact MS support professionals? I'm in New Zealand.

There is a support wizard you can walk through:http://support.microsoft.com/common/international.aspx?&sd=tech

Many thanks.

Hi, If ESEUTIL /p utility fails to repair the database corruption, It indicates database (edb file) corruption to an extent that cannot be repaired and dealt with inbuilt Exchange utilities. To resolve this issue you need solutions like: 1. A Exchange Server database backup that can be used to restore. 2. A third-party Exchange Server Repair utility that can repair and restore the database items. Stellar Exchange Recovery utility is an advanced edb repair softwre that uses effective, yet safe, scanning algorithms to repair, recover and restore exchange database items. Thanks Axel Culver