TrueCloudLab/restic
16
0
Fork 3
Code Issues 3 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Entered feedback from MichaelEischer

Browse source
This commit is contained in:
Markus Kramer 2023-08-20 17:20:46 +02:00
parent d57ef6ec75
commit 1925457b78
2 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/040_backup.rst
View file

@ -46,13 +46,13 @@ also tells us that only 1.200 GiB was added to the repository. This means that
some of the data was duplicate and restic was able to efficiently reduce it. some of the data was duplicate and restic was able to efficiently reduce it.
We just attached the absolute path ``~/work`` to the backup, so the path We just attached the absolute path ``~/work`` to the backup, so the path
within the repository is ``/home/user/work``, depending on your user name. within the snapshot is ``/home/user/work``.
If we attach a relative path ``work``, the path within the repository is ``/work``. If we attach a relative path ``work``, the path within the snaphot is ``/work``.
For example ``restic backup work`` run from ``/home/user`` crates a snapshot For example ``restic backup work`` run from ``/home/user`` creates a snapshot
with a attached path ``/home/user/work`` that contains the path ``/work`` with a directory ``/home/user/work`` that contains the path ``/work``
within the repository. This path-related discrepancy applies to each command within the snapshot. This path-related discrepancy applies to each command
that tries to access data within a snapshot. You can lookup the paths within that tries to access data within a snapshot. You can lookup the paths within
a repository using the ``ls latest /`` command. a repository using the ``ls latest /`` command.

10
doc/050_restore.rst
View file

@ -156,12 +156,12 @@ e.g.:
$ restic -r /srv/restic-repo dump --path /production.sql latest production.sql | mysql $ restic -r /srv/restic-repo dump --path /production.sql latest production.sql | mysql
This example assumes you attached an absolute path, which means it coincides with the This example assumes you ran a backup using an absolute path, which coincides with the
path within the repository. path within the snaphots.
See https://restic.readthedocs.io/en/stable/040_backup.html#backing-up for the difference See https://restic.readthedocs.io/en/stable/040_backup.html#backing-up for the difference
between attached path and path within the repository. between the path used to create the repository and the paths within the snaphots.
If you attached a relative path, the ``dump`` command would look like: If you ran a backup using the relative path ``work/``, the ``dump`` command would look like:
.. code-block:: console .. code-block:: console
@ -169,7 +169,7 @@ If you attached a relative path, the ``dump`` command would look like:
If dump results in the error message ``cannot dump file: path "/home" not found in snapshot`` If dump results in the error message ``cannot dump file: path "/home" not found in snapshot``
first double check you used the path within the repository, using the ``ls latest /`` command, first double check you used the path within the snaphot, using the ``ls latest /`` command,
which for the repository above results in: which for the repository above results in:
.. code-block:: console .. code-block:: console