Also, a simple thing to do is to take offline backups of the IS (priv and pub) and the transaction log files so that you can easily restore them (without losing any data), should the database move fail.
Missy ----- Original Message ----- From: "Couch, Nate" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[EMAIL PROTECTED]> Sent: Wednesday, July 23, 2003 2:25 PM Subject: RE: Exchange Disaster Recovery Story - Comments Appreciated It sounds like you did pretty well if you ask me, and you did. The only things I can think of would be the following: 1) After doing something like an IS move go into your Exchange Admin and verify where the server thinks the databases are located (select the server then Properties - Database Paths). 2) Also look at the database size to check for any inconsistencies. If the size doesn't look right (too small more than likely in this instance) you shoud investigate further and veirfy MS Exchange functionality. 3) After the failed move attempt check the event logs for anything out of the ordinary. If you check your logs daily you should be able to pick abnormal events pretty quickly. If you don't do this already. . .start. It is a good idea to get to know your MS Exchange servers and what is 'normal' for them. This is all I can think of right now. Nate Couch EDS Messaging > ---------- > From: Bridges, Samantha > Reply To: Exchange Discussions > Sent: Wednesday, July 23, 2003 1:04 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=&la > ng=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] _________________________________________________________________ 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]
