Automatic Consolidation Issue - Build 6053
Not sure if I have a stand alone problem with 6053 or a compatibility problem with W7 and 6053. Tasks that were created with Automatic Consolidation parameters in an earlier version of 2010 seem to continue to work. New tasks or modified tasks however lose their ability to have Automatic Consolidation. The Consolidation parameter never gets saved and thus the tasks run without it. Didn't realize it at first until I went to check on a backup and saw that only the latest one was there. Although I installed 6053 before upgrading to W7 other than a final complete Vista Image I never ran my normal routines under Vista and 6053. As a result I'm not certain whether I'm dealing just with a 6053 issue or a compatibility issue between W7 and True Image. Other than this issue after a week of running W7 I haven't encountered any other issues.
I've the same issue with Windows 7 and Build 6053. I did a fresh install of ATI2010 on Windows 7. (I had not the problem with build 6029)
But there's a workaround for the problem:
In the following folder you can find the files for the ATI backup tasks: C:\ProgramData\Acronis\TrueImageHome\Scripts
The filenames look like this "BE8EFABD-5C11-445A-BFF9-7668E1626414.tib.tis"
Open the file with a text editor and look for the following lines:
----------
<net_speed_limit speed_limit_mode="percent" value="100" />
<disk_speed_limit speed_limit_mode="percent" value="100" />
<quota count="10" type="4" /> <=Add this line for consolidation if number of backups is more than 10
</stream_options>
</common_options>
--------------
After editing the file, save the changes. Open the backup task in ATI2010 console to see if the consolidation option is set. Click on cancel to close the console (do not click on "finish" or otherwise the consolidation setting will be deleted again.)
Hopefully this bug will be fixed in the next build.
Can sombody from the support please check if this "Automatic consolidation option" problem can be reproduced by the QA team?
If yes, will it be fixed with the next release?
Thanks for your help!
Dear customers,
First of all, I would like to apologize for the delayed response in this thread. This issue appears to be the common one, and I was not able to find any similar common issue stored in our database.
However, this task has been forwarded to our QA team for reproducing, they will handle it as soon as possible. I will let you know the results.
Thank you for the understanding.
Hey, thank you WFK2431! Your suggestion to edit the file worked for me.
On my Windows XP machine, I found the .tis files in the following folder:
C:\Documents and Settings\All Users\Application Data\Acronis\TrueImageHome\Scripts
Hello all,
Let me update you with the state of issue.
As I have said, this case has been escalated to QA team, so they were able to reproduce it. For now, this case is assigned to Development Team. We will do our best to fix it as soon as possible.
I will keep you updated.
Best regards,
"I will keep you updated"
Via this thread I presume? When can we expect an update? At least give us some idea when the problem is likely to be addressed. Is anybody even working on it as yet?
Why not consider an alternate solution.
Use OracleDBA's free helper program (Chain2Gen) to help you control the number of backup archives you want to retain. It works and it is easy to set up. TrueImage does the scheduling and backups and C2G makes sure you have the number of backups desired and when you want a full backup. Check links 3 and 3B inside my signature index below.
Mainly because I've paid for software that should do it...but doesn't.
I appreciate the suggestion, but it's about time Acronis got this sorted.
I agree Acronis owes an update to fix this. But in the meantime I'd follow Grover's suggestion to use Chain2Gen to create what you need until TI 2010 is updated. It seems your ignoring a solution that is easily implemented even if only temporarily. Your the one that is paying the penalty in the meantime. I've implemented it and find it is well worth the time to understand how it works.
I did say I appreciated the suggestion, and I genuinely do - it's always nice when people try to help (as I do whenever I'm able). I'm not ignoring what I assume is a perfectly adequate workaround - it's just that I already have a workaround in place.
The reason for my post was that since Alexander told us on the 14th January he would keep us informed, we've heard nothing. After well over 2 months, I don't think it's unreasonable to expect that this issue should be resolved - or, at the very least, to have some indication of when a fix is likely to materialize.
I'm annoyed that any workaround is still necessary when Acronis have had ample time to resolve the issue. It's not like they're new to this game (when a little leeway may be in order), nor are we talking about new functionality (with which one might expect some teething problems).
I've worked in IT support for over 25 years and, unfortunately, know of many cultures where the amount of time devoted to a particular issue is directly proportional to the amount of noise generated by those experiencing the problem. You should consider my original post my way of making a little noise, in the hope that it might illicit a response, directly or indirectly, from those charged with resolving the problem.
Robin,
I understand your position. You can expect Acronis to fix some of the basic issues ( perhaps in the next build) but the feature and options provided by Chain2Gen far exceed any that fix that might be applied.
I really do appreciate the heads up regarding Chain2Gen. I just feel very aggrieved that several previous True Image versions have had one problem or another with functionality of this kind. In each case, I've forked out money for the upgrade, only to find that the issues have not been fixed, or that similar ones have appeared. I feel I've been extremely patient (not to mention charitable) throughout (I started with TI v8) but there comes a point when you can't help but feel you're being hoodwinked. That's exactly where I am now.
I didn't sign up to be a Beta tester, I purchased, several times, what were supposed to be finished products. So, even if Chain2Gen made me coffee in the morning, mowed the lawn and deposited large sums of money into my bank account on a regular basis, Acronis would still be the object of my considerable anger - for taking my money under false pretences.
Even though I have a workaround in place, I'll still take a look at Chain2Gen (thanks again for that) - but, as I said previously, my post was all about Acronis failing to get their act together. Their forums , for as long as I've been a customer, have been littered with issues of this nature and people such as yourself have been kind enough to offer workarounds. It's about time the developers demonstrated the same level of commitment and put in place correct, robust code that actually does the job it claims to do. If they can't manage that, then they should remove that 'functionality' - at least then, any decision I make regarding purchasing of the software, won't be influenced by false promises.
Robin,
Download the program zip file listed from the main Chain2Gen thread. The readme file is a good place to start.
http://forum.acronis.com/forum/5940
and be sure and download this new additional help file.
http://forum.acronis.com/sites/default/files/forum/2010/02/8670/TIH__C2…
The main thread covers several postings. If you can, look at them all because some of the later added features are listed toward the middle and end of the thread.
Good luck.
Oh, that sucks big time!
It is *TOTALLY* ridiculous that we all have to spend hours researching the web, just to discover that wasn't anything stupid we were doing, but instead a ridiculous bug that Acronis did not fix SINCE LAST YEAR! That's outrageous, specially considering it's a commercial software that we paid for.
I'm just upset that I lost FOUR hours of my night, first because a nasty compatibility problem with Win7 and RAID controllers (that freezes *completely* your OS, requiring a power down), and now a few more hours trying to understand what was going on with Automatic Consolidation...
Suggest we all tweet, post, blog, complain about how bad is the support from this company. It's really a shame.