Contents x
Jellyfish Integration with Backblaze B2
    • Print
    • Dark
      Light
    Contents

    Jellyfish Integration with Backblaze B2

      • Print
      • Dark
        Light
      Article summary

      You can back up directly from Jellyfish to Backblaze B2 Cloud Storage.

      Enable Backblaze B2

      Before you begin: You must have a Backblaze B2 Cloud Storage account. If you already have a Backblaze account and the left navigation menu contains a B2 Cloud Storage section, your account is already enabled for Backblaze B2.

      1. Sign in to the Backblaze web console.
      2. In the user menu in the upper-right corner of the page, select My Settings.
      3. Under Enabled Products, select the checkbox to enable B2 Cloud Storage.
      4. Review the Terms and Conditions, and click OK to accept them. 

      Create an Application Key

      1. Sign in to the Backblaze web console.
      2. In the left navigation menu under B2 Cloud Storage, click Application Keys.
      3. Click Add a New Application Key, and enter an app key name. Please note: You cannot search an app key by this name; therefore, app key names are not required to be globally unique. Key names are limited to 100 characters and can contain letters, numbers, and "-", but not I18N characters, such as é, à, and ü.
      4. Select All or a specific bucket in the Allow Access to Bucket(s) dropdown menu.
      5. Optionally, select your access type (Read and Write, Read Only, or Write Only).
      6. Optionally, select the Allow List All Bucket Names checkbox (required for the B2 Native API b2_list_buckets and the S3-Compatible API S3 List Buckets operations).
      7. Optionally, enter a file name prefix to restrict application key access only to files with that prefix. Depending on what you selected in step #4, this limits application key access to files with the specified prefix for all buckets or just the selected bucket.
      8. Optionally, enter a positive integer to limit the time, in seconds, before the application key expires. The value must be less than 1000 days (in seconds).
      9. Click Create New Key, and note the resulting keyID and applicationKey values.
      Note
      When you create a new app key, the response contains the actual key string, for example N2Zug0evLcHDlh_L0Z0AJhiGGdY. You can always find the keyID on this page, but for security, the applicationKey appears only once. Make sure you copy and securely save this value elsewhere.

      Connect and Activate Backblaze B2

      Before you begin: Connect an Ethernet cable from your router to a port on the back of the Jellyfish. In the Jellyfish Manager, select the network module, set the port to DHCP, and connect the other end of the cable to your internet router. After the connection is established, your Jellyfish can communicate with Backblaze B2.

      1. Sign in to the Jellyfish Manager.
      2. Click Advanced in the top menu.
      3. Click the Backblaze module.
      4. Click Install.
      5. Enter your Backblaze keyID and applicationKey.
      6. Click the check mark to activate the connection.

      Create a Backblaze B2 Bucket from Jellyfish Manager

      You can create a bucket using the Backblaze web console, or you can create a bucket in the Jellyfish Manager.

      1. Click + (add) in the Buckets field.
      2. Enter a bucket name.
      3. Select a lifecycle rule:
        • Keep only the last version of the file
        • Keep prior versions for x number of days
        • Keep all versions of the file
      4. Select private or public as the privacy type.
      5. Click the check mark.
      6. Select the directory to back up to the bucket.
      7. Turn on the toggle for the bucket that you just created.
      8. Select the appropriate backup settings:
        • Directory
        • Time
        • Days
      9. Click the check mark, and click Run Backup.

      A "Current Backup" status bar is displayed, showing the number of files being backed up to your Backblaze B2 bucket.

      For more information about this integration, see this Jellyfish blog article.

      Was this article helpful?
      What's Next