Thanks for the detail!
While @renestach is probably the expert on this, what I think what might be happening is you’re getting a run (like on 06/28) that is just a little bit later than the rest (like 05:00:04 not exactly at 05:00:00). This causes that run to roll over to a different retention “bucket” which makes it do things you don’t expect.
Are you able to check logs or emails of the other ones that got deleted unexpectedly and see if they also were “next to” a run that didn’t have an exact 05:00:00 time on it?
If you notice they all do, perhaps tweaking your retention policy to start with something like
1445m:U instead of
1D:U will give you a 5 minute buffer to ignore jobs that run a little late.
--full-results didn’t give what I was looking for so while we wait for renestach to hopefully have a chance to take a look at this we can try something else.
I tried running a backup using the “Commandline…” interface in the GUI and adding
--console-log-level=Information to the options which gave me the results below where I can see which backups would be deleted due to my retention rules (if I weren’t running
--dry-run-true), but not WHY they’re being deleted.
Backup started at 7/5/2018 2:17:28 PM
The operation Backup has started
Checking remote backup ...
Backend event: List - Started: ()
Listing remote folder ...
Backend event: List - Completed: (51 bytes)
Scanning local files ...
1 files need to be examined (0 bytes)
[Dryrun]: Would upload volume: duplicati-bffa2fab317b14ebbb4abf597bb566302.dblock.zip, size: 4.66 MB
[Dryrun]: Would upload volume: duplicati-ifb75b6f7315243cdb0c29690c05d5120.dindex.zip, size: 9.19 KB
3542 files need to be examined (153.10 MB)
[Dryrun]: Would upload volume: duplicati-20180705T191728Z.dlist.zip, size: 363.91 KB
Start checking if backups can be removed
Time frames and intervals pairs: 31.00:00:00 / 1.00:00:00, 730.00:00:00 / Keep all, Unlimited / Keep all
Backups to consider: 6/28/2018 10:23:27 AM, 6/26/2018 10:33:29 AM, 6/25/2018 9:28:54 AM, 6/25/2018 9:18:48 AM, 6/22/2018 2:06:29 PM, 6/22/2018 11:30:03 AM, 6/22/2018 10:48:58 AM, 6/20/2018 10:26:15 PM, 6/19/2018 11:55:18 AM, 6/19/2018 11:48:31 AM, 5/11/2018 2:51:47 PM, 5/11/2018 2:47:59 PM, 5/10/2018 3:29:51 PM, 4/10/2018 3:58:30 PM, 4/4/2018 2:36:51 PM, 4/4/2018 1:15:41 PM
Backups outside of all time frames and thus getting deleted:
------> All backups to delete: 6/25/2018 9:28:54 AM, 6/22/2018 2:06:29 PM, 6/22/2018 11:30:03 AM, 6/19/2018 11:55:18 AM
Deleting 4 remote fileset(s) ...
[Dryrun]: Would delete remote fileset: duplicati-20180619T165518Z.dlist.zip
[Dryrun]: Would delete remote fileset: duplicati-20180622T163003Z.dlist.zip
[Dryrun]: Would delete remote fileset: duplicati-20180622T190629Z.dlist.zip
[Dryrun]: Would delete remote fileset: duplicati-20180625T142854Z.dlist.zip
[Dryrun]: 4 remote fileset(s) would be deleted
[Dryrun]: Remove --dry-run to actually delete files
Compacting because there are 1 fully deletable volume(s)
[Dryrun]: Would delete remote file: duplicati-b206dbd683f4048b1a137c3804f27d9c1.dblock.zip, size: 3.94 MB
[Dryrun]: Would delete remote file: duplicati-ia98238a0dc404cb1b96b5c313a81abc4.dindex.zip, size: 9.75 KB
[Dryrun]: Would delete 2 files, which would reduce storage by 3.95 MB
[Dryrun]: Would upload verification file: duplicati-verification.json, size: 23.90 KB
Email sent successfully using server:
0 files need to be examined (0 bytes)
Duration of backup: 00:03:55
Remote files: 49
Remote size: 244.98 MB
Total remote quota: 195.54 GB
Available remote quota: 41.52 GB
Files added: 0
Files deleted: 0
Files changed: 92
Data uploaded: 0 bytes
Data downloaded: 0 bytes
Backup completed successfully!
Return code: 1