Backup Method Confusion
I am trying to use this schedule:
Full followed by 4 Inc then Full followed by 4 Inc
What I have is:
Only 1 Full and the rest Inc
Method set to Incremental
Create Full after 4 inc
Store 2 chains
What am I missing? How to update to get desired results?


- Log in to post comments

Also, if you are right now experimenting with the configuration, be aware that the counting of the incrementals is reset whenever you change the number of incrementals you want to keep, and possibly, when you change the auto clean up rules.
For example, if you first set your task to do 4 incrementals, wait for the first full and the first 3 incrementals to be produced and then change the setting to 3 imcrementals, you will end up with 6 incrementals (the first 3 that were done before the change, and the new 3 incrementals). I don't know what happends if you made several changes to the tasks simultanously. This is why we recommend you set up a new task, or simply move existing backup files to another directory, or simply wait for ATI to "catch up".
If ATI doesn't catch up, try to rename the database and the script folders under C:\programdata\Acronis\TrueImageHome, then add your backup back, then reconfigure it with the settings you want.
- Log in to post comments

Backups run when I manually do them. Attached are the requested items.
Attachment | Size |
---|---|
336367-126418.png | 304.21 KB |
336367-126421.png | 23.81 KB |
- Log in to post comments

It looks like something occured, or you manually made a change to the backup task between 1/8 and 1/18. If you had previously set up the task and modified it later, this is likely the cause. Once a job is setup, it is not recommended to modify it as it can lead to task/database corruption.
You have one full on 1/4/2016 (full_b11_s1_v1)
Followed by only one incrmental on 1/8/2016 (inc_b11_s2_v1)
Instead of 3 more incrementals though, it just goes to a new full on on 1/18/2016 (full_b12_s1_v1) ... which is why I'm assuming the task was modifed at some point.
You then get 1 full with all of these incrementals (5 in total instead of 4), which could mean that
A) the backup task database got corrupted, or you once again, changed the task somewhere along the line since 1/8/2016. Every time you change a task, it will start the incremental count over again.
Don't change the task in anyway and run a few more incrementals and see if it does what it's supposed to then.. create a full and then start incrementals.
If not, I would delete the backup job (you can keep the old backup files though), create a new task with a unique name (especailly if you keep the old backup files that have this name already) and let it run it's course without making any changes to the backup task.
Attachment | Size |
---|---|
336375-126424.png | 22.46 KB |
- Log in to post comments