Re: Eseutil utility Defrag question
- From: "Hank Arnold" <rasilon@xxxxxxx>
- Date: Fri, 20 Jan 2006 04:44:13 -0500
Oh come on.. Tell us what you *really* think! ;-)
BTW, I agree with your comments 1000%, except I think you were too kind...
"Experts" like this are extremely dangerous......
--
Regards,
Hank Arnold
"Andy David - MVP" <adavid@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:mhdvs15du33k6a4h6ap3tnrhq14t7mfub3@xxxxxxxxxx
>
> Answers inline...
>
>
>
>>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!
>
>
>>Keep in mind that while running out of disk space is a big problem,
>>letting
>>the Exchange databases get too large is an even bigger problem. Exchange
>>Server 2003 Enterprise Edition doesn't impose an Information Store size
>>limit, but all other versions of Exchange have a 16 GB limit. If the
>>Information Store reaches the 16 GB threshold, the repair process is very
>>messy, so it's important to keep tabs on things so that ceiling is never
>>reached.
>
> Exchange 2003 SP2 standard supports a 75 GB priv and public store.
>
>>
>>
>>? 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.
>
>>
>>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.
>
> Also, the 10% required is really 110% of the actual store size, not
> the size of the store on disk. Before running an offline defrag, you
> should always know how much free space is avail within the store.
> Events 1221 in the app log will tell you this.
>>
>>
>>? Schedule periodic reboots
>>Just as a database can become fragmented, so can the server's memory. 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.
>
>>
>>
>>
>>"Ben Winzenz [Exchange MVP]" wrote:
>>
>>> Membership required. Strike one.
>>>
>>> There is a fairly good reason that you don't find that information on
>>> Microsoft's website. You certainly won't find any PSS engineers that
>>> will
>>> recommend offline defrags every 1-2 months.
>>>
>>> What other items are on their "maintenance checklist"? There are
>>> perhaps
>>> other things that need to be cleared up, no?
>>>
>>> --
>>> Ben Winzenz
>>> Exchange MVP
>>> MessageOne
>>> Read my blog!
>>> http://winzenz.blogspot.com
>>> http://feeds.feedburner.com/winzenz (RSS Feed)
>>>
>>>
>>> "HockeyMullet" <HockeyMullet@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:16007481-B8C3-475F-803C-4516D9DF732E@xxxxxxxxxxxxxxxx
>>> > http://searchexchange.techtarget.com/tip/1,289483,sid43_gci1064013,00.html?track=NL-368&ad=539998
>>> >
>>> > "Andy David - MVP" wrote:
>>> >
>>> >> On Thu, 19 Jan 2006 06:32:02 -0800, HockeyMullet
>>> >> <HockeyMullet@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>> >>
>>> >> >I'm actually going through a "maintenance checklist" from an
>>> >> >Exchange
>>> >> >website
>>> >> >that recommends doing offline defrags every one to two months.
>>> >> >
>>> >>
>>> >> Can you post a link to that? I have never heard of this.
>>> >>
>>> >>
>>> >>
>>> >> >"Andy David - MVP" wrote:
>>> >> >
>>> >> >> On Thu, 19 Jan 2006 06:08:02 -0800, HockeyMullet
>>> >> >> <HockeyMullet@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>> >> >>
>>> >> >> >I'm about to run a defrag, so what I was wondering how long does
>>> >> >> >it
>>> >> >> >generally
>>> >> >> >take (average time)? My priv1.edb is about 12 GB. I'm trying to
>>> >> >> >plan a good
>>> >> >> >time to do this. Thanks.
>>> >> >>
>>> >> >>
>>> >> >> I am more interested in why you are running it in the first place.
>>> >> >>
>>> >>
>>>
>>>
>>>
.
- References:
- Re: Eseutil utility Defrag question
- From: Andy David - MVP
- Re: Eseutil utility Defrag question
- From: Andy David - MVP
- Re: Eseutil utility Defrag question
- From: Ben Winzenz [Exchange MVP]
- Re: Eseutil utility Defrag question
- From: HockeyMullet
- Re: Eseutil utility Defrag question
- From: Andy David - MVP
- Re: Eseutil utility Defrag question
- Prev by Date: Re: three questions for file searching
- Next by Date: Re: Eseutil utility Defrag question
- Previous by thread: Re: Eseutil utility Defrag question
- Next by thread: Re: Eseutil utility Defrag question
- Index(es):
Relevant Pages
|
