Direkt zum Inhalt

No full backup with Incremental chain

Thread needs solution

I have set up two incremental chains. Each is to make a new full backup after 10 incremental. I am currently on day 13, and the program will not make a new full backup. So, I currently have one full and 14 incrementals.

I do have the cleanup turned on -- to clean up only those backup more than 20 days old

Has anyone else run into the full backup not occuring as scheduled?

0 Users found this helpful

If you made some changes in the number of incremental backups, after the task started, or if you have ran some manual backups, ATI will be a bit perturbated, but will catch up.

For example, in ATI 2011, if you set up a task to do "5 incrementals before a new full", you let it do 2 backups, and then you change your settings to "6 incrementals before a new full", you will get 2+6 incrementals before the new full. If you decrease from 5 incrementals to 3, you will get another incremental before the full (as expected); if you decrease from 5 to 2, I don't remember what it does :-); if you do a manual backup inbetween scheduled backups, it might not count; if you do all manual backups, the rule is enforced normally.

I have exactly the same issue - but I have not made any changes to anything since I created the backup jobs. It should have performed a full after 10 and it is now on 13.

Same here... Tried to submit a bug report, but my ppi expired.

The last two versions (6942 and prior) of 2011 and the current 2012 has worked very well when the backup options are set to create x number of inc or diff and to keep x number of chains as shown in the illustration below.

My suggestion would be update to the current build and create a new task pointing to a new empty storage folder. The program will not delete the oldest backup until a new replacement has been made so you always need room for one more backup than indicated.

If you want the 2nd full to replace the first full, then set "keep x number of chains" to 1. The program will delete the oldest one when after the newest one has been created.

This type cleanup has worked much better than a cleanup based on days or disk space. I do not know how 6942 works on these two options but I know it works very well when told to keep x number of incs and chains as illustrated below. Change the 5 to your choice of 10 and set the number of chains to your choice.  Don't forget the risk factor of too many incrementals. If one of the older inc's become corrupt or non-readable, all the newer inc's are useless.

Pretty diagram, but it still doesn't work.

I have the latest build, and I recreated everything - Incremental backup with a full one after 10 incremental.

The last backup was at 2:00 this morning - it was #11

2011 worked fine.

VERY aggravating!

It might be beneficial if we could see a picture of your backup folder.

Did you start the a new task pointing to a new folder?

Which version and build of TrueImageHome?