Samantha, your problem seems quite similar to one I had 1.5 years ago, with regular disks (not SAN).
Optimizer hung and after that I couldn't start the store again. At that time Chkdsk didn't find errors, but Chkdsk /Fix found and fixed errors in the drive. After that I mirrored to a new drive, restored the last backup of the store, and all went well. (This is a long story made short. To figure out that "chkdsk /fix" was finding and fixing problems that "chkdsk" alone wasn't even noticing took me a couple of days with PSS) HTH, Alberto (MSX 5.5 SP4) -----Original Message----- From: Bridges, Samantha [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 8:05 PM To: Exchange Discussions Subject: Exchange Disaster Recovery Story - Comments Appreciated Hello All. Yesterday, working in Outlook, the Exchange server became unavailable (or network problems were preventing me from accessing the server). I oversee the Exchange server and knew this wasn't good. When I went to the server, I found a message that the drive had become corrupt and wanted to run the Chkdsk. In the Event log, an entry logged, The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume I:. After running CHKDSK, I could not get the IS to come up. Events that started appearing were: Event ID 125 - MSExchangeIS (2192) Unable to create the log. The drive may be read-only, out of disk space, misconfigured, or corrupt. Error -1811. Event ID 1111 - An error occurred while writing to the database log file. Attempting to stop the Microsoft Exchange Information Store. Event 193 - MSExchangeIS (2192) The database engine failed with error -510 while trying to log the commit of a transaction. To ensure database consistency, the process was terminated. Simply restart the process to force database recovery and return the database to a consistent state. Their is one more piece to this puzzle, on Sunday, we tried to move the IS to a SAN. During the move, the SAN connection failed and we were forced to abort during the Optimizer. When the server came back up, the IS (Priv.edb) appeared in both the new location and the old. When the server came back up, all worked fine so we decided not to attempt moving the IS until we investigated the issue with the SAN. I assumed that the move did not finish and reverted back to the original IS location. The I: drive was the SAN drive that eventually became corrupt. And when it did, it took out Exchange because obviously some things did go there and because unavailable during the corruption (Log files?). Well, to make a long story short, I never could get the IS to be Consistent. I used the eseutil with various switches to no avail. I ended up restoring from an Offline backup and running the ISINTEG -patch and restoring a couple more days backup and that was as good as I could get it. When all was said and done, I lost approximately 11 hours of data. From 9:00p.m. to 8:15 a.m. Any comments would be appreciated. What did I do wrong and what should I have done. Thanks and no laughing....it was not a fun day yesterday. :) Samantha _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
