mirrors
/
restic
mirror of https://github.com/restic/restic.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #3928 from restic/rawtaz-doc-b2-s3 

doc: Clarify S3 recommendation for B2 slightly
This commit is contained in:
Michael Eischer 2022-09-13 20:59:50 +02:00 committed by GitHub
parent d79e61ce5d 20f1913ef7
commit b48766d7b8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/030_preparing_a_new_repo.rst
View File

@ -466,13 +466,16 @@ Backblaze B2
.. warning:: .. warning::
The recommended way to setup Backblaze B2 is by using its S3-compatible API. Due to issues with error handling in the current B2 library that restic uses,
Follow the documentation to `generate S3-compatible access keys`_ and then the recommended way to utilize Backblaze B2 is by using its S3-compatible API.
setup restic as described at :ref:`Amazon S3`.
Different from the B2 backend, restic's S3 backend will only hide no longer Follow the documentation to `generate S3-compatible access keys`_ and then
necessary files. Thus, make sure to setup lifecycle rules to eventually setup restic as described at :ref:`Amazon S3`. This is expected to work better
delete hidden files. than using the Backblaze B2 backend directly.
Different from the B2 backend, restic's S3 backend will only hide no longer
necessary files. Thus, make sure to setup lifecycle rules to eventually
delete hidden files.
Restic can backup data to any Backblaze B2 bucket. You need to first setup the Restic can backup data to any Backblaze B2 bucket. You need to first setup the
following environment variables with the credentials you can find in the following environment variables with the credentials you can find in the