duplicity-team team mailing list archive

[trevj <question677428@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Answered => Open

trevj is still having a problem:
if you can manually extract _all_ files then duplicity should as well.
> btw. the "official" disaster recovery document resides here
> https://wiki.gnome.org/Apps/DejaDup/Help/Restore/WorstCase#Restoring_by_Hand
> but you seem to have found it already.
Yes, that's where my ideas came from.
>
> 1.
> first of all, can you show a 'df -h' that show there is ample space in your /tmp folder?
jtrevorj@jtrevorj-G31M-S2L:/tmp$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           394M  1.7M  392M   1% /run
/dev/sda5       183G   73G  101G  42% /
tmpfs           2.0G   55M  1.9G   3% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/loop0      3.8M  3.8M     0 100% /snap/gnome-system-monitor/51
/dev/loop1       35M   35M     0 100% /snap/gtk-common-themes/319
/dev/loop2       87M   87M     0 100% /snap/core/4917
/dev/loop3       35M   35M     0 100% /snap/gtk-common-themes/818
/dev/loop4      3.8M  3.8M     0 100% /snap/gnome-system-monitor/57
/dev/loop5      2.4M  2.4M     0 100% /snap/gnome-calculator/180
/dev/loop6       15M   15M     0 100% /snap/gnome-logs/37
/dev/loop7       90M   90M     0 100% /snap/core/6130
/dev/loop8       13M   13M     0 100% /snap/gnome-characters/139
/dev/loop10      13M   13M     0 100% /snap/gnome-characters/103
/dev/loop11      15M   15M     0 100% /snap/gnome-logs/45
/dev/loop12     2.3M  2.3M     0 100% /snap/gnome-calculator/260
/dev/loop13     141M  141M     0 100% /snap/gnome-3-26-1604/70
/dev/loop9      141M  141M     0 100% /snap/gnome-3-26-1604/74
tmpfs           394M   28K  394M   1% /run/user/121
tmpfs           394M   19M  376M   5% /run/user/1000
jtrevorj@jtrevorj-G31M-S2L:/tmp$


>
> 2.
> run duplicity w/ the backup data copied from another file system (just to rule out read errors)
I have copies the files to my main hard disk to /home/jtrevorj/temp
>
> 3.
> if the error persists run it w/ max. verbosity (-v9) and '--ignore-errors' and redirect the output to a log file. here's the description from the man page
jtrevorj@jtrevorj-G31M-S2L:~/temp$ duplicity -v9 --ignore-errors restore 
file:///home/jtrevorj/temp/trevorj-G31M-S2L /home/jtrevorj/Restore2 > 
duperrors.txt

Failed to read /tmp/duplicity-WSmXO_-tempdir/mktemp-GKr0Dn-16: (<type 
'exceptions.IOError'>, IOError('Not a gzipped file',), <traceback object 
at 0x7fc666926170>)

jtrevorj@jtrevorj-G31M-S2L:~/temp$

duperrors.txt

Running in 'ignore errors' mode due to --ignore-errors; please 
re-consider if this was not intended
Using archive dir: 
/home/jtrevorj/.cache/duplicity/84c5f4bc8fe1f59cf7352bf50ec67f1a
Using backup name: 84c5f4bc8fe1f59cf7352bf50ec67f1a
GPG binary is gpg, version 2.2.4
Import of duplicity.backends.acdclibackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Main action: restore
Acquiring lockfile 
/home/jtrevorj/.cache/duplicity/84c5f4bc8fe1f59cf7352bf50ec67f1a/lockfile
================================================================================
duplicity 0.7.17 (February 26, 2018)
Args: /usr/bin/duplicity -v9 --ignore-errors restore 
file:///home/jtrevorj/temp/trevorj-G31M-S2L /home/jtrevorj/Restore2
Linux jtrevorj-G31M-S2L 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 
14:45:28 UTC 2018 x86_64 x86_64
/usr/bin/python 2.7.15rc1 (default, Nov 12 2018, 14:31:15)
[GCC 7.3.0]
================================================================================
Using temporary directory /tmp/duplicity-WSmXO_-tempdir
Registering (mkstemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mkstemp-iH38YC-1
Temp has 49942343680 available, backup will use approx 272629760.
Synchronising remote metadata to local cache...
Copying duplicity-full-signatures.20181208T043900Z.sigtar.gz to local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-H19Vek-2
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-U0SOzI-3
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-H19Vek-2
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-H19Vek-2
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-U0SOzI-3
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-U0SOzI-3
Copying duplicity-full.20181208T043900Z.manifest to local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-6d2n3g-4
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-rxAlYI-5
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-6d2n3g-4
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-6d2n3g-4
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-rxAlYI-5
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-rxAlYI-5
Copying duplicity-inc.20181208T043900Z.to.20181213T043719Z.manifest to 
local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-XpvLMk-6
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-4aqMHo-7
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-XpvLMk-6
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-XpvLMk-6
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-4aqMHo-7
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-4aqMHo-7
Copying duplicity-inc.20181213T043719Z.to.20181215T230125Z.manifest to 
local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-PPUbG0-8
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-IbwhGq-9
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-PPUbG0-8
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-PPUbG0-8
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-IbwhGq-9
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-IbwhGq-9
Copying duplicity-inc.20181215T230125Z.to.20181220T034556Z.manifest to 
local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-1g956a-10
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-ApEIHm-11
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-1g956a-10
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-1g956a-10
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-ApEIHm-11
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-ApEIHm-11
Copying duplicity-inc.20181220T034556Z.to.20181221T034229Z.manifest to 
local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-Jgmkmm-12
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-onGpRf-13
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-Jgmkmm-12
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-Jgmkmm-12
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-onGpRf-13
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-onGpRf-13
Copying 
duplicity-new-signatures.20181208T043900Z.to.20181213T043719Z.sigtar.gz 
to local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-iAHAjw-14
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-efdt95-15
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-iAHAjw-14
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-iAHAjw-14
Deleting /tmp/duplicity-WSmXO_-tempdir/mktemp-efdt95-15
Forgetting temporary file /tmp/duplicity-WSmXO_-tempdir/mktemp-efdt95-15
Copying 
duplicity-new-signatures.20181213T043719Z.to.20181215T230125Z.sigtar.gz 
to local cache.
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-GKr0Dn-16
Registering (mktemp) temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-oqo2mc-17
Releasing lockfile 
/home/jtrevorj/.cache/duplicity/84c5f4bc8fe1f59cf7352bf50ec67f1a/lockfile
Removing still remembered temporary file 
/tmp/duplicity-WSmXO_-tempdir/mkstemp-iH38YC-1
Removing still remembered temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-oqo2mc-17
Removing still remembered temporary file 
/tmp/duplicity-WSmXO_-tempdir/mktemp-GKr0Dn-16
Releasing lockfile 
/home/jtrevorj/.cache/duplicity/84c5f4bc8fe1f59cf7352bf50ec67f1a/lockfile
Releasing lockfile 
/home/jtrevorj/.cache/duplicity/84c5f4bc8fe1f59cf7352bf50ec67f1a/lockfile


> "
> Try to ignore certain errors if they happen. This option is only intended to allow the restoration of a backup in the face of certain problems that would otherwise cause the backup to fail. It is not ever recommended to use this option unless you have a situation where you are trying to restore from backup and it is failing because of an issue which you want duplicity to ignore. Even then, depending on the issue, this option may not have an effect.
> Please note that while ignored errors will be logged, there will be no summary at the end of the operation to tell you what was ignored, if anything. If this is used for emergency restoration of data, it is recommended that you run the backup in such a way that you can revisit the backup log (look for lines containing the string IGNORED_ERROR).
>
> If you ever have to use this option for reasons that are not understood or understood but not your own responsibility, please contact duplicity maintainers. The need to use this option under production circumstances would normally be considered a bug.
> "
>
> might be that just one volume is corrupted.
>
> 4.
> possible but unlikely. we had a bug years ago where '--no-compression' didn't work.
>    https://serverfault.com/questions/726525/cannot-restore-duplicity-backup
> but your case looks different.
>
> ..ede/duply.net
>

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.