Skip to main content

Problem "shrinking" a tibx file using "Cleaning up tibx backup versions manually"

Thread needs solution

I'm wondering if the following is a known issue:

If I select from the "recent" i.e. current backup, the dependant versions are not auto-selected.

If I select from the "older" groups then all versions are auto-selected and any version I de-select results in auto-de-selection of the entire group.

This means I am prevented from "shrinking" a tibx file.

0 Users found this helpful

Chris, welcome to these public User Forums.

Sorry but you are not understanding how incremental backup chains work if you are trying to select an individual file from the middle of the incremental chain!  If ATI allowed you to do this, then all the subsequent files in the chain would be rendered unusable, as the point about an incremental chain is that each file captures only the changes since the previous one was made.

Steve,thank you for your comment. I made the example screenshot "ATI cleanup 2020-03-14 083306.png" at the point when ALL versions are ticked for the chain 22/11/19-22/12/19.

  • If I clear the "tick" next to ANY dependant version then ALL the "ticks" vanish. If I then click again on ANY dependant version, the check-boxes for ALL versions get ticked automatically, not just the remaining dependants, which means I am prevented from deleting just a part of a chain along with its dependants.
  • This behaviour does not happen with the "Recent" chain at the top of the list, instead the version clicked gets a tick but none of the dependants get an automatic tick which, as you imply, should not be allowed.
  • Ticking versions of backups which use the old tib format still behave as expected.

Steve, thanks for putting so much effort into researching this. I guess I'll have to tweak my strategy so I don't end up with too many historical incremental versions which I can no longer "prune".