Strange, long file TIB file names
I'm currently running TI 2011 6696, and I have a script which does a complete backup of partitions C: and D: every night. The intent is to overwrite the previous day's backup, keeping file names the same. Instead, the file names grow in length with each backup.
So, for example, after the first time the script is run, the file names are:
T60Daily1.tib
T60Daily2.tib
T60Daily3.tib
...
T60Daily10.tib
After the script has been run a few times, the file names are now:
T60Daily.tib_818D84B3-FE2D-4073-929E-F699FD1E1AE41.tib_580B2C3C-A621-4219-B6B4-FDC73E1AD4E01.tib
T60Daily.tib_818D84B3-FE2D-4073-929E-F699FD1E1AE412.tib
T60Daily.tib_818D84B3-FE2D-4073-929E-F699FD1E1AE413.tib
...
T60Daily.tib_818D84B3-FE2D-4073-929E-F699FD1E1AE4110.tib
Why is this happening, and how can I prevent it?
I would like the file names to remain unchanged.
Thanks for any suggestions.
This appears to be a bug which I reported here some time ago (the thread has disappeared!) and STILL is not fixed in 6696. I reverted to TI 2010 which functions correctly.
Thanks! I just downloaded TI 2010-7160, which is less than a month old. Time for me to go backward, too.
Question: Do you use ftp for backup or a shared folder/local disk/USB storage?
I've got the same issue with TIH 2011 #6696 backing up via ftp. I've just had a PPI session, and the supporter said the ftp server does it wrong. See also http://kb.acronis.com/content/1843 "The product cannot access FTP servers that do not confirm transfer completion after the LIST command or do not support MLST and MLSD commands. An example of such FTP servers is ProFTPD."
I use primarily USB storage, although on rare occasions I'll use our home network.
I'm now on 2010-7160 and have had no problems.
This problem exists in TI Home 2012 build 6131
Acronis Support is still in contact with me to solve this and other issues at least in "Acronis Backup and Recovery". But I think I'll soon migrate my last XP Pro machine to 7 Professional and use Windows Backup onto my NAS. Then I don't need Acronis any more.
Michael,
Several users reported issues with the single version backup scheme, which create these long backup names. The workaround is to do the following backup scheme:
- custom scheme.
- differential.
- do one full backup after one incremental.
- keep no more than X most recent version chains (X can be any number you want).
You will get an alternate of 1 full, 1 incremental, 1 full, etc.
Pat,
Thanks for your suggestion. My current backup process runs overnight without any intervention (I don't even think about it most days), and does a complete backup, overwriting the previous night's backup. Yes, if something goes wrong during the process, I would be left without any backup, so I regularly make additional backups (monthly or quarterly offsite, for example).
I fear that implementing a process which entails as much daily intervention as you suggest would leave me frustrated and probably without backups.
In any case, reverting to version 2010 has eliminated all the name problems. Until I learn that the problem has been corrected, I will likely stay here.
The scheme I recommended can be fully automated with ATi 2011, and can be run either with the Acronis scheduler or manually.