Skip to main content

ATI trying to make a full backup even when it's to make an incremental backup

Thread needs solution

I have this file backup (Audio):

It's programmed to do just the starting full backup and after just incremental backups:

However, when the backup starts, it's creating a NEW FULL BACKUP:

How to fix this?

0 Users found this helpful

Your screen image only shows that your full backup is being split into 4GB chunks (194 of them for the b1 chain full file) after which 2 incremental files were created for that b1 chain, then a new b2 chain was started but is significantly smaller in size.

This suggests to me that you have made changes to the configuration for this backup task since it was originally created, which is known to cause this type of issue.

Thanks, but if you look closer, you'll see that "b2" is a full backup. And the screenshot was made during the backup before it was interrupted.

ATI should have continued the incremental backup and not started a new full.

- Move manually all the existing backup files to another folder on the same disk (to avoid a long copy)

- in ATI, choose recover for this backup task. ATI will complain there are some missing files, click ignore this version until it tells you there is no backup data

- run the task again and verify the backup type is correct.

Did you make changes to the backup task configuration / settings?

Just looking at screen images won't explain what is happening here - the log files are needed for a better understanding, and as this is ATI 2020, that includes needing the backup_worker logs as well as ti_demon logs.

Pat L wrote:

- Move manually all the existing backup files to another folder on the same disk (to avoid a long copy)

- in ATI, choose recover for this backup task. ATI will complain there are some missing files, click ignore this version until it tells you there is no backup data

- run the task again and verify the backup type is correct.

Thanks, Pat, but before doing your suggestion, let me confirm: in your 3rd step should I "run the task again", even with the current backup still inside another folder, as you suggested? 
Or do I need to move the files back to the original folder before running this 3rd step?

Steve Smith wrote:

Did you make changes to the backup task configuration / settings?

Just looking at screen images won't explain what is happening here - the log files are needed for a better understanding, and as this is ATI 2020, that includes needing the backup_worker logs as well as ti_demon logs.

Actually, due to another mess created by the support team, I lost my backup scripts, but I got to recover them as suggested here: https://forum.acronis.com/forum/acronis-true-image-2020-forum/how-recover-backup-scripts

As indicated in images, I have 3 backup scripts (besides NonStop Backup).

I got to continue the incremental backups for 2 of them, using "Add backup -> Add Existing Backup".

I did the same for the 3 backups, but just this current backup "Audio" is having this issue.

That is a key factor here.  Your original backup files were all created in August, you recovered your backup scripts on or after 10th September, and a new backup full file was created on the 12th Sept.

If you only copied back the contents of the Scripts folder, then there was still a mismatch with information held in the internal Acronis Database for this task.  This could have resulted in ATI creating a new b1 full but using the _v1-1.tib file extension, but instead because it recognised that you already had a b1 chain, it created a new b2 full instead.

The acid test here is to continue this backup and confirm that it now creates incremental files for this new b2 full chain.

The alternative would be to make a fresh start with a new backup task for your Audio files where the above hasn't happened to distort how ATI works (and Support haven't been fiddling on your computer to cause the loss of existing tasks etc!).

rogeriodec wrote:
Pat L wrote:
[...]

Thanks, Pat, but before doing your suggestion, let me confirm: in your 3rd step should I "run the task again", even with the current backup still inside another folder, as you suggested? 
Or do I need to move the files back to the original folder before running this 3rd step?

You leave them in the other folder for safekeeping. We are trying to reset the backup task without having to do another one. If you prefer, you could simply delete the backup task after having moved the files out, then set a completely new task.

While editing backup tasks is obviously supported by the product, when users make multiple tweaks, manual deletions, it happens that the task settings get messed up, or appear to get messed up. Changing location is a big offender for example, but even tweaking backup type or retention rules can throw off the user and or the software.

Well, it's a shame that after so many years of ATI we still have to do many manual workarounds...