Re: Eseutil utility Defrag question

Andy David - MVP <adavid@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>>As you are no doubt aware, Exchange Server is hungry for disk space. If
>>Exchange runs out of disk space, the Information Store will shut down,
>>leaving you with no e-mail. It is therefore extremely important to keep tabs
>>on the amount of free disk space on the server. You not only want to monitor
>>the volumes containing the Exchange databases, but also those volumes
>>containing transaction logs.
>
>I wouldnt say Exchange is hungry for disk. Your user's are however!

Ain't *that* the truth?!

[ snip ]

>>? Defragment the databases
>>As messages are created and deleted, the Information Store becomes
>>fragmented. Exchange 2000 and 2003 perform automated defragmentation of the
>>databases to help reduce the effects of fragmentation. The problem with this
>>automatic defragmentation is that free space within the database is never
>>released. The only way to release the free space (and decrease the database?s
>>size) is to perform an offline defragmentation. To do so, you will need to
>>take the Information Store offline and run the ESEUTIL program with the /D
>>switch.
>
>Free space within the database *is* released. What doesnt change is
>the actual file size on disk.

And the "freed" space isn't going to stay free. The database will soon
begin expanding.

Best advice? Leave the thing alone unless there's been some dramatic
change in the database contents.

>>The volume containing the Information Store must have at least the size of
>>the database that you are defragmenting, plus 10% in free space. Therefore,
>>if you had a 1 GB database, an offline defragmentation would require 1.1 GB
>>of free disk space. The disk space will be returned to you after the
>>defragmentation is complete, but is needed as temporary work space. I
>>recommend performing an offline defragmentation once every one to two months.
>
>WRONG. THere is no reason to do this as part of regular maintenance.
>Bad things can happen when you do offline defrags, it causes downtime
>etc... Bottom line , it's rarely required.

I think I've done this twice, maybe three times, in the last six
years. And that was when we still had 125 servers! We only have 24
servers now, but somewhere around 100 databases, and I don't plan on
doing any offline defrags anytime soon.

You're right about the "bas things can happen." No disk operation is
zero-risk.

[ snip ]

>>? Schedule periodic reboots

<LOL> That's sad.

>>Just as a database can become fragmented, so can the server?s memory.

Imagine that! A Virtual Memory Manager that has to deal with
fragmented memory! About ten minutes after you reboot the machine the
memory's gonna be frgmented again.

>The
>>easiest way to get rid of the fragmentation is to reboot the server. If your
>>corporation?s server availability policy will allow it, I recommend rebooting
>>your Exchange server about once a month.
>
>Pure Crap.

You're being too polite.

If there's no critical security update to be installed, and no
imminent threat from any of the less critical vulnerabilities, let 'em
run.


--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.

Relevant Pages

  • RE: Exchange restore on SBS2003 from SBS2000 backup
    ... I agree with you that using ExMerge is a good ... How to recover or restore a single mailbox in Exchange 2000 Server ... >> the Exchange database from the SBS 2000 backup to the SBS 2003 Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows server 2003 SP1
    ... I agree with Marina that you must keep the same server name to restore Exchange database. ... please also refer to the following KB articles for restore Exchange database. ... >Do the same for the public folder store ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2k Exchange recovery - HELP!
    ... as it pulls mail out into a SQL database. ... I discovered something else I didn't know about Exchange.. ... If I could have got OWA working from the RDP into the Server (so only ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: Repairing / modyfing Exchange
    ... Thank you for posting in the SBS newsgroup. ... Exchange Database to another disk, ... Moving Data Folders for Windows Small Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • RE: Repairing / modyfing Exchange
    ... I'll setup a new server today to try it. ... Also, because I have messed something up with the First Storage Group, if I ... > Exchange Database to another disk, ...
    (microsoft.public.windows.server.sbs)