> Also, do you happen to know if these backups are full or incremental ones?
In my situation, it does not make a change whether it's a full or incremental backup: as soon as the upload begins, it starts with 0 (that's logical) en jumps to 100 when ready, no step between.
On the plus side: when doing a restore-action, (download) progress is shown per file, so that's good.
>1. The version of deja-dup and duplicity:
> dpkg-query -W deja-dup duplicity
deja-dup 19.92-0ubuntu1
duplicity 0.6.15-0ubuntu2
>2. The file /tmp/deja-dup.gsettings after running the following line (you may want to scrub the file of any incriminating file >names or details):
> gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
org.gnome.DejaDup backend 'u1'
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup include-list ['/home/user/Temp']
org.gnome.DejaDup last-backup '2011-09-18T07:11:33.662436Z'
org.gnome.DejaDup last-restore '2011-09-18T07:15:29.661215Z'
org.gnome.DejaDup last-run '2011-09-18T07:15:29.661215Z'
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup prompt-check '2011-09-03T21:42:06.499803Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path 'sftp://eco@192.168.0.210/home/eco/deja-dup'
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.Rackspace container 'asus-mark'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'asus-mark'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.U1 folder 'deja-dup/asus-mark'
> 3. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the > log of any incriminating file names or details):
> DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
See attachment.
> Also, do you happen to know if these backups are full or incremental ones?
In my situation, it does not make a change whether it's a full or incremental backup: as soon as the upload begins, it starts with 0 (that's logical) en jumps to 100 when ready, no step between.
On the plus side: when doing a restore-action, (download) progress is shown per file, so that's good.
>1. The version of deja-dup and duplicity:
> dpkg-query -W deja-dup duplicity
deja-dup 19.92-0ubuntu1
duplicity 0.6.15-0ubuntu2
>2. The file /tmp/deja- dup.gsettings after running the following line (you may want to scrub the file of any incriminating file >names or details): dup.gsettings 18T07:11: 33.662436Z' 18T07:15: 29.661215Z' 18T07:15: 29.661215Z' 03T21:42: 06.499803Z' DejaDup. File icon '' DejaDup. File name '' DejaDup. File path 'sftp:// eco@192. 168.0.210/ home/eco/ deja-dup' DejaDup. File relpath @ay [] DejaDup. File short-name '' DejaDup. File type 'normal' DejaDup. File uuid '' DejaDup. Rackspace container 'asus-mark' DejaDup. Rackspace username '' DejaDup. S3 bucket '' DejaDup. S3 folder 'asus-mark' DejaDup. S3 id '' DejaDup. U1 folder 'deja-dup/ asus-mark'
> gsettings list-recursively org.gnome.DejaDup > /tmp/deja-
org.gnome.DejaDup backend 'u1'
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup include-list ['/home/user/Temp']
org.gnome.DejaDup last-backup '2011-09-
org.gnome.DejaDup last-restore '2011-09-
org.gnome.DejaDup last-run '2011-09-
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup prompt-check '2011-09-
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
> 3. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the > log of any incriminating file names or details):
> DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log
See attachment.