Use a Backblaze Fireball with an Iconik Internet Storage Gateway
    • Dark

    Use a Backblaze Fireball with an Iconik Internet Storage Gateway

    • Dark

    Article Summary

    You can use a Backblaze Fireball with an iconik Internet Storage Gateway (ISG) setup. 

    Enable Backblaze B2

    Before you begin: You must have a Backblaze B2 Cloud Storage account. You can sign up here. 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 your Backblaze account.
    2. In the left navigation menu under Account, click 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 a Bucket

    This should be the same bucket in which the Fireball is linked.

    1. Sign in to your Backblaze account.
    2. In the left navigation menu under B2 Cloud Storage, click Buckets.
    3. Click Create a Bucket.
    4. Enter a name for your bucket.
      Bucket names must be at least six characters and globally unique. A message is displayed if your bucket name is already in use.
    5. Select a privacy setting: Private or Public.
      Files that are in a private bucket require authentication to perform an action, for example, downloading. Public buckets do not require authentication so you can easily share files. You can change a bucket's privacy settings at any time.
    6. If applicable, enable a Backblaze B2 server-side encryption key.
    7. Enable Object Lock to restrict a file from being modified or deleted for a specified period of time.
    8. Click Create a Bucket, and copy the value that is in the Endpoint field; you may need this value for other processes.
    9. Click Lifecycle Settings to control how long to keep the files in your new bucket.

    Create an Application Key

    Application keys control access to your Backblaze B2 Cloud Storage account and the buckets that are contained in your account.

    1. Sign in to your Backblaze account.
    2. In the left navigation menu under Account, click Application Keys.
    3. Click Add a New Application Key, and enter an app key name.
          You cannot search an app key by this name; therefore, app key names are not required to be globally unique.
    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.
    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.

    Set Up an ISG

    1. Configure ISG storage in iconik. Make sure your ISG storage root is the same root that you want iconik to manage.
    2. Configure a new Backblaze B2 Cloud Storage endpoint
    3. Copy your data to the Fireball. Ensure that the data that is copied to your fireball has the same relative pathing to your storage on the items that you want iconik to manage.
    4. Ensure that your ISG root and your Backblaze B2 bucket root are pointing to the same place in your storage configuration. For example, if your local ISG is mounted at /Volumes/MySAN/iconik/ISG, you can copy any tree into the Fireball, but ensure that the bucket that is defined as storage is set to this same root. If you copied /Volumes/MySAN to / on the Fireball, you set the storage root on the Fireball bucket to /iconik/ISG. It is important that the files on the ISG are seen in the same relative place in the Fireball-ingested bucket.
    5. Configure the ISG settings using the following command:
      auto-generate-filename-for-remote-upload = false
    6. Enable Upload on the ISG, and select B2 cloud storage. Ensure that the upload directory is the same as the root of the Fireball in cloud storage.
    7. Start the ISG.
      The system attempts to upload all files; it notices the files that are already in Backblaze B2, thus causing it to not perform any upload. After it completes indexing/generating proxies, you can move to the next step. If you do not let it index everything first, you pay egress to transcode the proxies from Backblaze B2.
    8. Optionally, scan the Backblaze B2 bucket that was tied to the Fireball in iconik. This triggers transcoding in the cloud if the files are found first on Backblaze B2.

    The assets in iconik now have format links to the ISG.

    Configure an ISG

    These steps assume that you already set up an ISG.

    1. Configure new B2 cloud storage endpoint.
    2. Copy your data to the Fireball.
    3. Contact iconik support to retrieve the script for checksum generation.
    4. Run that script against the Fireball drive. This creates checksums on all of the files on the Fireball.
    5. Scan the Backblaze B2 bucket that is tied to the Fireball in iconik.

    Files are now linked to the correct assets.

    You should maintain a local copy of your data until you have verified that your Fireball was uploaded accurately and completely to your Backblaze B2 bucket.

    Was this article helpful?