Hi,
Andrew Wood wrote:
Note that I'm not especially concerned with restoring the USB
exactly - with
all its partitions, etc.
In this case it seems consensus that you should wipe out its partition
table and create one that fits your intentions. E.g. one single partition
claiming the device up to its end.
Then create a new filesystem. The old one was obviously of type vfat.
Maybe you manage to get it automounted at the same directory as the
old stick filesystem.
Reasoning is that currently the partitions are supposed to be small
and the biggest partition is supposed to be inhabited by a read-only
ISO 9660 filesystem.
(We cannot know for sure as we did not see yet the output of the
proposed blkid run or some partition editor's listing.)
---------------------------------------------------------------------
From here on i can only guess from the man page of duplicity:
https://linux.die.net/man/1/duplicity
duplicity restore [options] source_url target_directory
I couldn't understand how to use this command! My first unknown is the
source URL. I'm using a external USB hardisk 'MyPassport' on /dev/sda1 for
the duplicity archive.
I would expect that it is the same address you gave as "target_url"
when making the backup, like in
duplicity full [options] source_directory target_url
The example in the man page relies on automatic recognition of the copy
direction by distinguishing URL from local file path:
duplicity scp://uid@other.host/some_dir /home/me
Is it source file:///dev/sda1/Deja-Vu-Back-up where Deja-Vu-Back-up
is the
directory with the back-ups??
(Does modern madness go so far to use "/dev/sda1" as virtual moint point
for URLs ?)
Whatever, i expect that a directory path which leads to "Deja-Vu-Back-up"
will serve as target_url, if you prepend it by "file://".
Somehow, I need to pass the name of the backed-up USB volume
The man page says "target_directory". So i would expect that it is the
path you gave at backup time as "source_directory".
But maybe you have to use a different mount directory of the USB stick.
E.g. if source_directory was
/run/media/awood/7160-75C1/some/deeper/directory
and the new filesystem of the stick is mounted as
/run/media/awood/MY_FAT
then i expect that the "target_directory" is
/run/media/awood/MY_FAT/some/deeper/directory
Of course the example "/some/deeper/directory" might in practice just
be empty text.
So i place my bet on something like
duplicity restore \
file:///path/to/Deja-Vu-Back-up/maybe/more \
/run/media/awood/MY_FAT/some/deeper/directory
Have a nice day :)
Thomas