Setting/Correcting options on backup
I added two weekly "full" backups, but on the second backup I made a mistake when setting the options, and after the initial backup Acronis TI started creating incremental backups instead of "full". I changed the settings to "full" but when the third backup was created was also incremental. I deleted all the backups and added two new weekly "full" backups, but the problem with the second backup reverting to incremental has persisted.
Does Acronis TI save the old settings somewhere and it keeps on reverting to them? If so, how do I delete these old settings and force Acronis TI to honor the new settings?


- Log in to post comments

Hi Steve,
I did not delete the backups using Windows Explorer. I deleted the backups using the ATI 2020 application interface, but I chose to only remove the backup itself, not deleting the physical images themselves. Then I renamed the folder they were contained in.
Do I have to also delete the images as well?
Obviously I don't know the internals of ATI, and of course what this internal database looks like or how it functions.
I suppose that I was wrong in thinking that removing the backup definition using the ATI interface it would actually remove them from whatever file it saves these options in.
Please let me know, do I have to delete not only the definition but also the .tibx images as well (of course always using the ATI interface), and when I add the new backup definitions/options, should I also rename the directory/folder where the .tibx images will be stored?
Thanks!
- Log in to post comments

George, the internal database (SQLlite) used by Acronis is something that should not be touched or changed other than by the ATI application itself, this is due to the complexity of the way information is stored.
With .tibx files used in ATI 2020, additional metadata information is stored within the backup files themselves, along with incremental backups being stored in the same file as the initial full backup they were based on.
For the above reasons, the simplest solution to your issue would be to set up a totally new backup task, with a name not used by any other backup tasks and let this create a new full backup image before then removing any files left over from the previous task or that task itself.
So long as each backup task has a unique name, there shouldn't be any issue with them sharing the same folder on your backup drive.
- Log in to post comments

Hi Steve,
Thanks for your quick reply.
I had no intention to meddle with ATI's internal database. As a software engineer of 40+ years, I know not to touch product databases, especially without the appropriate interface.
I will create new backups using different names. I wish that ATI would not depend on the name of the backup but on the actual options themselves, as in my view this is a short-coming.
- Log in to post comments

Hi Steve,
I created new backups, with full image scheme, using different names a week ago, and noticed today that the options were adhered to.
Thanks for your help !
- Log in to post comments

George, glad to hear that the options are being preserved correctly as they should be! Thanks for the feedback.
- Log in to post comments