Version Chain backups are as large as initial full backups
I'm using Acronis True Image Home 2011 (build 6696). I have a ~1.3 TiB data backup using the Version Chain backup scheme. It's on a 2 TB drive so there's only room for one full backup at a time. However, even though it's set to Version Chain, the "incremental backup" that gets created (e.g. a week after the initial full version) is clearly ending up as the same size (judging by the size of the file mid-backup, progress bar and estimated completion time - I can never let it actually finish since the drive would get full).
I've read other topics about this but none have a definitive solution. Automatic defragmentation is turned off in Windows, I've not ever restored the backup and it isn't system files being moved around all the time because this is a backup from my data drives.
So what's going on?
Yes, the backup is about ~1.3 TiB large (default compression). Is there not a way to stop TIB making TWO full versions before starting incremental backups? What about if I choose a custom backup scheme with just incremental backups?
Yes, you could choose a custom backup scheme and go for incremental. Just remember this:
- incremental backups are just a bit more fragile. If any increment gets corrupted, all subsequent backups become useless,
- therefore, it is highly recommended to limit the number of incrementals before a new full backup,
- when you do a new full backup, ATI will first try to do it before erasing the previous full. THis means you need at least the space for 2 full backups on your disk.
- the problem is similar for differential backups, although incremental chains are less fragile, but they tend to require more space...
If you consider running incremental backups only and having the backups consolidate, be warned that the consolidation of backups takes a lot of time and is a more risky process. If you go this route, make sure you validate your backups regularly...
Finally, if you change your backup scheme, I strongly recommend your start from a new task and new full. This will eliminate the risks of corruption of the ATI database.
Well I have to make a new full one every time as it is. If using a custom incremental-only scheme works then I'd delete and start afresh every month or so anyway so shouldn't be a problem.
Thanks for the advice.
Dave,
If you are doing some manipulation manually, consider adding Chain2Gen to remove the need for your intervention.
Chain2Gen (C2G) is helper program written by forum contributor MVP Oracledba. TrueImage does the scheduling and the actual backups. C2G provides the controls (your option settings inside C2G) to determine how many (or how few) backups you want to keep in a chain and how many(or how few) chains you wish to keep. Each chain is in a separate folder.
It's somewhat like an escalator. The oldest chain drops off while a new backup begins and you can have as many backup chains(steps) as you wish.
Lots of information about in my signature below and very easy to set up. I have used it with versions 2009-2010 and 2011 on a regular basis.