Salta al contenuto principale

how to manually delete backups from external drive

Thread needs solution

I appear to be running out of space on backup drive and what I read about deleting
existing backups is confusing. How can I manually delete older backups. I do Partial weekly and periodic full system
backup.
Thank you
jim geoghegan

0 Users found this helpful

2015 does not provide a means of deletion within the program so the only method available is to delete using the Windows Explorer and then simulate the start of a recovery to update the program with the changes.

However, what and whether you should delete the files is another issue.
If all are full, you can delete any you wish.

If you have a full plus incremental chain, only the NEWEST can be safely deleted and the oldest must be retained as the numbering must remain sequential.
or you can delete all the incrementals for that task but keep the full which is the base.

If you have other delete questions, show us a picture of your destination folder sorted by date and time.

You really need to start over with a new custom backup scheme using automatic cleanup so the program will do the deletions automatically without your intervention. Examples below.

*GH11. Create Custom Full Backup Scheme with Automatic Deletion of old files.
       Ex: Keep 4 versions (chains). The 4 is user choice.

*GH12. Create Custom Incremental Backup Scheme with Automatic Deletion of old files.
       Ex:/Full + 6 Inc. Keep 4 chains. The 6-4 is user choice.

*GH13. Create Custom Differential Backup Scheme with Automatic Deletion of old files.
       Ex: Full +2 Diff. Keep 2 chains. The 2-2 is user choice.

I have TI set up to do a full partition backup every 30 days, and an incremental every day until the next full. What I've been doing is keeping as many chains as will fit on my backup drive, then using TI 2014 to consolidate the oldest backup chains when I need space. As you noted, this feature is no longer available.

With TI 2014, deleting .tib files outside of TI could be a short path to trouble.

I want to confirm what you are saying:

With TI 2015, I can use Explorer to delete the incremental files from a chain safely?

Starting a recovery, and then canceling it before it actually starts to work, will rebuild the TI internal database?

Do I have to start a full recovery of the partition, or can I just restore some innocuous file?

Does it matter which version I try to use, or will simply starting the recovery rebuild the whole kit and caboodle?

You may find this link of interest.
https://forum.acronis.com/forum/72092

Jerry wrote:
With TI 2015, I can use Explorer to delete the incremental files from a chain safely?

No. The only inc which can be deleted safety and keep the file restorable is the newest most recent inc. The sequential numbering of the chain beginning with slice 1 (s1) to SX (x being newest most recent inc file) must remain intact as each inc has its own single piece of the chain. Any deletion of the any older slice will break the chain at that point so only backups prior to chain break will be usable.

Jerry wrote:
Starting a recovery, and then canceling it before it actually starts to work, will rebuild the TI internal database?

At the bottom of each task is the "recover" option. Simulating the first step of a restore for that specific chain will update the database for that single chain. If for example you create a new backup and then decide you want to delete it, you can delete it via Windows Explorer and then colick the Recover option which will update the database FOR THAT ONE SPECIFIC TASK. In some of 2015 my testing, I found that deleting an older task did break the chain at that point of deletion, but the task was still usable and the backup ran starting with a new full backup. All versions prior to 2015 would stop but 2015 would restart the chain with a new full.

The deletion of a complete chain of full plus all its incs should allow all remaining chains to work.

Do your own testing. Each situation is different. Establish what works for you.

GroverH wrote:

Do your own testing. Each situation is different. Establish what works for you.

Um — is that how you test your parachute, too? :)

I'm still not sure I understand, though: If I have a full plus 17 incrementals, I understand that deleting one in the middle of the chain would break it; but if I delete the incrementals starting from the end of the chain, can I delete more than one at a time?

For example, if all I want is the full backup at the start of the chain, can I delete all of the incrementals?

Jerry,
Were these created by 2015 or prior?
If by 2015, are the tasks still in use?
I am not a definitive expert but in my testing (only for my own use),
yes, you should be able to delete all inc in a chain and the full still be restorable.
Yes, if you deleted last inc #18 and then deleted #18, iff all prior existed, then yes, what is left should still work.
and if you continued to delete #17 and #16, as long as sequential listing is still sequential, all remaining should work.

On way of testing would be to copy the chains to another external disk and test with that safety copy not attached.

Don't you test a parachute by having two attached so if the primary does not work, you pull the secondary cord?? (and pray).
Former First President Bush #41 did a parachute jump on his 90 th birthday.

2014 had poor UI design and 2015 removes many useful features and the UI although pretty is terrible; do not have time to list all the problems.

Some of the answers here are confusing as well.

In an increment chain, you can only delete starting from the most recent but that destroys the concept of recovering space and maintaining the latest backups so long increment chains are not good. I do a full backup after every 3rd increment and I believe one should set up something like that with perhaps more increments - a long inc chain can be problematical but sometimes unavoidable but strongly advise against them.

A full backup with all its increments can be deleted manually from the OS without problems unless there is a bug in AC 2015.

Since I have 30-day backup chains going back to May, I took a leap of faith and deleted the incrementals from the oldest. As soon as I clicked on "Restore Files" I was prompted to ignore each of the missing files; but in the end it worked, as you prophesied.

This is still a short-sighted change. The very people who would be too inexperienced to use a consolidation tool are the ones who would be inexperienced enough to fill up their backup drives.