Does chain2gen still work with TI 2014?
I've been using chain2gen with TI 2009 and want to keep the ability to have rotating backup sets when I move to TI 2014 in a week or so.
Does it still work as is? Is there a new(er) version? Is it still needed, or can its functions be duplicated by TI 2014 as installed?
My needs are pretty simple.
Using "image backup," I do a full backup followed by 6 incremental backups, at which point chain2gen switches to the "other" target directory and repeats, toggling back and forth forever.
This avoided the nerve wracking case of having the last full backup deleted as the next full backup is being performed.
As you say, why change what's working, but if this can be easily performed with built-in features of TI 2014, why not at least investigate?
I looked at some of the examples and I found them a bit mind boggling. Of course, I had the same problem when I first looked at chain2gen some years ago.
In this C2G file,
!_USER_SPECIFIED_PARAMS_FOR_ACRONIS.bat
what is your setting for
set MAX_BACKUP_GENERATIONS=
Whether you do or do not use C2G, you still must create a new 2014 backup task so the only added work to use C2G would be minimal.
One difference between C2G and TrueIMage is that with C2G, each chain has its own folder (set0, set1, set2)
whereas in TrueImage, all files would be in the same folder as pictured above.
Either way, you should review signature link 2 below to become familiar with 2014.
I have MAX_BACKUP_GENERATIONS set to 1 (one), so there are just two directories of backups.
If TI 2014 can do the same thing without external help, I see no reason not to use the built-in function. There's nothing important to me about keeping the two backup generations in separate directories; that's just the way chain2gen happened to work.
Thanks for the pointers and info.
There is differences in how the two programs handle this.
With C2G, it deletes the old backup chain prior to creating the new replacment full backup.
With TrueImage, it creates the replacement backup prior to deleting old chain so its storage space needs requires the temporary need for emough space to store the extra full backup prior to the deletion of the old. This need for extra space must be planned in order to keep from getting a full disk error.
Refer signature link 2 below. You can use the illustration 11-Inc as your guide except change the ""keep 4 recent version chains" to a setting of "keep 1"
if you only want to keep 1 chain. My recommendation would be if you have the storage space for more than 1 chain, I would increase the number which would also serve as a little more safetiy in case you needed to go backup fuirther in order to restore a file.