alexvanin/restic
1
0
Fork 0
forked from TrueCloudLab/restic
Code Pull requests Activity

Merge pull request #2793 from greatroar/rclone-doc

Browse source 
Clarify rclone-over-SSH docs
This commit is contained in:
Alexander Neumann 2020-12-29 10:46:34 +01:00 committed by GitHub
commit c661518df9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/030_preparing_a_new_repo.rst
View file

@ -633,7 +633,17 @@ rclone e.g. via SSH on a server, for example:
.. code-block:: console .. code-block:: console
$ restic -o rclone.program="ssh user@host rclone" -r rclone:b2:foo/bar $ restic -o rclone.program="ssh user@remotehost rclone" -r rclone:b2:foo/bar
With these options, restic works with local files. It uses rclone and
credentials stored on ``remotehost`` to communicate with B2. All data (except
credentials) is encrypted/decrypted locally, then sent/received via
``remotehost`` to/from B2.
A more advanced version of this setup forbids specific hosts from removing
files in a repository. See the `blog post by Simon Ruderich
<https://ruderich.org/simon/notes/append-only-backups-with-restic-and-rclone>`_
for details.
The rclone command may also be hard-coded in the SSH configuration or the The rclone command may also be hard-coded in the SSH configuration or the
user's public key, in this case it may be sufficient to just start the SSH user's public key, in this case it may be sufficient to just start the SSH