"Restore" gives the following:Failed to read /tmp/duplicity-Rtd2wO-tempdir/mktemp-67n08q-1. Can I recover any of my data?
I backed-up my home folder with Ubuntu "Backup" prior to re-installing Ubuntu18.04.1. After installation, attempting to restore my data gave the following:
Failed to read /tmp/duplicity-
I have 4 timed backups on the back-up disk and all gave the same error. Is there any way that I could restore at least some of my folder, or have I destroyed my system?
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Duplicity Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
|
Revision history for this message
|
#1 |
On 10.01.2019 07:28, trevj wrote:
> New question #677428 on Duplicity:
> https:/
>
> I backed-up my home folder with Ubuntu "Backup" prior to re-installing Ubuntu18.04.1. After installation, attempting to restore my data gave the following:
>
> Failed to read /tmp/duplicity-
>
> I have 4 timed backups on the back-up disk and all gave the same error. Is there any way that I could restore at least some of my folder, or have I destroyed my system?
>
trevj,
please provide
1.
the full command you use to run duplicity
2.
what is your duplicity version?
3.
ideally run duplicity with max. verbosity '-v9' and provide the complete resulting terminal output. maybe by redirecting it to file 'command > /tmp/out.txt 2>1'
and provide it via pastebin or some download service.
..ede/duply.net
|
Revision history for this message
|
#2 |
Thank you for your prompt reply my answers follow your questions:
On 10/1/19 10:13 pm, edso wrote:
> Your question #677428 on Duplicity changed:
> https:/
>
> Status: Open => Answered
>
> edso proposed the following answer:
> On 10.01.2019 07:28, trevj wrote:
>> New question #677428 on Duplicity:
>> https:/
>>
>> I backed-up my home folder with Ubuntu "Backup" prior to re-installing Ubuntu18.04.1. After installation, attempting to restore my data gave the following:
>>
>> Failed to read /tmp/duplicity-
>>
>> I have 4 timed backups on the back-up disk and all gave the same error. Is there any way that I could restore at least some of my folder, or have I destroyed my system?
>>
> trevj,
>
> please provide
>
> 1.
> the full command you use to run duplicity
It was first run from Deja-dup but see the answer to question 3
>
> 2.
> what is your duplicity version?
Duplicity 0.7.17
>
> 3.
> ideally run duplicity with max. verbosity '-v9' and provide the complete resulting terminal output. maybe by redirecting it to file 'command > /tmp/out.txt 2>1'
> and provide it via pastebin or some download service.
The output below was cut and pasted from my terminal:
jtrevorj@
file://
Using archive dir:
/home/jtrevorj/
Using backup name: 2605f0dbc556032
GPG binary is gpg, version 2.2.4
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.
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
Acquiring lockfile
/home/jtrevorj/
=======
duplicity 0.7.17 (February 26, 2018)
Args: /usr/bin/duplicity -v9 restore
file://
Linux jtrevorj-G31M-S2L 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17
15:39:52 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-
Registering (mkstemp) temporary file
/tmp/duplicity-
Temp has 176266465280 available, backup will use approx 272629760.
Synchronising remote metadata to local cache...
Copying
duplicity-
to local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Failed to read /tmp/duplicity-
'exceptions.
at 0x7f324de01320>)
Releasing lockfile
/home/jtrevorj/
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
Releasing lockfile
/home/jtrevorj/
jtrevorj@
>
> ..ede/duply.net
>
|
Revision history for this message
|
#3 |
On 10.01.2019 23:32, trevj wrote:
> Question #677428 on Duplicity changed:
> https:/
>
> Status: Answered => Open
>
> trevj is still having a problem:
> Thank you for your prompt reply my answers follow your questions:
>
> On 10/1/19 10:13 pm, edso wrote:
>> Your question #677428 on Duplicity changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> edso proposed the following answer:
>> On 10.01.2019 07:28, trevj wrote:
>>> New question #677428 on Duplicity:
>>> https:/
>>>
>>> I backed-up my home folder with Ubuntu "Backup" prior to re-installing Ubuntu18.04.1. After installation, attempting to restore my data gave the following:
>>>
>>> Failed to read /tmp/duplicity-
>>>
>>> I have 4 timed backups on the back-up disk and all gave the same error. Is there any way that I could restore at least some of my folder, or have I destroyed my system?
>>>
>> trevj,
>>
>> please provide
>>
>> 1.
>> the full command you use to run duplicity
> It was first run from Deja-dup but see the answer to question 3
>>
>> 2.
>> what is your duplicity version?
> Duplicity 0.7.17
>>
>> 3.
>> ideally run duplicity with max. verbosity '-v9' and provide the complete resulting terminal output. maybe by redirecting it to file 'command > /tmp/out.txt 2>1'
>> and provide it via pastebin or some download service.
>
> The output below was cut and pasted from my terminal:
>
>
> jtrevorj@
> file://
> Using archive dir:
> /home/jtrevorj/
> Using backup name: 2605f0dbc556032
> GPG binary is gpg, version 2.2.4
> 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.
> 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
> Acquiring lockfile
> /home/jtrevorj/
> =======
> duplicity 0.7.17 (February 26, 2018)
> Args: /usr/bin/duplicity -v9 restore
> file://
> Linux jtrevorj-G31M-S2L 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17
> 15:39:52 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-
> Registering (mkstemp) temporary file
> /tmp/duplicity-
> Temp has 176266465280 available, backup will use approx 272629760.
> Synchronising remote metadata to local cache...
> Copying
> duplicity-
> to local cache.
> Registering (mktemp) temporary file
> /tmp/duplicity-
> Registering (mktemp) temporary file
> /tmp/duplicity-
> Failed to read /tmp/duplicity-
> 'exceptions.
> at 0x7f324de01320>)
> Releasing lockfile
> /home/jtrevorj/
> Removing still remembered temporary file
> /tmp/duplicity-
> Removing still remembered temporary file
> /tmp/duplicity-
> Removing still remembered temporary file
> /tmp/duplicity-
> Releasing lockfile
> /home/jtrevorj/
> Releasing lockfile
> /home/jtrevorj/
> jtrevorj@
>
Trevj,
this looks incomplete. it lacks the list of files on your backend as well as detected backup chains.
please run and post a
duplicity -v collection-status ...
..ede/duply.net
|
Revision history for this message
|
#4 |
On 11/1/19 9:13 pm, edso wrote:
> Your question #677428 on Duplicity changed:
> https:/
>
> Status: Open => Answered
>
> edso proposed the following answer:
> On 10.01.2019 23:32, trevj wrote:
>> Question #677428 on Duplicity changed:
>> https:/
>>
>> Status: Answered => Open
>>
>> trevj is still having a problem:
>> Thank you for your prompt reply my answers follow your questions:
>>
>> On 10/1/19 10:13 pm, edso wrote:
>>> Your question #677428 on Duplicity changed:
>>> https:/
>>>
>>> Status: Open => Answered
>>>
>>> edso proposed the following answer:
>>> On 10.01.2019 07:28, trevj wrote:
>>>> New question #677428 on Duplicity:
>>>> https:/
>>>>
>>>> I backed-up my home folder with Ubuntu "Backup" prior to re-installing Ubuntu18.04.1. After installation, attempting to restore my data gave the following:
>>>>
>>>> Failed to read /tmp/duplicity-
>>>>
>>>> I have 4 timed backups on the back-up disk and all gave the same error. Is there any way that I could restore at least some of my folder, or have I destroyed my system?
>>>>
>>> trevj,
>>>
>>> please provide
>>>
>>> 1.
>>> the full command you use to run duplicity
>> It was first run from Deja-dup but see the answer to question 3
>>> 2.
>>> what is your duplicity version?
>> Duplicity 0.7.17
>>> 3.
>>> ideally run duplicity with max. verbosity '-v9' and provide the complete resulting terminal output. maybe by redirecting it to file 'command > /tmp/out.txt 2>1'
>>> and provide it via pastebin or some download service.
>> The output below was cut and pasted from my terminal:
>>
>>
>> jtrevorj@
>> file://
>> Using archive dir:
>> /home/jtrevorj/
>> Using backup name: 2605f0dbc556032
>> GPG binary is gpg, version 2.2.4
>> 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.
>> 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
>> Acquiring lockfile
>> /home/jtrevorj/
>> =======
>> duplicity 0.7.17 (February 26, 2018)
>> Args: /usr/bin/duplicity -v9 restore
>> file://
>> Linux jtrevorj-G31M-S2L 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17
>> 15:39:52 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-
>> Registering (mkstemp) temporary file
>> /tmp/duplicity-
>> Temp has 176266465280 available, backup will use approx 272629760.
>> Synchronising remote metadata to local cache...
>> Copying
>> duplicity-
>> to local cache.
>> Registering (mktemp) temporary file
>> /tmp/duplicity-
>> Registering (mktemp) temporary file
>> /tmp/duplicity-
>> Failed to read /tmp/duplicity-
>> 'exceptions.
>> at 0x7f324de01320>)
>> Releasing lockfile
>> /home/jtrevorj/
>> Removing still remembered temporary file
>> /tmp/duplicity-
>> Removing still remembered temporary file
>> /tmp/duplicity-
>> Removing still remembered temporary file
>> /tmp/duplicity-
>> Releasing lockfile
>> /home/jtrevorj/
>> Releasing lockfile
>> /home/jtrevorj/
>> jtrevorj@
>>
> Trevj,
>
> this looks incomplete. it lacks the list of files on your backend as well as detected backup chains.
> please run and post a
>
> duplicity -v collection-status ...
>
> ..ede/duply.net
>
Edso
I ran the above command with a verbosity level 9 which produced a very
detailed output. Rather than append it to this e-mail I have attached a
text copy; "collection-
trevj
|
Revision history for this message
|
#5 |
> Trevj,
>
> this looks incomplete. it lacks the list of files on your backend as well as detected backup chains.
> please run and post a
>
> duplicity -v collection-status ...
>
> ..ede/duply.net
>
I'm not sure the original attachment survived transmission, so here's
attempt 2:
jtrevorj@
file://
Using archive dir:
/home/jtrevorj/
Using backup name: 2605f0dbc556032
GPG binary is gpg, version 2.2.4
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.
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: collection-status
Acquiring lockfile
/home/jtrevorj/
=======
duplicity 0.7.17 (February 26, 2018)
Args: /usr/bin/duplicity -v9 collection-status
file://
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]
=======
1116 files exist on backend
0 files exist in cache
Extracting backup chains from list of files:
[u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
u'duplicity-
File duplicity-
a known set; creating new set
Ignoring file (rejected by backup set)
'duplicity-
File duplicity-
set; creating new set
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
part of a known set; creating new set
File duplicity-
is part of known set
File duplicity-
part of a known set; creating new set
File duplicity-
is part of known set
File duplicity-
is part of known set
File duplicity-
is part of known set
File duplicity-
is part of known set
File duplicity-
is part of known set
File duplicity-
is part of known set
File duplicity-
is part of known set
File duplicity-
part of a known set; creating new set
File duplicity-
is part of known set
File duplicity-
part of a known set; creating new set
File duplicity-
is part of known set
File
duplicity-
is not part of a known set; creating new set
Ignoring file (rejected by backup set)
'duplicity-
File
duplicity-
is not part of a known set; creating new set
Ignoring file (rejected by backup set)
'duplicity-
File
duplicity-
is not part of a known set; creating new set
Ignoring file (rejected by backup set)
'duplicity-
File
duplicity-
is not part of a known set; creating new set
Ignoring file (rejected by backup set)
'duplicity-
Found backup chain [Sat Dec 8 15:39:00 2018]-[Sat Dec 8 15:39:00 2018]
Added incremental Backupset (start_time: Sat Dec 8 15:39:00 2018 /
end_time: Thu Dec 13 15:37:19 2018)
Added set Thu Dec 13 15:37:19 2018 to pre-existing chain [Sat Dec 8
15:39:00 2018]-[Thu Dec 13 15:37:19 2018]
Added incremental Backupset (start_time: Thu Dec 13 15:37:19 2018 /
end_time: Sun Dec 16 10:01:25 2018)
Added set Sun Dec 16 10:01:25 2018 to pre-existing chain [Sat Dec 8
15:39:00 2018]-[Sun Dec 16 10:01:25 2018]
Added incremental Backupset (start_time: Sun Dec 16 10:01:25 2018 /
end_time: Thu Dec 20 14:45:56 2018)
Added set Thu Dec 20 14:45:56 2018 to pre-existing chain [Sat Dec 8
15:39:00 2018]-[Thu Dec 20 14:45:56 2018]
Added incremental Backupset (start_time: Thu Dec 20 14:45:56 2018 /
end_time: Fri Dec 21 14:42:29 2018)
Added set Fri Dec 21 14:42:29 2018 to pre-existing chain [Sat Dec 8
15:39:00 2018]-[Fri Dec 21 14:42:29 2018]
Last full backup date: Sat Dec 8 15:39:00 2018
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir:
/home/jtrevorj/
Found 0 secondary backup chains.
Found primary backup chain with matching signature chain:
-------
Chain start time: Sat Dec 8 15:39:00 2018
Chain end time: Fri Dec 21 14:42:29 2018
Number of contained backup sets: 5
Total number of contained volumes: 1106
Type of backup set: Time: Num volumes:
-------
No orphaned or incomplete backup sets found.
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir:
/home/jtrevorj/
Found 0 secondary backup chains.
Found primary backup chain with matching signature chain:
-------
Chain start time: Sat Dec 8 15:39:00 2018
Chain end time: Fri Dec 21 14:42:29 2018
Number of contained backup sets: 5
Total number of contained volumes: 1106
Type of backup set: Time: Num volumes:
-------
No orphaned or incomplete backup sets found.
Releasing lockfile
/home/jtrevorj/
Using temporary directory /tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
jtrevorj@
|
Revision history for this message
|
#6 |
Umm, the message "Failed to read" appeared on the first listing, not on the second. I'd suggest downloading duplicity-
$ gzip -t duplicity-
Post the output here.
|
Revision history for this message
|
#7 |
On 17/1/19 2:57 am, Kenneth Loafman wrote:
> Your question #677428 on Duplicity changed:
> https:/
>
> Status: Open => Needs information
>
> Kenneth Loafman requested more information:
> Umm, the message "Failed to read" appeared on the first listing, not on
> the second. I'd suggest downloading duplicity-new-
> signatures.
> location and run:
>
> $ gzip -t duplicity-new-
> signatures.
>
> Post the output here.
>
I got no meaningful output kKenneth
jtrevorj@
duplicity-
jtrevorj@
duplicity-
jtrevorj@
|
Revision history for this message
|
#8 |
On 17/1/19 3:08 pm, trevj wrote:
> Your question #677428 on Duplicity changed:
> https:/
>
> Status: Needs information => Open
>
> You gave more information on the question:
>
> On 17/1/19 2:57 am, Kenneth Loafman wrote:
>> Your question #677428 on Duplicity changed:
>> https:/
>>
>> Status: Open => Needs information
>>
>> Kenneth Loafman requested more information:
>> Umm, the message "Failed to read" appeared on the first listing, not on
>> the second. I'd suggest downloading duplicity-new-
>> signatures.
>> location and run:
>>
>> $ gzip -t duplicity-new-
>> signatures.
>>
>> Post the output here.
>>
> I got no meaningful output kKenneth
>
> jtrevorj@
> duplicity-
> jtrevorj@
> duplicity-
> jtrevorj@
>
Kenneth if I use "gzip -tv etc" it appends "OK" to the output. Helpful?
|
Revision history for this message
|
#9 |
Have you retried the recovery? Does it still produce the same error?
On Wed, Jan 16, 2019 at 10:37 PM trevj <email address hidden>
wrote:
> Question #677428 on Duplicity changed:
> https:/
>
> trevj gave more information on the question:
>
> On 17/1/19 3:08 pm, trevj wrote:
> > Your question #677428 on Duplicity changed:
> > https:/
> >
> > Status: Needs information => Open
> >
> > You gave more information on the question:
> >
> > On 17/1/19 2:57 am, Kenneth Loafman wrote:
> >> Your question #677428 on Duplicity changed:
> >> https:/
> >>
> >> Status: Open => Needs information
> >>
> >> Kenneth Loafman requested more information:
> >> Umm, the message "Failed to read" appeared on the first listing, not on
> >> the second. I'd suggest downloading duplicity-new-
> >> signatures.
> >> location and run:
> >>
> >> $ gzip -t duplicity-new-
> >> signatures.
> >>
> >> Post the output here.
> >>
> > I got no meaningful output kKenneth
> >
> > jtrevorj@
> > duplicity-
> > jtrevorj@
> > duplicity-
> > jtrevorj@
> >
> Kenneth if I use "gzip -tv etc" it appends "OK" to the output. Helpful?
>
> --
> You received this question notification because your team duplicity-team
> is an answer contact for Duplicity.
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>
|
Revision history for this message
|
#10 |
On 18/1/19 12:08 am, Kenneth Loafman wrote:
> Your question #677428 on Duplicity changed:
> https:/
>
> Status: Open => Answered
>
> Kenneth Loafman proposed the following answer:
> Have you retried the recovery? Does it still produce the same error?
>
The result seems to be the same Kenneth:
jtrevorj@
file://
Using archive dir:
/home/jtrevorj/
Using backup name: 2605f0dbc556032
GPG binary is gpg, version 2.2.4
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.
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
Acquiring lockfile
/home/jtrevorj/
=======
duplicity 0.7.17 (February 26, 2018)
Args: /usr/bin/duplicity -v9 restore
file://
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-
Registering (mkstemp) temporary file
/tmp/duplicity-
Temp has 176062844928 available, backup will use approx 272629760.
Synchronising remote metadata to local cache...
Copying
duplicity-
to local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Failed to read /tmp/duplicity-
'exceptions.
at 0x7f016e1da320>)
Releasing lockfile
/home/jtrevorj/
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
Releasing lockfile
/home/jtrevorj/
jtrevorj@
> On Wed, Jan 16, 2019 at 10:37 PM trevj <email address hidden>
> wrote:
>
>> Question #677428 on Duplicity changed:
>> https:/
>>
>> trevj gave more information on the question:
>>
>> On 17/1/19 3:08 pm, trevj wrote:
>>> Your question #677428 on Duplicity changed:
>>> https:/
>>>
>>> Status: Needs information => Open
>>>
>>> You gave more information on the question:
>>>
>>> On 17/1/19 2:57 am, Kenneth Loafman wrote:
>>>> Your question #677428 on Duplicity changed:
>>>> https:/
>>>>
>>>> Status: Open => Needs information
>>>>
>>>> Kenneth Loafman requested more information:
>>>> Umm, the message "Failed to read" appeared on the first listing, not on
>>>> the second. I'd suggest downloading duplicity-new-
>>>> signatures.
>>>> location and run:
>>>>
>>>> $ gzip -t duplicity-new-
>>>> signatures.
>>>>
>>>> Post the output here.
>>>>
>>> I got no meaningful output kKenneth
>>>
>>> jtrevorj@
>>> duplicity-
>>> jtrevorj@
>>> duplicity-
>>> jtrevorj@
>>>
>> Kenneth if I use "gzip -tv etc" it appends "OK" to the output. Helpful?
>>
>> --
>> You received this question notification because your team duplicity-team
>> is an answer contact for Duplicity.
>>
>> _______
>> Mailing list: https:/
>> Post to : <email address hidden>
>> Unsubscribe : https:/
>> More help : https:/
>>
|
Revision history for this message
|
#11 |
Some questions,
- Are you running the same user as duplicity when testing gzip?
- Is your system up-to-date?
- Is /media/trevorj a Linux filesystem?
Just shooting in the dark here.
|
Revision history for this message
|
#12 |
On 20/1/19 3:12 am, Kenneth Loafman wrote:
> Your question #677428 on Duplicity changed:
> https:/
> => Needs information Kenneth Loafman requested more information: Some
> questions, - Are you running the same user as duplicity when testing
> gzip? - Is your system up-to-date? - Is /media/trevorj a Linux
> filesystem? Just shooting in the dark here.
On 20/1/19 3:12 am, Kenneth Loafman wrote:
>
> Your question #677428 on Duplicity changed:
> https:/
> => Needs information Kenneth Loafman requested more information: Some
> questions, - Are you running the same user as duplicity when testing
> gzip? Yes
>
> - Is your system up-to-date? Yes - Is /media/trevorj a Linux
> filesystem? Yes
>
> Just shooting in the dark here.
Desperate times call for desperate actions:
1 I copied all the files on backup to a temp directory on my main
hard disk.
2 In the temp directory I ran
for t in duplicity-
$t; done
that's just the files in the first back up on the disk (Dec 8th 2018)
3 That created two directories multivol_snapshot and snapshot.
snapshot was mainly empty folders but multivol_snapshot held most of my
data. Unfortunately. the files were in slices numbered 1, 2 3 etc.
"cat" worked to join test files together. But I cannot imagine going
through all the folders "cat" ing all the files.
I found this script
|find multivol_snapshot/ -type f -printf '%h\0' | \| |||sort -uz | \|
|||xargs -0 -n 1 sh -c 'cd "$1" ; cat $(ls | sort -n) > content' spacer |
It lists the containing directory for every file, removes duplicates
from the list, then goes to each directory and creates a |content |file
from the fragments there. (|spacer |is just to make|$1 |work.)
But it's still messy.
|
Revision history for this message
|
#13 |
On 22.01.2019 04:57, trevj wrote:
> Question #677428 on Duplicity changed:
> https:/
>
> Status: Needs information => Open
>
> trevj gave more information on the question:
>
> On 20/1/19 3:12 am, Kenneth Loafman wrote:
>> Your question #677428 on Duplicity changed:
>> https:/
>> => Needs information Kenneth Loafman requested more information: Some
>> questions, - Are you running the same user as duplicity when testing
>> gzip? - Is your system up-to-date? - Is /media/trevorj a Linux
>> filesystem? Just shooting in the dark here.
>
>
> On 20/1/19 3:12 am, Kenneth Loafman wrote:
>>
>> Your question #677428 on Duplicity changed:
>> https:/
>> => Needs information Kenneth Loafman requested more information: Some
>> questions, - Are you running the same user as duplicity when testing
>> gzip? Yes
>
>>
>> - Is your system up-to-date? Yes - Is /media/trevorj a Linux
>> filesystem? Yes
>
>>
>> Just shooting in the dark here.
> Desperate times call for desperate actions:
>
> 1 I copied all the files on backup to a temp directory on my main
> hard disk.
>
> 2 In the temp directory I ran
>
> for t in duplicity-
> $t; done
>
> that's just the files in the first back up on the disk (Dec 8th 2018)
>
> 3 That created two directories multivol_snapshot and snapshot.
> snapshot was mainly empty folders but multivol_snapshot held most of my
> data. Unfortunately. the files were in slices numbered 1, 2 3 etc.
> "cat" worked to join test files together. But I cannot imagine going
> through all the folders "cat" ing all the files.
>
>
> I found this script
>
> |find multivol_snapshot/ -type f -printf '%h\0' | \| |||sort -uz | \|
> |||xargs -0 -n 1 sh -c 'cd "$1" ; cat $(ls | sort -n) > content' spacer |
> It lists the containing directory for every file, removes duplicates
> from the list, then goes to each directory and creates a |content |file
> from the fragments there. (|spacer |is just to make|$1 |work.)
>
>
> But it's still messy.
>
Trevj,
if you can manually extract _all_ files then duplicity should as well. btw. the "official" disaster recovery document resides here https:/
1.
first of all, can you show a 'df -h' that show there is ample space in your /tmp folder?
2.
run duplicity w/ the backup data copied from another file system (just to rule out read errors)
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
"
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:/
but your case looks different.
..ede/duply.net
|
Revision history for this message
|
#14 |
if you can manually extract _all_ files then duplicity should as well.
> btw. the "official" disaster recovery document resides here
> https:/
> 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@
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-
/dev/loop1 35M 35M 0 100% /snap/gtk-
/dev/loop2 87M 87M 0 100% /snap/core/4917
/dev/loop3 35M 35M 0 100% /snap/gtk-
/dev/loop4 3.8M 3.8M 0 100% /snap/gnome-
/dev/loop5 2.4M 2.4M 0 100% /snap/gnome-
/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-
/dev/loop10 13M 13M 0 100% /snap/gnome-
/dev/loop11 15M 15M 0 100% /snap/gnome-logs/45
/dev/loop12 2.3M 2.3M 0 100% /snap/gnome-
/dev/loop13 141M 141M 0 100% /snap/gnome-
/dev/loop9 141M 141M 0 100% /snap/gnome-
tmpfs 394M 28K 394M 1% /run/user/121
tmpfs 394M 19M 376M 5% /run/user/1000
jtrevorj@
>
> 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@
file://
duperrors.txt
Failed to read /tmp/duplicity-
'exceptions.
at 0x7fc666926170>)
jtrevorj@
duperrors.txt
Running in 'ignore errors' mode due to --ignore-errors; please
re-consider if this was not intended
Using archive dir:
/home/jtrevorj/
Using backup name: 84c5f4bc8fe1f59
GPG binary is gpg, version 2.2.4
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.
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
Acquiring lockfile
/home/jtrevorj/
=======
duplicity 0.7.17 (February 26, 2018)
Args: /usr/bin/duplicity -v9 --ignore-errors restore
file://
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-
Registering (mkstemp) temporary file
/tmp/duplicity-
Temp has 49942343680 available, backup will use approx 272629760.
Synchronising remote metadata to local cache...
Copying duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying duplicity-
local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying duplicity-
local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying duplicity-
local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying duplicity-
local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying
duplicity-
to local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Deleting /tmp/duplicity-
Forgetting temporary file /tmp/duplicity-
Copying
duplicity-
to local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
Releasing lockfile
/home/jtrevorj/
> "
> 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:/
> but your case looks different.
>
> ..ede/duply.net
>
|
Revision history for this message
|
#15 |
Trevorj,
as '--ignore-errors' did not help. let's try something else.
1.
can gunzip all files and capture the output '> log.txt 2>&1' (notice the STDERR redirect) ? send it so i can see if there are errors.
2.
after that you can try to restore on the resulting files using '--no-compression', although duplicity should detect it as uncompressed backup by itself.
..ede/duply.net
|
Revision history for this message
|
#16 |
On 23/1/19 9:26 pm, edso wrote:
> Your question #677428 on Duplicity changed:
> https:/
>
> Status: Open => Answered
>
> edso proposed the following answer:
> Trevorj,
>
> as '--ignore-errors' did not help. let's try something else.
>
> 1.
> can gunzip all files and capture the output '> log.txt 2>&1' (notice the STDERR redirect) ? send it so i can see if there are errors.
I used:
jtrevorj@
> log.txt 2>&1
The error file is one line:
gzip:
duplicity-
invalid compressed data--format violated
I then tried:
gunzip duplicity-
of the old and got an empty error file and all of the old
duplicity-full. *.difftar.gz are now just .diftar
>
> 2.
> after that you can try to restore on the resulting files using '--no-compression', although duplicity should detect it as uncompressed backup by itself.
>
> ..ede/duply.net
did this first on the files and got
jtrevorj@
file://
duperrors.txt
Failed to read /tmp/duplicity-
'exceptions.
at 0x7fd060ee9488>)
once it was gunziped I got:
duplicity -v9 --no-compression restore
file://
duperrors.txt
Failed to read /tmp/duplicity-
'exceptions.
at 0x7fcfdef24488>)
and the file duperrors.txt
reads
Using archive dir:
/home/jtrevorj/
Using backup name: 84c5f4bc8fe1f59
GPG binary is gpg, version 2.2.4
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.
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
Acquiring lockfile
/home/jtrevorj/
=======
duplicity 0.7.17 (February 26, 2018)
Args: /usr/bin/duplicity -v9 --no-compression restore
file://
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-
Registering (mkstemp) temporary file
/tmp/duplicity-
Temp has 45454807040 available, backup will use approx 272629760.
Synchronising remote metadata to local cache...
Copying
duplicity-
to local cache.
Registering (mktemp) temporary file
/tmp/duplicity-
Registering (mktemp) temporary file
/tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Removing still remembered temporary file
/tmp/duplicity-
Releasing lockfile
/home/jtrevorj/
Releasing lockfile
/home/jtrevorj/
>
|
Revision history for this message
|
#17 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
