Set for differential, but creates incremental backups
I have repeatedly configured it to do differential backups after the full backup. However it seems to lose my settings and is making incremental backups.
Click on signature link #2 below and look at figure 11-Diff.
This is an example of how to setup a diff backup scheme.
You need only one task for this. The first run will be a full backup and the 2nd run of the same task will create a diff backup.
To get the 2nd & later run of the single task either use the scheduler for all or click the Backup Now option of the same task.
For each new task created, always use a new empty storage folder. My suggestion is not to mix backup files. One storage folder per task.
Thank you, Grover11.
It finally made a differential backup. However the log is utterly confusing compared to the straightforward logs in 2010.
It seems to say it failed, and it then went on to create a new full backup.
The error appears to have been: "Failed to prepare data stream. Check whether the source and target partitions exist."
It then went on to say: "Failed to open backup C:\Users\Coly\AppData\Local\Temp\tmpd2.tmp\HP_(C)_diff_b1_s3_v1.tib. It may be inconsistent or corrupted." (There is actually no C:\Users\Coly\AppData\Local\Temp\tmpd2.tmp\ and I don't know why it was attempting to open that file).
That makes no sense to me.
The full backup it then created was valid.
Perhaps I should just let it make incremental backups, although I consider differential more reliable and prefer them.
Is there any known bug in differential? My full backups are large - around 40 GB.
I would encourage you to create a new task as per my example. Once you have issues with a task, it best to stop using it and start over.
Note my attachment. It is an example of diff backups on a schedule with occasional added manual backups.
My attachment was set to keep the original backup.
My guess is that the old task uses some type of consolidation and the consolidation failed. Your error has appeared in other postings.
Start over with a new task and point the task to a new or empty sub-folder so the *.tib backup files are not intermixed.
Yes, your attachment looks like exactly what I want.
I did not set any consolidation, but did configure it to make a full backup after 7 differential backups. And to delete any backups older than 30 days. I wouldn't expect any trouble from those, would you? However I did have trouble creating the settings - it seemed to keep forgetting them. Oh, and I also configured it to add a comment.
I'm sorely tempted to uninstall 2013 which has features I don't need, and reinstall 2010 which was completely reliable and I was very happy with.
I had made a new folder Acronis2013. I'll make another, Acronis13, and a new task for it as you suggest. And see how it goes.
My personal recommendation is NOT to use the age factor option. When the age factor is reached, then merging tasks place much like the problems you just had. My recommendation is to base your retention on # of recent version chains you wish to retain.
If you were to project forward my example after a couple months, you would find that most backups retained will be full, with only the last one to have individual diff. Much of how it would look would depend upon its age and how many x recent version chains you keep.
Actually, 2013 is much better than 2012 or 2011 in its backup retention but my practice is to completely avoid the age settings or the space limit settings as I want it to keep it simple to keep a certain number of backups.
I have several storage disks that I use for backups so I have a variety of tasks and backup because I do not want to be caught with only one backup and one (or none if issues) chance for restore.
Changed it to keep no more than 5 chains. I assume a chain is full backup plus 7 differentials. (It's configured to make a full after 7 diffs.)
I do so much appreciate your help with this. Stay tuned! I'll see how it goes the next few days. It's scheduled to run every day at 10:00 AM.
Minor puzzle: my 2010 let me create more than one task and enable/disable as desired. But 2013 seems to just have one task? Or am I not looking in the right place?
Yes, I would be interested to know your results. You will get a full backup every 8th day so the full will be on a different day each week.
I do not know of any limit on the number of tasks except you would want each task to have a different name for identification purposes. I vary between 4-8. Some are scheduled--some not scheduled but executed via "Backup now" or a desktop shortcut. Each task will be located under the other but there is a sort option at the top menu so the task can be arrangement several different ways.
For example, if you have an old backup you want validated, from inside the program, you would use the Browse for Backup option and once *.tib file located, you would use the adjacent "add to backup list" option so then the validation task for that file would appear on your listing of tasks.
I believe you would benefit by studying the link #2 below--especially the comments with each picture. 2013 is so much different than 2010 in that you almost need a roadmap or GPS to keep track of all the different options and where located.
For storage on one disk, I usually use one main folder but each task has its own sub-folder so to keep separate.
My whole 1TB second hard drive (F:) is reserved for backups and there is plenty of room to make new folders etc..
Your link # 2 is a gold mine! I've bookmarked it. Thank you for it!
Finally I understand how to name the task. But there doesn't seem to be a way to see a list of the tasks? Anyway I'm going to wait and see whether my current task behaves as I expect before I start adding any other tasks.
If your storage disk is an external, consider assigning a drive letter to it (such as X or Y or Z) so the insertion of a flash drive or camera or printer will not cause a change of drive letter to the storage disk.
If you have some other reading time, click on the link #1 below and look at some of entries in the index item #3.
If you have not created any additional tasks, there will be none to see and no listings.
You can create a listing of tasks by clicking the browse for backups option but the listing will not be of any value and you will get tired of seeing it and the added delays and later you will be wanting to delete the non-usable entries. If you have *tib backup files, they are all accessible when needed by simply browsing for them and adding them to the list.
My backup hard drive is internal and always F:
Bookmarking your link # 1
I guess the way to manage a task is right click the backup location, select Edit Settings, and turn on or off the Schedule. Not too bad. :)
Keeping track of things by the folder names is sort of ingenious now that I finally get it.
Last post for tonight. Other than turning the schedule on or off, editing the task not recommended. Changes confuse the program and the results are usually not what the user expects.
That I can believe!! I'll post in a few days after I see whether my new task is cool or not.
Thanks again for all your truly wonderful help.
It's working beautifully. Doing exactly what I want. Totally happy with it now.