Veeam Backups Migration from AWS S3 to 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. 

1. Sign in to the Backblaze web console.
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.
   Note

   You can change a bucket's privacy settings at any time.
   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. If this is your first time creating a public bucket, complete the following tasks to ensure that you have the correct permissions to create a public bucket:
   
   1. Verify your email address.
   2. Have a payment history on file, or use the credit card form to pay a small fee that is credited to your account balance.
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 later.
9. Click Lifecycle Settings to control how long to keep the files in your new bucket.

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.
   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 select a specific bucket in the Allow Access to Bucket(s) menu.
5. Optionally, select your access type (Read and Write, Read Only, or Write Only).
6. Optionally, select Allow List All Bucket Names.
   This option is 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.

Add Object Lock to a New Bucket

1. Enable Object Lock on the bucket that you want to use.
2. Create a new bucket-restricted application key.
3. Configure Veeam to use the application key.
4. Set the bucket as a destination.

Add Object Lock to a Bucket Already Used by Veeam

1. Enable Object Lock on the bucket that is already used by Veeam.
2. Create a new bucket-restricted application key.
3. Configure Veeam to use the new application key on the bucket.