Automatic clean up
I have TI2016 set to keep no more that 6 versions, however older versions are not being deleted. I have tried creating a new task and the same thing happens. Any ideas on getting this to work?
This may help.
http://forum.acronis.com/forum/100416
Please post a screen capture of your Backup scheme (prefereably both tasks if you still have both tasks)
Also, this link if applicable
https://forum.acronis.com/forum/96972
Here is the screen shot of the scheme. The older task is no longer available
Nothing unusual stands out. The backup deletion should have occurred after Full B7 was created.
If the task was edited, this may have delayed the deletion.
Was this task created new in 2016?
If you wish, zip the logs folder and the script file and attach and I will look at later tonight.
The script files can be found at
c:\programdata\Acronis\TrueImageHome\Scripts
The logs at
c:\programdata\Acronis\TrueImageHome\logs
Thanks for the reply. Yes task created in 2016, not edited as far as I recall.
There are 4 script files and loads of log files do you want them all?
Yes, you can include them all in a zip file.
Any or all of the log files can be deleted as these are for your benefit and not used by the program.
Curious: it capture would imply that you have two 2016 scripts. Maybe the others two are for validation.
The script files can be viewed in notepad is see what they are. The task title usually found in the upper left corner of the file when veiwed in notepad.
How was 2016 installed? Was this A fresh install with no prior true image install?
The task listing would seem to indicate that 2016 was overtop a prior version. If yes,
you will probably have the uninstall 2016 and reinstall again as there is no cleanup utility for 2016.
Some computers can handle an upgrade overtop but others seem to need a fresh install.
Do you have any registry cleanser (such as ccleaner, etc) which you run to do cleanups after the uninstall.
I had TI 2014 installed I ran the Clean up utility prior to installing TI2016. I have no idea why the 2014 backups are listed
I attach the Log & scripts and look forward to your comments
Maybe I am not understanding your questions.
I have TI2016 set to keep no more that 6 versions, however older versions are not being deleted. I have tried creating a new task and the same thing happens. Any ideas on getting this to work?
Would you clarify your question "What do you mean when you write "older versions not being deleted".
After a review of your zip file, the two current 2016 tasks have only completed 4 Fulls each (B4 reached in each task) so these tasks have not reached your preset quota of 6 files per task. Cleanup deletionis not due until your preset retention quota of 6 files has been exceeded, On these two tasks, quota will not be exceeded until after SECONDS after Full B7 has been successfully created, then the oldest Full (B1) will be deleted keeping a quota of 6 Versions which will be Full B2, B3, B4, B5, B6, B7.
The task cleanup rules only apply to the backups created by that specific task. So your question must not relate to these two tasks as deletion is not yet due--or maybe I don't understand the question? If the folder or disk has too many files, different scheme settings may be needed to keep the larger piciture within size limits.
Task=Libraries
successfully created: Libraries_D2015-10-02_full_b4_s1_v1.tib
quota chain_count="6"
Task=Crucial_CT500MX200SSD1
successfully created: Crucial_CT500MX200SSD1-2015-10-07_full_b4_s1_v1.tib
quota chain_count="6"
You can expect cleanup deletion to apply to each task configured to keep 6 full as per this example
Looking at the folder containing the backups. I can see the Libraries hasn't reached the 6 yet. The disk backup numbering looks strange. I did install Windows 10 and ran the task twice then reverted to windows 7 not sure if this messed up numbering. I have manually deleted the earlier backups
The switch from 10 to 7 involved registry changes. The backups which ran in 10 has a different ID than the one in 7--according to the log files.
This would cause name confusion at the very least. I do not believe any of the backups have any real credability.
If it were me, I would stop and start over with new tasks. Each new task to have a name different than any prior.