On 13.05.2020 15:30, Andrew Wood via Duplicity-talk wrote:
Dear Edgar (Nate/ everyone)
SOLVED! The command which you suggested below worked. Thank-you so much - I was
really at my wits end.
good to hear
Now I'm wondering if there is anyway to reduce the likelihood of this happening
again, or to suggest improvements/enhancement requests to Duplicity or Deja Vu.
well. how about not backing up empty mount points? not sure if deja-dup
supports conditions, but running duplicity using a condition via cron would
look roughly like
grep -q '/mount/srcpath' && duplicity '/mount/srcpath' scheme://targethost/path
most important thing is that it'd be a separate backup set that'll only be
backed up if the source is mounted!
On the plus side: I've learned something and this email would be searchable to
others which is helpful to others. I guess there is - if nothing else - a
use-case here for the developers.
It's slightly confusing that duplicity takes the parameter --file-to-restore
when it actually restores a directory or indeed a whole volume.
yeah well that's legacy. maybe some kind soul at some point implements
'--in/exclude' support for restores.
Once again - thank-you so much for all your assistance,
de nada.. ede/duply.net
Andrew, Oxford, UK
On 13/05/2020 10:31, edgar.soldin--- via Duplicity-talk wrote:
On 13.05.2020 09:59, Andrew Wood via Duplicity-talk wrote:
Hello Edgar/ Nate/ everyone
Thanks for you help and assistance. Here's the output of the two commands as
requested:
1)
[awood@localhost ~]$ duplicity collection-status
file:///run/media/awood/MyPassport/Deja-Vu-Back-up
Last full backup date: Thu Mar 26 09:21:33 2020
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive directory: /home/awood/.cache/duplicity/d8a1ed559e366bb0ccdf1d4f1d1954b1
Found 4 secondary backup chains.
Secondary chain 1 of 4:
-------------------------
Chain start time: Tue Mar 19 08:49:48 2019
Chain end time: Thu Jun 13 08:29:32 2019
Number of contained backup sets: 13
Total number of contained volumes: 857
Type of backup set: Time: Number of volumes:
Full Tue Mar 19 08:49:48 2019 692
Incremental Thu Mar 21 08:45:13 2019 2
SNIP
looks healthy so far
Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Thu Mar 26 09:21:33 2020
Chain end time: Thu Apr 30 09:36:18 2020
Number of contained backup sets: 7
Total number of contained volumes: 1187
Type of backup set: Time: Number of volumes:
Full Thu Mar 26 09:21:33 2020 884
Incremental Thu Apr 2 09:23:45 2020 1
Incremental Thu Apr 9 09:49:48 2020 1
Incremental Thu Apr 16 11:53:39 2020 1
Incremental Mon Apr 20 13:37:06 2020 292
the above looks like suddenly there was a lot more to backup. maybe the stick
was reattached? it actually seems to be the date we are listing files from.
note 2020/04/21 is between the backup's date and the next one's.
Incremental Thu Apr 23 09:20:53 2020 1
Incremental Thu Apr 30 09:36:18 2020 7
-------------------------
No orphaned or incomplete backup sets found.
2)
duplicity list-current-files --time 2020/04/21
file:///run/media/awood/MyPassport/Deja-Vu-Back-up
The output of this is huge 64,725 lines (using wc -l)!... shall I attach the
output file? But I note that it includes references to both
run/media/awood/7160-75C1 files and also home/awood which is a good sign I
guess.
nope, not needed. it's important if it lists the files you are missing! if so
try
duplicity --time 2020/04/21 --file-to-restore run/media/awood/7160-75C1
file:///run/media/awood/MyPassport/Deja-Vu-Back-up
/run/media/awood/MyPassport/USB-Restore/7160-75C1-restored
..ede/duply.net
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk