Re: [Duplicity-talk] When modifying a file under the backup dir, duplicity still thinks that there are no differences with the backup (stored on GDrive)

[edgar . soldin]

On 22.04.2015 03:48, Kostas Papadopoulos wrote:> Hi,
> 
> After ~1yr of hiatus from duplicity, I've tried doing some quick testing of 
> the latest duply 1.9.1 /duplicity 0.7.02.
> 
> But *when I add or modify a file under the backup dir, duplicity still thinks 
> that there are no differences* with the backup (stored on GDrive). although I 
> hadn't run a backup for several weeks.
> 
>     address@hidden:~/src/duplicity-0.7.02# ~/bin/duply mytest verify
>     Start duply v1.9.1, time is 2015-04-22 01:32:26.
>     Using profile '/root/.duply/mytest'.
>     Using installed duplicity version 0.7.02, python 2.7.3, gpg 1.4.12 (Home: 
> ~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', bash 
> '4.2.37(1)-release (x86_64-pc-linux-gnu)'.
>     Autoset found secret key of first GPG_KEY entry '0841EA59' for signing.
>     Checking TEMP_DIR '/tmp' is a folder (OK)
>     Checking TEMP_DIR '/tmp' is writable (OK)
>     TODO: reimplent tmp space check
>     Test - Encrypt to '0841EA59' & Sign with '0841EA59' (OK)
>     Test - Decrypt (OK)
>     Test - Compare (OK)
>     Cleanup - Delete '/tmp/duply.2138.1429666346_*'(OK)
> 
>     --- Start running command VERIFY at 01:32:27.075 ---
>     Reading globbing filelist /root/.duply/mytest/exclude
>     Local and Remote metadata are synchronized, no sync needed.
>     Last full backup date: Sun Apr  5 15:55:20 2015
>     Verify complete: 73 files compared, 0 differences found.
>     --- Finished state OK at 01:33:47.897 - Runtime 00:01:20.821 ---
>     address@hidden:~/src/duplicity-0.7.02#
> 
>     address@hidden:~/src/duplicity-0.7.02# grep -v ^# 
> ~/.duply/mytest/conf|grep -v ^$
>     GPG_KEY='REMOVED'
>     GPG_PW='REMOVED'
>     TARGET='gdocs://address@hidden/duplicity-backup-test'
>     TARGET_PASS='REMOVED'
>     SOURCE='/root/docs'
>     MAX_AGE=7D
>     MAX_FULL_BACKUPS=3
>     MAX_FULLS_WITH_INCRS=2
>     MAX_FULLBKP_AGE=2D
>     DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE "
>     address@hidden:~/src/duplicity-0.7.02#
> 
>     address@hidden:~/src/duplicity-0.7.02# cat /root/.duply/mytest/exclude
>     /root/docs/dir4
>     /root/docs/dir6
>     address@hidden:~/src/duplicity-0.7.02#
> 
>     address@hidden:~/src/duplicity-0.7.02# ls -la /root/docs/
>     total 48
>     drwxr-xr-x 12 root root 4096 Apr 22 00:58 .
>     drwx------  9 root root 4096 Apr 22 01:00 ..
>     drwxr-xr-x  2 root root 4096 Nov 16  2013 dir2
>     drwxr-xr-x  2 root root 4096 Nov 17  2013 dir3
>     drwxr-xr-x  2 root root 4096 Nov 18  2013 dir4
>     drwxr-xr-x  2 root root 4096 Apr 22 01:00 dir5
>     drwxr-xr-x  2 root root 4096 Nov 18  2013 dir6
>     drwxr-xr-x  2 root root 4096 Apr 22 00:58 dir7
>     drwxr-xr-x  2 root root 4096 Apr  5 16:59 DOKIMH-AGGLIKA-directory
>     drwxr-xr-x  2 root root 4096 Nov 17  2013 thin-client
>     drwxr-xr-x  2 root root 4096 Apr  5 16:32 ΔΟΚΙΜΗ-ΕΛΛΗΝΙΚΟ-directory
>     address@hidden:~/src/duplicity-0.7.02#
> 
> 

please post the output of something along the lines

1. duplicity backup
2. touch a file
3. duplicity incr backup (here the summary log should show one changed file)

note that 'verify' is not a backup but a temp restore with comparision to the 
original local file.

also: use the duplicity-talk mailing list, that's what it's there for. we don't 
do one on one support.

..ede