Regular Corruption Issues?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Regular Corruption Issues?

duplicity-talk mailing list
Hey all,

I've just started playing around with duplicity. Local file
destinations I've had no issues with - however, backing up to B2 I've
had some issues. I've backed up large folders, small folders, and
different folders (to different buckets), and it seems that within
every 2-3 incrementals I end up with corrupt sigchains, and have to do
the backup from scratch again.

This leads to increased storage costs on B2, so I'd like to avoid this
if I can (plus, it's annoying as I don't feel like it should be doing
this). Here is an output from a recent job log:

[root@mailhost mailcow-dockerized]# duplicity --encrypt-key $GPG-ID /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/maildomain.com par2+b2://b2-id:b2-key@b2-bucket/duplicity/docker-volumes/
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Thu Aug 24 16:23:03 2017
GnuPG passphrase:
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
No signatures found, switching to full backup.
--------------[ Backup Statistics ]--------------
StartTime 1503571852.19 (Thu Aug 24 20:20:52 2017)
EndTime 1503573433.99 (Thu Aug 24 20:47:13 2017)
ElapsedTime 1581.81 (26 minutes 21.81 seconds)
SourceFiles 177238
SourceFileSize 2143737375 (2.00 GB)
NewFiles 177238
NewFileSize 2143737375 (2.00 GB)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 177238
RawDeltaSize 2121254431 (1.98 GB)
TotalDestinationSizeChange 667281735 (636 MB)
Errors 0
-------------------------------------------------

[root@mailhost mailcow-dockerized]# duplicity --encrypt-key $GPG-ID /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/maildomain.com par2+b2://b2-id:b2-key@b2-bucket/duplicity/docker-volumes/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu Aug 24 20:20:50 2017
--------------[ Backup Statistics ]--------------
#####SNIP - SUCCESSFUL#####
-------------------------------------------------

[root@mailhost mailcow-dockerized]# duplicity --encrypt-key $GPG-ID /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/maildomain.com par2+b2://b2-id:b2-key@b2-bucket/duplicity/docker-volumes/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu Aug 24 20:20:50 2017
--------------[ Backup Statistics ]--------------
######SNIP - SUCCESSFUL#####
-------------------------------------------------

## Listed cache directory just to verify that cache directory existing correctly

[root@mailhost mailcow-dockerized]# ls ~/.cache/duplicity/
2ab8c5556869913fc7e155e72d27d713  e128840ffc2dd98aebc5a27f2c14fd4d

[root@mailhost mailcow-dockerized]# duplicity --encrypt-key $GPG-ID /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/maildomain.com par2+b2://b2-id:b2-key@b2-bucket/duplicity/docker-volumes/
Synchronizing remote metadata to local cache...
Deleting local /root/.cache/duplicity/e128840ffc2dd98aebc5a27f2c14fd4d/duplicity-full-signatures.20170824T105050Z.sigtar.gz (not authoritative at backend).
Deleting local /root/.cache/duplicity/e128840ffc2dd98aebc5a27f2c14fd4d/duplicity-full.20170824T105050Z.manifest (not authoritative at backend).
Deleting local /root/.cache/duplicity/e128840ffc2dd98aebc5a27f2c14fd4d/duplicity-inc.20170824T105050Z.to.20170824T114005Z.manifest (not authoritative at backend).
Deleting local /root/.cache/duplicity/e128840ffc2dd98aebc5a27f2c14fd4d/duplicity-new-signatures.20170824T105050Z.to.20170824T114005Z.sigtar.gz (not authoritative at backend).
Warning, found the following local orphaned signature file:
duplicity-new-signatures.20170824T114005Z.to.20170824T114833Z.sigtar.gz
Warning, found the following remote orphaned signature file:
duplicity-new-signatures.20170824T114005Z.to.20170824T114833Z.sigtar.gpg
Warning, found the following orphaned backup file:
[duplicity-inc.20170824T114005Z.to.20170824T114833Z.manifest.gpg, duplicity-inc.20170824T114005Z.to.20170824T114833Z.vol1.difftar.gpg]
Last full backup date: none
No signatures found, switching to full backup.


Here's where I cancelled, and decided to hit up the list. Any advice that can be offered would be much appreciated!

_______________________________________________
Duplicity-talk mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk