Skip to main content

Acronis TIH 2018 will not recognize moved or renamed backup *.tib files for validation or restore, A BIG PROBLEM !

Thread needs solution

Gentlemen,

I only use Acronis TIH for the C:\ partition containing the OS and program files.
I keep all data files on different partitions so that newer data is not overwritten with older data when restoring the OS and programs to a workable, earlier version after problems occur. 

I save these *.tib image files, organized & labeled by date, so that I have multiple dated backups in case the most recent turns out to be invalid.

In earlier versions of ATIH this was vastly easier; naming the *.tib image file by what it contained and the date.

With version 2018 of Acronis TIH, the program:
(1) does not accept custom naming,
(1) will not recognize *.tib files which have been renamed and 
(2) will not recognize *.tib files which have been moved.

How can these failures be resolved?

Respectfully,
Milton Alvis

0 Users found this helpful

With version 2018 of Acronis TIH, the program:
(1) does not accept custom naming,
(1) will not recognize *.tib files which have been renamed and 
(2) will not recognize *.tib files which have been moved.

How can these failures be resolved?

Milton, sorry but these are not program / application failures as such but more a case of user requirements that are not being met for you.

ATI 2018 can accept custom naming within the limits applied by the application.  You can give any valid name when you create a backup task and that name will be used for the backup image file(s) that the task creates.  There are methods of including certain variable values in the file names such as %DATE% and %TIME% but this requires a manual edit of the associated task script .tib.tis file to achieve.

ATI 2018 can recognise .tib files which have been renamed or moved but you would need to use the option to 'Add existing backup' to get such files to show in the ATI GUI, and the names used will need to meet the naming conventions required by ATI.

Note: If you are renaming or moving files within a Backup Version Chain, i.e. Incremental or Differential files then it is very easy to break such version chains by doing so. ATI stores information about all backup files created by your tasks in an internal database and move / rename actions outside of ATI does not reflect such changes in the database, hence breaks how ATI is able to handle the tasks that created those changed or moved files.