[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] --full-if-older-than 26W oddity
From: |
Kenneth Loafman |
Subject: |
Re: [Duplicity-talk] --full-if-older-than 26W oddity |
Date: |
Thu, 11 Dec 2008 10:06:55 -0600 |
User-agent: |
Thunderbird 2.0.0.18 (X11/20081125) |
Andrew Kohlsmith (lists) wrote:
> On December 11, 2008 10:16:31 am Kenneth Loafman wrote:
>>> duplicity --full-if-older-than 26W --archive-dir
>>> ${ARCHIVEDIR}/root --encrypt-key ${MIXDOWN_KEY} --encrypt-key
>>> ${ANDREW_KEY} --include /etc --include /usr/local/scripts --exclude '**'
>>> / file:///mnt/duplicity/media.mixdown.ca/root
>>>
>>> When I ran the backup last night, it said that the last incremental was
>>> done too long ago (Oct 31 2008) and that it was going to do a full
>>> backup.
>>>
>>> My question is why... The date on the server is correct, the timestamp on
>>> the incremental backups is fine... Am I specifying "26 weeks"
>>> incorrectly?
>> Was it that your last full was too long ago? That's what the intent of
>> the --full-if-older-than option means. When was the last full backup?
>
> Oct 31 2008 is not more than 26 weeks away from December 10, 2008. :-)
You are specifying 26 weeks correctly.
If your last *full* backup was on Oct 31 2008, then there is indeed a
problem. If your last incremental was on Oct 31 2008, then that does
not matter at all. The only date that matters is the date of the last
full backup.
...Ken
signature.asc
Description: OpenPGP digital signature