Aller au contenu principal

Create full version after every 3 incrementals doesn't

Thread needs solution

I have a custom backup scheme set to Incremental with "Create a full version after every 3 versions" set. True Image 2016 creates the full image then continues to make incremental images afterward, well beyond the 3 version limit set.  I've tried the same thing with Differential and get the same result. The only way I can get a Full image is by changing the Backup Scheme.  I never had this problem with earlier versions of True Image.

I sent a description of this problem to Acronis via Feedback but never got a response.  Do I have something configured wrong or is this a bug in TI 2016?  Is there some way to contact Acronis to get help on this problem?

0 Users found this helpful

Randy,

If you are within the initial 30 days of support following your 2016 purchase, you can contact Acronis via the support option (upper right corner of webpage and contact them via Live Chat or an email response.  YOur 2016 serial must be registered to received support.

------------------------------------

As for your issue, there could be several causes. The most frequent cause is the user making changes to the task so the task is no longer original settings.  Another possibility could be if this is a task which was created prior to 2016 install.  Or, there could be other issues involved.

In any event, the first solution to start with would be to stop using the old task and create a new task with the desired settings.

Use a never before used task name*. Point the Storage location to be a new folder or sub-folder** not used before.

Once task is in use, make NO changes to the task and allow it to perform.  I would expect it to work without issues if no changes made.

If additional changes need, then stop using the new task and create a new corrected task with new name and new location again.

Here is a suggested backup scheme but you can  set your number incrementals and your store number to 3--if that is your desired quota to keep.

GH12. Create Custom Incremental Backup Scheme w/auto cleanup.
...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

Getting backup tasks to work successfully. These are the rules by which I find work for me.

1. Before installing a new verson of Acronis, I remove the old and then run a TI cleanup utility such as item 4 inside my signture link below. Cleanup the residue and install into a fresh new install. I don't try to carry old tasks into a new installation.

2. I create all new tasks and do not later modify. If changes needed, I stop using the old task and create a new task. Each task name is different so no duplication or confusion for the program. In my experience, the most frequent cause of a task not working is that the user makes changes to the task and the changes do not get implemented. Avoid those type problems. Simply create a new task with the new revised settings and a new name.

3. Each of my is tasks is uniquely named, and is set up for a custom backup scheme for automatic cleanup. Backup scheme name MUST read "custom". A backup scheme with automatic cleanup usually does not require manual deletion of old backups as the cleanup is automatic. The cleanup setting I recommend is "store no more than (n) recent version cleanups with the number of chains kept your choice based on available storage space.

4. If a backup is restored, I stop using the restored tasks (which are now out of sync, and create new tasks after the restore. Each new task has its own unique name.

* & ** Explanation:

* Something as simple as adding a different sequential number to each new  task name.

** The storage folder can be a subfolder inside another major folder.  The point being that tib files are not intermixed between other tasks. Each task has its own individual folder or sub-folder. This help to avoid confusion on part of the user and the program.

It hadn't occurred to me to use a new name for the task. I will try that right away.  I have run into problems with tasks after restoring a backup. True Image doesn't seem to handle that very well.

Thanks very much, Grover.

Randy

As listed in my item 4 above, after a restore, I cease using restored tasks and start over with all new tasks with a new task name and a new task folder. Following a restore, the restored TI history file lisiting of existing  tib files does not match the real existing files, so the program starts out confused. Thus, starting with new tasks following a restore eliminates this confusion.

Randy, try restarting your computer to flush the RAM.  I had the same problem. I also used CCleaner to clean the registry and cashed files using the default settings.  It solved my problem for now, but I'm still evaluating True Image 2016.

David