Invalid Incremental Backups after Change of Folder Name

I have problems to restore incremental images with TI-2014.

My strategy is to automatically (per task) save incremental images on several internal (Sata) and external (USB) hard disks. To avoid capacity exceedances of the disks, I regularly start fresh incremental backups with the existing TI task by renaming the backup folder and adding a new folder with the same name. Example:

Original folder = “Backup C”
New name after renaming = “Backup C old – 2015-12”
New folder for fresh incremental backup = “Backup C”

As I now tried to restore backups, TI refused this in nearly each case with the error message “Image not existing or defect”. This happened with at least three hard disks, so that it cannot be a disk defect. The use of the “Validation” function did not “heal” these backups.

When applying the TI Recovery Start-up Manager (which is the Linux tool for use while booting), the backups on the PC are sometimes shown and sometimes not, but they can be made visible again in any case by the build-in image managing functions. Many of them (not all) can be also restored – although this was not possible with TI from inside Windows!

Up to now I assumed, that TI tib-files are self-contained files, which can be stored to and restored from any location. Now it seems, that the disk, the folder or the folder name contribute to the validity and visibility criteria for a backup. The tib-files seem not to be self-containing backups, but depending from external information somewhere stored in TI, in the registry or at another hidden place.

Is this really true? Or is there any way to “convince” TI to use backups also after folder name change or moving to another location?

Best regards