Backblaze B2

Low-cost object storage with an S3-compatible API. It is S3-compatible, which means blitcp supports it out of the box: pick the b2 preset in creds add, paste your keys, and every transfer gets blitcp's usual treatment — content-hash deduplication before upload, verified writes after, and incremental re-runs that skip unchanged files.

Endpoint

https://s3.<region>.backblazeb2.com
The region is part of your bucket's endpoint, e.g. us-west-004 — shown on the bucket page. Region: Use the region from the endpoint (e.g. us-west-004).

Where the keys come from

Backblaze console → App Keys → Add a New Application Key. keyID is the access key, applicationKey is the secret.

Set it up once

$ blitcp creds add myb2
  Type [s3/azure/gcs/ssh/smb — or a preset: r2/b2/wasabi/…]: b2
  Backblaze B2 — S3-compatible. Keys: …
  Region: your-region
  Endpoint: https://s3.….backblazeb2.com
  Access key ID: ********
  Secret access key: ********
  Default bucket (blank = none): backups

Then copy

blitcp ~/photos myb2:backups/photos          # upload, dedup + verify on
blitcp myb2:backups/photos ~/restore     # download

Re-running the same upload only transfers new or changed files. Duplicate content inside the tree is uploaded once. Credentials live in blitcp's AES-256-GCM encrypted credentials file — see the cloud storage guide for the full creds manager.

Notes

Application keys can be scoped to one bucket — scope the blitcp key to your backup bucket.

Also supported: Cloudflare R2 · Wasabi · DigitalOcean Spaces · Scaleway Object Storage · Hetzner Object Storage · IDrive e2 · Storj · Oracle OCI Object Storage · iCloud Drive