Old chains don't get deleted as scheduled - wrong config?
I've set my incremental backup scheme to delete old version chains after seven days - see attached screenshot:
However, even though 7 days passed a long time ago my disk is still occupied with the 1st version of the backup + all incremental increases as well as all later full backups + all incremental increases.
I use this scheme to backup my documents so there are about 10-12 new files each day (I've set the backup to run every hour).
My intention was to create a full backup ca. every 2-3 days and keep no more than 3 such files.
This apparently doesn't work - anyone can look at my config and advise what's wrong with it? Many thanks in advance!
Yep, here's the screenshot of my backup folder. As you see the "LaptopFiles" job started at October 23rd thus today the oldest files should get deleted I believe...
Do you think that it only delete the files after two conditions are met together - there are 7 days since last backup AND there are 20+1 new backup chains (created after those 7 days)?
Geee... If so - there's a bit too much for me ;)
OK, I was playing a bit with that an decreased the number 7 (days to keep chains) and run backup. It then... Consolidated the backup and deleted the 1st full backup and all later chains associated with that.
I suppose it is the date of the last chain in a particular backup path that determines whether the whole backup path (meaning: initial full backup and later incremental parts) is eligible for deletion.
I mean: supposed I had a full backup on October 23rd and then 20 chains out of which the last one was created on October 25th - so NONE of them will get deleted until November 1st (or 2nd) with days to keep backup set at 7. And it doesn't matter that some of them are in fact older than 7 days.
The conclusion is (am I correct by the way?) that ATIH will NOT delete only selected chains (those older than x days) but it will delete the whole backup path (= initial full backup and later incremental chains until the next full backup). So there will never be situation I have such files in my folder:
chain_3_19.tib
chain_3_20.tib
full_4.tib
chain_4_1.tib
chain_4_2.tib
(...)
but only:
full_4.tib
chain_4_1.tib
chain_4_2.tib
(...)
What I believe will happen is on first backup on Nov 1, it will create the first inc due on b2 (if due) and then delete all of b1 chain.
I do not believe it will delete the b2 chain until all 20 inc has been created and the 7 days past last slice of b2.
When viewing your storage folder, click on the "date created" header so the sort will be based on date/time created.
These comments based on post #2, I had not seen your post #3.
Yep, you gave me the same answer I was suspecting - many thanks for that!
I wish there was something "between" standard backup and sync features - meaning syncing but with ability to restore to given folder(s). Such option would create much less confusion than different backups variations. They are clear for IT professionals but not necessarily for home users.
mikolajek,
You might find this link of interest as it is an extension of my illustrations used in this posting.
http://forum.acronis.com/forum/45927