automatic cleanup of older backups fails
hello community,
when i configure ati to automatically cleanup older backups (exactly: to keep only the last 3 backups stored), it does not work. when i create a fourth backup, the oldest backup won't be deleted. i have configured all the three older backups with backup-scheme > userdefined scheme > backup-method: complete > cleanup-rules: do not safe more than 3 actual versions.
i would assume that ati at first does the next (fourth) backup and when finishing this completely and well done, then it would delete my oldest (or first) backup. but nothing happens.
is this a wellknown bug or do i make any mistakes in the configuration???
info: i use win7 x64, the newest build of ati 2016 (5634) and do all my backups with a validation. the backup is always saving my system-partition C (200 GB) on a harddisk (1TB), where there is still another partition (D).
i would be very glad to get some help here. thanx a lot!
grashalm
Hi GroverH,
thank you very much for this comment. you are right: I used a user named backup scheme. I will try to use the backup scheme "custom" now.
I hope it will work now. If I get more problems with that, I will post again.
Thank you very much,
grashalm
The best chance of success would be to create a new task. making changes to aN EXISTING task rarely works.
hi, groverh,
in the meantime i created a lot of new backups, but it still does not work. at first i always click "add a new backup" to determine source and destination folders (for each new backup i create a separate new folder). then i click on "options". because i do not use the planning feature, i directly click on "backup scheme". in this window i now always use "custom" backup scheme (in german it is called "user-defined scheme"), then i choose backup method "complete" and choose "do not save more than 3 newest versions" in the automatic cleanup area.
then i click okay and start the backup. i do not save this configuration with an own name. i always just make my coniguration clicks and start the backup. but no matter how many backups i create, the older ones wont be deleted. even with 5 backups the oldest one wont be deleted automatically. i always wait until the backup is finished and the new backup will be shown in the list at the left side. but when i check my folders with the older backups, they are all still there.
you said it would work, when i use the backup scheme "custom". do i make any mistakes yet?
you may still have an idea, what i am doing wrong...
thanks a lot, grashalm
grashalm,
Try creating a new task using this scheme without any changes. If created exactly as example, the automatiac deletion should occur after Full B5 and after each new full thereafdter.
GH11. <a href="/system/files/10-1full--custom_keep4.jpg"><strong>Create Custom Full Backup Scheme w/auto cleanup.<br />...Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..</strong></a><br />
The new task should have a new name and the folder or sub-folder target name should also be new.
https://forum.acronis.com/system/files/forum/2014/11/71342/save_new_tas…
The automatic deletion of the backups will only occur on the backups created by this specific task. Old backups created by other tasks are not involved in deletion by this task.
The new task can be scheduled or non-scheduled and all backups should have the same name except for the Acronis syntax at the end of each tib file.
I might help to see a picture of your storage folder with the tib files sorted in date/time order.
hi groverh, thank you very much for your quick reply. i made a copy of your comment and give some comments to different sentences [...], because i can answer your post better then. Try creating a new task using this scheme without any changes. [which scheme do you mean? the one i always try to use and which i described in post #4 or yours in post #5?] If created exactly as example, the automatiac deletion should occur after Full B5 and after each new full thereafdter. [i do not get a "full B5". my backups have all the same name: "Volume C - System (C)_full_b1_s1_v1.tib". the number at "b" is always "1". GH11. Create Custom Full Backup Scheme w/auto cleanup.
...Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..
[i do not understand these 3 sentences]. The new task should have a new name and the folder or sub-folder target name should also be new. [okay. i now called my new task "grashalm". i always create a new subfolder for each new backup and name it "2015 11 27 -1" or "2015 11 28 -2" with changing dates and counting up the last number.] https://forum.acronis.com/system/files/forum/2014/11/71342/save_new_task... [i did as you described] The automatic deletion of the backups will only occur on the backups created by this specific task. Old backups created by other tasks are not involved in deletion by this task. [that seems logical for me.] The new task can be scheduled or non-scheduled and all backups should have the same name except for the Acronis syntax at the end of each tib file. [okay. in my case they are non-scheduled. as i mentioned above, all the filenames in my backups are all the same. even the acronis syntax does not change. the number with the "b" does not count up. it is always "1".] I might help to see a picture of your storage folder with the tib files sorted in date/time order. [i send you a screenshot of my backup folders. each folder contains only one file with the same name: "Volume C - System (C)_full_b1_s1_v1.tib". [this may be the reason for the failure. maybe all the backups (from one and the same task) have to be collected in one folder, so that the number with the "b" is counting up then.] [added comment: i just tried so, but the name for the second file in the same folder was: "Volume C - System (C)_full_b1_s1_v1-2.tib". so this does not seem to be the right way...] maybe these comments and the screenshot help you to understand, what i am doing wrong. thank you very much for your patience, groverh. grashalm
hi groverh,
after 8 long month of frustration I spend some time again last night to consider about my problems with the automatic deletion. I tried a lot again, failed a lot again and began to read once more all the threads I posted here to you. And finally I found the solution! When I read your sentence:
"The automatic deletion of the backups will only occur on the backups created by this specific task. Old backups created by other tasks are not involved in deletion by this task.",
I suddenly stopped, when reading your words: "...this specific task." I realized that I always created a completely new task, when planning a new backup. So it couldnt work. I then started to use the same task for a second and a third backup (only always changing the destination folder) and now it works. finally the "B"-element in the destination file name is counting up from 1 to 2 and 3 and so on (depending on my configuration) and the first files are deleted automatically now, after the backup is done.
Still interesting is the following: Though you said in the beginning that the backup scheme should be "custom" and no name should be given to a personal configuration of a backup scheme, the program seems to accept even own configurations that are named by myself now. That's really great!
So: Once more I say thank you for your posts and patience!
grashalm
grashalm,
Thank you for the update. Which version of TrueImage are you using?
Would you consider posting a picture of how your custom backup scheme is named. Note, I am referring to the scheme name and not referring the the task name.
Is it necessary to have a different folder each backup?
hi, GroverH,
i am using trueimage 2016, build 6571 now. i also post a screenshot here, where you can see the name of the new configured backup-scheme. the name is "lothar C".
i don't think that it is necessary to have a different folder for each backup. a few nights ago, when i was trying and testing all the configurations again, I also tried to save all the different backups in the same folder. and it worked, i mean: trueimage gave each file a different name by adding a "-2" or "-3" to the additional file names. the program did this, because at that time the file names were still all the same and the "b-value" in the name did not yet count up. and it could not of course, because at that time I still started each backup with a new task.
since I do the backups now with the same task again, it all works fine. but now i have not yet tried to save the new backups in the same folder. so i cannot grant for a working backup, when both of these configurations are combined, but I would assume, that it will work!
best wishes to you,
grashalm
