Debsyl99
asked on
Exchange Information Store Won't Mount - Dirty Shutdown
Hi
Our exchange server 2000 standard sp3 server suffered a raid 5 hard drive failure last night - blue screened and rebooted spontaneously from what I can tell. Now the information stores will not start although all exchange services are started. Eseutil shows dirty shutdown. We've got backups of the information store and exmerge to pst's from 3 days ago. Most of our users are running oulook 2003 in cached exchange mode. What's going to be our best bet to get this up and running with as little data loss as possible?
Thanks in advance
Deb :))
Our exchange server 2000 standard sp3 server suffered a raid 5 hard drive failure last night - blue screened and rebooted spontaneously from what I can tell. Now the information stores will not start although all exchange services are started. Eseutil shows dirty shutdown. We've got backups of the information store and exmerge to pst's from 3 days ago. Most of our users are running oulook 2003 in cached exchange mode. What's going to be our best bet to get this up and running with as little data loss as possible?
Thanks in advance
Deb :))
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi
Thanks for your responses. I'd already backed up what was already there prior to trying to recover then repair with eseutil. Unfortunately the Raid failure extended to 3 out of six drives (I'm expecting more) so even though it's not reported on the server I'm thinking it's a raid controller problem. Hence the databases were completely unrecoverable no matter what flavour of eseutil I applied. I ended up recovering to a new exchange temp server from a backup using the disasterrecovery switch, then importing from pst's using exmerge. The pig is that Outlook 2003 won't automatically reconnect the OST's. I needed to export anything not included in the IS backup from OST's to PST whilst offline, recreate the mail profiles, then re-import. We'll be at this for the next five days with all our users. Still, it gives me a good argument for better backup resources,
Deb :))
Thanks for your responses. I'd already backed up what was already there prior to trying to recover then repair with eseutil. Unfortunately the Raid failure extended to 3 out of six drives (I'm expecting more) so even though it's not reported on the server I'm thinking it's a raid controller problem. Hence the databases were completely unrecoverable no matter what flavour of eseutil I applied. I ended up recovering to a new exchange temp server from a backup using the disasterrecovery switch, then importing from pst's using exmerge. The pig is that Outlook 2003 won't automatically reconnect the OST's. I needed to export anything not included in the IS backup from OST's to PST whilst offline, recreate the mail profiles, then re-import. We'll be at this for the next five days with all our users. Still, it gives me a good argument for better backup resources,
Deb :))
The below technet article is th right solution for problem . It clearly describes that when u use Eseutil utility and it shows your error that the databse is in inconsistence state , then what to do
http://support.microsoft.com/kb/327346/en-us
I think your problem will be solved from this
Amit.