Jason said:
I've used Acronis and other image backup programs for years AND
defragment the disks occasionally. I have NOT seen the issue mentioned in
the Acronis KB article cited above. In fact, just to see, I defragmented
C: and then did an incremental backup - I'd done one yesterday - and the
backup was quite small even though defrag had moved a LOT of files. (I
did a Complete defrag - rarely do that - so that nearly every file got
touched.)
I think the generic term is "smart sector moving" (every vendor probably
uses a different name for this). The backup program sees the sector got
moved but sees its content didn't change. It can record just the sector
move rather than record what all was in that sector.
You didn't mention which version of TrueImage Home that you use. I kept
using v9 (circa 2005) since it remain a viable backup solution -- until
it stopped working (after I added SATA drives to mix in with IDE drives
on the old mobo with an early SATA controller that Acronis didn't like
during the verify phase of backups). I had to move to other backup
software that would work on my old hardware. That old version of TI
Home *did* generate much larger backups after a defrag. I can't find
that old forum discussion but, as I recall, others claimed to perform
the same test and notice little increase in the size of an incremental
backup.
I was using the Auslogics Disk Defrag, not the one included in Windows
(which won't move as much as 3rd party alternatives: 0% in Windows
defrag is far higher in all other defraggers). I don't remember what
defraggers the others were using that claimed their incremental backups
did not get larger after a defrag. Also, even using the quick-method
GUI defrag in Windows (the one in the Start menu and which runs as a
snap-in within the MMC program) results in *far less* movement than
using the defrag.exe command-line program, so when users noted they were
using the Windows defrag it was unclear which one they were using. If
using the quick-method defragger, not much got moved so there would be
little to track in the imaging program. Also, in my testing, I
deliberately SWITCHED between defraggers to force a large move of
sectors. You can't defrag with one and then expect much to change by
the time during the testing when you defrag again using the same one.
Switching to a different defragger on each defrag operation employs
different algorithms each believes is the better layout and results in
much more movement. A zero-percent defragged drive reported by one
defragger will still result in lots of movement in another defragger
whose algorithm sees perhaps not so much fragmentation but instead where
files are "better" placed on the platters. I think the real problem
between me saying an incremental after a defrag could result in a huge
backup file versus the others is that the others incurred little
movement in their defrags.
The incremental backup after a defrag wasn't as large as a full image
backup but it was a lot larger than an incremental backup where there
had been no defrag since the prior backup. Since I stopped using
Acronis stuff for a few years now, I don't know if they incorporated
"smart sector moving" detection which would reduce how much had to get
backed up (since the content of the moved sector didn't change) but
still track the movement of sectors.
I found a forum discussion when I was using Easeus Todo Workstation
(
http://forum.easeus.com/viewtopic.php?f=27&t=24643&p=49324&hilit=defrag#p49324)
for image backups (fulls and incrementals). Here I tested a "full
backup, no defrag, incremental" versus "full, defrag, incremental" and
noted the difference in the incremental backup sizes. Instead of 28MB
for the incremental backup, the incremental after a defrag was 10GB in
size (a full backup was 16GB). So the incremental got far more huge
after a defrag.
Which backup product you use, which version of it, how it handles
unchanged but moved sectors, and which defragger you use (and how much
it actually moves) can probably all affect the outcome.