True Image backup file name

It's possible yo have more than one problem goning on here. Files being named incorrectly and/or files being orphaned from the the task that made them and therefore, not being deleted when they should be. But in any event it's a problem having to do with the ati database.
You can try deleting the existing tasks (first save you backups to some other location if you want to keep them) and then recreating the tasks. The deletion should wipe out the bogus things in the Regiastry or in the database.

I know some folks using ati2011 just quiting using the automated backup because it was easier for them to manually manage the backup files than mess with the tasks, get renamed files or get orphaned files.

We are waiting to see if the latest build of ati2012 has conquered the task/database problems.

This was descended from a backup job that I have had running for about 2 years, and was originally created by an older version of True Image.

I have just deleted all of my backup tasks and tried to recreate one of them from scratch. I tried creating a new task, and then moving back the .tib file before running it, but when I did the .tib file name did not stick and the output ended up getting named My_partitions.tib.

I then tried again and let the job create the .tib file itself, and it seems to have done that properly, When I ran it a second time it did overwrite the file as it was supposed to, so I guess that fixed things. I should be able to recreate the other job I run nightly, and that should hopefully do it.

If I have to abandon automated backup, then I am abandoning True Image. I am getting a bit tired of having to pay to upgrade not to get new features or compatibility with hardware or new OS's, but just to fix things that don't work correctly in True Image, but are supposed to. And then to have to pay for support after 30 days, even if it is an issue that is a deficiency in the product makes it even more frustrating.

Barry

Barry,

Some users have had issues with the single version scheme, for unknown reasons.
A workaround is to approximate a single version scheme with an incremental scheme:
- backup scheme: custom
- incremental
- do a full after 1 incremental
- keep only 1 most recent version

Create a new task to do that.

Also, if recreating tasks, any files (tibs) in the traget direcdtory tend not to be identified as part of the new task so best to move them away.

I've been using True Image ever since version 8. The file naming problem only started after they released version 2011. I have complained about this problem since the program was first released. They apparently don't care since they have never came up with a fix. Unless you pay for support, they aren't interested, and usually won't even reply to emails or posts, even while you are still under the initial warranty. I like the program features, it's just the problem with the file names, that's the reason I won't upgrade to the new version. Actually, version 10, or version 2010 are just as useful and don't have this issue. You can try deleting backup jobs, etc., I've tried every possible solution, needless to say, you'll always have the file naming problem with their software. The file name has something to do with the date it created the files, but there is no work around. Their archaic way of setting up the jobs is almost impossible for new or inexperienced users to get the program setup to put the files where you want them and with the correct options. Save your money and don't pay for a new version.

>I just upgraded to less than 4 months ago, and applied the update to the latest version yesterday (and which I apparently no longer am entitled to support for ????).

I encountered this oddity when purchasing ATIH 2011 Netbook Edition a couple months ago, and their website showed that my support would end just a few weeks later, in October, which would be one year from the software's release of Oct 2010.

I did contact them about an issue (age-old "need latest SnapAPI drivers") and they responded within a couple days, but I haven't tried since to use Support so dunno if I'm cut-off already or not.

It's a bizarre business practice to base "available support" on the software's release date instead of the purchase date, but apparently the problem is that their registration system doesn't have any mechanism for the entry of one's "proof of purchase". They oughta fix that!!!

Ok, so after recreating new backup jobs on the 17th and having them run successfully for a few days, the job ran into a problem the night before last and once again started to accumulate new tib files with extended file names, leaving the previous 27GB file in place. The messages from the program event list are:

Pending operation 144 started: 'Saving partition structure'.
The file (folder) already exists. (0x40013)
function = "MoveFileW",
filename = "\\?\G:\Disk Images\Computer\MyComputerName_C_Disk.tib_66A87739-4498-4A4B-A0AB-43A448DA70C3.tib"
Tag = 0xF35F747B3B21F8DF
Cannot create a file when that file already exists (0xFFF0)
code = 800700B7)
Tag = 0xBD28FDBD64EDB8BC

Is there any way to get this to work properly?

If not, anyone have experience with DriveImage XML?

Thanks,

Barry

I chatted with a sales rep and told him I would only consider upgrading to 2012 if he guaranteed me the 2012 version won't do the same thing. He talked me into downloading the trial version after assuring me they solved this problem a long time ago. He didn't have an answer when I asked why none of the 2011patches included this supposed fix. After downloading and installing 2012, the first image named correctly. When I ran it the second time, it too renamed the files with the long cryptic names. I tried running a batch file which deletes the previous images prior to creating a new set, only to still end up with the goofy names. There is some credence to the idea that the single version scheme is responsible. It appears that, if you don't want to hassle with incremental images, you can set it up to do a custom setup and tell it to overwrite the original. I haven't had timt to test it extensively yet, but after a couple of attempts, this seems to solve the problem.

I had reported this same issue with a support ticket, and was told that they will "help you until your issue is completely resolved" if I pay for "Pay per incident" support, since I am beyond 30 days. Since the problem only started when I purchased the upgrade, I am not going to pay them again to get the upgrade to work properly. So, I have reverted back to the 2010 version and will stay there until it no longer works, or until I switch to another product.

Simply write a batch file which deletes *.tib files and put it in each backup directory.
Go to Acronis to edit each individual backup
Go to Disk backup options
First, select a Custom backup scheme using a full backup method
On the Advanced tab, in Pre/Post commands, check custom options, then select the batch file
For some reason, the single version scheme is the culprit. I personally don't like incremental or differential backups. There is a bug in the program which will cause the file naming issue if files already exist in the destination directory. If the directory doesn't contain any tib files, the names will come out correct. Since I like creating a new set of images each time, this method takes the same anmount of time and doesn't make the archaic names. You would think that Acronis would have figured out what the problem is a long time ago, but since the new version does the same thing, they don't seem to care, or can't figure out how to solve the problem. Anyway, this works just fine.

I'm going to try that on the one machine that has ATI 2011, but I will not upgrade at all and will stick with ATI 2010 for every other computer. ATI 2011 and 2012 is just too buggy.

I provide support to several individuals, one using TI 2011, and I just encountered this issue. In this case the backup started failing, which prompted the call to me. What I found was that by reusing the same file name, but appending characters to it each time, TI eventually was trying to create a name beyond Window's 256 character limit, causing the backup to fail.

This was a Single Version Scheme also. I recreated the job as a differential, creating and retaining just one version. Hopefully that will resolve the issue.

This isn't the first time I've had issues with Acronis and their lack of support (per discussion above that this is a long standing issue). I had a go round with them a year or so ago. The backup was failing and there was no notification. Acronis support didn't seem to think a backup program failing and not notifying the user was an issue. They said the user could just look in the log and see it failed. Right, the user was expected to follow up daily to make sure the program was working? Kinda defeated the point of scheduling.

The next time I have an issue with Acronis I'm convincing the user to move to something else. I already actively discourage others from using it. A backup program you have to babysit is useless.

As I mentioned in my earlier post, if you write a batch file to run before the backup starts, it will solve the problem. If no files exist in the destination directory it will create the files with the proper file name and not append the long cryptic names to the files. The incremental backups are just a space hog which to me, is rediculous. The imaging goes fast enough that it is nice to have one clean image. Acronis has had this issue for the last two versions and refuses to admit the problem exists. No matter how many times you correspond with them, they tell you the issue has been resolved, but all you have to do is look at the posts, and see what happens with your own backups to know nothing has changed. I personally like the program, I don't like the support and the failure to recognize and correct problems. I don't feel the new version has any "imporvements" making the investment worthwhile if you have version 2011, or 10 for that matter. Since I'm not a programmer I don't know how difficult it would be to correct the problem, but if I can write a simple batch file to solve the problem, you would think they could come up with a solution. The problem is simple to recreate but they just won't admit the problem exists. What a shame a fairly good product has such lame support. As far as I am aware, since I won't spend the time trying more things, the problem is only when you attempt to overwrite images with a new image and there are files in the destination folder. Just same time and aggravation and write the batch file and have Acronis run it before it creates the image. If you follow the instructions from my previous post the problem will go away.