NOTICE: This Documentation is for JetBackup 4 for Linux.

Please CLICK HERE for the latest JetBackup 5 for Linux Documentation.

Backblaze B2

Step 1 Configure Backblaze

Sign up/in with your account at https://www.backblaze.com/.

Click on "Bucket" at the "B2 Cloud Storage" sidebar, then click on "Show Account ID and Application Key".

Show Account ID


Click on "Create application key". Keep your application key & account id for later usage.
Note that when you create a new application key, the old one will no longer work.

backblaze create application key


click on "create a bucket". Give your bucket a unique name, and choose "private".

create a bucket


Step 2 Create a backup destination

  1. Specify "Destination Type" as "Backblaze".
  2. Write a name for your destination.
  3. Fill in Account ID, Application Key and Bucket name that you have just created.
  4. Click the "save" button.
Example configuration page for the destination:

create backblaze destination


Destination Name

A generic name for your internal ease of use, so it will be easier to recognize the backup destination roll, in case you have more than one.
Max length is 40 characters.


Backup Directory

This will be our starting point when accessing this destination.
Make sure to not start with "/".
Write your path to where you want the backup to be stored.
You can leave the backup directory empty if you want that the backup will be stored in the main directory.


Free Disk Space Limit

This option will check if destination disk space reached the specified limit before it performs the backup. If you enable this option and available disk space is less than the amount specified, the system will not perform the backup.


Account ID

The identifier for the account.


Application Key

The account Application Key.


Bucket

In order to create a bucket using BackBlaze console go to Creating a Bucket in the Backblaze B2 Cloud Storage Buckets.


Upload Retries

If the upload fails for some reason retry upload x times.


Retry timeout

Wait x seconds before next retry