-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

 status confirmed
 importance medium
 done
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmHRQACgkQH1G0ZBEH
M/E/AAf+MZaZWPdkBWLx6pZV/wxe6uj8ONurmdDQokXiXWyCflydf9gJxCUX1FKb
M51L4nlApghWR9uYf5lX0JYb8oaSsspIu8JMz5IS/7l29MeGS6b0wt0shPmQM6fY
c2gcLdq9cbuLGw98ZonZf8Q2hCfYjtBI4SL2VxWSXZ3mcEWY4YP140iv053DmLnp
BFtdQpgFX+1V5a7TC5B8UwzQ+i6eW7B7OIUM2J4KJrVcqdp9AOsYkWXKfiNVVCjj
0cB3PE4jsk/S+Q4DvJJR4A8FE7uJnfZGv0r01ugC0JMcxbRqOsOnv3VfNHKpPvCT
PwsSlp9CfJKLto64SymqJU3SWIUTWw==
=CdqP
-----END PGP SIGNATURE-----


** Changed in: duplicity
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/676042

Title:
  duplicity falsely reports succeeded backup, empty manifest file

Status in Duplicity:
  Confirmed
Status in duplicity package in Ubuntu:
  New

Bug description:
  duplicity version duplicity 0.6.09
  Python 2.5.2
  Distributor ID:       Debian
  Description:  Debian GNU/Linux 5.0.6 (lenny)
  Release:      5.0.6
  Codename:     lenny

  ==backup log snip==
  ionice -c 3 nice -n 9 duplicity incremental --full-if-older-than 2W 
--asynchronous-upload --no-encryption --asynchronous-upload --no-encryption 
--exclude '/tmp/**' --exclude '/proc/**' --exclude '/dev/**' --exclude 
'/sys/**' --exclude '/root/.cache/**' --exclude '/var/cache/duplicity/**' 
--exclude '/var/marsnet/duplicity/**' --exclude '/var/alternc/mnt/**' --exclude 
'/var/lib/mysql/**' --exclude '/var/alternc/db/**' --exclude 
'/var/log/mysql/**' / ssh://backup@mybckhost//opt/marsnet/backups/
  Local and Remote metadata are synchronized, no sync needed.
  Last full backup date: Thu Oct 28 01:13:25 2010
  Last full backup is too old, forcing full backup
  --------------[ Backup Statistics ]--------------
  StartTime 1289607215.28 (Sat Nov 13 01:13:35 2010)
  EndTime 1289636885.88 (Sat Nov 13 09:28:05 2010)
  ElapsedTime 29670.59 (8 hours 14 minutes 30.59 seconds)
  SourceFiles 1730868
  SourceFileSize 106161258939 (98.9 GB)
  NewFiles 1730868
  NewFileSize 106161244989 (98.9 GB)
  DeletedFiles 0
  ChangedFiles 0
  ChangedFileSize 0 (0 bytes)
  ChangedDeltaSize 0 (0 bytes)
  DeltaEntries 1730868
  RawDeltaSize 105419449446 (98.2 GB)
  TotalDestinationSizeChange 65491887291 (61.0 GB)
  Errors 0
  -------------------------------------------------

  ++ hostname --fqdn
  + ionice -c 3 nice -n 9 duplicity remove-all-but-n-full 1 --force 
--no-encryption ssh://backup@mybckhost//opt/marsnet/backups/
  Local and Remote metadata are synchronized, no sync needed.
  Last full backup date: Sat Nov 13 01:13:30 2010
  Deleting backup set at time:
  Thu Oct 28 01:13:25 2010
  Deleting this file from backend:
  duplicity-full-signatures.20101027T231325Z.sigtar.gz
  ==end snip==

  This is the log from the backup that failed. Ihave conditional execution so 
backups aren't removed if duplicity fails. In this case there was no error, but 
I found an empty manifest file in the destination directory. Sorry, i don't use 
extra verbose output in my backup scripts.
  All the restore scripts fail silently: they see the archive as empty, this 
could be the reason why duplicity reported success on exit?
  (very annoying, i just had to restore a file, i'm trying to recover at least 
a part of it using simple gunzip and tar..)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/676042/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to