duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] duply list


From: Adam Gold
Subject: Re: [Duplicity-talk] duply list
Date: Fri, 18 Apr 2014 15:51:26 +0100

>> On 17.04.2014 21:52, Adam Gold wrote:
>> I have two backup sets I run, let's call them A and B. Sometime in >> the
>> last month or so (I think), when I run duply A list it returns the >>
same
>> result as if I'd run duply status rather than providing a list of all
>> the files. I have tried this on two different machines, one running
>> Fedora 19 and one running Ubuntu 14.04 beta 2. I'm using duply 1.60
>>
>> However with backup set B, I get an individual list of files as >>
would be expected.
>>
>> Could anyone give me suggestions on how I can try and track down why
>> this is happening? Thanks.

> first update to the latest release 1.7.3. you can simply download the
> tarball from http://duply.net/ and replace your local ./duply with
>the on contained in the archive. alternatively place it somewhere else
>and simply run it from there.

I tried with the latest version but still the same (repo A only, repo B
still works)

> secondly.. see if the error persists and if so.. run duply with the
>--preview option to see the generated command lines and post the out
>put here..

Here go you:

==============================================
Start duply v1.7.3, time is 2014-04-17 22:19:37.
Using profile '[ ]'.
Using installed duplicity version 0.6.23, python 2.7.6, gpg 1.4.16
(Home: ~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D.
Brennan', bash '4.3.8(1)-release (x86_64-pc-linux-gnu)'.
Use configured key '[ ]' as signing key.
-- Run cmd 'Test - Encrypt to [ ] & Sign with [ ]' --
echo 'passphrase' | /usr/bin/gpg --sign --default-key [ ]
--passphrase-fd 0 --batch -r [ ] --status-fd 1 --compress-algo=bzip2
--bzip2-compress-level=9 --trust-model always -o
/tmp/duply.30257.1397769577_ENC -e ./duply 2>&1
-- Run cmd 'Test - Decrypt' --
echo 'passphrase' | /usr/bin/gpg --passphrase-fd 0 --batch
--compress-algo=bzip2 --bzip2-compress-level=9 --trust-model always -o
/tmp/duply.30257.1397769577_DEC -d /tmp/duply.30257.1397769577_ENC 2>&1
-- Run cmd 'Test - Compare' --
test "$(cat './duply')" = "$(cat '/tmp/duply.30257.1397769577_DEC')" 2>&1
Cleanup - Delete '/tmp/duply.30257.1397769577_*'(FAILED)

--- Start running command LIST at 22:19:37.798 ---
TMPDIR='/tmp' PASSPHRASE='passphrase' SIGN_PASSPHRASE='passphrase'
GS_ACCESS_KEY_ID='[ ]' GS_SECRET_ACCESS_KEY='[ ]' duplicity
list-current-files --archive-dir 'cache' --name duply_data --encrypt-key
[ ] --sign-key [ ] --verbosity '8' --gpg-options
'--compress-algo=bzip2 --bzip2-compress-level=9 --trust-model always'
--full-if-older-than 6W --volsize 25 --allow-source-mismatch
--asynchronous-upload -t now 'gs://bucket/folders/'
--- Finished state OK at 22:19:37.873 - Runtime 00:00:00.074 ---
==============================================

One other thing which I just had a look at. This backup is the
recreation of a previous backup now using GS as the backend (previously
I was using some remote drives with sftp). The total number of volumes
is approximately the same with this latest full backup vs a full backup
of the old version. However I had a look at the sig file in the local
cache: for the old version of this backup, the file was appx 400MB but
this time around it's 209MB. I think at this point, I'm going to run a new 
backup and I'll report the results.‎



reply via email to

[Prev in Thread] Current Thread [Next in Thread]