I have a working backup, and directory restore works fine as well. But if I try to restore using 'duplicity restore -v8 --use-agent --ssh-options="-oIdentityFile=/dup/.ssh/id_duplicity" --name=`hostname` scp://address@hidden/BackUps/'
with any combination of "--file-to-restore system1/test.txt" and "/home/me/test_root", in any order and regardless of path settings (relative, absolute) I get either
"Restore destination directory /home/me/test_root already exists. Will not overwrite."
or at best
"Command line error: restore option incompatible with inc backup"
With "verify --compare-data" I get the correct chains .... Found primary backup chain with matching signature chain: ------------------------- Chain start time: Sun Dec 4 10:36:14 2016 Chain end time: Sun Dec 4 10:43:21 2016 Number of contained backup sets: 2 Total number of contained volumes: 2 Type of backup set: Time: Num volumes: Full Sun Dec 4 10:36:14 2016 1 Incremental Sun Dec 4 10:43:21 2016 1
.... and differences Local and Remote metadata are synchronized, no sync needed. Last full backup date: Sun Dec 4 10:36:14 2016 Difference found: File system1 has mtime Sun Dec 4 11:15:37 2016, expected Sun Dec 4 10:36:59 2016 Difference found: File system1/test.py is missing Difference found: File system1/test.txt is missing Verify complete: 8 files compared, 3 differences found.
Version is duplicity 0.7.10, on CentOS 7 Kernel 3.10.0-327.28.2.el7.x86_64;
I despreately do not understand the difficulty I am facing with such a quite simple but essential operation.
Please, I need your help to figure out what I'm doing wrong. [In addition, what is needed to restore / operate on multiple files, i.e. with wildcards?]