New
#21
Any program that moves large numbers of files around disk in a short amount of time is going to cause some (or more) destruction of VSS stored data, due to the way this looks to the OS (oh, some program needs a ton of space - free up volume shadow copies and mount points to make that space available post haste!). Defragmenters that are spartan about moving actual files around unnecessarily can avoid this (especially if they avoid large files, like the inbox defragmenter does), but this means potentially less defragmenting done to the drive itself. It's a tradeoff - have great file structure for head reads/writes, or leave a bit of fragmentation (define "a bit" ) and don't go whacking a ton of mount points.
You get to choose one or the other, but not both, at least not on a running system.
Well, I wonder if Piriform doesn't use the W7 defragger already. It seems to me that I've used Defraggler a couple times and
1. Not noticed any problems from its use, and
2. Observed that it didn't completely defrag my volume either
I have a W7 PC with an SSD (bad to defrag! don't do it!) and a couple others with spinners and I'm gonna stick with W7 built-in defrag for the time being...
Well, the APIs to use for defragmentation are pretty well documented, as is the way VSS works when you move around lots of files in short order (KB article). It's not surprising that they could put 2 and 2 together . Using VSS is also documented, so there are other ways to handle this as well - none of them are perfect, of course, but there are possibilities.
OK guys, I mentioned it before. I suggest you use Contig. Check the thread where I showed how to use it.
Safe and effective defrag.