[pbs-devel] [PATCH proxmox-backup] docs: s3: add Backblaze B2 configuration example

[Christian Ebner]

Backblaze B2 currently requires to set provider specific quirks and
their access key naming might be confusing as there is also the key
name.

While it should be avoided to create a different example for each of
the existing providers, adding a dedicated example for B2
configuration is justified.

This indirectly also documents the provider quirks configuration
parameter.

Signed-off-by: Christian Ebner <c.ebner at proxmox.com>
---
 docs/storage.rst | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/docs/storage.rst b/docs/storage.rst
index 54540219b..627b26557 100644
--- a/docs/storage.rst
+++ b/docs/storage.rst
@@ -390,6 +390,28 @@ otherwise request authentication might fail:
         backend bucket=pbs-r2-bucket,client=cloudflare-r2,type=s3
         path /mnt/datastore/r2-s3-store-local-cache
 
+Backblaze B2 currently does not accept the ``If-None-Match`` http header, set by the PBS s3 client
+in some cases for put object API calls. It is therefore required to explicitley disable this by
+setting the ``skip-if-none-match-header`` as ``provider-quirks``. The access key is stated as
+``keyID`` in the Backblaze web interface. An example configuration is:
+
+.. code-block:: console
+
+   # cat /etc/proxmox-backup/s3.cfg
+
+   s3-endpoint: backblaze-b2
+        access-key XXXXXXXXXXXXXXXXXXXXXXXXX
+        endpoint {{bucket}}.s3.{{region}}.backblazeb2.com
+        provider-quirks skip-if-none-match-header
+        region eu-central-003
+        secret-key XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
+    # cat /etc/proxmox-backup/datastore.cfg
+
+    datastore: b2-s3-store
+        backend bucket=pbs-b2-bucket,client=backblaze-b2,type=s3
+        path /mnt/datastore/b2-s3-store-local-cache
+
 
 Managing Datastores
 ^^^^^^^^^^^^^^^^^^^
-- 
2.47.2