Is there a way to repair a Corrupted TIBX File?

Mike, there are no published methods of repairing any corrupted backup files of .tib / .tibx format.

There are various reasons why backups may become corrupt, especially with the new .tibx file format.  The main reason is when any files are deleted outside of using the options provided by Acronis using either automatic cleanup or the Clean up versions tool.  It is especially important to never remove or delete the 12KB metadata file that is a part of any .tibx version chains, as this will cause the remaining files in the chain to be deemed as corrupt!

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-2021: new tibx backup format FAQ

KB 63425: Acronis True Image: 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 and 2021: tibx backups in local destinations

Hi Steve

Thanks for the reply - I did not see this easily.  I was waiting for the Mods to OK the post.  I thought I would get some kind of notification? 

My new backup set is working - I check it often.  But I don't have / see the small  file that is often mentioned.  So I doubt I deleted it.

I will read the KB articles you posted - THANK YOU!

Still, I'd like to find an easy way to fix the broken ones - there is data in one of them that I NEED.

Thanks again

M

The small file [for backups using *tibx architecture - Disks & Partitions or whole PC) only appears after the fist cleanup operation has completed.

Ian

Mike Foose wrote:

I think this may be MY fault?  Once the drive gets too full I go in and delete the oldest files starting with the Large full BU and then the smaller VC's - I'll delete several 'Sets' till I have more room.  I always keep at least 2 'Sets' - Full & Version Chains.  Is this what is corrupting the remaining sets of Full & Versions?  I looked in the newer, working sets and still cannot find this '12KB metadata file'.

Am I doing this wrong?  Shooting myself in the foot?

Mike, if you are deleting these files manually via Explorer, then yes, you are doing this wrong!

See KB 61844: Acronis True Image 2019, 2020 and 2021: How to delete old backups

You should only ever delete .tibx files using the Clean up versions tool option described in the KB document so that metadata is preserved correctly.  There should be a 12KB metadata file for your version chains shown in your screen image for when a further new Full backup is being created and automatic cleanup is performed.

KB 63518: Acronis True Image 2020: do not delete first tibx file

Hi Steve and thank you for the reply!  And, BTW, Thank you for ALL The help you've given to SO many people here.  You really are a super star!

The image I posted it current.  The highlighted files are the NEW version chain that seems to be working as I can open and view drives and folders in each one.  I looked in several and cannot find that 12kb file.  Maybe it doesn't make it till there are more versions?  I am confused but want to get this right in the event of a failure.  I am a big fan of back ups but it seems that I would have been 'up the creek' had I needed the data.

Here is a Screen Capture of the FIRST NEW BACKUP on that list.  It is the full BU - for some reason it will not list sizes so I can't tell if that small file is in the set.  How do I find that SOB?

Also, I will be posting a new question about Cloning a drive for a new PC - looking for the slick way to do it so it works (I've used the clone feature before and it worked perfectly!)

Thanks again!!

Mike, what you are seeing for your new backup version chain is correct for a Differential backup prior to a new version chain being created and automatic cleanup being used to 'clean up' the oldest version chain where the initial / first .tibx gets reduced to just 12kb to hold only metadata.

You will not see the 12kb .tibx file contained within the view inside of the other files, it is a separate stand-alone file (which has caused confusion with users thinking it is a corrupt file!).

The images above show how this looks on my system with a couple of my backups on different drives.

For the top image, the older Win 10 SSD backup was set to only keep 1 version chain and had been cleaned up using the Clean up versions tool which reset the numbering back to -0001

The Win 11 SSD was a new backup task created after upgrading the system from 10 to 11 and hasn't yet created the 12kb metadata file.

For the lower image, you see a 12kb DriveD.tibx file and then because of the automatic cleanup rules and keeping 2 version chains, I have -0022 and -0023 version chain files.

What I am finding a little puzzling in your earlier file listing image, is how you have what looks to be the size of a new Full backup file (148 or 149 GB) but given the next sequential number, i.e. -0006 in the new version chain?  This may be a peculiarity of how differential version chains work that I am not familiar with as I have only used this type for testing purposes.  All my own backups use Incrementals which get consolidated with the Full backup for the chain, so don't get a separate sequence number per backup file.

If you could post an image of your Backup Scheme settings page, then should help clear up this for me?

Thanks for the reply - Is this adequate?

I'll review it all later.  Have to go into the field and do some work :+(

Mike, thanks for the further screen image.

My first comment is to hope that you have a very large destination backup storage drive to hold all the backups that are going to be created by your chosen backup scheme!

Looking at the earlier image showing the files, sizes and dates created, you are looking at creating backup version chains of around 170GB every 6 days, and the settings shown from the settings page will only delete the oldest such version chains when they are over 6 months old.

Doing some simple maths, this suggests you will create 30 version chains of 170GB each which will require over 5TB storage to hold.

Differential backups also increase in size with each backup run by virtue of always capturing all changes since the initial Full backup each time.  Incremental backups only capture the changes found since the previous backup whether a Full or previous incremental, so sizes are normally smaller.

My own personal preference for backups is as shown in the image below:

The above backup is only run once per week but is accompanied by different backups going to alternative destinations so that the disk is being backed up 3 times per week on different days and stored in different destinations each time (to avoid all eggs in one basket!).

Thanks f or the wisdom - I am VERY glad to have the coaching!!

I want daily back ups.  This is a business computer.  Some custom software for the company and quickbooks data that changes daily.

What do YOU suggest for a scheme?  I like the VC idea but if there's a better way, I'm all ears!

The Custom software for the company does it's own backup every night and that file is included in the ATI files - so there are 2 of them (but both end up on the 4 TB USB External)

Let me know & I'll set it up

Thanks

M

Mike, you could still keep to a daily backup schedule and even increase this to either twice daily or even hourly though the destination storage requirements will obviously increase if doing so!

Some questions to consider?

Do you really need to keep 6 months worth of backup version chains?

Do you really need to do a whole disk backup of the OS, all applications and all data as a single operation, or could this be split into multiple separate backup tasks with different schedules?

If both QuickBooks and your custom business software provide their own backup tools, then why not make a separate Acronis backup of just those business backups using a Files & Folders task.  This could be scheduled to run after these business backups have completed.

For business data, you could setup a separate backup task with an increased frequency, i.e. hourly if appropriate, where the volume of data being generated will be significantly less than the current 170GB version chain creates.

Most OS and application data does not change as often as business / user data, so this could be backed up on a lower frequency such as once or twice weekly.

I would also suggest considering using Incremental backups to take advantage of the lower backup image size plus also the automatic consolidation of incremental 'slices' into the same file as the full backup of each version chain. 

I would suggest testing out the above suggestions by setting up some separate incremental tasks, ideally using another destination storage drive if you have one.  Please ensure that all backup tasks have unique names and the backups are stored in separate folders where possible - this helps protect against any accidental changes or deletions etc.

I did not forget about this.  Am waiting for 2 5TB Externals that will be here Tue.  When I get them I will set em up and create new back-ups.  In the mean time I DID change from VC to Incremental.  I will study more as I set it all up.  I have always been a BIG FAN of backed up data and I like Acronis.  It's actually quite sophisticated.  I want to be able to use all or most of it's power