The incremental backup option is broken in build 6613 (the latest update).
1) Create a new backup
2) On "Schedule" tab select "Daily" and specify a start time. I used 5am.
3) On the "Backup scheme" tab select "Incremental"
4) Select "Create a full version after every ___ incremental versions". I used 6 as the number of increments.
The next morning the incremental backup ran at 5am. And again at 5:20. And 5:40. It starts at 5am, runs every 20 mins and continues for SIX times, then it does a full backup. WTH? Is it a coincidence that I specified "6" as the number of incremental backups to run before making a full? Why is it running every 20 mins?
cheers,
Chris Curran
Anhang | Größe |
---|---|
acronis-incremental.png | 16.23 KB |

- Anmelden, um Kommentare verfassen zu können

Hi Chris,
Whats happening with the unwanted/unscheduled backup is not normal.
Simulate editing the task schedule. There should only be the one single start time listed with no repeat frequency listed. What does yours show?
A task edit usually does not fix problems, so lets start over with a new task but with slightly different settings.
Start over one more time with new task but with in the backup scheme selection, be sure and choose the "custom type" in the first windows as the GH12 example plus 5 inc after full, plus choose the option "store no more than 1 recent version chain." If you use your full plus 5 inc, your chain length is 6 files. (full plus 5 inc). If you wish to keep more than 1 chain of 6 files, then change the "store n" from 1 to 2 or more--however many chains you wish to keep.
With the chain length of 6 files and keeping only 1 chain, your retention quota is 1 chain. Deletion of oldest chain will occur when your quota of 1 chain is exceeded. The complete of the 2nd Full ( backup #7-beginning of chain 2) will cause your retention quota of 1 to be exceeded. Seconds after the 2nd Full is completed, the deletion of oldest chain will automamtically occur. If you should deciide to keep more chains, then deletion will be delayed until a later full - after an increased chain quota (store n) has been exceeded.
As for the schedule, I would use the 'WEEKLY" (daily did not work for you) and click on each day you wish to run your backups.
The new chain will begin on the next day which is checked. and run each following day checked.
GH64. 71342: 2015 How to save a non-scheduled task.
GH25. Understanding differences between Inc and Dif for Safety
GH63. 64640: Hints to help prevent issues with your TIB backup files creation.
GH63. 75086: A discussion on how to configure backup schemes.
Offficial Log File.
https://kb.acronis.com/content/49484
-----------------------------------------------
Other examples of types of backup with automtic cleanup.
Depending upon the type of backup scheme you wish to create, here is an example of each type. These can be set up for Disk image, or Partiton, or Files-folders backups. These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.
Editing an existing task is not recommended. Rarely does an edited task perform to user expectations. It is usually better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.
-----------------------------------------
- Anmelden, um Kommentare verfassen zu können

Thanks for the long thoughtful reply.
I did start fresh with a new backup definition, using defaults. Attached are the Schedule and Backup scheme screenprints (for the run of 14). It couldn't be any more basic of a backup spec, and it fails miserably. Acronis, seriously, you guys need help with your QC process.
cheers,
Chris
Anhang | Größe |
---|---|
286773-121105.png | 15.23 KB |
286773-121108.png | 20.23 KB |
- Anmelden, um Kommentare verfassen zu können

Hey! From one user to another. I am not Acronis. Make a new task like my custom GH12 with auto cleanup and you will be back in business.
- Anmelden, um Kommentare verfassen zu können

Thanks, but that's not the fix. It running every 20mins is the problem...
cheers,
Chris
- Anmelden, um Kommentare verfassen zu können