Skip to main content

All these issues and still released?

Thread needs solution

With all these known issues, why was this released now (I suspect to hit the deadline)?

Known issues and limitations of this version

  • Please note that the new technology for disk-level backup is introduced in Acronis True Image and is being improved, so it may currently have the following limitations:
    • TI-169821 Backup conversion to VHD format is not present for the new backup format.
    • TI-171553 Moving the backup through the Acronis True Image console is not present for the new backup format.
    • TI-169548 Renaming local backups is not possible for the new backup format.
    • TI-172340 Backup mounting option is not present for the new backup format.
  • TI-168095 Cloud Entire PC backups are empty if browsed from mobile applications.
  • TI-172086 Differential backup is created instead of a full backup after the second launch of a local disk backup with "Version chain" scheme.
  • TI-168969 Acronis Universal Restore cannot detect external USB drives.

Granted not all are very important, but conversion to VHD is pretty major and not being able to use USB drives in UR is potentially a huge issue!  Annoying is not being able to rename backups and mount images anymore too.

All for a new file format, which should have these abilities of the former and for what?  Better cloud backups at the expense of local ones?

These going to get fixed soon?  There an option to stick with the previous format for now?

1 Users found this helpful

My understanding is that .tibx is the default and looks to be the only option moving forward.  Right now, if you do a disk or partition backup, it is .tibx, but if you do a file/folder backup it is .tib.  I believe they plan to make them all .tibx in the future.  The only work-a-round we've seen (and I haven't been able to test with the public release yet) is to start a disk backup from rescue media and it would be in .tib format (at least in beta).  Then you could import it and it would continue with the .tib format. Definitely not user friendly, but may be a work-a-round in the interim.

I'll add to other broken or unfinished things I'm finding in my testing of the public release today (so far).  Overall, it's working, but kind of bummed to see so many unaddressed issues and I hope that updates come more quickly than just quarterly to polish this up a bit more.

01. The gui scroll bar is still very skinny and hard to see.

02. The scroll bar in the task bar notification area is still very skinny, hard to see and covers the "X" to delete entries

03. There re still no options to enable/disable AAP in the taskbar notification area, although it is being planned.

04. Incremental and Differential backup times are still very slow compared to the original full.  I.E. my full backup is 15GB and takes about 8 minutes.  I immediately do an incremental (with no changes to the system) and it takes a little more than 3 minutes to complete just 85MB.  This behavior repeats for all incremental and differential files in my tests.

05. Validation of a backup with the .tibx format still validates all backups and not just the most recent one or even just the current chain.

06. The GUI still auto-scans and automatically adds existing backups that it finds and there is no way to prevent this or change the behavior

07. In the GUI under the activity tab, validation has no information about start, stop or total time to validate a backup

08. In the taskbar notification area, validation is not referenced at all

09. Manual cleanup of incremental jobs in the .tibx forma is all or nothing for a chain.  For instance, if I select the first incremental, it deletes the full and the incrementals after it.  If I select the 2nd incremental, it selects the full, 1st incremental and all incrementals after it.  In the older version, you could leave the full and any incrementals before a particular file in the chain.

10. The calculations for a backup or validation are still inaccurate and fluctuate a lot.  Basically, the progress bar doesn't offer much assistance in actual performance, time elapsed or time needed to complete

11. I noted this, but it's in the notes... can't rename a backup job once it's been run

12. Not in the notes, but if you clone a backup job, you can't rename it, even if the job has not been run yet or not.

13. Editing post to add this as well - bitlocker with manage-bde command in rescue media is still not functional.  Bitlocker is successfully removed (disk is unlocked) but True Image 2020 rescue media still thinks the disk is locked.