TIH 2010 - 3 week backup cycle not behaving as it should
I am trying to implement the 3 week backup cycle detailed in the TIH 2010 user guide (I was one of the people who asked for this capability).
I have defined three identical backup jobs, JobA, JobB, JobC. Each of these jobs backs up the same thing (an image backup of drive C). Each of these jobs runs on every day of the week once every three weeks. The 'start on' day (a Sunday in each case) is staggered by one week for each job so that in week # 1, JobA runs each day, in week #2 JobB runs each day and in week #3 JobC runs each day. When we reach week #4, JobA again runs each day and so on. The scheduling aspect of this is working fine. Each job uses a different archive file name in the same output directory. JobA uses BackupA.tib, JobB uses BackupB.tib and JobC uses BackupC.tib. There is no consolidation defined for any of these jobs. Each job is set to perform incremental backups and to create a new full backup (removing the previous backup) after 6 incremental backups.
What is happening is that each job started off fine by first creating a full backup but then instead of creating 6 subsequent incremental backups the job will create somewhere between 2 and 4 incrementals and then for no reason the next run will drop the existing backup set and create a full backup even though it has not reached the defined limit of 6 incrementals. It seems that TIH 2010 is not properly tracking how many incremental backups have been taken in this backup set. This seems clearly to be a bug to me.
Thoughts anyone? This is very annoying since the main reason I upgraded to 2010 was due to the better scheduling support that finally enabled me to setup an automated backup plan that made sense...

- Log in to post comments

Chris,
I agree what you want should work.
If you still are having issues you can get the exact same 3 generation rolling backup effect you want by using a single backup job and chain2gen
http://forum.acronis.com/forum/5940
take care.
- Log in to post comments