{"action":"opened","issue":{"url":"https://api.github.com/repos/duplicati/duplicati/issues/1570","repository_url":"https://api.github.com/repos/duplicati/duplicati","labels_url":"https://api.github.com/repos/duplicati/duplicati/issues/1570/labels{/name}","comments_url":"https://api.github.com/repos/duplicati/duplicati/issues/1570/comments","events_url":"https://api.github.com/repos/duplicati/duplicati/issues/1570/events","html_url":"https://github.com/duplicati/duplicati/issues/1570","id":131860778,"number":1570,"title":"Duplicati2 dlists uploaded \"rarely\" - would --maxtime-between-dlist-put be possible?","user":{"login":"hcjehg","id":12269445,"avatar_url":"https://avatars.githubusercontent.com/u/12269445?v=3","gravatar_id":"","url":"https://api.github.com/users/hcjehg","html_url":"https://github.com/hcjehg","followers_url":"https://api.github.com/users/hcjehg/followers","following_url":"https://api.github.com/users/hcjehg/following{/other_user}","gists_url":"https://api.github.com/users/hcjehg/gists{/gist_id}","starred_url":"https://api.github.com/users/hcjehg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hcjehg/subscriptions","organizations_url":"https://api.github.com/users/hcjehg/orgs","repos_url":"https://api.github.com/users/hcjehg/repos","events_url":"https://api.github.com/users/hcjehg/events{/privacy}","received_events_url":"https://api.github.com/users/hcjehg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-06T14:30:18Z","updated_at":"2016-02-06T14:30:18Z","closed_at":null,"body":"I am experimenting with large backup sets (>5TB). It seems that the file lists are uploaded only after a complete full/incremental backup completes.\r\n\r\nI have the problem that the initial backup takes days - which is normal - but if there is a small hickup during this period, duplicati comes back and says nof ile lists in remote, and then starts over checking all the files from adam and eva, and since the metadata have changed the files are re-uploaded...\r\n\r\n2/6/2016, 3:06:47 PM Checking file for changes /volume1/data/technical/sots/resources/takes/00001834393/00001834393_0768x0576.m4v, new: True, timestamp changed: True, size changed: True, metadatachanged: True, 02/10/2014 11:30:35 vs 01/01/0001 00:00:00\r\n\r\nThis particular file has been uploaded many many times (with no change in metadata)\r\n\r\nThe problem seems to be that file lists are only uploaded at the end of a complete run... Is that correct?\r\n\r\nIf it is, would it be possible to make a parameter similar to \r\n\r\n--maxtime-between-dlist-put = 10m    or \r\n--maxtime-between-dlist-put = 1h or\r\n--maxminutes-between-dlist-put = 60\r\n\r\nTo make sure that already uploaded files are remembered at the far end. \r\n\r\nI guess it is fair enough to make dlists contain at least one complete file, so that if it takes more than --maxtime-between-dlist-put then it would only be uploaded once at least one file is complete...\r\n\r\nWhat do you think ?\r\n\r\nHC"}}