Greg,
Good points, except that the Diskeeper documentation is misleading about the
manual defrag. Although you don't have the "improved free space" option,
doing a manual defrag actually moves all the files as close to the front of
the disk as possible without entering the MFT. What you probably don't know
is that Diskeeper won't defragment the Metadata files such as the hibernate
file - it's even in their FAQ it says that certain system files cannot be
defragmented because NTFS maps them at startup and requires they not be
moved for file system integrity reasons. The documentation doesn't say
which files these are, however.
As for PerfectDisk 7, I just had a server that had an extremely fragmented
metadata file (over 5000 excess fragments) and Diskeeper wouldn't touch it,
even at boot time. The largest contiguous block of free space was less than
50 Mb on an 18Gb disk that was only half full. I downloaded the trial
version of PerfectDisk 7, deinstalled Diskeeper and installed PerfectDisk.
Then I did an on-line defrag followed by a boot time defrag and PerfectDisk
and it defragged the MetaData, saving me a weekend's worth of rebuild.
Needless to say I have now put on our purchase list for this year
PerfectDisk Server for our servers. We're small enough that my assistant
identifies the workstations needing defragged using a network fragmentation
analysis tool and goes and defrags the two or three workstations each month
that need defragging.
Also, can you feed back that the Defrag API needs to be fixed to avoid the
problems listed in KB 282791, "FRS: Disk Defragmentation Causes Excessive
FRS Replication Traffic". I believe this was the cause of my our Metadata
fragmentation problems. Basically, the Defrag API needs to mark the USN
journal in such a way that the FRS service won't try to replicate a
defragged file.
Thanks,
Mike.