duply: Incrementals not shown

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

duply: Incrementals not shown

duplicity-talk mailing list
Hello,

Everybody have a Happy New Year!

I use duplicity though Duply on Debian Testing and have a weird problem. I have two profiles, that differ only by the SOURCE setting:

root@venus ~ # grep -v "^#" .duply/home/conf | grep -v "^$"

GPG_KEY='disabled'
GPG_PW='_GPG_PASSWORD_'
TARGET='scp://[hidden email]:2022/Backup/home'
SOURCE='/home'
MAX_AGE=1M
MAX_FULLBKP_AGE=2W
DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE "
VOLSIZE=25
DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE "
VERBOSITY=5

The other profile works perfectly. duply status shows all backups I did.

However, at the home profile does not show any incremental backups I did after the initial full backup.

I do a successfull incremental backup:

# duply home backup
Start duply v1.11.3, time is 2017-01-01 15:08:21.
Using profile '/root/.duply/home'.
Using installed duplicity version 0.7.10, python 2.7.13, gpg 2.1.16 (Home: /root/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D.
Brennan', grep 'grep (GNU grep) 2.27', bash '4.4.5(1)-release (x86_64-pc-linux-gnu)'.
Checking TEMP_DIR '/tmp' is a folder and writable (OK)
Test - En/Decryption skipped. (GPG disabled)

--- Start running command PRE at 15:08:22.162 ---
Running '/root/.duply/home/pre' - OK
--- Finished state OK at 15:08:23.161 - Runtime 00:00:00.998 ---

--- Start running command BKP at 15:08:23.185 ---
Using archive dir: /root/.cache/duplicity/duply_home
Using backup name: duply_home
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.copycombackend 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
ssh: Connected (version 2.0, client OpenSSH_7.4)
ssh: Authentication (publickey) successful!
Reading globbing filelist /root/.duply/home/exclude
Main action: inc
================================================================================
duplicity 0.7.10 (August 20, 2016)
Args: /usr/bin/duplicity --name duply_home --no-encryption --verbosity 5 --full-if-older-than 2W --volsize 25 --exclude-filelist
/root/.duply/home/exclude /home scp://[hidden email]:2022/Backup/home
Linux venus 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64
/usr/bin/python2 2.7.13 (default, Dec 18 2016, 20:19:42)
[GCC 6.2.1 20161215]
================================================================================
Using temporary directory /tmp/duplicity-QVGvCy-tempdir
Temp has 403978645504 available, backup will use approx 34078720.
Local and Remote metadata are synchronized, no sync needed.
Processing local manifest /root/.cache/duplicity/duply_home/duplicity-full.20161231T112717Z.manifest (72624054)
Found 1280 volumes in manifest
Last full backup date: Sat Dec 31 12:27:17 2016
Deleting /tmp/duplicity-QVGvCy-tempdir/mktemp-WObfvN-2
Processing remote manifest duplicity-full.20161231T112717Z.manifest (72624054)
Found 1280 volumes in manifest
Processing local manifest /root/.cache/duplicity/duply_home/duplicity-full.20161231T112717Z.manifest (72624054)
Found 1280 volumes in manifest
Using temporary directory /root/.cache/duplicity/duply_home/duplicity-nrCnBQ-tempdir
Using temporary directory /root/.cache/duplicity/duply_home/duplicity-ji_7UJ-tempdir
AsyncScheduler: instantiating at concurrency 0
A .
[...]
AsyncScheduler: running task synchronously (asynchronicity disabled)
Writing duplicity-inc.20161231T112717Z.to.20170101T140824Z.vol1.difftar.gz
Deleting /tmp/duplicity-QVGvCy-tempdir/mktemp-1jbiXd-3
AsyncScheduler: task completed successfully
Processed volume 1
Writing duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
Deleting /root/.cache/duplicity/duply_home/duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
Writing duplicity-inc.20161231T112717Z.to.20170101T140824Z.manifest
Deleting /root/.cache/duplicity/duply_home/duplicity-inc.20161231T112717Z.to.20170101T140824Z.manifest
--------------[ Backup Statistics ]--------------
StartTime 1483279824.09 (Sun Jan  1 15:10:24 2017)
EndTime 1483280050.73 (Sun Jan  1 15:14:10 2017)
ElapsedTime 226.64 (3 minutes 46.64 seconds)
SourceFiles 625298
SourceFileSize 50371934529 (46.9 GB)
NewFiles 929
NewFileSize 51839669 (49.4 MB)
DeletedFiles 318
ChangedFiles 346
ChangedFileSize 1963514289 (1.83 GB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 1593
RawDeltaSize 55127302 (52.6 MB)
TotalDestinationSizeChange 22379617 (21.3 MB)
Errors 0
-------------------------------------------------

--- Finished state OK at 15:14:18.024 - Runtime 00:05:54.839 ---

--- Start running command POST at 15:14:18.042 ---
Skipping n/a script '/root/.duply/home/post'.
--- Finished state OK at 15:14:18.061 - Runtime 00:00:00.019 ---
duply home backup  235.42s user 24.56s system 72% cpu 5:56.35 total



So everything looks ok, but:

# duply home status
Start duply v1.11.3, time is 2017-01-01 15:27:29.
Using profile '/root/.duply/home'.
Using installed duplicity version 0.7.10, python 2.7.13, gpg 2.1.16 (Home: /root/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D.
Brennan', grep 'grep (GNU grep) 2.27', bash '4.4.5(1)-release (x86_64-pc-linux-gnu)'.
Checking TEMP_DIR '/tmp' is a folder and writable (OK)
Test - En/Decryption skipped. (GPG disabled)

--- Start running command STATUS at 15:27:30.392 ---
Using archive dir: /root/.cache/duplicity/duply_home
Using backup name: duply_home
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.copycombackend 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
ssh: Connected (version 2.0, client OpenSSH_7.4)
ssh: Authentication (publickey) successful!
Main action: collection-status
================================================================================
duplicity 0.7.10 (August 20, 2016)
Args: /usr/bin/duplicity collection-status --name duply_home --no-encryption --verbosity 5 --full-if-older-than 2W --volsize 25
scp://[hidden email]:2022/Backup/home
Linux venus 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64
/usr/bin/python2 2.7.13 (default, Dec 18 2016, 20:19:42)
[GCC 6.2.1 20161215]
================================================================================
Synchronizing remote metadata to local cache...
Deleting local /root/.cache/duplicity/duply_home/duplicity-inc.20161231T112717Z.to.20170101T140824Z.manifest (not authoritative at backend).
Deleting local /root/.cache/duplicity/duply_home/duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz (not authoritative at backend).
Processing local manifest /root/.cache/duplicity/duply_home/duplicity-full.20161231T112717Z.manifest (72624054)
Found 1280 volumes in manifest
Last full backup date: Sat Dec 31 12:27:17 2016
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /root/.cache/duplicity/duply_home

Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Sat Dec 31 12:27:17 2016
Chain end time: Sat Dec 31 12:27:17 2016
Number of contained backup sets: 1
Total number of contained volumes: 239
 Type of backup set:                            Time:      Num volumes:
                Full         Sat Dec 31 12:27:17 2016               239
-------------------------
No orphaned or incomplete backup sets found.
Using temporary directory /tmp/duplicity-4Q6Jyg-tempdir
--- Finished state OK at 15:27:39.887 - Runtime 00:00:09.494 ---
duply home status  7.38s user 1.35s system 87% cpu 10.015 total


The incremental backup is never shown.

I already tried to redo the first full backup (completely wiped TARGET), but it changed nothing.

Any idea what could cause the problem here?

Thanks,
Florian


_______________________________________________
Duplicity-talk mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
Reply | Threaded
Open this post in threaded view
|

Re: duply: Incrementals not shown

duplicity-talk mailing list
hi Florian, comment inline below

On 01.01.2017 15:30, Florian Lindner via Duplicity-talk wrote:

> Hello,
>
> Everybody have a Happy New Year!
>
> I use duplicity though Duply on Debian Testing and have a weird problem. I have two profiles, that differ only by the SOURCE setting:
>
> root@venus ~ # grep -v "^#" .duply/home/conf | grep -v "^$"
>
> GPG_KEY='disabled'
> GPG_PW='_GPG_PASSWORD_'
> TARGET='scp://[hidden email]:2022/Backup/home'
> SOURCE='/home'
> MAX_AGE=1M
> MAX_FULLBKP_AGE=2W
> DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE "
> VOLSIZE=25
> DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE "
> VERBOSITY=5
>
> The other profile works perfectly. duply status shows all backups I did.
>
> However, at the home profile does not show any incremental backups I did after the initial full backup.
>
> I do a successfull incremental backup:
>
SNIP
>
>
>
> So everything looks ok, but:
>
> # duply home status
> Start duply v1.11.3, time is 2017-01-01 15:27:29.
SNIP

> Synchronizing remote metadata to local cache...
> Deleting local /root/.cache/duplicity/duply_home/duplicity-inc.20161231T112717Z.to.20170101T140824Z.manifest (not authoritative at backend).
> Deleting local /root/.cache/duplicity/duply_home/duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz (not authoritative at backend).

see here your locally cached inremental get's deleted because duplicity does not seem to see it on your backend.

can you browse there and check if the files really ended up there? try switching to the pexpect+scp:// backend and see if the error resolves. paramiko sometimes has issues listing files on the backend

SNIP
>
> The incremental backup is never shown.
>
> I already tried to redo the first full backup (completely wiped TARGET), but it changed nothing.
>
> Any idea what could cause the problem here?
>

..ede

_______________________________________________
Duplicity-talk mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
Reply | Threaded
Open this post in threaded view
|

Re: duply: Incrementals not shown

duplicity-talk mailing list
Hey,

Am 03.01.2017 um 12:08 schrieb edgar.soldin--- via Duplicity-talk:

> hi Florian, comment inline below
>
> On 01.01.2017 15:30, Florian Lindner via Duplicity-talk wrote:
>> Hello,
>>
>> Everybody have a Happy New Year!
>>
>> I use duplicity though Duply on Debian Testing and have a weird problem. I have two profiles, that differ only by the SOURCE setting:
>>
>> root@venus ~ # grep -v "^#" .duply/home/conf | grep -v "^$"
>>
>> GPG_KEY='disabled'
>> GPG_PW='_GPG_PASSWORD_'
>> TARGET='scp://[hidden email]:2022/Backup/home'
>> SOURCE='/home'
>> MAX_AGE=1M
>> MAX_FULLBKP_AGE=2W
>> DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE "
>> VOLSIZE=25
>> DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE "
>> VERBOSITY=5
>>
>> The other profile works perfectly. duply status shows all backups I did.
>>
>> However, at the home profile does not show any incremental backups I did after the initial full backup.
>>
>> I do a successfull incremental backup:
>>
> SNIP
>>
>>
>>
>> So everything looks ok, but:
>>
>> # duply home status
>> Start duply v1.11.3, time is 2017-01-01 15:27:29.
> SNIP
>
>> Synchronizing remote metadata to local cache...
>> Deleting local /root/.cache/duplicity/duply_home/duplicity-inc.20161231T112717Z.to.20170101T140824Z.manifest (not authoritative at backend).
>> Deleting local /root/.cache/duplicity/duply_home/duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz (not authoritative at backend).
>
> see here your locally cached inremental get's deleted because duplicity does not seem to see it on your backend.
>
> can you browse there and check if the files really ended up there? try switching to the pexpect+scp:// backend and see if the error resolves. paramiko sometimes has issues listing files on the backend

Files on TARGET:

root@marduk /home/venus/Backup/home # ll *sig*
-rw------- 1 venus venus 661868201 31. Dez 17:21 duplicity-full-signatures.20161231T112717Z.sigtar.gz
-rw------- 1 venus venus  11327438 31. Dez 17:36 duplicity-new-signatures.20161231T112717Z.to.20161231T163047Z.sigtar.gz
-rw------- 1 venus venus  11345015 31. Dez 17:45 duplicity-new-signatures.20161231T112717Z.to.20161231T163906Z.sigtar.gz
-rw------- 1 venus venus  11763366  1. Jan 02:11 duplicity-new-signatures.20161231T112717Z.to.20170101T010504Z.sigtar.gz
-rw------- 1 venus venus  12878011  1. Jan 15:14 duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
-rw------- 1 venus venus  13268770  1. Jan 20:20 duplicity-new-signatures.20161231T112717Z.to.20170101T191037Z.sigtar.gz
-rw------- 1 venus venus  13271921  1. Jan 20:32 duplicity-new-signatures.20161231T112717Z.to.20170101T192657Z.sigtar.gz
-rw------- 1 venus venus  13526360  2. Jan 02:11 duplicity-new-signatures.20161231T112717Z.to.20170102T010504Z.sigtar.gz
-rw------- 1 venus venus  14738759  3. Jan 02:13 duplicity-new-signatures.20161231T112717Z.to.20170103T010511Z.sigtar.gz
-rw------- 1 venus venus  15035322  3. Jan 13:26 duplicity-new-signatures.20161231T112717Z.to.20170103T121953Z.sigtar.gz

The ones in the night are from the backup cronjob, the last one 13:26 is from the backup I just did. So everything looks in order (for me).

Trying pexpect+scp:


# duply home status
[...]
Synchronizing remote metadata to local cache...
Copying duplicity-inc.20161231T112717Z.to.20161231T163047Z.manifest to local cache.
[...]
Copying duplicity-new-signatures.20161231T112717Z.to.20161231T163047Z.sigtar.gz to local cache.
[...]
Copying duplicity-new-signatures.20161231T112717Z.to.20170103T010511Z.sigtar.gz to local cache.
Warning, found the following local orphaned signature files:
duplicity-new-signatures.20161231T112717Z.to.20170101T192657Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T010504Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T191037Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170103T121953Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20161231T163047Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20161231T163906Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170102T010504Z.sigtar.gz
Warning, found the following remote orphaned signature files:
duplicity-new-signatures.20161231T112717Z.to.20161231T163906Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T010504Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T191037Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170101T192657Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170102T010504Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170103T010511Z.sigtar.gz
duplicity-new-signatures.20161231T112717Z.to.20170103T121953Z.sigtar.gz
Warning, found signatures but no corresponding backup files
Last full backup date: Sat Dec 31 12:27:17 2016
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /root/.cache/duplicity/duply_home

Found 1 secondary backup chain.
Secondary chain 1 of 1:
-------------------------
Chain start time: Sat Dec 31 12:27:17 2016
Chain end time: Tue Jan  3 13:19:53 2017
Number of contained backup sets: 2
Total number of contained volumes: 1282
 Type of backup set:                            Time:      Num volumes:
                Full         Sat Dec 31 12:27:17 2016              1280
         Incremental         Tue Jan  3 13:19:53 2017                 2
-------------------------

Ok, I think this is ok, because the incremental backups didn't see the previous incremental backup. duply home cleanup --force fixed that, except
Warning, found signatures but no corresponding backup files. I will do a new complete backup later.

So I assume everything is working fine now.

Do you have any idea why only one profile is affected while the other one, same settings, same TARGET is not troublesome?

Anyway, big thanks to you!

Florian
Florian

_______________________________________________
Duplicity-talk mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
Reply | Threaded
Open this post in threaded view
|

Re: duply: Incrementals not shown

duplicity-talk mailing list
On 03.01.2017 13:39, Florian Lindner via Duplicity-talk wrote:

> Hey,
>
> Am 03.01.2017 um 12:08 schrieb edgar.soldin--- via Duplicity-talk:
>> hi Florian, comment inline below
>>
>> On 01.01.2017 15:30, Florian Lindner via Duplicity-talk wrote:
>>> Hello,
>>>
>>> Everybody have a Happy New Year!
>>>
>>> I use duplicity though Duply on Debian Testing and have a weird problem. I have two profiles, that differ only by the SOURCE setting:
>>>
>>> root@venus ~ # grep -v "^#" .duply/home/conf | grep -v "^$"
>>>
>>> GPG_KEY='disabled'
>>> GPG_PW='_GPG_PASSWORD_'
>>> TARGET='scp://[hidden email]:2022/Backup/home'
>>> SOURCE='/home'
>>> MAX_AGE=1M
>>> MAX_FULLBKP_AGE=2W
>>> DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE "
>>> VOLSIZE=25
>>> DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE "
>>> VERBOSITY=5
>>>
>>> The other profile works perfectly. duply status shows all backups I did.
>>>
>>> However, at the home profile does not show any incremental backups I did after the initial full backup.
>>>
>>> I do a successfull incremental backup:
>>>
>> SNIP
>>>
>>>
>>>
>>> So everything looks ok, but:
>>>
>>> # duply home status
>>> Start duply v1.11.3, time is 2017-01-01 15:27:29.
>> SNIP
>>
>>> Synchronizing remote metadata to local cache...
>>> Deleting local /root/.cache/duplicity/duply_home/duplicity-inc.20161231T112717Z.to.20170101T140824Z.manifest (not authoritative at backend).
>>> Deleting local /root/.cache/duplicity/duply_home/duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz (not authoritative at backend).
>>
>> see here your locally cached inremental get's deleted because duplicity does not seem to see it on your backend.
>>
>> can you browse there and check if the files really ended up there? try switching to the pexpect+scp:// backend and see if the error resolves. paramiko sometimes has issues listing files on the backend
>
> Files on TARGET:
>
> root@marduk /home/venus/Backup/home # ll *sig*
> -rw------- 1 venus venus 661868201 31. Dez 17:21 duplicity-full-signatures.20161231T112717Z.sigtar.gz
> -rw------- 1 venus venus  11327438 31. Dez 17:36 duplicity-new-signatures.20161231T112717Z.to.20161231T163047Z.sigtar.gz
> -rw------- 1 venus venus  11345015 31. Dez 17:45 duplicity-new-signatures.20161231T112717Z.to.20161231T163906Z.sigtar.gz
> -rw------- 1 venus venus  11763366  1. Jan 02:11 duplicity-new-signatures.20161231T112717Z.to.20170101T010504Z.sigtar.gz
> -rw------- 1 venus venus  12878011  1. Jan 15:14 duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
> -rw------- 1 venus venus  13268770  1. Jan 20:20 duplicity-new-signatures.20161231T112717Z.to.20170101T191037Z.sigtar.gz
> -rw------- 1 venus venus  13271921  1. Jan 20:32 duplicity-new-signatures.20161231T112717Z.to.20170101T192657Z.sigtar.gz
> -rw------- 1 venus venus  13526360  2. Jan 02:11 duplicity-new-signatures.20161231T112717Z.to.20170102T010504Z.sigtar.gz
> -rw------- 1 venus venus  14738759  3. Jan 02:13 duplicity-new-signatures.20161231T112717Z.to.20170103T010511Z.sigtar.gz
> -rw------- 1 venus venus  15035322  3. Jan 13:26 duplicity-new-signatures.20161231T112717Z.to.20170103T121953Z.sigtar.gz
>
> The ones in the night are from the backup cronjob, the last one 13:26 is from the backup I just did. So everything looks in order (for me).
>
> Trying pexpect+scp:
>
>
> # duply home status
> [...]
> Synchronizing remote metadata to local cache...
> Copying duplicity-inc.20161231T112717Z.to.20161231T163047Z.manifest to local cache.
> [...]
> Copying duplicity-new-signatures.20161231T112717Z.to.20161231T163047Z.sigtar.gz to local cache.
> [...]
> Copying duplicity-new-signatures.20161231T112717Z.to.20170103T010511Z.sigtar.gz to local cache.
> Warning, found the following local orphaned signature files:
> duplicity-new-signatures.20161231T112717Z.to.20170101T192657Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T010504Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T191037Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170103T121953Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20161231T163047Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20161231T163906Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170102T010504Z.sigtar.gz
> Warning, found the following remote orphaned signature files:
> duplicity-new-signatures.20161231T112717Z.to.20161231T163906Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T010504Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T140824Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T191037Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170101T192657Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170102T010504Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170103T010511Z.sigtar.gz
> duplicity-new-signatures.20161231T112717Z.to.20170103T121953Z.sigtar.gz
> Warning, found signatures but no corresponding backup files
> Last full backup date: Sat Dec 31 12:27:17 2016
> Collection Status
> -----------------
> Connecting with backend: BackendWrapper
> Archive dir: /root/.cache/duplicity/duply_home
>
> Found 1 secondary backup chain.
> Secondary chain 1 of 1:
> -------------------------
> Chain start time: Sat Dec 31 12:27:17 2016
> Chain end time: Tue Jan  3 13:19:53 2017
> Number of contained backup sets: 2
> Total number of contained volumes: 1282
>  Type of backup set:                            Time:      Num volumes:
>                 Full         Sat Dec 31 12:27:17 2016              1280
>          Incremental         Tue Jan  3 13:19:53 2017                 2
> -------------------------
>
> Ok, I think this is ok, because the incremental backups didn't see the previous incremental backup. duply home cleanup --force fixed that, except
> Warning, found signatures but no corresponding backup files. I will do a new complete backup later.

yeah, better start clean. and do verifies from time to time. i cannot stress that enough.

> So I assume everything is working fine now.

don't assume, verify ;)

> Do you have any idea why only one profile is affected while the other one, same settings, same TARGET is not troublesome?

me neither, but you can have an eye out for max. verbosity messages like this

"
Extracting backup chains from list of files: [u'duplicity-full.20161022T121330Z.manifest.gpg', u'duplicity-full.20161022T121330Z.vol100.difftar.gpg', u'duplicity-full.20161022T121330Z.vol101.difftar.gpg', u'duplicity-full.20161022T121330Z.vol102.difftar.gpg', u'duplicity-full.20161022T121330Z.vol103.difftar.gpg',
SNIP
full.20161022T121330Z.vol169.difftar.gpg', u'duplicity-full.20161022T121330Z.vol16.difftar.gpg', u'duplicity-full.20161022T121330Z.vol170.difftar.gpg', u'duplicity-full.20161022T121330Z.vol171.difftar.gpg', u'duplicity-full.20161022T1213']
"

it's one long line but the end entry seems to be cut, which it is essentially. consider joining the paramiko bug report mentioned on
  https://bugs.launchpad.net/duplicity/+bug/1265765

maybe when enough people complain someone from paramiko will have a look at it?
 
> Anyway, big thanks to you!

nP.. ede/duply.net

_______________________________________________
Duplicity-talk mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk