Aller au contenu principal

Questions re the recent True Image update from Acronis - "Known issues and limitations"

Thread needs solution

AFTER I installed this update last week, the Acronis system showed these warning messages:

Known issues and limitations of this version

    Acronis True Image 2020 introduces a new technology for disk-level backup. The technology is still being improved, so you might encounter the following limitations:
        TI-169821 Backup conversion to VHD format is not present for the new backup format, *.tibx.
        TI-171553 Moving backups by using the Acronis True Image console is not available for the new backup format, *.tibx.
        TI-169548 Renaming local backups is not supported for the new backup format, *.tibx.
        TI-172340 The backup mounting option is not supported for the new backup format, *.tibx.

What exactly do these messages mean?

That I can't move new backups from their original location and expect them to work?  Does that mean I can't copy backups from my desktop to an external hard drive and expect it to be usable?  Really?

That I can't rename backups on my system?

And what exactly is the "backup mounting option" which is now not supported for the new backup format?

Will all new backups now utilize the new *.tibx format?  Is there any way to continue to use the old format?

Finally -- can you believe that just as I was keyboarding this input, my Win 10 pro system flashed a message to the effect that "New updates are available from Acronis!"     Dandy.....

0 Users found this helpful

Welcome to these public User Forums.

These are all current limitations for the new .tibx file format used by ATI 2020 when creating new Disks & Partitions backup chains.

They do not apply to Disks & Partitions backups continued from ATI 2019 or earlier versions which will continue to use .tib file format.  Nor do they apply to Files & Folders backups which also use .tib files.

I would suggest looking at the following documents:

The following KB documents published by Acronis with regards to .tibx files.

KB 63518: Acronis True Image 2020: do not delete first tibx file

KB 63227: Acronis True Image: Do not delete .TIB or .TIBX files outside of Acronis True Image

KB 63498: Acronis True Image 2020: new tibx backup format FAQ

KB 63425: Acronis True Image 2020: Limitations of tibx backups

KB 63516: Acronis True Image 2020: Incremental backups do not create separate files when using new backup format

KB 63445: Acronis True Image 2020: how to view and manage backup versions in new backup format

KB 63444: Acronis True Image 2020: tibx backups in local destinations

KB 63613: Acronis True Image: local backups are not available for recovery if "metadata" file appears in the backup destination - if you see metadata file(s).

Final comment: Acronis are well aware of the customer reactions to these limitations and are working on bringing back as many of these features in future new builds or versions, but with no published time scale for doing so.

To put all the above in context, TIBX files have been used in the Acronis premium business product range for some years with success, so this is part of an attempt by Acronis to bring the ATI products into line with their business applications, which in turn will reduce the need to develop and maintain two separate backup product technologies.  The limitations are an indication of the complexity of this consolidation of product technology while keeping the same look & feel of the ATI application.

Well, I'll try to carve out time to read all that stuff. But as far as I'm concerned it's a huge black mark against Acronis.

Any software that updates after purchase and thereby no longer provides basic functions (which is why I bought it in the first place) has broken the implicit agreement with customers.  I have to read 8 (!!) documents to figure out what functionality I've lost and what different things I have to do to retain functionality? 

Especially with regard to

" TI-171553 Moving backups by using the Acronis True Image console is not available for the new backup format, *.tibx.
and  TI-169548 Renaming local backups is not supported for the new backup format, *.tibx."

Give me a break.

Please note that Acronis are currently running a beta program for the next version of ATI (2021) where the two issues you mention above (Especially with regard to...) have been addressed in the ATI 2021 version in response to all the feedback from users.

See https://www.acronis.com/en-us/personal/computer-backup/beta/ if interested in having a voice via the beta?

All changes take time to adjust to but personally I am happy with the way the new features of both ATI 2020 and now 2021 are working for me.  I am speaking purely as a user in this context - I am not an Acronis employee or paid by them to help in these forums.

These limitations don't apply to 'boot from the rescue media and making full backups offline from Windows", right?

William, the answer is 'it depends!'

If you use the rescue media and create a new backup with a unique name each time, then those full backups are independent of each other.

If you create incremental or differential backups using the rescue media, then they are dependent on each other for obvious reasons.

So if I user your option 1 above, 'useing the rescue media and create a new FULL backup with a unique name each time', then there will be no limitations to the backup files?  i.e., I could rename and move the backup files without any restrictions.

William, sorry but at cross purposes here.

Using the rescue media and unique names will keep your backup files as fully independent of each other.  You can rename those backup files and move them provided you do this outside of any involvement by the ATI GUI, i.e. do this in Explorer.

If you add any of the backup files into the GUI using the 'Add existing backup' then some of these limitations will come back.