And I agree with the below.
(But I know there are people who think differently).
The Exchange disks that hold the Information Store databases should
hopefully not be holding anything else. The characteristics of these
databases are not the same as those of a conventional file store.
For example, all the database pages are 4K in size - so you would tend to
optimise your disk subsystem for this size of transfer - whereas, if I
remember correctly, when transferring files, NT tends to preload up to seven
times the amount requested in anticipation that the rest of the file is also
going to be required...
(Thus you get resource contention if using an Exchange machine also for a
I also understand that the recommended size for transfer to / from the disk
holding the paging file is 64K.
One more point, and a question :
a) Exchange does its own internal defragmentation....
b) ... so does Diskkeeper, which is general purpose, claim to be able to do
it better ?
Does having a contiguous database on disk mean accessing these pages is any
more efficient ?
I think probably not - and you would get a *massive* performance hit during
defragmentation unless you did it offline (which means you have to stop your
Exchange Server, bye bye Service Level Agreements).
So tell the technical people to leave it alone (unless you really are using
your Exchange machine for lots of other things). And they should know
better :-) (but they probably all have MCSE after their name and who am I
but a thick administrator)
> Any file-level defrag would not do Exchange much good at best.
> So keep your tech service people of your Exchange Server machine. If they
> document your opinion in written, make sure that you have good backups and
> do what they want.
> > My tech services people are telling me that they need to run Diskeeper
> > program) on my exchange server (NT 4.0 and Exchange 5.5). I realize
> > Exchange defrags itself but they say this should also be done and they
> > it without shutting down any services. Any comments on this?
> > Thanks
> Corrections are welcome.
> For "Good post" practice visit