"Single Version Scheme" generating multiple backups
If I understand the "Single Version Backup" scheme correctly, I'm generating a nightly backup that replaces the previous night's backup? The backed-up drive is "Ganymede" and I expect the nightly backup to be named "Ganymede.tib." And usually it is.
But every week or so I check my backup directory and see several extra copies with random characters appended to the file name:
10/05/2011 09:43 AM .
10/05/2011 09:43 AM ..
09/25/2011 11:08 PM 30,460,276,736 Ganymede.tib
10/02/2011 11:09 PM 30,997,553,152 Ganymede.tib_2E7016F1-BD06-4A1A-9F81-6523BA8EEC72.tib
10/04/2011 11:09 PM 36,938,787,840 Ganymede.tib_2E7016F1-BD06-4A1A-9F81-6523BA8EEC72.tib_833ED73A-9265-412E-A3F1-7D428BEB98D3.tib
What is happening? Why is ATIH2012 randomly deciding to start new backups? Any thoughts?
Richard is correct, the files with CLSID type names are temporary files that have been made whilst TIH is making the new file, it should delete the temp files afterwards. This sometimes fails if TIH is interrupted by another system process (hybernate or sleep eyc) or when a disk is signalled as about to not have enough space to continue the image process, if a space is made and 'retry' is clicked, TIh willl often make a new temp file and when this happens both temp files get left on the system.
@woodp,
It would appear from what you have written above your new full file has not succeeded or TIH has failed to rename the temp file to the original name. Are you able to explore or mount the temp files?
Well, I waited for it to happen again and checked the logs. Even though the event log signaled a green check mark, it appears an error was encountered.
"The file (folder) already exists. (0x40013)
function = "MoveFileW",
filename = "\\?\D:\Backups\Ganymede.tib_B283906B-3981-4540-9FB4-D0AC32A5C9B5.tib" "Cannot create a file when that file already exists (0xFFF0)"
Well of course the file already exists! I'm using Single Version Backup!
And now when I validate, ATIH2012 ignores the original Ganymede.tib and validates the news CLSID version (attachment). And there's no entry for the original Ganymede.tib so how do I resync file names and backups? My solution has been deleting both .tib files and starting over again. But with the error occurring every 4-6 days, that's just silly.
I've been using True Image since 7.0 - What broke in 12.0?
I've been using True Image since 7.0 - What broke in 12.0?
Just about everything. See also the forum thread at http://forum.acronis.com/forum/25701 entitled "Bad date on backup." I can only suggest awaiting the forthcoming TIH2012 "bug fix" release and hoping that it includes a solution for this problem along with all the others.
Alternatively, you could do what I'm going to do. My own solution is to install the most recent downloadable release for the previous TIH2011 version and, henceforth, stay one full version behind the Acronis "upgrade" cycle. By the time they begin promoting the "wonderful new" TIH2013 version, maybe they'll have made available a release for TIH2012 that actually works -- more or less -- as it's supposed to.
The only other option for users of Acronis "home" products appears to be playing the role of an involuntary beta tester. Or maybe alpha?
Once a task goes circular, the choices are (at present), delete and make a new one (you can then add the existing tib file to it) or take a deep breath and manually remove the CLSID type file name which will be in the task script (when it shouldn't be) and the reason why everything is going around in circles. However, this is not recommended as it is easy to cause even more strange behaviour.