[Duplicity-talk] step by step: How is the status of my collection ?

[T. Prost]

Since the discussion about "what files do I need ..." obviously seems
somewhat stuck, I created a new scenario for my problem - with speaking
names for the directories I'm using with my "experiments" ;-)

I hope that makes the configuration clearer :-)

What I have backed up once upon a time with deja dup is in
~/Vorlagen/restoresource
with actual contents
drwxr-xr-x 3 thomas thomas    24576 2012-02-28 09:21 .
drwxr-xr-x 4 thomas thomas    20480 2012-03-01 18:19 ..
-rw-r--r-- 1 thomas thomas 31458019 2012-01-31 13:35
duplicity-full.20120131T133515Z.vol1.difftar.gz
-rw-r--r-- 1 thomas thomas 31468122 2012-01-31 13:35
duplicity-full.20120131T133515Z.vol2.difftar.gz
-rw-r--r-- 1 thomas thomas 31460323 2012-01-31 13:35
duplicity-full.20120131T133515Z.vol3.difftar.gz
-rw-r--r-- 1 thomas thomas 31440502 2012-01-31 13:36
duplicity-full.20120131T133515Z.vol4.difftar.gz
(...)
-rw-r--r-- 1 thomas thomas 31466586 2012-01-31 14:22
duplicity-full.20120131T133515Z.vol257.difftar.gz
-rw-r--r-- 1 thomas thomas 17235968 2012-01-31 14:23
duplicity-full.20120131T133515Z.vol258.difftar.gz
{END}
Nothing else !

To make the best of a bad job, my question in the end will be: Will I
succeed to restore it here ?
~/Vorlagen/restoretarget
with actual contents
drwxr-xr-x 2 thomas thomas  4096 2012-02-09 12:43 .
drwxr-xr-x 4 thomas thomas 20480 2012-03-01 18:19 ..


But as I said: step by step. So the first attempt was to answer the
question about my collection status:

$$$duplicity collection-status
file:///home/thomas/Vorlagen/restoresource
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted
session
Last full backup date: none
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.

So: How do I have to interpret the output ? Is there something
salvageable ???

If up to here someone already found information, which I could not
interpret correctly, there's no need to read further, because I merely
raised the verbosity-level of the outputs starting from here.


$$$duplicity collection-status -v5
file:///home/thomas/Vorlagen/restoresource
Using archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831
Using backup name: 4ed90083e9ac3f1d20ca074f1ca37831
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Main action: collection-status
================================================================================
duplicity 0.6.13 (April 02, 2011)
Args: /usr/bin/duplicity collection-status -v5
file:///home/thomas/Vorlagen/restoresource
Linux K7VT4A 2.6.38-13-generic #56-Ubuntu SMP Tue Feb 14 12:40:40 UTC
2012 i686 athlon
/usr/bin/python 2.7.1+ (r271:86832, Apr 11 2011, 18:05:24) 
[GCC 4.5.2]
================================================================================
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted
session
Last full backup date: none
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Using temporary directory /tmp/duplicity-lsqdm1-tempdir


$$$duplicity collection-status -v8
file:///home/thomas/Vorlagen/restoresource
Using archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831
Using backup name: 4ed90083e9ac3f1d20ca074f1ca37831
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Main action: collection-status
================================================================================
duplicity 0.6.13 (April 02, 2011)
Args: /usr/bin/duplicity collection-status -v8
file:///home/thomas/Vorlagen/restoresource
Linux K7VT4A 2.6.38-13-generic #56-Ubuntu SMP Tue Feb 14 12:40:40 UTC
2012 i686 athlon
/usr/bin/python 2.7.1+ (r271:86832, Apr 11 2011, 18:05:24) 
[GCC 4.5.2]
================================================================================
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted
session
Last full backup date: none
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Using temporary directory /tmp/duplicity-5MPANZ-tempdir


$$$duplicity collection-status -v9
file:///home/thomas/Vorlagen/restoresource
Using archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831
Using backup name: 4ed90083e9ac3f1d20ca074f1ca37831
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Main action: collection-status
================================================================================
duplicity 0.6.13 (April 02, 2011)
Args: /usr/bin/duplicity collection-status -v9
file:///home/thomas/Vorlagen/restoresource
Linux K7VT4A 2.6.38-13-generic #56-Ubuntu SMP Tue Feb 14 12:40:40 UTC
2012 i686 athlon
/usr/bin/python 2.7.1+ (r271:86832, Apr 11 2011, 18:05:24) 
[GCC 4.5.2]
================================================================================
Local and Remote metadata are synchronized, no sync needed.
259 files exist on backend
0 files exist in cache
Extracting backup chains from list of files:
(... or did I leave here something of interest ? ...)
(...)
File duplicity-full.20120131T133515Z.vol45.difftar.gz is not part of a
known set; creating new set
File duplicity-full.20120131T133515Z.vol31.difftar.gz is part of known
set
(... for the rest of the files ...)
(...)
File duplicity-full.20120131T133515Z.vol189.difftar.gz is part of known
set
File duplicity-full.20120131T133515Z.vol218.difftar.gz is part of known
set
Warning, found incomplete backup sets, probably left from aborted
session
Last full backup date: none
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive
dir: /home/thomas/.cache/duplicity/4ed90083e9ac3f1d20ca074f1ca37831

Found 0 secondary backup chains.
No backup chains with active signatures found
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Using temporary directory /tmp/duplicity-7VVagJ-tempdir