Different behavior in newly-created backup task versus existing tasks from pre-upgrade
I recently had the opportunity to perform a clean re-installation of my Windows 10 machine, which included Acronis True Image 2021 build 39287.
Previously my incremental scheme backup would write a .TIBX file with "full" in the name for each full backup segment, and "inc" in the name for each incremental backup segment.
When I re-created the same incremental backup scheme on the new machine it has been writing both the full segments and the incremental segments into the same single .TIBX file. I haven't reached the point of making the second full backup segment, but I'm presuming a different .TIBX file will be created that that point. i.e. The full backup, and all incremental segments relative to that full backup, are now being stored in the same single file.
I'm not sure I completely dislike that approach, but one practical effect it has is that I manually replicated my backups to an additional storage locations, whenever I was in proximity to those locations. Now instead of being able to replicate just a "small" incremental segment .TIBX file most days, now I have no choice but to replicate the entire full + incremental single .TIBX file every time.
Which is not a deal breaker, but do I have the option to return to "separate full versus inc backup segment files", if I wanted to?
The other thing I noticed when re-creating my backup task from scratch was that the "limit backup to <size>" option was no longer offered. Only the choice of "how many days old" versus "how many chains" was offered for the automatic cleanup.
Is size still an option for automatic cleanup, and if so, how do I enable that?
Since at least for me, that was definitely the more practical option. e.g. "Fit as many backups as you can within 2TB of space". Maybe that's 12 chains or maybe sometimes that's only 8 chains. Whatever fits within 2TB, so that the rest of the storage volume remains available for other priorities.


- Log in to post comments