Contents x
Migrate Veeam Backups from AWS S3 to Backblaze B2
    • Print
    • Dark
      Light
    Contents

    Migrate Veeam Backups from AWS S3 to Backblaze B2

      • Print
      • Dark
        Light
      Article Summary

      The Backblaze integration with Veeam lets you migrate your existing backup repositories that are in Amazon S3 storage to Backblaze B2 Cloud Storage. 

      The Backblaze B2 S3-Compatible API allows thousands of integrations to natively work with Backblaze B2. If you are new to the S3-compatible API, click here. If you have issues using Veeam Backup & Replication with Backblaze B2, send an email to [email protected].

      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

      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. In the Allow Access to Bucket(s) dropdown menu, select All or a specific bucket.
      5. Select your access type (for example, Read and Write).
      6. Select the optional Allow List All Bucket Names checkbox (required for the Backblaze B2 S3-compatible API List Buckets operation).
      7. 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.

      Migrate Data from Veeam AWS to Backblaze B2

      Before you begin: You must have a scale-out repository that is configured to use Backblaze B2. For more information about setting up scale-out backup repositories, click here.

      1. Open your Veeam console.
      2. Select the Home tab, select Backup Copy, and select Virtual Machine.
      3. Enter a name for your backup job, and click Next.
      4. Click Add, and select the backup job that currently copies to AWS.
      5. Click OK, and click Next.
      6. Select the scale-out backup repository that you configured to use Backblaze B2, and click Next.
      7. Click Finish.

      Your backup job begins migrating your completed backups from AWS to Backblaze B2.

      Was this article helpful?
      Related articles
      What's Next