Sure. Some people reboot their servers weekly,
too.
For
the average deployment, offline defragging using eseutil as a regular
maintenance tool remains a complete waste of time and
resources.(Read: reclamation of whitespace that will be reused
anyway)
William
Well, to be more specific....
Exchange's online defragmentation is great for defragmenting
and reclaiming white space; however, this process does not reduce the size of
the database file. So, if you move a large amount of data from your
databases (e.g., you purge a whole lot of messages; you move a whole lot of
mailboxes; etc.) then performing an offline defragmentation using ESEUTIL is
completely acceptable maintenance that does not need the hand-holding or
blessing of PSS to perform.
If you aren't move large amounts of data out of your
databases, and you aren't running into any storage limitations (e.g., because
you are running Standard or because you're running out of disk space), then
running ESEUTIL won't provide much, if any, benefits.
So, whether or not this is a regular maintenance tool really
depends on your environment. For the large majority of Exchange orgs, it
probably won't be a regular maintenance tool.
My $.02.
--
Regards,
Scott Schnoll
----- Original Message -----
Sent: Wednesday, October 31, 2001 8:21
AM
Subject: RE: Eseutil
Only use it if you are directed to by PSS, or if you are using the
standard edition of Exchange 5.5 and are running into the 16GB limit.
Exchange handles online defrag quite well so there should be no need to run
and offline defrag unless you are running into the 16GB limit on Standard
Edition.
So what is
the best practice with defragmentation?
MS says that
"ESEUITL is not considered a tool for regular maintenance and should
only be used in case of emergency after contacting Microsoft Technical
Support". On the other hand, there're people here that use it on monthly
basis!
So, to use
or not to use?
List Charter and FAQ
at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at: