Finally upgraded MIAB to Ubuntu 18 and followed the instructions with the back up. I uploaded the backup files exactly the way it was originally and ran the command:
root@box:~# sudo mv /home/user-data /tmp/user-data.empty
root@box:~# export PASSPHRASE=$(cat /path/to/secret_key.txt)
cat: /path/to/secret_key.txt: No such file or directory
root@box:~# sudo -E duplicity restore --force file:///path/to/backup /home/user- data/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Traceback (innermost last):
File “/usr/bin/duplicity”, line 1555, in
with_tempdir(main)
File “/usr/bin/duplicity”, line 1541, in with_tempdir
fn()
File “/usr/bin/duplicity”, line 1393, in main
do_backup(action)
File “/usr/bin/duplicity”, line 1472, in do_backup
restore(col_stats)
File “/usr/bin/duplicity”, line 728, in restore
restore_get_patched_rop_iter(col_stats)):
File “/usr/bin/duplicity”, line 750, in restore_get_patched_rop_iter
backup_chain = col_stats.get_backup_chain_at_time(time)
File “/usr/lib/python2.7/dist-packages/duplicity/collections.py”, line 974, in get_backup_chain_at_time
raise CollectionsError(“No backup chains found”)
CollectionsError: No backup chains found
Rather than sanitizing the output, could you paste the ACTUAL output please? @Moderndayfreak
There is nothing of a confidential nature in the output. If, for some reason there is in your case, feel free to PM it to me.
If that is actually what you are entering, you need to specify the ACTUAL LOCATION of the secret_key.txt file and of the back up … hence replace /path/to/secret_key.txt with the actual path to that file. Same with the path to the backup.