Re: [Duplicity-talk] duply: Incrementals not shown

[edgar . soldin]

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:
> 
> address@hidden ~ # grep -v "^#" .duply/home/conf | grep -v "^$"
> 
> GPG_KEY='disabled'
> GPG_PW='_GPG_PASSWORD_'
> TARGET='scp://address@hidden: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