Skip to main content

[ISSUE] Incremental Backups Contained within Main/Full Backup File TIBX

Thread needs solution

I am not sure who was the genious (please fire them) who thought it will be a great idea to merge incremental backups into the main backup file as I am having trouble with synching the same HUGE file to cloud every single day due to main backup file modification.

At least make it an option to create seperate incrmental files because then we won't have to synch the main file again and again, every single day.

I can manually remove the auto synch with my cloud provider but then what if forget to manually synch and why it has to be a manual process for the customers because Acronis decided to have this terrible design choice?

 

How do I get out of this problem? Is there a back up type that does the similar thing where main back up is created once and then the rest are smaller files until a full back up is made again?

 

Thanks

 

0 Users found this helpful

George, welcome to these public User Forums.

The change to .tibx files occurred with the release of ATI 2020 and only applies to Disks & Partitions backup schemes with the automatic consolidation of incremental backup slices within the full backup file.

See forum topic: How to create a Disk backup as .tib (not .tibx) which will create a new backup task using the older .tib format in the Windows ATI 2020 or 2021 GUI.

Hi

 

I followed the process but it did not work work with CPHO version. Even though I was able to modify and save the settings file, the back is still being created in tibx format and my network is under immense stress to upload the backup file to cloud!

 

Is there another way to force TIB file instead of TIBX? I need to resolve this ASAP, please!

 

Why this was not considered when the decision was made to use TIBX file to merge incremental backups? Don't the devs see the issue here or they had a work around in mind when they made that design choice?

 

George, the process to force .tib files instead of .tibx only works for new backup tasks - it does not work for tasks which have already created .tibx files.

Why the devs forced this change to .tibx files is one they haven't shared with the public, and I doubt they even considered users uploading backup files to other locations / remote servers etc.