How to remove some old backups without deleting the backup job?
How do you delete some old backups without deleting all of them as well as the job?
Thanks for confirming that this still isn't possible in ATI2015. The removal of that function was my main reasoning for downgrading back to ATI2014 (which allows it: https://forum.acronis.com/forum/65498). I would have thought it was a critical part of any backup software. At least once a month I get a single incremental backup that is corrupted and I need to be able to delete that one corrupt backup but keep the full backup chain intact.
With Win10 on the horizon it is time for me to upgrade my backup software and I guess I will have to find a different backup software provider.
Nick,
When you perform such a manual deletion, follow the deletion with a validation and resond "ignore" to each prompt.
After the successful completion of the validation, I believe the task will continue to make new backups.
Try it and let me know your results.
Hi there, this worked for me. Wanted to post that so if someone else was wondering. My backup that I tried it on was a full backup not an incremental so can't say for that type.
When I first started using acronis I would delete backups because my disks were full but then I didn't know why my backups failed all the time. this could be reported to the user in a different way so that it explains that a backup was deleted so their backup can't run anymore.
***** Another thought is for Acronis to add an option that "Should previous backups be deleted BEFORE or AFTER the backup job runs". That way jobs that will make the hard drive overfill can still be run.
The Developer,
The best way currently to control your backups is the use of the automatic cleanup option located in each backup scheme whereby the program will automatically do its own deletion of oldest chains whenever the progam reaches the user set retention quota. Here are four examples of how this can be achieved depending upon which type backups you wish to use. Example GH11 is for full backups. A new task is needed to start a fresh set of chains with the proper configuration.
------------------------------------------------
Depending upon the type of backup scheme you wish to create, here is an example of each type. These can be set up for Disk image, or Partiton, or Files-folders backups. These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.
Editing an existing task is not recommended. Rarely does an edited task perform to user expectations. It is usually better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.
GH25. Understanding differences between Inc and Dif for Safety
GH64. 71342: 2015 How to save a non-scheduled task.
GH63. 64640: Hints to help prevent issues with your TIB backup files creation.
GH63. 75086: A discussion on how to configure backup schemes.
-----------------------------------------
Exactly, that's the whole point. I do use the automatic cleanup tools in ATI 2014 and I don't want to risk deleting individual backup files in Windows Explorer. But about once a month the backup fails (e.g., Windows crashes) and leaves a corrupted chain. In ATI2014 I just use the built-in backup browser then scroll through validating and/or deleting each version until I have got rid of the problem backup (see attached screenshot). Doing so makes sure I am deleting the correct backup version. Then the backup chain just keeps ticking along like nothing happened. I do this all the time with 100% success.
As long as ATI2014 works with Windows 10 I'll keep using it. If I do eventually have to go backwards to ATI2015 I'll try manually deleting files in Explorer and validating, but gosh that sounds risky.
I know that I can copy the task and start over but my problem is that I don't want to because my drive is full and I can't do anymore backups to it.
I also don't want to delete the old backups myself to make space to run the new job created because that might affect the backups that I do have.
what I do need is the job to delete previous backups BEFORE it runs the next backup. Right now it deletes the job AFTER the backup runs. Then I can set the job to only keep 4 sets instead of 8 and then it will clear enough space to run again.
The Developer,
what I do need is the job to delete previous backups BEFORE it runs the next backup.
Well, yes, that would be a very helpful option. Unfortunately, that is not an option available to you at this specific time.
Let us see a screen capture of your backup scheme; and also a screen capture of the storage folder with the tib backup files sorted in detail view and by date/time--similar to the GH14 example.
GH14. Custom Differential Backup Scheme . 6 Diff, Keep 4 chains. & folder
After we see the suggested captures, maybe we can offer some suggestions.
Based on your comments, it appears your choices to be if the backup type last done is an incremental., then
1. Use Windows Explorer and delete the most recent most current single inc tib file.
2. Do a manual validation on the remaning by selecting the single most recent inc file for validation.
3. Respond "ignore" to each prompt. respond ignore multiple times if needed.
4. After validation is successful.
5. Use the task "edit settings" and change the task scheme from "store 8" to "store 4" and save the changes.
6. Run the task manaully via "Back lup now" and hope that the task backup and deletion is successful.
Sadly, task editing is not successful very often and it is not one of my normal recommendtons, but you have little choice here.
Hi Nick,
I do this all the time with 100% success.
Thanks for reporting this. This confirms that this procedure does work for some.
The important key is to get the progam to update itself about the deletions. I recommend the validation method and respond "ignore" to each prompt for each file deleted. Another method of getting the program to update itself is via the simulated restore method. This gets the program to prompt the user for the ignore response for each file deleted.