Why did Diskeeper run for such a long time, when run for the first time on a disk?
The
Diskeeper Manual
, in Section 1.8,
Installation Overview
, recommends an image backup and restore of the disks before installing and running Diskeeper to ensure that you start with a near-perfect disk and get the best possible performance immediately. Some Data Center Managers choose to skip this step for a variety of reasons, so they may be starting with a far-from-perfect disk.
If the disk is badly fragmented when Diskeeper is run for the first time, a lot of work must be done to defragment the disk. On a large disk, it may even take several hours. This elapsed time should diminish as Diskeeper continues to run on a regular basis.
Response time to other users and elapsed time for other batch jobs may be affected by Diskeeper running on a badly fragmented disk as well, because it queues so many I/O operations. This adverse impact will be relieved as the disk becomes less fragmented.
When image backup and restore are undesirable at installation time, there is a way to get the disk into near-perfect condition in a relatively short amount of time.
During an off-peak time on the system, such as a weekend, specify a Diskeeper job with the QUICK-FIX preset template.
Selection of this preset template will cause Diskeeper to run once at higher than normal priority and gets the worst fragmentation thoroughly cleaned up as fast as possible. Unlike backup and restore, this can be run without operator intervention and without taking the disk out of service. After that, set up Diskeeper to run on a regular basis for maintenance purposes.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
