how far back when doing restore will duplicity go?

Asked by Chris Stankaitis

We keep 6 Months of Full Backup's and we believe we had seen when doing a restore that it went back beyond the current monthly full to restore the file. As I understand it, you should never need to go back to restore a file beyond the current monthly full (assuming you are not trying to restore an older version of the file) as a "full" should contain everything duplicity should need to restore any file.

Am I correct on this behaviour? if so what's the best test case for this that I can do.

Question information

Language:
English Edit question
Status:
Answered
For:
Duplicity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
edso (ed.so) said :
#1

On 07.09.2011 22:10, Chris Stankaitis wrote:
> New question #170480 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/170480
>
> We keep 6 Months of Full Backup's and we believe we had seen when doing a restore that it went back beyond the current monthly full to restore the file.

how and where would you have seen this?

> As I understand it, you should never need to go back to restore a file beyond the current monthly full (assuming you are not trying to restore an older version of the file) as a "full" should contain everything duplicity should need to restore any file.

correct

>
> Am I correct on this behaviour?

:)

>if so what's the best test case for this that I can do.
>

find a file older than the latest full and restore it with -v9 (debug verbosity), check what volumes are downloaded.
OR
create your self a test setup. create a file do a full, some incr, another full, somm more incr and do the above.

ede/duply.net

Can you help with this problem?

Provide an answer of your own, or ask Chris Stankaitis for more information if necessary.

To post a message you must log in.