Duplicity fails to restore with --no-compression enabled: "No files found in archive"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm unable to complete a restore using the --no-compression option in 0.6.18 and 0.6.19:
duplicity full /opt/graphite/
The backup completes successfully:
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
--------------[ Backup Statistics ]--------------
StartTime 1343269272.86 (Wed Jul 25 21:21:12 2012)
EndTime 1343278162.25 (Wed Jul 25 23:49:22 2012)
ElapsedTime 8889.40 (2 hours 28 minutes 9.40 seconds)
SourceFiles 31128
SourceFileSize 173292409215 (161 GB)
NewFiles 31128
NewFileSize 173292409215 (161 GB)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 31128
RawDeltaSize 173291150126 (161 GB)
TotalDestinatio
Errors 0
-------
And the restore:
duplicity restore s3+http://
and result with -vinfo:
Using archive dir: /root/.
Using backup name: 9042287f5ee10d6
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Main action: restore
=======
duplicity 0.6.18 (February 29, 2012)
Args: /usr/bin/duplicity restore s3+http://
Linux graphite1 3.2.22-
/usr/bin/python 2.6.8 (unknown, Jun 29 2012, 06:50:56)
[GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
=======
Using temporary directory /tmp/duplicity-
Temp has 4699389952 available, backup will use approx 34078720.
Listing s3+http://
Local and Remote metadata are synchronized, no sync needed.
Listing s3+http://
Last full backup date: Wed Jul 25 21:21:12 2012
Downloading s3+http://
Deleting /tmp/duplicity-
Processed volume 1 of 179
Downloading s3+http://
No files found in archive - nothing restored.
I'm able to reproduce this with the file:// backend as well. The same backup/restore procedure performed without the --no-compression option works fine
Changed in duplicity: | |
status: | Confirmed → Fix Released |
I'm seeing the same behavior with 0.6.20.