ATI 2016 suddenly creates only full backups anymore
Hello,
I'm using ATI 2016 to do a simple volume based backup of my Computer to my NAS. I set the backup job to do incremental backups and to create a new full backup after every 6 incremental backups. The job is scheduled to run once a day and versions older than 7 days are beeing deleted. Recently (5 days ago) I added another volume to the backup job so there are two volumes to be backed up now by this job. So far so good.
Today, I got a notification from my NAS about disk space running low. So I checked for possible reasons and found out, that since I added the second volume to the backup up ATI only created full backups every day instead of incremental backups. All of them named like "MY_BACKUP_full_b16_s1_v1-n.tib" where "n" has the values from 1 to 5.
I checked the settings of the backup but couldn't find anything wrong. I even tried to change, save and rechange the backup type settings and manually started the backup job. Everything I got was another full backup.
I don't know how to debug and for the best fix this problem. Has someone here got an idea how this issue can be fixed? For storage reasons I really need to get back to incremental backups.
Thanks in advance
Max
EDIT: Fixed some typos


- Se connecter pour poster des commentaires

Bobbo, thank you very much for your advice.
Today, TI gifted me with an incremental backup again! Without having changed anything, neither the backup settings nor the NAS.
Still not knowing what caused TI to create 5 full backups in a row I starting to believe this was some kind of intented behavior... I can exclude any possible issues with the NAS as there were no changes in privileges, no connectivity losses and always enough space available (even it was running low in the end...).
Is there documentation available about the backup file naming? I'm wondering why all of the said full backups are meant to be the same version "b16" and are only distinct by an additional number as suffix...
- Se connecter pour poster des commentaires

By modifying an existing backup task you confused the applications backup database. This is why task modification is not recommended. It is recommended that if changes are needed the existing task be abandoned and a new task created using new names and backup folder locations.
I think you are extremely lucky that the app picked up the modified task and began to function as you intended on its own. That is a first I have seen here in the Forum for me! I would keep close watch on it to make sure it sticks however!
- Se connecter pour poster des commentaires