Erasing Old copies, not per setup
I have it set up to save a certain number of copies. It keeps erasing the old ones and only keeping the new one. This is problematic for both losing the copies and slowing down each new disc backup. Anyway to fix this? Thank you.
I have W7 64-bit and TI2014. It was working as instructed. Then I was out for a few weeks, and cancelled a backup when it started the moment I turned on my computer after returning. As I posted in an earlier post, if compter is not on on Thursday, then it gets all weird.
Partition scheme is Incremental, New full after 7, store no more than 2 chains. This is weekly
Files backup scheme is Incremental, full after 20 versions, store no more than 3 chains. This is daily
It is not doing any of this. It is erasing too early. Not always backing up on time. And when I stop a backup it messes up the computer and I think the program.
Thank you
Stop using the existing tasks and start two new tasks. Set the new tasks with the correct settings and then do not edit or make any further changes. Each scheme is to be a custom scheme as per example.
Use GH-12 as your example but with the your number settings.
----------------
Your specificstions were:
Partition scheme is Custom/Incremental, New full after 7 incremental, store no more than 2 chains. This is weekly
Files backup scheme is Custom/Incremental, full after 20 incremental, store no more than 3 chains. This is daily
Partition task:
What you can expect from the partition scheme of full + 7 incremental--keep 2 chains
Chain length is 8 files (full Plus 7 inc), Keep 2 chains of 8 or 16 files total max keep.
Automatic deletion of the oldest chain of 8 files will occur seconds after 2 chains have been completed plus after the next full (full b3) backup,
or auto delete seconds after backup FULL #17 is successfully completed. Program will create the full backup #17 (2 chains of 8 plus the 3rd full)
at which time it checks the cleanup setting and finds (for the first time Full b3 exceeds the limit of 2) more than 2 chains and then deletes the oldest chain (of 8 files) leaving chain #2 (backup b2) plus the Full b3- beginnings of b3. As backups continue, the deletion process will next re-occur after full b4 is completed when the limit of 2 chains is next exceeded.
Files/Folders Task:
What you can expect from the files scheme of full + 20 incl-- Keep 3 chains
Chain length is 21 files (Full plus 20 incremental), Keep 3 chains of 21 files or 63 total max keep.
Automatic deletion of the oldest chain of 21 files will occur seconds after 3 chains have been completed plus after the next full (full b4) backup,
or seconds after backup #64 is successfully completed. Program will create the full backup #64 (3 chains of 21 plus the 4th full)
at which time it checks he cleanup settings and finds (for the first time Full b4 exceeds the limit of 3) more than 3 chains and then deletes the oldest chain
(of 21 files) leaving chain #2 & 3 (backup b2 & b3) plus the Full b4- beginnings of b4. As backup will continue, the deletion process will next re-occur after Full B5 is completed when the limit of 3 chains is next exceeded.
If the preceding number of keeps is not what you had intended, you will need to adjust the task scheme numbers using the procedures outlined in my explanations.
Thank you. So are you saying once you make a scheme, you can never adjust it in any way?
Also, that turning off a backup when its running and not really finishing will mess up the scheme and I will need to make another one?
What you wrote is what I expect to happen, you didnt have to go into that detail. Most of us would prefer detail on why this "simple" program does not actually do what you at length say it is going to do.
I would love to set up the scheme and never think about it, but that is not what happens. I remember you saying a while back about issues related to deleting a scheme. I hope that once I put in new ones and just delete the old ones, things will work ok. But I am sure I will be posting on here again.
Thank you.
The scheduliing changes can be handled via the example below so editing of the task is not needed in order stop/start/change schedulle.
The program permits changes but never reacts correctly to those changes,or never reacted correctly for the many that have posted for problems and never reacted correctlly in my changes. Of course, much could have to do with the actual content of the changes but since the changes never worked for me, my recommendation I use and suggest to others is to avoid all changes via the "edit settings" option.
My signature link 2A. Using 2014can help.
GH0. 56872: New! Grover's How to Backup 2014 from within Windows.
GH1. How to change a backup task from scheduled to "Do Not Schedule".
GH2. How to enable a backup task schedule or change a schedule time..
GH3. How to create a non-scheduled backup task on the first try.
I really dont understand. One day, I will take a few hours or days and read how to do this. I thought the program was a simple one, but I guess not. I had read a few of your links, but it never seems enough to get the program to just do the two simple types of backups.
I never wrote "Also, that turning off a backup when its running and not really finishing will mess up the scheme and I will need to make another one? "
As there is no "pause" option, any stoppiing will be a cancellation. I would believe that the program would disregard a cancellation but hey, I'm just another user offering suggestions which work for me. I have found when I followed my own suggested procedures, the backup schemes always works for me, and I believe they will for you as well. Note in all my scheme examples that the type scheme begins with Custom and do not use any default scheme.
I start new tasks when changes are neeed,
or after I perform a restore,
or after I upgrade to a new build or new version.
My signature link #1 offers suggestions mostly for 2014 and before. All my comments in this post were directed relating to True Image 2014 which was your version indicated.
I thought the program was a simple one
2013 and 2014 have a very distinct learning curve. To be successful with either version, it is best to learn how the program works via real time usage. Version 2015 is unlike any prior version and has another learning curve. Disk characteristics (GPT) of Windows 8.1 and some prior systems with UEFI/GPT is making the newer systems even more diffucult in the learning curve category.