Select “App Keys” to navigate to the Application Keys page and then “Add a New Application Key” An application key is used to connect the File Fabric to Backblaze B2 storage. This is the point you’ll verify the region where you’ll be storing data.īackblaze uses application keys to manage authentication and authorization. If you’re not using Backblaze already sign up for an account at. You can also download a software appliance from that page, or run from Google or AWS marketplace. If you don’t have a File Fabric account sign up for a free trial for our SaaS service.

This blog walks through setting up a Backblaze B2 provider, highlighting some of the nifty features as well as nuances and recommended settings. Many organizations are already using Backblaze for cloud backup and want other data and workflows to take advantage of low cost cloud storage. It’s been one of our most requested storage providers.

compression: as of restic 0.The Storage Made Easy Enterprise File Fabric™ platform now supports Backblaze B2 Cloud Storage as a first-class storage provider.

dedup: data is naturally deduplicated, including across snapshots.

you can prune the data in the repository by tolerating some percentage or fixed maximum amount of unreferenced garbage you can delete snapshots by schedules or explicitly, tag them to keep them from being deleted, etc.

snapshots: when you do a backup it makes a snapshot, kinda like git does if you know about that, which you can browse and mount and restore data from later.

you can even copy backups between repositories (though if you want this to be efficient take care to follow the docs regarding -copy-chunker-params) i personally only use it with just file folders but it supports any s3-like object store including b2. you must supply a password or a password-file, so the object-store you're putting it onto never actually sees any of your data decrypted

If you are storing backups on B2, use restic ( docs).

Backblaze linux support