True Image 2011: Version chain backup scheme does not work correctly
Hello,
I have got some problems with the version chain backup scheme.
I set it up last Friday and initiated a first backup manually. It was called "Volume-Backup_System-reserviert_C" and was about 67 Gigabytes
On Monday evening I set a scheduling for this backup setting: every day at 12 a clock (German time).
On Tuesday the backup worked fine but there was placed not a differential backup to the first one but a second full backup called "Volume-Backup_System-reserviert_C2".
I started a backup manually then on Tuesday afternoon (German time) by Button click, and a third full (!!) backup appeared then, called "Volume-Backup_System-reserviert_C(1)".
I contacted support (even bought a ticket to get phone support) but no quick answer - still waiting...
In the meantime I tried to start the backup again and - surprise - the first differential backup worked, named "Volume-Backup_System-reserviert_C(1)2.
I tried several repeats then expecting that after 5 differential backps a new full backup will be generated but this didn't happen: I have got 10 diffential backups now but no additional full backup.
Can anybody help and telling me what I am doing wrong?
What does the numbering in the file names mean? Which ones belong together, which ones not? (..._C, ..._C2, ..._C(1), ..._C(1)2, ...C(1)3)
Kind regards,
Mathias
Exactly the same problem here. Now up to 11 Differentials on my Partition Backup.
Makes the product useless for my purposes.
Not happy to read all the reports of poor support response from Acronis. Seems like some fundamental problems take a long time before they get fixed.
From ATI 2011 Help:
Version chain scheme
This backup scheme differs for disk backup and file backup types.
Disk backup version chain
At first the program creates the 1st full backup version. The version will be kept until you delete it manually. After that, according to the specified schedule (or when you run backup manually) the program creates: 1 full and 5 differential backup versions, then again 1 full and 5 differential backup versions and so on. The versions will be stored for 6 months. After the period the program analyzes if the oldest backup versions (except the 1st full version) may be deleted. It depends on the minimum number of versions (eight) and version chains consistency. The program deletes the oldest versions one by one after creating new versions with the same backup method (for example, the oldest differential version will be deleted after creation of the newest differential version). First of all the oldest differential versions will be deleted, then - the oldest full version.
Backup scheduler setting: monthly
Result: you have monthly backup versions for the last 6 months plus the initial full backup version that may be kept for a longer period.
Required storage space: depends on the number of versions and their sizes
File backup version chain
According to the specified schedule (or when you run backup manually) the program creates: 1 full and 6 incremental backup versions, then again 1 full and 6 incremental versions and so on. The versions will be stored for 1 month. After the period the program analyzes if the oldest backup versions may be deleted. It depends on the version chain consistency. To keep the consistency, the program deletes the oldest versions by chains "1 full + 6 incremental backup versions" after creating a new analogous version chain.
Backup scheduler setting: daily
Result: you have backup versions for every day of the last month
Required storage space: depends on the number of versions and their sizes
IN reply to: From ATI 2011 Help:
Yes, that is what it SHOULD do. I just does NOT work.
Using the 'Disk Version Chain' scheme, I get the first full backup then just continuous incremental backups. It does not initiate the backup cycle and create a new full backup.
Yes EXACTLY.
That is what it is supposed to to, and what I want it to do, BUT IT DOESN'T ACTUALLY DO IT IN THE REAL WORLD.
PLEASE PLEASE MR ACRONIS, START READING THE REPORTS PROPERLY.
WE ALL KNOW WHAT IT IS SUPPOSED TO DO, BUT IT DOESN'T DO IT, RENDERING IT USELESS AS A BACKUP PRODUCT.
The Acronis name is fast going down the pan with this inability to respond in anything like a meaningful or useful way when it comes to problem solving. They seem to have their head's so far up their <edited> that they can't see that they have a big problem with this product.
Please prove me wrong and get this fixed as a matter of urgency, before we are all forced to abandon the product for the more expensive, but working ShadowProtect.com
I thank you.
I have got around the problem to some extent by defining my own scheme under 'Custom' setting.
Doing this has, however, brought up another problem. Every time I edit an the active scheme , I get seemingly random additions and changes to the suffix on the next backup filename. It certainly makes doing a quick status check on the backup directory interesting!!
Actually, I think that you have to re-read (or learn to read, better) with attention. The help file is very clear: "At first the program creates the 1st full backup version." So, THE PROGRAM CREATES. This means that if you do a MANUAL full backup, the program ignore it. Can you understand this?
For this, is not strange at all that when you"tried to start the backup again and - surprise - the first differential backup worked, named "Volume-Backup_System-reserviert_C(1)2" is not at all a "SURPRISE"!! It is very normal!! Because, THE PROGRAM, had made previously the firs full backup called "Volume-Backup_System-reserviert_C(1)".
So, "PLEASE PLEASE MR ACRONIS, START READING THE REPORTS PROPERLY" is a very good prayer to do to yourself.
Your attitude is despicable. You need to learn to read people's emails properly and fully.
"So, "PLEASE PLEASE MR ACRONIS, START READING THE REPORTS PROPERLY" is a very good prayer to do to yourself."
How dare you, <edited>.
Perhaps you would like to explain why after update 5519 everything I and a large number of other people were complaining about is now working correctly???????
How dare you, <edited>!
Dear Users,
Please note that you're violating Acronis Forum Terms of Use, the following points in particular:
- Respect the community and its members at all times.
- Not post any material or select a username that is abusive, harassing, threatening, sexual explicit, obscene, racially or ethnically offensive or vulgar.
Please note that your account will be blocked should you continue doing this.
Andrey.
This issue is of particular interest to me because Acronis has wrestled with it for at least four versions now and has introduced different functionality (and new bugs) in each of the last two at least.
My own expectation is minimal: start a new full backup every N incrementals -- I'll manage the cleanup of older stuff. But even this small functionality has a very buggy history. Even now, I have had 2010 running for a year now making such version chains and for the most part it has worked correctly, but every now and then and for no apparent reason it will fail and either go past my N or start a new full archive at something less than N.
I think if Acronis Support will cast its collective mind over the history of this sort of backup management feature, it will acknowledge the importance of getting it right early and not subjecting the user community to further rounds of waiting and frustration.
Is this thread alive? I for one would like to know if this is a problem with 2011 (before I update :)
MKairys.
Much work has been done to make sure this function does work as you descirbe but only time will tell.
Give the trial a test and see how it works for you.
Do take a full disk image backup of your entire system disk before you upgrade.
As 2011 is a new version, Acronis says you do not have to un-install first but most of us regulars suggest that you do un-install before installing 2011.
If you like the 2011, you can buy your serial number and insert it into the trial version to convert it to a registered version.
Well perhaps, but not until http://forum.acronis.com/forum/14144#comment-44041 is resolved.
I have the same issue with the failure of the version chain to create a full backup after 5 incrementals as it is configured to do. Very disappointing as I was hoping Acronis would get it right after ATI2010 being such a diaster that I had to use ATI 2009 all last year. If Acronis is not able to provide a quick solution to this and produce a product that delivers the functionality as advertised I will be going to another solution and not coming back.
Even though most of the exotic parts of TIH do not work, the parts that do work are much than than the competition. The part that you mentioned can be fixed by chain n chain or pre.bat which Acronis wrote. What I do to avoid frustration is wait until the next version is released and then evaluate the older version which has most of the bad bugs fixed.
>>Even though most of the exotic parts of TIH do not work, the parts that do work are much (presumably "better") than than the competition.<<
I'd like to know just which parts you mean, and how they're better for BASIC backup & restore operations.
As I said in a post on another thread, "... the program STILL doesn't seem to clean up after itself to keep the storage from filling up, nor does the scheduler work properly (by using Win& 64-bit scheduler, I can automate a backup, but not verify & notify, and certainly not sleep/hibernate afterwards). I fail to see what the incremental value of TI is over several other free/less expensive programs, given the crippling of these functions."