Fwd: duplicity including files in backup that have not changed?
Over the past several months I have slowly switched over about 600 machines from rdiff-backup to duplicity with an S3 back end at Soft Layer. Overall it has been great.
For some reason on four of my machines(all el5) incremental backups with duplicity sync about 1.2 million of 1.6 million files that I do not believe have changed. When I switch back to rdiff-backup the files do not get sync’d.
I can’t run duplicity currently as it uses about 8G of RAM and kills the machine, so I can’t do a verbose run to see exactly which files are changing. Would anyone have an idea as to a situation where duplicity would treat files as changed when rdiff-backup would not?
Another side effect of this is the memory footprint incremental backup duplicity process gets gigantic. I would expect it to store all files in the latest backup chain since the latest full, but it appears to read in all volumes from all chains? Here is a graph of the size of the duplicity memory footprint growing. Note full backups happened on the 1st/2nd and 15th/16th:
Re: Fwd: duplicity including files in backup that have not changed?
On 15.05.2017 23:57, Chris Newton via Duplicity-talk wrote:
> I can’t run duplicity currently as it uses about 8G of RAM and kills the
> machine, so I can’t do a verbose run to see exactly which files are
are you by any chance doing unencrypted/uncompressed backups? ..ede/duply.net