Skip to main content

Old backups not being deleted during consolidation

Thread needs solution
Beginner
Posts: 3
Comments: 9

I am using Acronis True Image 2014 Premium, Build 6673

I have been trying for some time now to figure out a backup scheme that doesn't cause me to run out of room on my backup disks. I have enough room on the backup drive to do 2 full backups and the backup drive doesn't have anything else on it. The problem is that consolidation doesn't seem to be deleting old backups. My current consolidation settings are as the follows (I have tried many other combinations without success):

Backup method: Incremental
Create a full version after every 6 incremental versions
Old Version cleanup rules: Delete version chains older than 7 days

My intention was to create a new full backup every 7 days, deleting the previous full backup and its increments after the new full backup is made. It does indeed do a full backup after 6 incremental versions, but it does not delete the previous full version and it's increments, which is what I was trying to do. I thought that setting it up this way, I would only ever have one full back on the backup disk at a time, allowing enough room to create a new full backup before deleting the old one, and would therefore not run out of space. Unfortunately, it doesn't delete ANY of the old full backups or their increments. Hence, every 2 weeks, the backup drive no longer has the space to continue as it tries to create a third full backup, having preserved the first two full backups along with their increments. I end up deleting the old backup and starting all over again, which is a pain.

BTW, I DO NOT have the "Do not delete the first version of the backup" checkbox selected, so that's not it.

I have a corollary question. When Acronis tries to access how much room it needs on the backup disk to do a full backup, what does it use for the determination? Does it use the raw size of the source drive without factoring in the actual usage and any compression, e.g. if you have a 1TB source drive, would it look for at least 1TB of free space on the backup drive? Or does it factor in the actual data usage on the source drive, e.g. if you have a 1TB source drive with 500GB of actual data on it, would it look for at least 500GB of free space on the backup drive?

I really need a method that is going to do automatic cleanup correctly so I don't run out of space. If anyone can help, it would be greatly appreciated. TIA.

0 Users found this helpful
Legend
Posts: 172
Comments: 11125

maybe I can offer some suggestions. It would help to see a screen capture of your storage folder showing the tib files sorted into detail mode and date/time.

Used space is the control factor.

Beginner
Posts: 3
Comments: 9

Thanks. I just had to clean it out and start over, but when it happens again, I will post a capture of the tib files along with a snapshot of my settings.

Beginner
Posts: 0
Comments: 2

I have the same problem and have changed the settings three times but it never deletes the old backups.

Attachment Size
191270-114712.jpg 84.55 KB
191270-114715.jpg 57.28 KB
Beginner
Posts: 1
Comments: 3

I have the same problem. It never deletes old (automatic cleanup) backups and if deleted manually the backup job no longer recognizes - what should be - the current backup.

Legend
Posts: 172
Comments: 11125

Nigel,

It is too soon to say the task is not working correctly, or at least the task which you have captured.
15 days has not elapsed since B5,s6,v1 was completed. I am assuming that the backups prior to B5 are not involved in this scheme.
My personal preference is that no two tasks are assigned the same name nor the to the same backup folder. Each task has its own sub-folder so the program nor the user becomes confused.

Your backup scheme is  full after 5 iincrementals. Chain=6 files (full + 5 inc)

Delete chains older than 15 days.

Chain b5 completes its chain Aug 5 and deletion of all of chain b5 will occur on Aug 21 when last file of chain (b5,s6,v1) is older than 15 days.

Chain b6 completes its chain  Aug 11 and deletion of all chain b6 will occur on Aug 27 when last file of chain (b6, s6, v1)  is older than 15 days.

Chain b7: deletion of all chain b7 will occur on when last file of chain (b7, s6, v1)  is older than 15 days.

Frankly, I avoid the elapsed time setting and find better success using the automatic cleanup based on "store x number of chains" as illustration below.
GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is user choice.

Legend
Posts: 172
Comments: 11125

Jan H,
We need more info about what is not working. A picture of the backup scheme and storage folder would help--same as provided b Nigel.

When manual deletion needed, this example is the correct way. If the files are incremental, only the newest can be deleted so the numbering scheme remains continuous. However, if you set up the correct backup sheme, with the proper options, then the program will perform its own deletion and manual deletion is not necessary.

GH5. How to delete backup files using Acronis Backup 'Explorer'

One major cause for a task not to work correctly is that the user makes changes in the backup scheme, rather than leaving it un-altered.
If the task needs correction, stop using the task and start over with the correct settings.
Here are some examples of what has worked for me but it would be helpful to see what isn't working for you.

GH11. Create Custom Full Backup Scheme.Keep 4 versions (chains). The 4 is user choice.
GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is user choice.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains. The 2-2 is user choice.

Beginner
Posts: 0
Comments: 2

Thanks GroverH, I now get it - perhaps I need more patience! I will come back if it fails again.

Beginner
Posts: 3
Comments: 9

OK, I forgot that I had another computer set up with the same backup settings, i.e., a week worth of incremental backups before creating a new full backup and erasing the old backups. It has started a new backup chain, but did not delete the old one.

I have attached two snapshots.

  Snap1.jpg: A capture of my consolidation settings

  Snap2.jpg: A capture of the tib files, sorted by date.

As you can see, the first full backup and its incremental backups have not been deleted. According to my understanding of the settings, they should have been removed.

What am I doing wrong?

Attachment Size
191708-114751.jpg 110.87 KB
191708-114754.jpg 184.69 KB
Beginner
Posts: 3
Comments: 9

BTW, just so you know this has nothing to do with available free space, here is a properties snapshot of the C Drive, i.e. the source drive, and the E drive, i.e. the target drive.

Attachment Size
191714-114757.jpg 85.68 KB
191714-114760.jpg 91.18 KB
Beginner
Posts: 3
Comments: 9

I was reading through your responses to Jan and Nigel and possibly see the problem. You are saying that the "deleted when older than" setting is based on the last incremental in the chain, not the first. Hence, when I said to delete chains older than 7 days, the "b4" chain in my folder won't be deleted until Aug 22 (is that correct?), which is the date of the last incremental backup in the b4 chain + 7 days. If it's Aug 23, I can see why it might create a problem for my other system which can only hold two chains. It wouldn't be attempting to deleted the first chain until after it has created two more full chains, which would explain why I am running out of space. So to do what I want, I could set it up to create a new full backup after every 6 incrementals, but delete chains older than 1-6 days. This would ensure that the first chain is deleted before it attempts to start a third one. Did I get that right? Is that why you don't use the "older than X days" setting in your examples?

Forum Hero
Posts: 87
Comments: 9259

As Grover said, using the "keep the X most recent chains" is much more reliable and simple.

Legend
Posts: 172
Comments: 11125

Blue Wolf and others:

Based on what I have been able to ascertain as I have read the various postings and my experience, what happens is this:

The bacikup runs. When done, it then does its testing of settings.
If the oldest completed chain is older than the X setting, it will delete the oldest chain.
If X has not been reached, then the next test will be at the completion of the next backup.
Remember, in order to pass the X test, time enters the picture as well.
In order for the X test (elapsed days) to be yes, The sum of X times 24 hours must have passed. The test could be missed by a few minutes or hours which could pass the test to the next backup run. I assume the test is based on backup completion time but that is a guess on my part. Remember, I am a user and not a programmer so my comments are personal observations.

I will not use the "older than x days" option. It works for some but not for others. Most do not understand it and want the programmer to be "perfect and be able to think and program for all possible changes the user can imagine.
I prefer test based on how many chains exist(store X number of chains) rather then x days. Some base their testing on a few days and other use many many days as the test. Too confusing. Keep it simple. Create the task and let the settings alone. If changes needed, start a new task. Each task should have its own folder.

If a restore made, start over with new tasks as the restored system no longer matches what existed at backup time. The no-matach exists as the backup used for the restore (plus any newer) did not exist at time of backup so when the next backup runs following the restore, the program finds backups with the same name (archives.xml) as it was going to use and the resultiing new backup (following the restore) will now contain the 1-1 name as part of the name. My suggestion after a restore would be to start a new task and a new chain for sake of clarity and knowing the content of the backups. Others may feel differently, but I offer suggestions that work for me.

Whether or not a certain set circumstances will react a specific way sometime must be tested by the user and circumstances can vary and a test by me may not be the same as a test by you. Pictures are much more specific. Words can be mis-interpreted. Both needed for a good interpretation.

Beginner
Posts: 1
Comments: 3

GroverH - thank you for your very informative answer. Unfortunately I had to delete the job I was having cleanup problems with because I had manually deleted the older .tib files and ATI got confused. I hadn't thought of using the Explorer to delete the old files cleanup didn't get, thank you for that and I will do it that way in the future.

I am currently having problems of a different sort with the job I created to replace the one that wasn't cleaning up threads. I will post it as a different support thread, but I have to say I am very disappointed in this product--at least on my computer. I've updated twice hoping to correct problems I hadn't taken the time to report and they still exist. Just this morning it said it successfully backed up at 6am but when I check the backup with Restore it doesn't see the latest chain... only yesterday's.

Legend
Posts: 172
Comments: 11125

Jan,

All files created by a specific task should be viewable using the Acronis Backup explorer. The link GH5 below "should" show all thse specific files.

GH5. How to delete backup files using Acronis Backup 'Explorer'

If by chance, not all files "created by this specific task" are displayed, then you can use GH21 which should add those none listed files to the task display.

GH21. How to add backup files to the listing of backup tasks for assorted uses             such as validation or recovery or add missing files to backup tasks.

Post a screen capture of your main menu listing your tasks,
A picture of the files listed or missing via the Explorer view
A picture of the tib storage folder sorted in date/time sequence.

Added/Edit:
One check would be using this link. Look at the diaplay of the task in question

GH57. Assorted task features.

1. Look at the number of "versions" (upper left of task). This is the number of tib files.
2. Click on the "location" button and view the contents of the storage folder and the number of tib files displayed should match the number listed in preceding item 1.
3. Using the Acronis Backup Explorer view, this view listing the tib files should match the same number as preceding 1 and 2.

Beginner
Posts: 3
Comments: 9

Thanks, Grover, for all the great information. The time you spent explaining things and answering all our questions is greatly appreciated.

Legend
Posts: 172
Comments: 11125

BlueWolf wrote:
I could set it up to create a new full backup after every 6 incrementals, but delete chains older than 1-6 days. This would ensure that the first chain is deleted before it attempts to start a third one. Did I get that right?

The chain must be completed before the check will be made. The check on elapsed days would be made following the completion of the full backup.

In order for the X test (elapsed days) to be yes, The sum of X times 24 hours must have passed when the chevk is made following the creation of the full backup.