Inconsistent and incorrect naming of backup sets

Here are some examples of the incorrect and inconsistent naming mechanism that True Image uses when naming backup sets and when naming individual backups within a chain, as I've mentioned in the wish list thread ( http://forum.acronis.com/forum/44509 ).

Red boxes in the screenshot: For file backups, True Image names the backups according to the user-defined name given to the backup job. And for image backups, True Image names the backups according to the file names. Inconsistent.

Orange boxes in the screenshot: At the end of a full backup, True Image names that backup according to the temporary file name that was used when it was just beginning to generate that backup, which is actually based on the file names used for the previous backup chain. That is why you see it doesn't match up with the actual resulting new file name (32 vs 33 in the screenshot). This incorrect naming is evident when consolidating backups and it's also evident when it comes time to restore. What you have to do as a result is ignore the names of the backups and just look at the file names to know what to choose.