Automatic cleanup
Can it be that in version 2017 the automatic cleanup also does not work!
True Image always stops with the message: The last backup was stopped ...... Drive is full.
I have however in the options the automatic adjustment so that the backup archive should not exceed the size of the archive.
If the automatic cleaning does not delete old backups before?
Thanks, I believe with the tip of you:
I can solve the problem.
Because of the current usability of the SecureZone, I have created a separate partition with 1 TB on another disk, in which I created a folder where I saved my backups.
Now I had the automatic cleanup set so that it becomes effective only when the backup archive is greater than 1 TB.
And that was probably the problem. The archive was full before the version chain was complete - the automatic cleanup did not work.
Now I have set the automatic cleanup so that the archive is not bigger than 900 GB and today the automatic cleanup has also worked.
This would have had in my opinion, but also the lady from the support, I had to deal with the problem and which also got all the information about the backup archive of me!
In any case, again THANKS to you!
I was going to create my own thread but this thread is the gist of my problem which is no matter how I setup Automatic Cleanup it does not work.
It has never deleted any of my files or consolidated my backups so how can I fix this problem as I annoyed I have to keep manually deleting my backups and starting over with cloned settings.
Techman, we have nothing to go on here so will be difficult to help without more information about your backup settings, configruations, etc.
For starters, take some screens shots of each tab of your backup task and post them here. Also post the content of your backups as shown in Windows file explorer so we can see all of the file names (full file name) and the creation dates to compare them to what is shown in your backup.
FYI, if you go into a backup job after it has been created and started running, and then make a change and save it, your backup chaing goes back to zero. Leave the task alone once it's been configured and started running.
Example: You have 1 full on Monday with 6 daily incrementals (version chain #1). You tell it to keep keep 2 version chains before cleanup. If you don't touch it once it's started, the cleanup will start at the end of version chain #2, which is triggered by the completion of the next full backup (the start of version #3).
However, if, in week 1, you have gotten to incremental #4 and then make a change to the task and save, you've reset the chain back to 0 so it will need to complete 6 more incrementals before the next full has been run. If you like to play with the settings often, this will keep resetting that count each time you go in, make a change and save it again. If you are/have been doing this, this could/would prevent version chains from completing and that would prevent consolidation from occuring.
LAST... if you have a # of days set for cleanup, that is the # of days AFTER YOUR VERSION chains have completed. So, using the example above, if you didn't touch anything and told it to keep them for 14 days, it would start to cleanup 14 days after the 2nd version chain completed (7 days for version 1, 7 days for version 2, 14 days to wait = 28 days total if you didn't mess with the backup job and resave it anywhere in between).
Techman, we have nothing to go on here so will be difficult to help without more information about your backup settings, configruations, etc.
For starters, take some screens shots of each tab of your backup task and post them here. Also post the content of your backups as shown in Windows file explorer so we can see all of the file names (full file name) and the creation dates to compare them to what is shown in your backup.
FYI, if you go into a backup job after it has been created and started running, and then make a change and save it, your backup chaing goes back to zero. Leave the task alone once it's been configured and started running.
Example: You have 1 full on Monday with 6 daily incrementals (version chain #1). You tell it to keep keep 2 version chains before cleanup. If you don't touch it once it's started, the cleanup will start at the end of version chain #2, which is triggered by the completion of the next full backup (the start of version #3).
However, if, in week 1, you have gotten to incremental #4 and then make a change to the task and save, you've reset the chain back to 0 so it will need to complete 6 more incrementals before the next full has been run. If you like to play with the settings often, this will keep resetting that count each time you go in, make a change and save it again. If you are/have been doing this, this could/would prevent version chains from completing and that would prevent consolidation from occuring.
LAST... if you have a # of days set for cleanup, that is the # of days AFTER YOUR VERSION chains have completed. So, using the example above, if you didn't touch anything and told it to keep them for 14 days, it would start to cleanup 14 days after the 2nd version chain completed (7 days for version 1, 7 days for version 2, 14 days to wait = 28 days total if you didn't mess with the backup job and resave it anywhere in between).
Tell how to setup backup of my 1tb SD Windows 10 OS so I get a ffull backup and then 5 incrementals backups then when done with that it will either combine the backup to a full backup or delete the backups and then it would start over with a full backup and then starts doing 5 incremental backs again. TIA!
Techman, you haven't told us what actual size of used data there is on your 1TB SSD Windows 10 drive, or what size of backup drive you are storing your backups on? These are important factors with regard to your question.
Making some assumptions here about the missing information:
Using the Automatic Cleanup rule to 'Store no more than 1 recent version chain'
Acronis would create 1 Full backup plus 5 Incremental backups = 1 version chain. However, nothing gets deleted until the next version chain has been successfully created with the next Full backup.
Your backup drive would need to have sufficient capacity to store at least 2 x Full backups plus 5 Incremental backups.
If you use the Automatic Cleanup rule to Delete version chains older than 7 days, then the age count does not begin until the next version chain has been successfully created with the next Full backup. So again, nothing is deleted until 7 days after the second Full backup was created.
I have to keep checking back at these forums because even though I setup it to email when someone leaves a message it not working.
My current situation I am backing up atm 745gb of data which will grow as add more games to my OS partition which looks like will need bigger backup drive
My data is currently being backed up on my SATA 2TB seagate HD which is just being used for this backup.
I will set my backup to 1 full and 3 incremental with 1 version chain and see if I have room.
My first full backup has been done which is 551gb after compression and leaving 1.27 TB remaining fyi
Techman, I hear you on the forum notifications, I haven't had any about new posts since around Saturday so something has broken there!
For your automatic cleanup, you will still need space to hold 2 x 745GB approximately if we assume that your three incremental backups will be equivalent to the compression data saved on the full backups - this just in order to keep just one version chain.
Techman, I hear you on the forum notifications, I haven't had any about new posts since around Saturday so something has broken there!
For your automatic cleanup, you will still need space to hold 2 x 745GB approximately if we assume that your three incremental backups will be equivalent to the compression data saved on the full backups - this just in order to keep just one version chain.
Thanks for the help and it worked and I even had to use the newly completed full backup to restore my PC which is why I able to post this followup message.
It great to be able to use and understand this feature imho.
Thanks for the positive feedback, glad to hear all is working for you.
I regret my bad English.
I have reached the defined limit of 1TB and there is no cleaning.
I attach all requested screens.
I thank in advance for help.
Norberto Kelijman
Hi Norberto.
I would manually delete the items listed as outlined int the attachment (via Windows file Explorer). Then go back into Acronis and immediately validate your backup. That will trigger Acronis to ask you to remove those backups or locate them. Remove them as that will still give you 2 full backups and some incrementals to hold on to.
Additionally, you should change your backup settings from 1TB to a smaller amount - I'd say 800Gb since your backups are roughly 150GB. Cleanup will only cleanup older backups after the next full backup has completed. So, you don't have enought room for another full backup. By reducing your limit from 1TB to 800GB, that should be OK as long as your full backups remain about 150GB.
Alternatively, instead of using a size, you can choose a number of version chains to keep. In your case, it looks like you would be able to keep 4 version chains (as long as the backup sizes remain about the same).
I regret my bad English.
I have reached the defined limit of 1TB and there is no cleaning.
I attach all requested screens.
I thank in advance for help.
Norberto Kelijman
I'm sorry, I think the clean up is working.
Acronis perhaps was not doing the backup because I spent several days on vacation and use USB backup disk changed its letter.
Norberto, thanks for the feedback / update. If your USB drive did change drive letter then this could cause some of the problems you have seen.
I would recommend giving the drive a letter from later in the alphabet via Windows Disk Management then reselecting the drive in your backup task - this should help stop it from getting a different letter in future when you plug in a memory stick etc.