Skip to main content

file name bug

Thread needs solution

Hi,

I like to use a custom file naming "@task@_@exec@.tib". I would expect the files to be named like that:

test_1_full_b1_s1_v1.tib
test_2_inc_b1_s2_v1.tib
test_3_inc_b1_s3_v1.tib
test_4_full_b2_s1_v1.tib
test_5_inc_b2_s2_v1.tib
and so on...

But in reality the files are named like that:

test_1_full_b1_s1_v1.tib
test_2_inc_b1_s2_v1.tib
test_3_inc_b1_s3_v1.tib
test_4_full_b1_s1_v1.tib
test_5_inc_b1_s2_v1.tib

The chain numbering don't work in this case. It seems that the chain number is counted up only when there is already a file with the same name. There is no problem with "@task@.tib".

Regards,
Axel

0 Users found this helpful

Axel, welcome to these public User Forums.

I believe that this is working correctly given that you are giving each backup a new task name.

The " @task@_@exec@ " portion of the name you are using simply equates to your test_# numbering, not to the default _b1_s#_v1 detail being added by Acronis.

See forum topic: Customize the tib.tis file, unable to save in TI 2018 - which has a good overview of how the naming works.

Steve,

 

Thanks but I still think it's a bug. In TI 2017 and 2018 it worked as expected. After upgrading to 2019 the chain naming is broken.

Axel, if that is the case, then I can only recommend opening a Support Ticket direct with Acronis for this issue as it would suggest something has changed in the 2019 version.  Unfortunately Acronis do not document any file naming options in the user guides and do not officially support any manual editing of the Script .tib.tis XML file contents.