Backup Tib Filenames totally messed up
Hello, I have a problem with my file names of one of my backups. The tib files are getting named with the same date of the first file created i.e.: SeekSuccess-Backup8_29_20101(8)3.tib, SeekSuccess-Backup8_29_20101(8)4.tib, SeekSuccess-Backup8_29_20101(8)5.tib, etc, etc. Has anyone else experienced this issue, and does anyone know how to fix it? These files should be named accroding to their date. Thanks

- Log in to post comments

GroverH wrote:What version of TrueImageHome are you uising?
The (8) appearing within the file name is the 8th backup chain since you began the backup. It will appear on all the backup files associated with that particular "SeekSuccess-Backup8_29_20101(8).tib" chain. The 3 backups you listed above are either incremental or differential type backups and all associated with the "SeekSuccess-Backup8_29_20101(8).tib" chain and the (8)5.tib is the most recent inc/dif you have listed and is associated with a specific date and time the file was created. The last full chain had the (7) listed with it and the next full chain will carry the (9) designation. This appearance is the norm for 2010 & 2011.
The files now have a new naming scheme I never saw before and now look like this:
SeekSuccess-Backup8_29_201018533(2)6.tib
SeekSuccess-Backup8_29_201018533(3)2.tib
SeekSuccess-Backup8_29_201018533(3)6.tib
This naming scheme sucks! I will just change the name of the backup, hopefully that doesn't cause anymore issues.
- Log in to post comments

Don't just change the name of the backup, this will confuse TI and you will end up with a stange numbering system - although TI will be able to recover the files OK.
Delete the task and remake it is the better way to go. Make sure you only remove the task otherwise all your images associated with it will be deleted as well.
- Log in to post comments

If you are using versioon 2011, I suggest you download the new update as it has fixes for this type problem.
In your last example, it looks like date and time was accidentally added.
- Log in to post comments

What exactly is it that is being fixed in the new version?
- Log in to post comments