Skip to main content

tibx vs tib (yes, again)

Thread needs solution

This past weekend I wiped clean my 2tb portable drive. I created one differential backup job of the C: drive only. I has run twice so far - on Sunday and today. File names on those two backups are Phred_Boot.tibx and Phred_Boot-001.tibx.

Today I created another differential job on the same machine with the same portable as the destination, but to a different directory. This is a backup of all the drives and partitions on the machine. The name of this job is Phred Full. The file name of the backup created today is Phred Full_full_b1_s1_v1.tib

Both backs have validated as good, But why would one job have the new naming format and the other job have the old? I'm not looking to change one to the other. I'm just confused as to why this would happen. Curious minds want to know.

0 Users found this helpful

Phred, what version of 2020 do you have installed?  My understanding is that the current release uses .tibx for all NEW backup jobs (both disk/partition and file/folder) and should apply to "entire pc" as well.

In earlier versions of 2020, a disk/parition backup was still .tibx, but file/folder were .tib.  I still believe "entire pc" was .tibx though.

--------------

EDIT: just started an "entire pc" backup (only one internal drive though) and it did use the .tibx format and new name scheme as expected.  Acronis True Image 2020 build 21400.

If you have ever used this name before, try a new, and very unique name (never used) and see if it still uses .tib or .tibx as it should.  Perhaps, if the name was used before, and there is a remnant of it in the database lingering somewhere (like if it was used in an older version where .tib was used), it is still reverting to .tib for some reason (bug) and you can avoid it by using something completely unique to test with to see if you can recreate the behavior or make it go away.

 

A little correction for Bobbo's post - file level backups (non-Cloud) still use the .tib format.

 

 

@Bobbo - I'm using 21400 and at this point it's not worth my time to create a new never used name as the backups are indeed valid and tested good no matter what the naming format and extension is. Perhaps I'll have some time to experiment over the weekend.

 

@ Renata - I do not use the cloud for any of my backups. All are either to a NAS or a USB portable drive connected to each of the PCs. The backups I mentioned in my first post in this thread both have to portable as their destination. And as stated, one job is tibx and one is tib.

Unless you feel something is going on that shouldn't be, I'm not considering this an issue since restoring works from both.

For the record, I checked the other PCs and one of them show the same behavior as mentioned here, while the third has both jobs being saved as tibx.

Phred,

Did you use the default Source selection of Entire PC to make this backup in question here or did you manually select the data in the backup?

If you manually selected the data did you do so using the Disk and Partitions option?  If yes, did you manually exclude any data selected in your selection process?

If you made manual exclusions doing so may be the factor that causes the behavior.

Enchantech wrote:

Phred,

Did you use the default Source selection of Entire PC to make this backup in question here or did you manually select the data in the backup?

Enchantech -  I manually selected Disks & Partitions and then selected all disks and partitions except the USB portable, which is the backup destination.

Thank you for clarifying.