Skip to main content

Custom Incremental Backup Scheme - Creating Full Version After Incremental Versions

Thread needs solution

I'm using Acronis True Image 2013.

I've configured a custom incremental-based backup scheme like the following:

Custom Scheme
Backup Method: Incremental
Create a full version after every 5 incremental versions
Store no more than 1 recent version chains
Do not delete the first version of the backup

The problem is that ATI doesn't create any full versions after many (ten) incremental versions.
The backup directory now looks like attached.

Thanks!

0 Users found this helpful

No picture attached.

Generally, two of the major reasons for what has happened to you is
1. You restored a backup and continued using the old task, rather than starting a new task.
2. User made changes to the backup task changing its original configuration.

As the task is not working, I would suggest you start over with a new task pointing to a new empty sub-folder for storing the new tib filess.

GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is user choice.

Your new backup scheme should look like the above example except change the "keep 6 inc" to your 5 inc, and change the "store no more than 4" to store no more than 1", plus checkmark to "do not delete the original.

What you can expect the new task to do is
Backup 1 will be a b1 full which is your option to keep the original (do not delete the original).
Backup 2 will be the first full (b2) of chain2.
Backup 3, 4, 5, 6, 7 will be the 5 incrementals completing chain 2.
Backup 8 will be the next full (b3), followed by the immediate deletion of backups 2, 3, 4, 5, 6, 7 (chain 2)
What is left is the B1 original and the B3 recent full.
The next 5 inc will be created before Full b4 is created. After B4, the chain 3 will be immediately deleted, followed by the creation of the 5 inc files.
AS you can see from the process, you must always have storage space on at least 2 full backups and the 5 incrementals, otherwise, you will get a full disk message.

As you are starting over with a new task, you may have to delete some old files in order to create additional storage space for the new files. Here is a link how.
Remember, you can only delete the newer incrementals to maintain the backup sequence, If you were to delete the oldest incrementals before deleting the newer inc's, all your newer inc's will be useless as the chain numbering sequence has been broken.

GH5. How to delete backup files using Acronis Backup 'Explorer'

An assortment of links. My signature link 2 may be of assistance.

GH1. How to change a backup task from scheduled to "Do Not Schedule".
GH2. How to enable a backup task schedule or change a schedule time..
GH3. How to create a non-scheduled backup task on the first try.
GH4. Illustrate Manual Backup Now option or Repeat backups.

GH7. How to create a desktop backup shortcut from an existing backup task.
GH8. How to view or set somewhat hidden advanced scheduled backup settings.
GH9. How to view or change error timeout settings frequency.

GH11. Create Custom Full Backup Scheme.Keep 4 versions (chains). The 4 is user choice.

GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains. The 2-2 is user choice.

Thank you for the detailed answer you've provided!

Sorry for the file that was supposed to be attached, actually I've tried to attach it, but something went wrong. I'll try to do it again.

My situation is that I had several tasks and backups already done, and then I had to reinstall and lost all my tasks. I recreated tasks and it worked (i.e. new backups followed the old ones) except that full backups were not created.

Now I'll try to follow your recommendations, i.e. I'll remove old backup files, recreate tasks as suggested, and then see how it will work.

Thanks again!

Attachment Size
191600-114748.jpg 54.27 KB

Yes, I believe a fresh start with new options as per my example would be beneficial.
I looked at your folder and the sizes are confusing--especially the full which should be the largest and any inc file should be small with just the changes since the last prior inc.