Not only does it take a long time to copy back the defragd db but he could have tested/verified the consistency of it before going on if it would have dumped out on him. scary.
Thank you, Erik L. Vesneski Internal Network Manager Epicentric, Inc. -----Original Message----- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 12:42 PM To: Exchange Discussions Subject: RE: disaster debriefing Sounds like he got impatient and didn't wait for the database to finish being copied back to exchsrvr\mdbdata from the network share - which needs to complete before you get your dos prompt back. After he killed ESEutil, he could've also copied it back manually and renamed back to priv.edb instead of tape restore. Then, the defrag effort would not have been in vain. Louise -----Original Message----- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3:27 PM To: Exchange Discussions Subject: RE: disaster debriefing He followed the KB article, whatever it was. Services were down. I think he followed all the "right" procedures. The temp file was on a network drive that had plenty of room. The defragged temp database exists on the temp drive and is whole. That's how he figures it freed 3.5 gigs. -Yanek. > -----Original Message----- > From: Josefowski, Larry [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 29, 2001 2:26 PM > To: Exchange Discussions > Subject: RE: disaster debriefing > > > The utility is dangerous in the wrong hands. It can take a > very, very, very > long time to run. It also gets very snitty when you don't > have enough room > on the HD (or network share) to create the temp file that is > part of the > defrag process....Where did he attempt to create the temp > file....on the > same drive that is almost full? > > > And how is he enjoying his time at home these days? > > -----Original Message----- > From: Yanek Korff [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 29, 2001 2:16 PM > To: Exchange Discussions > Subject: disaster debriefing > > > Ok, so we had a disaster the other day. Co-Worker of mine ran eseutil > against the private IS to free up some disk space. We were > at about 95% > capacity on the drive, and it would creep up to about 98% > before the nightly > incrementals, which brought it back down. Now, I'm not positive what > command he ran, but apparently it cleared about 3.5 gigs out > of the IS. > Right before eseutil exited, however, it apparently "hung" > waiting for a > command prompt. > > I'm a little fuzzy as to what happened after this. I think > he tried to > reboot, and then the IS didn't come up -- he got some errors, > looked them up > in the KB to very little avail. So when I got in at 9 the > next morning, > mail was down. He was still there. > > We managed to put humpty dumpty back together again restoring > from the full > backup we made right before starting this procedure. It took several > attempts - he had tried restoring from backup before but > hadn't had any > success. I think the procedure we followed was this: > Shut down all exchange services > Start System Attendant & directory service > Restore DS > Stop System Attendant & directory service > Restart System Attendant > Restore IS > > > Any other combination of services running/not running didn't work out. > We're using Veritas Backup Exec BTW. Well everything's back > to the way it > was before we started this whole mess. I know I've seen > discussions about > eseutil on this list before, but I wanted to revisit this and get some > concrete information. > > What did we do wrong? What's the right way to use eseutil to > gain disk > space? I'd appreciate any non-flaming advice, pointers, > docs, etc. I find > the archives non-intuitive -- or maybe I'm looking in the wrong place? > Can't seem to find a good place to type in a search phrase > "eseutil" and > have it return relevant data (I'm here: http://www.swynk.com) > > -Yanek. > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
