| 1 |
% bup-import-duplicity(1) Bup %BUP_VERSION% |
| 2 |
% Zoran Zaric <[email protected]>, Rob Browning <[email protected]> |
| 3 |
% %BUP_DATE% |
| 4 |
|
| 5 |
# NAME |
| 6 |
|
| 7 |
bup-import-duplicity - import duplicity backups |
| 8 |
|
| 9 |
# WARNING |
| 10 |
|
| 11 |
bup-import-duplicity is **EXPERIMENTAL** (proceed with caution) |
| 12 |
|
| 13 |
# SYNOPSIS |
| 14 |
|
| 15 |
bup import-duplicity [-n] \<source-url\> \<save-name\> |
| 16 |
|
| 17 |
# DESCRIPTION |
| 18 |
|
| 19 |
`bup import-duplicity` imports all of the duplicity backups at |
| 20 |
`source-url` into `bup` via `bup save -n save-name`. The bup saves |
| 21 |
will have the same timestamps (via `bup save --date`) as the original |
| 22 |
backups. |
| 23 |
|
| 24 |
Because this command operates by restoring each duplicity backup to a |
| 25 |
temporary directory, the extent to which the metadata is preserved |
| 26 |
will depend on the characteristics of the underlying filesystem, |
| 27 |
whether or not you run `import-duplicity` as root (or under |
| 28 |
`fakeroot`(1)), etc. |
| 29 |
|
| 30 |
Note that this command will use [`mkdtemp`][mkdtemp] to create |
| 31 |
temporary directories, which means that it should respect any |
| 32 |
`TEMPDIR`, `TEMP`, or `TMP` environment variable settings. Make sure |
| 33 |
that the relevant filesystem has enough space for the largest |
| 34 |
duplicity backup being imported. |
| 35 |
|
| 36 |
Since all invocations of duplicity use a temporary `--archive-dir`, |
| 37 |
`import-duplicity` should not affect ~/.cache/duplicity. |
| 38 |
|
| 39 |
# OPTIONS |
| 40 |
|
| 41 |
-n, \--dry-run |
| 42 |
: don't do anything; just print out what would be done |
| 43 |
|
| 44 |
# EXAMPLES |
| 45 |
|
| 46 |
$ bup import-duplicity file:///duplicity/src/ legacy-duplicity |
| 47 |
|
| 48 |
# BUP |
| 49 |
|
| 50 |
Part of the `bup`(1) suite. |
| 51 |
|
| 52 |
[mkdtemp]: https://docs.python.org/3/library/tempfile.html#tempfile.mkdtemp |