Aller au contenu principal

Can TI Home 2012 delete excess backups?

Thread needs solution

My biggest beef with TI Home 2011 is that it won't delete excess backups. E.g., you can tell it to only keep the last two backups, so when it makes a new backup that brings the total to three it should delete the oldest one, but it never does. So every morning I have to manually delete it to not exceed my backup drive's capacity (I have my PC do a complete system backup every night and then shut itself off). Does anyone know if this feature actually works in TI Home 2012?

0 Users found this helpful

No one as yet has reported that it isn't working for them.

This has worked on 2011 and 2012

Jeff,

If you modify this parameter "to try", you'd better set up a new task, with a different name, ideally to a different folder. Once you have a stable set of parameters, you can set up your "definitive" task.

Thanks, Grover. I've tried that a number of times, to no avail. I see, however, that an update has become available since the last time I visited the home screen, so I've installed that and will try again, using a new backup task per Pat's suggestion. I'll post how it turns out in a few days (after I've accumulated enough backups to trigger cleanup).

My upgrade to build 6868 seems to have fixed things. I can now automatically: 1) do a complete backup; 2) delete excess backup sets; and 3) turn off the computer. I'm happy.

Jeff Davis wrote:

My upgrade to build 6868 seems to have fixed things. I can now automatically: 1) do a complete backup; 2) delete excess backup sets; and 3) turn off the computer. I'm happy.

Build 6868 is ATIH 2011, not 2012....

twokatmew wrote:
Build 6868 is ATIH 2011, not 2012....

I know. I was only going to upgrade to 2012 if I couldn't get this fixed in 2011.

Jeff Davis wrote:
twokatmew wrote:
Build 6868 is ATIH 2011, not 2012....

I know. I was only going to upgrade to 2012 if I couldn't get this fixed in 2011.

FWIW, I periodically have this problem and have observed it in both 2011 and 2012. The logs don't have enough detail to know what the problem is, and eventually it starts working again. Sometimes I have to turn off auto clean-up and reconfigure it