Discussion Locked

Diskeeper on Exchange

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

What are the pros and cons of running Diskeeper on my Microsoft Exchange 5.5 Server? My Tech Services people want to run this (without shutting down any services).

Thanks

5 replies

by mckaytech

Interesting question - we're looking at the same product for our non-Exchange servers but I'm not impressed that it does anything beneficial for Exchange v5.5 servers.

Exchange runs a frequent on-line database maintenance procedure that defrags the database within the priv.edb and pub.edb files. Periodically, it's a good idea to run an off-line defrag as well but that is a file-level defrag as opposed to a disk-level defrag. Exchange is also heavily dependent on RAM and somewhat less dependent on disk access as compared to some other applications.

The pros are that it can reportedly speed up disk access; the cons are that it may suck up a lot of resources in the process.

I would be hesitant to run it unless I had clear evidence of a disk subsystem bottleneck and then only with good verified backups and a lot of attention to Performance Monitor. But I'll be interested in reading any comments from people who have actually built up some experience with it on an Exchange box.
paul

by richard.donovan

We have used Diskeeper (current version 6) since 1998 on Exchange Server (s). Currently we use it in conjunction with Echange 5.5, SP3. We have scheduled each partition for a defrag every 4 hours. I believe that Diskeeper does not defrag the variousdata bases maintained by Exchange (Director, Private, & Public Stores), but it does defrag the remaining files, directories, Page (swap) file, etc. In that regard, I believe that there are sufficent tests to demonstrate that your Exchange server will be healther (less disk writes, etc.) becuase you use Diskeeper versus not using it. The use of Diskeeper should also allow you to have better disks (longer life), andeasier backups because files and directories are not fragmented.

This discussion is closed to new replies.