Questions re the recent True Image update from Acronis - "Known issues and limitations"
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.....


- Log in to post comments

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.
- Log in to post comments

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.
- Log in to post comments

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

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.
- Log in to post comments

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.
- Log in to post comments

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.
- Log in to post comments
