I took the liberty of tagging Revise default backup filter UI · Issue #3030 · duplicati/duplicati · GitHub to the experimental milestone because the filter is much too strict now.
Besides that I think we’re looking at:
- The issue with
--keep-timeand--retention-policythrowing not-that-user friendlywarningserrors after upgrade (because they’re now mutually exclusive) Release: 2.0.2.18 (Canary) 2018-02-11 - #11 by Tapio - More testing of
--retention-policyand preferably some Unit tests to verify edge cases etc as it’s hard to test many different cases with a feature that depends on time passing
- Problem selecting “Smart backup retention” in the Web UI "Smart backup retention" causes error: Retention value must be more than 5 minutes · Issue #3010 · duplicati/duplicati · GitHub
Additionally, @kees-z and I were discussing two alterations on --retention-policy that I think would make sense to add before retention policy was released to everyone to avoid confusion if added later. The first being a semantic U notation for unlimited (U:1M instead of writing 200Y:1M and 1W:U instead of 1W:0s). And the second being a K notation for keep as there are some things you can’t do like 1M:1D without risking ending up with just a single backup if your machine is offline for longer than a month. New retention policy deletes old backups in a smart way - #51 by kees-z
And we should have a couple of people running windows try and replicate the above problem with Duplicati Server not upgrading when using the windows installer. Not worth much pushing updates if no one gets them