Re: [Duplicity-talk] 0.5.06 "manifests not equal because different volume numbers" ??

[Kenneth Loafman]

Andrew Kohlsmith (lists) wrote:
> I'm running into an issue with duplicity on a new server, and I'm lost as to 
> how to fix it.  I'm running this command twice (for testing):
> 
> duplicity --full-if-older-than 26W --encrypt-key 
> 12345678 --archive-dir /var/duplicity/archive/plone --exclude 
> /home/plone/Plone-3.1/zinstance/var/filestorage/Data.fs /home/plone/ 
> file:///var/duplicity/foo/plone
> 
> The first time runs great, but the second time gives this error:
> 
> Manifests not equal because different volume numbers
> Fatal Error: Remote manifest does not match local one.  Either the remote 
> backup set or the local archive directory has been corrupted.
> Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 583, in ?
>     with_tempdir(main)
>   File "/usr/bin/duplicity", line 577, in with_tempdir
>     fn()
>   File "/usr/bin/duplicity", line 562, in main
>     check_last_manifest(col_stats) # not needed for full backup
>   File "/usr/bin/duplicity", line 497, in check_last_manifest
>     last_backup_set.check_manifests()
>   File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 137, 
> in check_manifests
>     log.ErrorCode.mismatched_manifests)
>   File "/usr/lib/python2.4/site-packages/duplicity/log.py", line 164, in 
> FatalError
>     sys.exit(code)
> SystemExit: 5
> 
> Can anyone point me in the right direction?

I've never seen this one.  It says that the number of volumes in one
manifest is different than the other.  I'm not able to reproduce this
one, so you're going to need to help... a couple of questions...

1) did you run both runs with --archive-dir?
2) were there two copies of duplicity running at the same time?
3) did the 1st run try a full backup and the 2nd one an incremental?
4) were there any error messages during either run?

...Ken

signature.asc
Description: OpenPGP digital signature