Re: [Duplicity-talk] Restore single file from incremental, retrieving full

[Kenneth Loafman]

We're looking at an edge case here without enough info.  I have a thought.

The way duplicity finds which volume to search for the restore file is to look at the start path and ending path in the volume info in the manifest.  So, if the test is something like:

full backup has only the file 'foo', the range in the manifest will be ['.'..'foo']

inc backup has only the file 'bar', the range in the manifest will be ['.'..'bar']

So, when a recovery is requested, duplicity will download the full volume because 'bar' is in the range.  Hmmm, no 'bar' there, so it will download the inc volume, and there it is.

Does that match your test case and observations?  If so, then duplicity is working correctly.

...Thanks,

...Ken

On Fri, Apr 6, 2018 at 12:43 AM, Oliver Cole via Duplicity-talk <address@hidden> wrote:

Thanks for replying!

On 05/04/2018 10:33, address@hidden wrote:

The backup set consists of 1 full and 1 incremental - and the requested file only exists in the incremental. (This is a test scenario I put together, so I'm certain this is the case).

could show that by posting a collection-status?

Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sun Apr  1 14:18:00 2018
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /backup/duplicitycache/e3b115cb91b96e04a62ff54cd95bdbac

Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Sun Apr  1 14:18:00 2018
Chain end time: Wed Apr  4 19:38:45 2018
Number of contained backup sets: 2
Total number of contained volumes: 3
 Type of backup set:                            Time:      Num volumes:
                Full         Sun Apr  1 14:18:00 2018                 2
         Incremental         Wed Apr  4 19:38:45 2018                 1
-------------------------
No orphaned or incomplete backup sets found.

When I retrieve the single file (with --verbosity debug) I can see it is retrieving the full backup volumes.

right, it shouldn't.
 

Am I misunderstanding the duplicity model, or is my restore command wrong? It seems to me the metadata should know the file only exists in the incremental and just get that?

can you post a list of the files on the remote?

dataduplicity-full.20180401T141800Z.vol1.difftar.gpg
dataduplicity-full.20180401T141800Z.vol2.difftar.gpg
dataduplicity-inc.20180401T141800Z.to.20180404T193845Z.vol1.difftar.gpg
duplicity-full-signatures.20180401T141800Z.sigtar.gpg
duplicity-full.20180401T141800Z.manifest.gpg
duplicity-inc.20180401T141800Z.to.20180404T193845Z.manifest.gpg
duplicity-new-signatures.20180401T141800Z.to.20180404T193845Z.sigtar.gpg

Thanks again!

Oli

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk