Skip to main content

Naming of backup .tib files?

Thread needs solution

Perhaps not hugely important but can anyone explain to this novice exactly which step in the process of setting up a backup scheme determines the name of the saved backup .tib file? I have had to recreate my backup scheme settings after the reset-to-default debacle caused by installing an update to ATI 2020 Build 22510. I deleted the former scheme from the drop-down list in the name field in the upper right pane on the Backup scheme tab in the dashboard but I used the same settings as I had been using previously. However, backup .tib files now being created are being named according to the old, deleted scheme despite the current scheme and Backup (in left pane) being named differently. Not a major issue but it offends my OCD nature and I'd like to understand things better if I can!

0 Users found this helpful

If you are setting up a totally new backup task, then this will be given a default name taken from the drive or folder etc you select for the source, but this can be renamed to whatever name you want provided you do so before running the task for the first time.

The files created will assume the name of the task and for .tibx files can no longer be renamed after any files for the task have been created.

See 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).

Thanks Steve - some reading to do there; I'll start working my way though it. I have a lot to learn it seems!