Quote:
|
Originally Posted by ghayes Here's what is going on. When defragmenting with PerfectDisk and Smart Placement (default defrag method), PD is not only defragmenting files, it is also consolidating free space, placing boot files, and grouping files together by modification date. When the built-in defragmenter is defragmenting, it is doing far less work. VSS is detecting the drive changes generated by PD as changes and as a result older restore points/shadow copies get purged. If you have PD defragment using the Defragment Only option, PD essentially works like the built-in defragmenter - simply defragmenting fragmented files - no free space consolidation, no boot file placement, no grouping of files.
VSS does have code in it to detect defrag activity and limit purging restore points/shadow copies (MS KB article). However, that code only works if the cluster size on the drive is a multiple of 16k. The default cluster size on Vista is 4k. Why not 16k if it will limit the impact that defragmenting can have on the life our your restore points/shadow copies? Because NTFS compression doesn't work for cluster sizes greater than 4k.
The first time that you defragment with PerfectDisk using Smart Placement will result in the most changes to the drive (as seen by vss) and when it is most likely that restore points/shadow copies may be purged. It all depends on the amount of work that PD is doing, how much total free space there is on the drive, how much space that restore points/shadow copies take, etc... Subsequent defrag passes should result in less changes to the disk and less likelyhood that restore points/shadow copies will be purged.
- Greg/Raxco Software
Microsoft MVP 2003-2007
Windows File Systems
Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a commercial defrag utility, as a systems engineer in the support department. |
Thanks for posting here Greg! So, are you saying the more I use PD, the less likely it will delete the restore points then? Will it eventually leave them alone or should we just not use the default Smart Placement mode? Personally, I would rather use Smart Placement since that's part of the reason we use PD, because it defrags better than the default defragger with Vista, but if we have to disable or bypass that then I guess that's what we'll have to do.
So it sounds like your saying MS needs to release a hotfix in order for 3rd party defraggers to leave the restore points alone in Vista so that they can read the 4k clusters. Diskeeper has this problem too BTW. I just don't understand why Raxco can't issue a fix in the way of an update as well. I don't really care who fixes it, as long as it does get fixed at some point fairly soon. Anyway, thanks again Greg.