Misleading 'last full backup' when restoring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned |
Bug Description
When restoring (using version 0.6.13), I am being told this:
Last full backup date: Tue Dec 13 10:46:14 2011
However, that's not the case. That's the last full backup in the primary chain, but there are secondary ones that are older. Fortunately regardless of that output, it looks like Duplicity can see the older backups, and successfully restores from that when asked to (via --restore-time). (However, there's no way of knowing it's worked, other than recognising that the restored output is as old as expected - duplicity says nothing else at all after the above output).
Full collection status corresponding to the above:
Found 1 secondary backup chain.
Secondary chain 1 of 1:
-------
Chain start time: Sun Nov 27 12:54:20 2011
Chain end time: Sun Nov 27 12:54:20 2011
Number of contained backup sets: 1
Total number of contained volumes: 25
Type of backup set: Time: Num volumes:
-------
Found primary backup chain with matching signature chain:
-------
Chain start time: Tue Dec 13 10:46:14 2011
Chain end time: Tue Dec 20 03:41:31 2011
Number of contained backup sets: 8
Total number of contained volumes: 28
Type of backup set: Time: Num volumes:
-------
No orphaned or incomplete backup sets found.