Creating Multiple One Time Backups

You can create a Custom Full backup and use the Automatic cleanup options to set how many full backup files to be stored before the oldest file is deleted.

The name for the backup files will be the name given to the backup task and the only change to this will be the numeric suffix, i.e. MyBackup-0001, -0002 etc.

With ATI 2021, disk backups will use .tibx files and the backup files are interdependent by being linked via metadata and must not be manually deleted except either via automatic cleanup or by using the clean up versions tool.

For automatic cleanup, I would recommend using 'Store no more than X recent versions' and setting X to a value that would allow for X+1 full backups to be stored on your dedicated backup drives.  Automatic cleanup deletes the oldest backup when the X+1 new full backup file has been created successfully.

I am responsible for backing up two separate pcs at my company, both standalone.

In what way are they standing alone? As in not connected to any network?

I'm thinking about what this means for True Image and how you do backups. On a network or not, I believe each of them will need to have True Image installed on them. However, it's not impossible to envision a scenario where you can backup each of the two PCs to a third PC as backup destination, and having the backup operation remotely controlled from the third PC (clients and a server). That's a scenario probably reserved for Acronis' business products, not something that True Image is capable of.

I want to create multiple onetime backups on each of my dedicated backup disks, with each one having a different name.  If I use Acronis single backups, each of my backup will be overwritten.

You mean you want to do a full backup each time you run a backup operation? By single backups you mean a backup plan that does not run automatically on schedule, i.e. it just runs when you click the button or by some other trigger? That's the "Do not schedule" schedule option, or the "Upon event".

I think Steve's suggestion is what you're after.

The name for the backup files will be the name given to the backup task and the only change to this will be the numeric suffix, i.e. MyBackup-0001, -0002 etc.

With ATI 2021, disk backups will use .tibx files and the backup files are interdependent by being linked via metadata and must not be manually deleted except either via automatic cleanup or by using the clean up versions tool.

Steve, I'm curious, would each of these files (MyBackup-0001.tibx, MyBackup-0002.tibx) be a full version? Can they be used independently to recover from a disaster, for example in case MyBackup-0001.tibx gets a few corrupted bytes, but the other file is not corrupted? Does it too become corrupted by not having its partner along with it?

Samir wrote:

Steve, I'm curious, would each of these files (MyBackup-0001.tibx, MyBackup-0002.tibx) be a full version? Can they be used independently to recover from a disaster, for example in case MyBackup-0001.tibx gets a few corrupted bytes, but the other file is not corrupted? Does it too become corrupted by not having its partner along with it?

To my knowledge, these are independent if used with the Acronis Rescue Media (as this does not use the internal SQLite database used by the Windows app).  Where metadata may be used even with rescue media is to offer choices for restore points in the calendar type panel during recovery, so ideally all linked files should be kept together and only removed as below.  I mainly create incremental backups where all the increments are consolidated within the single .tibx file so the calendar panel makes more sense in that context than with full backups.

If one of the 'linked' full backup files became corrupted, then you can use the Clean up versions tool to remove just that one backup and clean up the metadata / linkage to the other files.

If a Custom Full backup scheme is used, then each file is a full backup image.