How to manually name full backup files?
I'm using Acronis True Image 2021. I'm doing single-version full backups. How can I manually assign a name to the backup file so that it doesn't over write the same file name each time. With my previous version of Acronis it would prompt me for the backup file name and location each time I performed a backup and I was able to maintain multiple versions of the full backup, each with a unique file name and date.
Thank you for the quick reply. I will try your recommendation. It's a bit disappointing that the new version omits the simple task of choosing a file name during the backup process.
Let me ask another silly question. I notice that after ATI creates a full backup I have (2) *.TIBX files. One with a size of 12KB and another with a size representative of the data I backed up (115GB in this case).
Does ATI need both of these files to do a restore? My previous ATI version only ever created one file.
After the backup is complete, could I simply rename both of these files and then if I ever needed to restore them simply browse to them in the "restore" portion of ATI? I did this all the time with my old version.
John Gayman wrote:Thank you for the quick reply. I will try your recommendation. It's a bit disappointing that the new version omits the simple task of choosing a file name during the backup process.
John, I have to confess that I have no recollection of ever seeing any option is any version of ATI that provides a means of choosing a file name during the backup process?
There was a method of editing the associated backup task script (.tib.tis) file to allow an automated renaming of backup files to include such as date & time etc, but this no longer works with the new .tibx backup files introduced with ATI 2020 due to the additional dependencies now present with these type of files.
John Gayman wrote:Let me ask another silly question. I notice that after ATI creates a full backup I have (2) *.TIBX files. One with a size of 12KB and another with a size representative of the data I backed up (115GB in this case).
Does ATI need both of these files to do a restore? My previous ATI version only ever created one file.
After the backup is complete, could I simply rename both of these files and then if I ever needed to restore them simply browse to them in the "restore" portion of ATI? I did this all the time with my old version.
John, the 12KB .tibx file is essential to the correct operation of ATI for Backup or Recovery! It holds metadata that links the files and is one reason why you should also not rename the files once this file is present!
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 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
Steve Smith wrote:John, I have to confess that I have no recollection of ever seeing any option is any version of ATI that provides a means of choosing a file name during the backup process?
Attached is a screen shot from my ATI 2013. I believe this same choice was in at least 2018 or perhaps later. It was so simple; choose a location, designate a file name and off you go. :-)
Thanks for the KB article references. I will definitely give those a read.
I did as you suggested and created a new backup instance with a descriptive name. It worked great. I now have a full backup file with a description name and a date. However, the original 12KB TIBX file remains with the original cryptic name. I thought by deleting everything it would create a new 12KB TIBX file with the new naming structure.
I still can't believe they took something that was so simple and made it a mess.
John, the image from ATI 2013 is essentially the same as creating a new backup task in all later versions, where the file takes the name from the task.
The 12kb TIBX file is only creating when a new Full or backup chain is created for a task where an earlier chain or full has already been created, thus the interdependence for the same.
If you only create a single Full backup for a task, then there is no 12kb metadata tibx file.
John, if you did not delete and remove the first backup name then you should still have the two originally named .tibx files you mentioned earlier... one 12KB .tibx and one full size .tibx.
If you create a second backup with the new name and your cleanup says to only keep one full version, then you would be left with the two .tibx files, the first being only 12 KB.
Basically in 2020 and newer with the .tibx file extension, manual manipulation of backup files is frowned upon because of the meta captured in the original backup and then later appended in a separate additional file with subsequent full backups in the chain.
Since OP wants to have a single backup scheme, but keep older backups, this causes an issue with the history of the backup file in the meta.
Solution is to create a new backup each time (using Steve's suggestion of cloning the backup), or simply using a single backup scheme, but with a retention policy. This will create a full backup each time, but maintain the other backups for the number that is set in the retention policy. Essentially this is what OP is wanting to do, minus the name differences. Unfortunately, you can't / shouldn't rename files manually this way.
You have always been able to set the backup name prior to the first full backup. You can actually change the name in the GUI later on, but may not reflect in the actual file created (and should not manually change it either if you want a working backup file in 2020/2021).
This KB should probably be renamed to "do not delete or rename outside of Acronis", but it explains the issue better
Steve Smith wrote:John, the easiest / simplest way of doing what you ask is as follows:
Create your first single version backup task with its own unique task name.
When you want to make the next backup with a new unique name, use the option to 'Clone settings' for the first task, then use the 'Rename' option to set the new name.
At this point you now have two backup tasks, so if the original task won't be used further, you can use the 'Delete' option followed by 'Remove only the settings' to leave the backup file in place.
I just wanted to let you know that I've used this method for several backups now and it works just fine. Using the clone function it is quite effortless. Thanks!