duplicity-team team mailing list archive

[edso <question207344@xxxxxxxxxxxxxxxxxxxxx>]

Question #207344 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/207344

    Status: Open => Answered

edso proposed the following answer:
On 31.08.2012 09:05, Paul Bernet wrote:
> New question #207344 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/207344
> 
> Hi,
> 
> I want to backup a Jackrabbit FileDataStore with duplicity and it works fine. However, the  "data store garbage collection function" of the FileDataStore touches the modified timestamp on all the files in the FileDataStore [1].
> This causes duplicity/rsync to backup unchanged files.
> 
> I tried the duplicity option --rsync-options [2] so the call in the log of the wrapper script [3] looks like this:
> duplicity 0.6.19 (May 22, 2012)
> Args: /usr/local/bin/duplicity -v6 --tempdir /var/tmp --archive-dir /var/duplicity_cache --rsync-options="--size-only" ….
> 
> I tried the --checksum option and even a falsified --xxx option, but duplicity/rsync seems to ignore this.

well, it sure does not. you simply fell victim of a common
misunderstanding: the --rsync-options does not influence duplicitys's
librsync behaviour but the one of the rsync backend.

> 
> -> How can I configure duplicity/rsync NOT to check on modified timestamps?
> 

while not an experienced python hacker i still took ten minutes to check
the duplicity sources and couldn't find a switch in there. in theory
this is possible for sure but it dfoes not seem to be implemented.

btw. why is Jackrabbit touching all the files if they did not change?
that pretty much confuses all backup software out there.


..ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.