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

doc: recommend usage of B2's S3 API

Browse source
This commit is contained in:
Michael Eischer 2022-08-21 11:39:03 +02:00
parent 0d9ac78437
commit c586a5e20f
1 changed files with 12 additions and 0 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

@ -450,6 +450,16 @@ The policy of the new container created by restic can be changed using environme
Backblaze B2 Backblaze B2
************ ************
.. warning::
The recommended way to setup Backblaze B2 is by using its S3-compatible API.
Follow the documentation to `generate S3-compatible access keys`_ and then
setup restic as described at :ref:`Amazon S3`.
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
dashboard on the "Buckets" page when signed into your B2 account: dashboard on the "Buckets" page when signed into your B2 account:
@ -488,6 +498,8 @@ The number of concurrent connections to the B2 service can be set with the ``-o
b2.connections=10`` switch. By default, at most five parallel connections are b2.connections=10`` switch. By default, at most five parallel connections are
established. established.
.. _generate S3-compatible access keys: https://help.backblaze.com/hc/en-us/articles/360047425453-Getting-Started-with-the-S3-Compatible-API
Microsoft Azure Blob Storage Microsoft Azure Blob Storage
**************************** ****************************