Continuing the discussion from Confused with prune retention policy:
Let’s take this part of the complex discussion into this separate topic:
Indeed, it would be good if @gchen could clarify.
I think we need to clarify what “independent” means here. Because if it means what you suggest here (that running multiple
keep options in one command is the same as running multiple individual commands after each other) then this actually means that the different time periods do not respect each others boundaries (as @towerbr suspects), which would mean that they very well may interfere (because they run independently).
However, such interference won’t happen in practice as long as your keep options always specify a lower snapshot frequency for older snapshots. For example,
-keep 7:30 -keep 1:14 should be fine, but not
-keep 1:30 -keep 7:14
If duplicacy doesn’t already throw a warning in the latter case, I think it should do so.