Aller au contenu principal

TI 2019 v. TI2020

Thread needs solution

TI-2020 and the .tibx disk backups are turning out to be a disaster for me.

I'm planning on going back to TI-2019.  Can anyone tell me what the advantage of TI-2020 is.

A full disk backup should always be restorable as a stand-alone file logically.

Stand-alone backups always made sense to me.  TI-2020 is really complicating  things from my viewpoint.

If I have to go back to a stand-alone older disk backup because of a corruption or malware, etc. that did not get noticed or caught, I've been able to restore an older disk backup, then update if necessary, and then restore a new file backup to correct the problem.

TI-2020 just adds absurd validation times with no significant improvement.  The idea that if the first backup file gets deleted in a schedule doing full disk backups then makes all the remaining full disk backups useless is seems very illogical to me.

So, explain why I should stick with TI-2020.

I've been using Acronis for about 15 years but I'm getting very frustrated with the changes made beyond Backup 11.5 and TI-2019.  I will be switching back to TI-2019 shortly.

Thanks,

Ralph Nielsen

0 Users found this helpful

Ralph, please edit your post and remove your email address unless you don't mind it being harvested by spammers etc!  These forums are open to the world and its dog!

ATI 2020 can work well provided that you know the new rules to follow and only allow any unwanted backup files, especially .tibx files, to be removed by using automatic cleanup rules or else using the 'Clean up versions' tool.  Using Explorer to remove files is a recipe for a disaster!

If you truly want single version full backup files then there are several ways of achieving this in ATI 2020:

  1. Set the task to do this but understand that ATI 2020 (& later) now keep metadata information about backup files in a small 12kb .tibx file.  If you keep all the files together whether in the original destination folder or if copied to a second location, then there should be no issues with recovery!  This is the recommended method.
     
  2. Copy or Move the initial full .tibx backup file (before any 12kb metadata file is created) to another location.  That copied / moved file is fully independent.
     
  3. Rename the file extension for the initial full .tibx backup file (before any 12kb metadata file is created).  This again will cause the renamed file to be fully independent but will need to have the extension corrected to be used for recovery.

The 2nd & 3rd options above can be done via a Post Command for the backup task if needed but you would either need to have Acronis Active Protection turned off, or use a standalone program that has been excluded from AAP.

I have used both options previously when testing this out for other users.

Note: if copying or moving .tibx files, it is best to rename the extension along with adding extra information to the root file name, i.e. MyBackup.tibx renamed to MyBackup5Oct20.~tibx - the reason here is to stop Acronis from finding these files and adding them to the GUI as new tasks that need to be reconfigured!

Steve:

Thanks for your comments. I did go back and remove my email.

I see where now in the new TI-2021 release, they allow setting validation on only the last backup version to alleviate the issue of validating the whole "merged" chain.

Your comments are generally helpful, but for now I'm sticking with TI-2019 because my schedules will basically run OK without the long validation times.

I was basically already doing your #1 suggestion and may have stuck with it but when I experienced the long validation time I went on the forum and then understood the issue.

I will eventually have to upgrade, but for now I will stick with TI-2019.

But your comments are always appreciated.

Ralph Nielsen