
11-21-2008
|
|
|
|
Re: This is a bit of a showstopper
From Diskeeper (inside the running program):
"It is important to be aware that when VSS is enabled on a volume
with a cluster size smaller than 16 KB, VSS will see file
movement done by the defragmentation process as "changed data"
and take a point-in-time snapshot, even though only the location
of the data has changed. Unnecessary snapshots will cause the
VSS storage area to increases in size, possibly resulting in
earlier VSS snapshots being purged.
Diskeeper provides special defragmentation methods to allow you
to defragment these VSS enabled volumes, yet minimize the
possibility that older VSS snapshots will be purged.
When the VSS defragmentation option is enabled, Diskeeper uses
proprietary defragmentation engines to help reduce the chance of
the defragmentation operation causing new VSS snapshots from
being created, thus potentially preventing older snapshots from
being purged. In order to do this, the VSS defragmentation
engines use more conservative file movement algorithms, which
can result in slightly less thorough defragmentation of the volume"
Richie Hardwick
|