RE: disaster debriefing
Where did you get that idea? I've (had to) run ESEUTIL numerous occasions (especially in the good old Exchange 4.0 days). It was always on raid5 sets and NEVER had any problems. Then again, I won't mention the name, but I was running on quality hardwareq. On the other hand, I agree that putting the TEMP db on a network share is a no-no. S. -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3:26 PM To: Exchange Discussions Subject: Re: disaster debriefing Running eseutil on a raid drive subsystem may cause problems. T _ 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]
RE: disaster debriefing
Also, next time you need to do this, build another Exchange box, move all the users to the new one. Stop the IS on the old one, delete the PRIV.EDB, start the IS and then move everybody back. Voila! No risks, no hassles. S. -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]
RE: disaster debriefing
That pretty much goes without saying. Ed Crowley MCSE+Internet MVP Tech Consultant Compaq Computer Corporation (soon to be HP) All your base are belong to us. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Roger Seielstad Sent: Friday, November 30, 2001 6:26 AM To: Exchange Discussions Subject: RE: disaster debriefing Its a she. We don't have a college fund. We've got a therapy fund. Its not a matter of IF we screw her up - we know that we will, its just a matter of how and how much we screw her up. -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:50 AM To: Exchange Discussions Subject: RE: disaster debriefing He's gotta pay for a college education somehow. John Matteson; Exchange Manager Geac Corporate Infrastructure Systems and Standards (404) 239 - 2981 Believe nothing because it is written in books. Believe nothing because wise men say it is so. Believe nothing because it is religious doctrine. Believe it only because you yourself know it to be true. -- Buddha -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
Hey, they keep him away from the deep fryer -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
She's legal to work the the US.[1] -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com [1] Very long story that longtime readers of the list know -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
He's gotta pay for a college education somehow. John Matteson; Exchange Manager Geac Corporate Infrastructure Systems and Standards (404) 239 - 2981 Believe nothing because it is written in books. Believe nothing because wise men say it is so. Believe nothing because it is religious doctrine. Believe it only because you yourself know it to be true. -- Buddha -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
LOFR!! -Michèle Immigration site: http://LadySun1969.tripod.com Miata: http://members.cardomain.com/bpituley Tiggercam: http://www.tiggercam.co.uk - Frisbeetarianism (n.), the belief that, when you die, your soul goes up on the roof and gets stuck there. - -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:50 AM To: Exchange Discussions Subject: RE: disaster debriefing She's legal to work the the US.[1] -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com [1] Very long story that longtime readers of the list know -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
Its a she. We don't have a college fund. We've got a therapy fund. Its not a matter of IF we screw her up - we know that we will, its just a matter of how and how much we screw her up. -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:50 AM To: Exchange Discussions Subject: RE: disaster debriefing He's gotta pay for a college education somehow. John Matteson; Exchange Manager Geac Corporate Infrastructure Systems and Standards (404) 239 - 2981 Believe nothing because it is written in books. Believe nothing because wise men say it is so. Believe nothing because it is religious doctrine. Believe it only because you yourself know it to be true. -- Buddha -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
anyone know what event viewer id # 4093 is? -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
You are leaving out the write time to the hard drive. Depending on RAID, drive speed, etc., etc., I doubt you would get your theoretical rate. -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
I was thinking that it was YOU.. You see, since they young'un is only three, she can't open a checking account on her own, so you'd have to have a trustee account. Eventually all those minimum wage pay checks would add up enough for you to write just one check to the college. But a therapy fund? I think you've gone wy too deep into the mindset that everyone needs therapy. * I* certainly don't need twitch no stinking therapy. [yes you do! No! YES YOU DO!, YOU WERE ON THAT STINKING SUBMARINE FOR 8 YEARS!] Ahhh... Excuse me. John Matteson; Exchange Manager Geac Corporate Infrastructure Systems and Standards (404) 239 - 2981 Believe nothing because it is written in books. Believe nothing because wise men say it is so. Believe nothing because it is religious doctrine. Believe it only because you yourself know it to be true. -- Buddha -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:26 AM To: Exchange Discussions Subject: RE: disaster debriefing Its a she. We don't have a college fund. We've got a therapy fund. Its not a matter of IF we screw her up - we know that we will, its just a matter of how and how much we screw her up. -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:50 AM To: Exchange Discussions Subject: RE: disaster debriefing He's gotta pay for a college education somehow. John Matteson; Exchange Manager Geac Corporate Infrastructure Systems and Standards (404) 239 - 2981 Believe nothing because it is written in books. Believe nothing because wise men say it is so. Believe nothing because it is religious doctrine. Believe it only because you yourself know it to be true. -- Buddha -Original Message- From: Renouf, Phillip [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:36 AM To: Exchange Discussions Subject: RE: disaster debriefing You have your 3 year old working at McDonalds? Sheesh! ;) Phil There is no need for retraining this person - even my 3 year old can say Would you like fries with that? _ 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]
RE: disaster debriefing
anyone know where MSKB and Google are? -Original Message- From: Tener, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:31 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know what event viewer id # 4093 is? -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
MSKB's main site in s Redmond WA, and googles is in mountain View CA. Kevinm M WLKMMAS, UCC+WCA, CKWSE -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 30, 2001 6:56 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know where MSKB and Google are? -Original Message- From: Tener, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:31 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know what event viewer id # 4093 is? -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
http://www.eventid.net/display.asp?app=WebEventseventid=4093 -Original Message- From: Tener, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:31 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know what event viewer id # 4093 is? -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
Kevin Shoots, Kevin scores :) -Original Message- From: Kevin Miller [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 10:00 AM To: Exchange Discussions Subject: RE: disaster debriefing MSKB's main site in s Redmond WA, and googles is in mountain View CA. Kevinm M WLKMMAS, UCC+WCA, CKWSE -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 30, 2001 6:56 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know where MSKB and Google are? -Original Message- From: Tener, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:31 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know what event viewer id # 4093 is? _ 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]
RE: disaster debriefing
What about dethonged? ~ -K.Borndale Network Administrator Sybari Software 631.630.8569 -direct dial 631.439.0689 -fax http://www.sybari.com One man's ceiling is another man's floor |+--- || AD [EMAIL PROTECTED]| || Sent by: | || bounce-exchange-148870@ls| || .swynk.com | || | || | || 11/29/2001 08:04 PM | || Please respond to| || Exchange Discussions | || | |+--- ---| | | | To: Exchange Discussions [EMAIL PROTECTED] | | cc: | | Subject: RE: disaster debriefing | ---| I just pray that I am never de-briefed before a disaster... Andy I want to know how much White Space was there before the defrag. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Drewski Sent: Thursday, November 29, 2001 1:38 PM To: Exchange Discussions Subject: RE: disaster debriefing You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon the same drive that is almost full? And how is he enjoying his time at home these days? -Original Message
RE: disaster debriefing
MSKB has had a makeover today - looks totally different! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 30 November 2001 14:56 To: Exchange Discussions Subject: RE: disaster debriefing anyone know where MSKB and Google are? -Original Message- From: Tener, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:31 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know what event viewer id # 4093 is? -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
MSKB's main site is in Redmond WA, and googles is in mountain View CA. Kevinm M WLKMMAS, UCC+WCA, CKWSE -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 30, 2001 6:56 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know where MSKB and Google are? -Original Message- From: Tener, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:31 AM To: Exchange Discussions Subject: RE: disaster debriefing anyone know what event viewer id # 4093 is? -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
That's all fine and good, but you're forgetting a few things. Like drive speed, the actual speed at which the drive controllers on both ends can push data, etc. Roger -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 9:25 AM To: Exchange Discussions Subject: RE: disaster debriefing Well it was a 10G file, which is about 81920 megabits. Let's say you're getting 60MBps transfer rate on your 100Mbps LAN (since it's nighttime, things are pretty quiet), that should take about 25 minutes. Lemme know if my math is wrong. -Yanek. -Original Message- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:35 AM To: Exchange Discussions Subject: RE: disaster debriefing Which means nothing. Try it out yourself - cut and paste, drag and drop, xcopy, whatever - a large file, and while its copying, look at the byte count on the destination drive. That's the FIRST thing done in the copy process. You ever time doing a copy of a 20GB file across a LAN??? It takes a while. A LONG while. There is no need for retraining this person - even my 3 year old can say Would you like fries with that? -- Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com -Original Message- From: Yanek Korff [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
What did you do wrong? You ran ESEUTIL!!! We have been over this a dozen times in here -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 11:16 AM 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]
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 processWhere did he attempt to create the temp fileon 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]
RE: disaster debriefing
grounds for termination in my mind Thank you, Erik L. Vesneski Internal Network Manager Epicentric, Inc. -Original Message- From: Josefowski, Larry [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 11:26 AM 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 processWhere did he attempt to create the temp fileon 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]
Re: disaster debriefing
Your lucky. The other guy should be regulated to making cables and coffee. But make sure he gets trained on both. Running eseutil online gee wheeze - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 2:15 PM 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]
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 processWhere did he attempt to create the temp fileon 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]
RE: disaster debriefing
You gonna pay for the training? -Yanek. -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 2:26 PM To: Exchange Discussions Subject: Re: disaster debriefing Your lucky. The other guy should be regulated to making cables and coffee. But make sure he gets trained on both. Running eseutil online gee wheeze - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 2:15 PM 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]
Re: disaster debriefing
Running eseutil on a raid drive subsystem may cause problems. That may have something to do with to it. Best is to just buy more disk. Then run it offline as per instructions. I don't trust networked drives. Exchange and support SANs are another sticky point with MS. Well talked about on here. - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 3:26 PM 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 processWhere did he attempt to create the temp fileon 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]
Re: disaster debriefing
Depends on how you like your coffee - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 3:27 PM Subject: RE: disaster debriefing You gonna pay for the training? -Yanek. -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 2:26 PM To: Exchange Discussions Subject: Re: disaster debriefing Your lucky. The other guy should be regulated to making cables and coffee. But make sure he gets trained on both. Running eseutil online gee wheeze - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 2:15 PM 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]
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 processWhere did he attempt to create the temp fileon 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]
RE: disaster debriefing
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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
Although not recommended I was forced to run it about a month ago with perfect results. I defrag'ed the database to a network share because my disk space was to low. I followed the Microsoft procedures found in the following q182903 q183888 q192185 q255035 I also read up on it first in Mark Russinovich's book about managing exchange. It gave me some good background. Take your time and hit all the steps. -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 2:26 PM To: Exchange Discussions Subject: Re: disaster debriefing Your lucky. The other guy should be regulated to making cables and coffee. But make sure he gets trained on both. Running eseutil online gee wheeze - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, November 29, 2001 2:15 PM 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]
RE: disaster debriefing
He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 12: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 processWhere did he attempt to create the temp fileon 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]
RE: disaster debriefing
How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
I want to know how much White Space was there before the defrag. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Drewski Sent: Thursday, November 29, 2001 1:38 PM To: Exchange Discussions Subject: RE: disaster debriefing You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
Yanek, look for event 1221 or something like that. -- Drew Visit http://www.drewncapris.net! Go! Go there now! So let us not be petty when our cause is so great. Let us not quarrel amongst ourselves when our Nation's future is at stake. Let us stand together with renewed confidence in our cause--united in our heritage of the past and our hopes for the future--and determined that this land we love shall lead all mankind into new frontiers of peace and abundance. -- JFK (To Be Delivered 11.22.63) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Blackstone Sent: Thursday, November 29, 2001 3:38 PM To: Exchange Discussions Subject: RE: disaster debriefing I want to know how much White Space was there before the defrag. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Drewski Sent: Thursday, November 29, 2001 1:38 PM To: Exchange Discussions Subject: RE: disaster debriefing You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
Yeah found it... it says 751. I can see where the services were stopped -- looks like the server was in process of doing online defrag (I suppose it does this every night) when the offline defrag was started. Could cause problems, yes? -Yanek. -Original Message- From: Drewski [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:49 PM To: Exchange Discussions Subject: RE: disaster debriefing Yanek, look for event 1221 or something like that. -- Drew Visit http://www.drewncapris.net! Go! Go there now! So let us not be petty when our cause is so great. Let us not quarrel amongst ourselves when our Nation's future is at stake. Let us stand together with renewed confidence in our cause--united in our heritage of the past and our hopes for the future--and determined that this land we love shall lead all mankind into new frontiers of peace and abundance. -- JFK (To Be Delivered 11.22.63) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Blackstone Sent: Thursday, November 29, 2001 3:38 PM To: Exchange Discussions Subject: RE: disaster debriefing I want to know how much White Space was there before the defrag. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Drewski Sent: Thursday, November 29, 2001 1:38 PM To: Exchange Discussions Subject: RE: disaster debriefing You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
I just pray that I am never de-briefed before a disaster... Andy I want to know how much White Space was there before the defrag. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Drewski Sent: Thursday, November 29, 2001 1:38 PM To: Exchange Discussions Subject: RE: disaster debriefing You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
RE: disaster debriefing
de-thonged, you mean? We pray that too, believe me. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Pure religion and undefiled [...] is this, To visit the fatherless and widows in their affliction, and to keep himself unspotted from the world. (James 1:27) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of AD Sent: Thursday, November 29, 2001 7:04 PM To: Exchange Discussions Subject: RE: disaster debriefing I just pray that I am never de-briefed before a disaster... Andy I want to know how much White Space was there before the defrag. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Drewski Sent: Thursday, November 29, 2001 1:38 PM To: Exchange Discussions Subject: RE: disaster debriefing You're assuming that the Eseutil didn't chew up some of the database. -- Drew Visit http://www.drewncapris.net! Go! Go there now! Only the dead have seen the last of war. - Plato -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 3:25 PM To: Exchange Discussions Subject: RE: disaster debriefing Alas, I don't know. Seeing as 3.5 G were cleared, can I assume there were 3.5 gigs of whitespace? Adding a drive isn't so easy as the system's already full up on drives. -Yanek. -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:16 PM To: Exchange Discussions Subject: RE: disaster debriefing How much white space was there before the defrag? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Yanek Korff Sent: Thursday, November 29, 2001 1:10 PM To: Exchange Discussions Subject: RE: disaster debriefing He did wait an hour... And he's confident the copy was complete - same byte count on both the network drive and the local drive. -Yanek. -Original Message- From: Exchange Discussions [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 3: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 processWhere did he attempt to create the temp fileon 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
