Hi, On 2017-04-22 03:17, Alexander Zangerl wrote: > On Thu, 20 Apr 2017 23:47:19 +0200, Maarten Aertsen writes: > >Using duplicity with a S3 remote for a while, until multiple backup > >chains exist. > > could you please provide the output of a collection-status, > 'multiple chains exist' is a bit too little information to debug.
I'm afraid I can't for exactly the same reason I think this is a bug: memory usage explodes, the machine locks up and I never get a result. This on a 1024MB vhost with 515MB free -/+ buffers/cache and 2GB nearly unused swap. > how often do you remove chains? Full backups happen every week, incrementals twice per day. Cleanup happens on S3 (duplicity has append-only rights to S3), with 90 day retention of full backups, 14 day retention of incrementals. > how many chains are there? I can make a count based on S3. There's 320 files, making up 8 chains, > how many incrementals per chain? Within the 14 day retention, there's a maximum of two chains with a week's worth of incrementals (2*7*2=28 increments). Because duplicity does not perform the cleanup, at some point the oldest chain breaks (when the first incremental gets deleted). The backups are very small, a full has ~42 volumes of 200MB = ~8.4G. Total size is ~76G. Workaround is to move the files to a separate dir to make them invisible for duplicity. > > * What exactly did you do (or not do) that was effective (or ineffective)? > >/usr/bin/duplicity full --s3-use-ia --asynchronous-upload --encrypt-key > ><KEYID> > > --encrypt-key <KEYID2> --include-filelist /etc/backup-targets / <AWSBUCKET> > > does your /etc/backup-targets exclude /proc, /sys and /dev? otherwise your > invocation as given here would attempt to back up everything, including > stuff like /dev/mem. No, /etc/backup-targets has "- /" as last line, and none of the mentioned paths is explicitly included in earlier lines. thanks, Maarten
