Re: [Duplicity-talk] What files are needed for listing and restoring ?

[T. Prost]

Am Freitag, den 17.02.2012, 16:24 +0100 schrieb T. Prost:
> Am Freitag, den 17.02.2012, 16:00 +0100 schrieb address@hidden:
> 
> > source_url is the folder or remote location where your duplicity volumes 
> > reside. target_dir the folder where you want it restored, choose a new one.
> > 
> > options like --no-encryption come after the command before target and 
> > source.
> > 
> > try 
> > duplicity collection-status [options] target_url 
> > first to check if duplicity sees your backup chains.
> 
> duplicity collection-status file:///home/thomas/Vorlagen/X1
> 
> 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/43289ee51e536a1c0d78a0f564acfa4a
> 
> 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.
> 
> NOTE: I never ran duplicity cleanup but I´m afraid, deja-dup did that !?
Main action: collection-status
================================================================================
duplicity 0.6.13 (April 02, 2011)
Args: /usr/bin/duplicity collection-status -v9
file:///home/thomas/Vorlagen/X1/X1
Linux K7VT4A 2.6.38-13-generic #55-Ubuntu SMP Tue Jan 24 14:27:59 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.
1 file exists on backend
0 files exist in cache
Extracting backup chains from list of files:
['duplicity-full.20120131T133515Z.vol45.difftar.gz']
File duplicity-full.20120131T133515Z.vol45.difftar.gz is not part of a
known set; creating new 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/12a60c54b42f2f9eb1d4927f0eea4b24

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/12a60c54b42f2f9eb1d4927f0eea4b24

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-tj2hDt-tempdir