Skip to main content

Acronis 2020 backup filename issues

Thread needs solution

Hi,

Can someone please explain to me why, when I boot from either the Acronis 2020 Bootable Rescue Media USB memory stick or from the Acronis 2020 F11 Boot Recovery Environment, why the filenames I specify for Full backups are not actually used for the created files? Except occasionally they are...

Allow me to explain: Having booted from either of the above methods with a view to creating an entire ("Full" not incremental) backup of my internal hard drive (apart from the ASZ of course), I specify to save the image in either the ASZ or directly to my USB stick and enter the filename I want (eg "GPT-Base"). I then select the other options such as max compression, verify backup, add comment, etc and that the file type field is set to "*.tibx; *.tib", and then the backup process starts. After a successful completion, I then reboot the PC to check the files and how much space they've used, etc, only to find that instead of being named "GPT-Base", "GPT-Base-001" and so on, they're either named "AA1" or "AAA1" and then the 001, 002, etc.

This occurs 99% of the time when I create images this way, but every so often it will then create one with the filename that I specify, but usually in those cases the imaging process fails for some reason halfway through. 

Both the ASZ and my memory stick are formatted as FAT32 and have more than enough storage space for the image to be created. The USB stick was created in Windows 10 using the Acronis 2020 tool, which I then used to create the ASZ and BRE.

I'm not so bothered about the backup failing part (I've usually identified why myself) but the filename issue is really annoying. 

0 Users found this helpful

Ben, welcome to these public User Forums.

Please see the ATI 2020 User Guide sections below related to your questions:

1. Backups created in Acronis True Image 2020 or later

Backup file naming

With .tibx files, the file name has only the backup name and an incremental counter. It does not contain any additional information such as backup method, backup chain number, backup version number, or volume number, which were used with the TIB format.

A backup name may look like:

  1. my_archive.tibx
  2. my_archive_0001.tibx
  3. my_archive_0002.tibx
  4. my_archive_0003.tibx

2. Backup file naming

Depending on the version by which a backup was created, its name will differ.

Naming convention for backup files created by Acronis True Image 2020 or higher

A backup file name has only the backup name and an incremental counter. It does not contain any additional information such as backup method, backup chain number, backup version number, or volume number.

A backup name may look like:

  1. my_documents.tibx
  2. my_documents_0001.tibx
  3. my_documents_0002.tibx
  4. my_documents_0003.tibx

Full and differential backups are stored in separate files and incremental backups are automatically merged into full backups.

The following backups continue to use the TIB format and naming convention:

  • File-level backups for all destinations except for Acronis Cloud. File-level backups to Acronis Cloud are in .tibx format.
  • Nonstop backups
  • Notarized backups
  • Backups which use CD/DVD/Blu-ray, FTP, or Acronis Secure Zone as their destination

Naming convention for backup files created before Acronis True Image 2020

A backup file name has the following attributes:

  • Backup name
  • Backup method (full, inc, diff: full, incremental, differential)
  • Number of backup chain (in the form of b#)
  • Number of backup version (in the form of s#)
  • Number of volume (in the form of v#)

    For example this attribute changes when you split a backup into several files. Refer to Backup splitting for details.

Thus a backup name may look the following way:

  1. my_documents_full_b1_s1_v1.tib
  2. my_documents_full_b2_s1_v1.tib
  3. my_documents_inc_b2_s2_v1.tib
  4. my_documents_inc_b2_s3_v1.tib

If you are creating a new backup, and there is already a file with the same name, the program does not delete the old file, but adds to the new file the "-number" suffix, for example, my_documents_inc_b2_s2_v1-2.tib.

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 for the response, but this still doesn't answer the question.  'Full' disk backups with multiple parts created using the Windows client have the file naming convention as "My-Backup-001.tibx", "My-Backup-002.tibx", etc, but if creating 'Full' disk backups having booted the PC from either the Boot Recovery Environment or an Acronis bootable USB stick, whatever filename I specify is just ignored, and backups with multiple parts are named "AA1.tibx", "AA2.tibx", etc.  In both scenarios the backup location is a newly created empty folder on the Acronis bootable USB stick. If I create a second, unrelated Full backup in the same folder as an existing Full backup called "AA1.tibx" then the second backup file parts are called AAA1.tibx", "AAA2.tibx", etc.  It doesn't matter whether the PC being backed up is configured using Legacy MBR mode or UEFI GPT mode, the results are as above.

Sorry but I have never had any issues with backup file naming using either the Windows ATI application or doing the same from the bootable rescue media.  The name used has always been the one I have chosen.