duplicity-team team mailing list archive

[edso <question212772@xxxxxxxxxxxxxxxxxxxxx>]

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

edso proposed the following answer:
On 06.11.2012 18:06, Keith Cornwell wrote:
> Question #212772 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/212772
> 
> Keith Cornwell posted a new comment:
> Upgraded to 0.6.20
> 
> Before running another incremental. I ran a cleanup.
> duplicity cleanup --force file:///mnt/external/backup-Shared
> 
> Then I ran this:
> duplicity --dry-run --verbosity debug --name opus-shared --volsize 100 --asynchronous-upload /filestore01/Shared file:///mnt/external/backup-Shared
> 
> But this time it gets confused about the full that it's working against and decides to do another full.
> No backup chains with active signatures found
> No orphaned or incomplete backup sets found.
> No signatures found, switching to full backup.
> 
> Here's the pastebin of the log file:
> http://paste.ubuntu.com/1337731/
> 

the below could explain why it ignores your previous full...

6183 File duplicity-full-signatures.20121026T211319Z.sigtar.gpg is not part of a known set; creating new set
6184 Ignoring file (rejected by backup set) 'duplicity-full-signatures.20121026T211319Z.sigtar.gpg'

anyway, it is not guaranteed that newer version /always/ work perfectly
with backup sets created with previous versions. the easiest way out of
it is probably:

- install the duplicity version used previously in parallel (see here under TIP http://duply.net/?title=Duply-documentation )
- check that your old backup chain verify's ok with it
- do a new full with 0.6.20 to a new repository folder
- do incrementals on it and observe if the error persists

if it does, sent the two outputs i mentioned above... ede/duply.net

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