Skip to main content

Chain2Gen Query

Thread needs solution

Hi

I have encountered a problem with using Chain2Gen which is a really useful program designed to help Trueimage keep generations of back ups.

I have followed all the instructions but when I am setting up the back up task in Trueimage (I have version 11.0) I get an error message after selecting "incremental" as the back up method. The error message tells me that I am starting a new back up and incremental back ups must reference an existing file.

My puzzle is that I have used Chain2Gen on a different task and for some reason did NOT get this problem but cannot fathom what is going wrong this time.

Any ideas?

0 Users found this helpful

If using Chain2Gen on two tasks, each task must have its own individual set of Chain2Gen control files.

Yes, TrueImage will not create an incremental file until after a full backup has been created.

Click on my signature index below and review item 3B. It will help explain the setup procedure.

I do not have V11 installed but I will look of my past examples and see I see anything that could be helpful.

When I upgraded from V11 to v2010 I discovered that v2010 was much harder to use - particularly for performing generation backups.
I invented chain2gen to yield the capability enjoyed back in V11. What you see today is the end result of that attempt.

Back in V11 to acheive backup generations you needed two jobs.
One job was a "full" backup you would use the acronis scheduler to run this job on those days/dates that a new generation is to occur (such as Sunday).
This job would have a "pretask" bat file would take the existing target folder and rotate the contents into history thus leaving an empty target folder for acronis create the new full backup into.

The 2nd job would be an "INCR" backup that MUST use the exact same filename as the "full" backup job.
At runtime acronis would take the INCR job and do a directory listing of the TARGET folder and dynamically determine the next file# to be created.
this incr job would NOT have a pretask only the FULL backup job has the pretask.

Back then A typical configuartion is to schedule the full backup on sunday and then the incr file for every other day of the week.
Basically 100% of the time the full backup job runs means its time for a new generation.
also
100% of the time the incr backup job runs its simply to tack on a new incr file to the chain.

Back in v11 I used a script called "rotate_folders" as the pretask for the full backup job.
this script is documented here. http://www.wilderssecurity.com/showthread.php?t=193420

you do not need to use the rotate_folders script mentioned above as Chain2Gen includes the rotate folders capablity.
However for C2G to work correctly with V11 you
set TRGR_ON_MAX_TIB_CNT=1

The above will force a new generation to occur every time C2G is run.
This is the correct behavior because C2G would only be run with the full backup job and that backup job is scheduled to only run when a new generation is to occur (such as sunday).

Thanks for these replies.

I can confirm I did give each backup task its own Chain2gen control files.
I read the item 3B which was a very clear exposition of what (I think) I was doing.
I then tried changing "set TRGR_ON_MAX_TIB_CNT" parameter from 3 to 1 as suggested by Oracledba. I then went through the routine to set up a new Chain2gen backup and "Hey Presto" this time it did not object to my choosing an incremental back up.

So, hopefully, problem now solved. My only puzzle is that I have a different Chain2gen backup job which did not object to the "set TRGR_ON_MAX_TIB_CNT=3". Strange.

If I want to go back to allowing more incremental backups before a new full backup, can I go back into the user settings and edit this parameter without starting a new job from scratch?

Thanks for all the help.

can I go back into the user settings and edit this parameter without starting a new job from scratch?

There is no issues with editing the file:
"!_USER_SPECIFIED_PARAMS_FOR_ACRONIS.bat"