Let alone break all of the single instance store! -----Original Message----- From: Don Ely - Verizon [mailto:[EMAIL PROTECTED]] Posted At: Friday, January 25, 2002 8:05 AM Posted To: Exchange Sunbelt Conversation: ESEUTIL DEFRAGS LIMITATIONs Subject: RE: ESEUTIL DEFRAGS LIMITATIONs
That's a rather ignorant solution... D -----Original Message----- From: Ben Ong [mailto:[EMAIL PROTECTED]] Sent: Friday, January 25, 2002 3:25 AM To: MS-Exchange Admin Issues Subject: RE: ESEUTIL DEFRAGS LIMITATIONs What I did before was, I'll transfer their mail to their "personal folder", than use eseutil.exe to defrag. -----Original Message----- From: James Chris L [mailto:[EMAIL PROTECTED]] Sent: 25 January 2002 03:31 To: MS-Exchange Admin Issues Subject: RE: ESEUTIL DEFRAGS LIMITATIONs We have another drive we have added for the defrag and we need to defrag the database because there is only 300mb of free space on the database drive and to expand the disk, we need to move the database of the disk and expand them move it back. -----Original Message----- From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 12:41 PM To: MS-Exchange Admin Issues Subject: RE: ESEUTIL DEFRAGS LIMITATIONs Here is a snippet from Q272234 that tells you about offline defragmentation. "Generally, however, avoid offline defragmentation because it is an expensive procedure. When offline defragmentation runs, it creates a new database file and then copies all the data in the old file to the new file, which can take a long time. On average, it takes about one hour to defragment 5 to 10 GB of disk space. Also, you need enough free space for the offline defragmentation process to hold the new file. As a general rule, you should have 100 percent more free space than the amount you are defragmenting." So the question then begs whether you have the free space to even perform the defrag. May I also ask why you feel that it is so completely necessary to defragment your database? Is there a problem with the server? Is it not running smoothly? Are you anticipating that it will never grow larger? Basically, all you are doing with eseutil is reclaiming the white space. That is it. White space simply explained is just space in the database that is not currently being used, but will be used as the database grows. Since the space has already been reserved, your server does not have to work nearly as hard to procure more space and increase the size of the database. Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems -----Original Message----- From: James Chris L [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 1:27 PM To: MS-Exchange Admin Issues Subject: ESEUTIL DEFRAGS LIMITATIONs We have an on going problem in our company, our Exchange database exceed 60gb on some of our servers. One of these databases has 13gb of free space in it. We have tried to defrag this database multiple times and have failed to complete in the time window every time. Does anyone know what if any the limitations of the ESEUTIL are for Exchange 5.5? Has anyone ever done this before? Is there any other third party tools that can be used to defrag our database? What would you recommend? Chris List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
