Remove older than

Registered by Philippe Delodder on 2009-10-05

Implement: "--remove-older-than" time (check at startup or do when called backup ?)

Blueprint information

Status:
Not started
Approver:
None
Priority:
High
Drafter:
Philippe Delodder
Direction:
Needs approval
Assignee:
Rob Oakes
Definition:
Discussion
Series goal:
Accepted for 0.5
Implementation:
Unknown
Milestone target:
milestone icon 0.5

Related branches

Sprints

Whiteboard

Part of the auto-remove functions:

(% Robert Oakes %)
I think we need to be careful with this particular flag and should keep it completely separate from backup operations or startup. In my mind, it makes the most sense to include it into it's own operation. I was planning on it living in the "autoremove" group of functions, along with combining of snapshots and deleting of backup sets. It should also run on its own batch process, that can also be scheduled separately (or offer an option so that it can run at the same time as the batch backup operation; this second option would be my preference). There is already a dedicated button in the Gui for running it. Because it meshes with the combination of snapshots, I would prefer to see this
targeted to the 0.3 series rather than the 0.4 release.

(% Philippe Delodder %)
in the duplicity-bin i have found code easy to figure out

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.