Skip to main content

tib Backup Files Version? At a Loss

Thread needs solution
Forum Member
Posts: 13
Comments: 24

All,

Here is the following scenario, I created backups every Monday morning. 

5/6   P:\Samsung SSD 850 EVO 250GB_diff_b17_s2_v1.tib    (success, looks good normal, everythings fine)
5/13 Cannot find the partition selected for the backup   (swapped out hard drives, that is why it errored, i re-established the backup)
5/20 P:\Samsung SSD 850 EVO 250GB_diff_b17_s2_v1-2.tib     (success, but now my version is v1-2?  not sure if I have an issue or not, it validated successfully)

Can anyone shed some light?

Thanks in advance.

 

Scott

0 Users found this helpful
Legend
Posts: 73
Comments: 16447

Scott, Acronis will use the v1-2 file name if it encounters an existing file with the name it is going to use for a new backup.

The v1-2 is described in the ATI 2019 User Guide where it says:

If you are creating a new backup, and there is already a file with the same name, the program does not delete the old file, but adds to the new file the "-number" suffix, for example, my_documents_inc_b2_s2_v1-2.tib.

Forum Member
Posts: 13
Comments: 24

Thanks I will check out the document.  Does that mean I am ok if I need to restore to "V1-2"?  And going forward with future backups should be ok?  Thanks.

 

Scott

Legend
Posts: 73
Comments: 16447

Scott, there should be no issue with recovering from the v1-2 file provided the previous file(s) in the version chain are present, i.e.
Samsung SSD 850 EVO 250GB_full_b17_s1_v1.tib and
Samsung SSD 850 EVO 250GB_diff_b17_s2_v1-2.tib

Your Samsung SSD 850 EVO 250GB_diff_b17_s2_v1.tib would also be OK to use along with the same _full_b17 initial file if needed.

Forum Member
Posts: 13
Comments: 24

And that is the case thank you again Steve.

Forum Hero
Posts: 62
Comments: 7495

You should be good to go.  Keep in mind... when you restore from a backup, anything that was created afterwards is "unknown" to the Windows version of the installed Acronis application.  Hence, why it sees the original file, but doesn't know that it is related and appends the 1-2 to the end.  When using the rescue media, you should be able to use either version of the differential files (the original or the 1-2) without issue... especially since they are for the same backup chain and differentials which don't rely on any other files but the initial full in that backup chain.