So, I always stay clear of deleting versions or backups whether within ATI or in Windows. Deleting versions from within ATI updates the database, but can corrupt the backup chains anyway because of other bugs. What is certain is that deleting TIB files manually does corrupt the database. IMO, the database is creating more problems than it is solving. The database is enabling fancy options like doing a full backup on one disk, but continuing the differentials or incrementals on another disk. It is just a way for ATi to track where each TIB file is, and how they form chains.įortunately, even if the database is corrupt, you can restore files in some cases. The database doesn't influence how the archives can be restored. It will take a couple of weeks to get an answer and I will let you know if it works. The backup schedules only take a couple of minutes each to create so rather than importing them I will start from scratch, that way I know everything is clean. It was a while ago and I didn't remove the backups first, however it didn't register the old files when I reinstalled and I created a new set of schedules that work in every respect but don't automatically clean.Īs there is no evidence that the database is corrupt I will completely remove ATI from the PC and reinstall with the latest version. I have in the past removed and reinstalled the software. In addition I have recently created a set of entirely new schedules that also don't automatically clean. This suggests that the database isn't corrupt. tib files that physically exist, they all verify and I have recently successfully restored a complete image from one of the. Secondly when I go into ATI it only sees the.

Firstly because it has never worked and I had to start manually deleting files because ATI was not automatically cleaning them. I'm sceptical that this issue is a corrupted database caused by manually deleting.

Delete acronis true image 2017 backups