some minor bugs when adding an existing backup chain

Preview description: These 2 bugs have to do with TrueImage having problems to continue the naming pattern of a backup chain when it is re-added to the backup list.

My System:

My system is a 64-bit Windows 7 with Acronis TrueImage 2014, build 6614
yes, it just got updated

Steps to understand/recreate the bugs:

I have made a few backup runs resulting in a list of tib-files with the following suffixes (b1_s1 to b1_s6, b2_s1 to b2_s3). So there are 9 files in total with two full and 7 incremental backups. All backup files reside on my local hard drive.

At some time I removed the backup from the backup list. And after that, I added the chain again by selecting the b1_s1 file. As expected, the backup's name was set to the common string (before the "bx_sy" suffixes) and the "Versions" info line in the backup list displayed "9"; i.e. no problem so far.

Actual bug descriptions:

Then, I recreated the backup settings. But when I selected "backup now", TrueImage started creating the new backup using the suffix "b1_s6"; after a short time, it switched to using "b1_s7". I canceled the operation as I expected it to be "b2_s4"!

Same behavior when I select the "b1_s2" file to add the backup chain.

When I add the chain by selecting the "b2_s1" file, the backup's name is initialized to "[common-string]_b1_s1_v1_(1)" thus breaking the naming pattern.

Workaround:

Adding the backup by using the "b2_s1" file, i.e. the last full backup, and then fixing the name seems to solve the whole problem. That is, TrueImage correctly continues the naming pattern with the next backup using the suffix "b2_s4".

Still, I do hope that TrueImage really uses the "b2_s3" file as it's predecessor?