Can Acronis use/read these files

See the ATI 2017 User Guide: Backup file naming which covers your file names.

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.

I would suggest running a validation for the files with the most recent timestamp and that looks to have the correct / expected file size.

I'm sure that Acronis can read them,  but, what I meant to ask are these sets complete, and would that be a problem for Acronis, because I need to make room on the drive, and that would be the easiest way...

I read the link you posted, and I would like to know what has to be a complete set V# or B#. The article didn't address the consequences if the the V# or B# go out of sequence.

Taking the Samsung SSD 850 EVO 1TB backups...

full_b140_s1_v1-3.tib and diff_b140_s2_v1-2.tib look to be a matched pair of files.

The files shown below these 2 with earlier dates could be moved to a temp folder then do a validation for the remaining diff file to prove none of the moved files are needed and can be removed if not needed.

Thanks.

Are the backups dated 7/4, 7/8/, and 7/31/2020 a matched set?

(From: the Local Data backup)

No, 7/8 & 7/32 belong to the b253 backup sequence, while 7/4 is a new full for seq b254 with no other diffs created for that shown.  The b253 files look to have got pretty confused with out of sequence diff files going by the file dates!

Thanks Steve,

I appreciate the help.

Hi,

I was wondering if

_diff_b253_s3_v1-2.tib   7/8

_diff_b253_s3_v1-3.tib  7/31

could be used to do a recovery, in Acronis-speak. because they are two differential files. Aren't differential files dependent on having a full backup being stored in the same location?

For example:

_full_b253_s3_v1-1.tib (something like that)...

but since it is not there...are the other two files useful to Acronis? Or would the other two files just cause it to error out because it's missing v1-1 (the full backup?)

Those files are most likely created based on _full_b253_s1_v1-2.tib as this was the last new full backup before the diff's were created.

You would need to do validation of each file to confirm all is ok.