ATI 2019 looking for full version in wrong location
The way my backups work is that a daily full then differential backups of my PC's system drive are created on my Synology DS1618+ (\\Therver\my backups\this). On the last day of the month a script runs which copies all the .tib files to the appropriate yyyyymm folder, deleting any folder more than six months old, and the cycle starts again the next day. In addition, on the last Sunday of the month, a full backup of the PC is made to removable drive G:. I have six of these drives, used in rotation.
A week or so ago the differential backups stopped working, claiming the full backup on G: wasn't available. This is very true as there's at least a metre air-gap between the PC and the draw in which my backup drives live but why is it looking on G: now when it's been happy since initial installation four months ago? Is this a faulty database and can it be fixed? Is the easiest route just to delete and re-create the job?
ATI 2019 17750, W10 x64 Pro 1809
I'm sorry this has ended up here as it's the second time I've tried to create it in the ATI 2019 section. I'll have a third go and delete this if I succeed. (Later) My third attempt failed as well so I'd be grateful if a mod could move this to the right place.
Jonathan
Thanks for the reply. The backups run automatically via the Acronis scheduler either late at night or in the early morning. There are only two jobs - one daily and one monthly. There's no need to check for the correct G: drive as they're labelled Jan/Jul etc. so I insert the correct one and a pre-backup script simply deletes the previous ????MM.tib to make space. Yes, if I was still doing this professionally I'd add a check for the correct drive but so far I'm still capable of following my own instructions......
On the last day of the month a script runs which copies all the .tib files to the appropriate yyyyymm folder, deleting any folder more than six months old, and the cycle starts again the next day. In addition, on the last Sunday of the month, a full backup of the PC is made to removable drive G:. I have six of these drives, used in rotation.
Assuming that you are also deleting files after doing the copy of the .tib files on the NAS, plus your use of 6 rotating backup drives all using the same drive letter G: for a single backup task - then there is a very real chance that the internal Acronis database is out of sync with the real, actual status of backup files for your tasks
Any time that .tib files are moved or deleted outside of using the Automatic Cleanup rules or the new 2019 option to Cleanup versions, then information is left behind in the database, and you would need to perform a validation for the task that created those moved or deleted files in order to try to reconcile the information in the database.
ATI is not designed to be used with rotating drives for a single backup task though the impact of doing this is lessened by only making full backups - if doing this, then at a minimum you should reselect the destination for the backup task then do a validation before running it.
It would be better and recommended to have a set of backup tasks using the same names as your set of backup drives, then only run these when the correct drive is connected to avoid problems.
Your methodology of handling backups is not an anticipated method used in the design of True Image. True Image by design expects to find all backup files it has created by defined tasks in the defined destination location of the that task. Therefore, changes made to the location of backup files outside of the application GUI will result in unexpected behavior like that you have experienced.
The advise Steve offers is sound and I concur that a separate task should be created for each of your G drives as a possible solution for you.
Thank you, gentlemen. I understand what you're saying so will need a hard think about how to proceed. ATI 2014 worked perfectly for five years under W7, ignoring my scripted clean-ups of the month's differential backups as well as the monthly full backups so it's only become a problem with 2019. It may be that ATI is no longer the product I need and I will need to look for an alternative which would be a pity as my use of ATI goes back to V11.
It is a long time since I used ATI 2014 so not in a position to test how it handled rotating drives but there is evidence in the forums that this is not a new problem with ATI 2019 but has been around and happening for some years!
See the following topics that have discussed this over the past couple of years.
Thanks, they were very interesting and could prove helpful.