Note that by default this will create a folder on the destination with the same name as your job. Choose the source for what should be replicated to Backblaze, and set the destination as the S3 target. Navigate back to the Slingshot page to create a new replication job.ħ. Save the changes, allow a few moments for authentication to complete, and confirm a Volume ID is displayed to show registration was successful.Ħ. Under Region, select Custom host and provide the correct service URL (Endpoint) for your Backblaze region, and enter the bucket name as it appears in the Backblaze Console.Įnter the AccessKey (keyID) and SecretKey (applicationKey) generated in the Backblaze Console.ĥ. Give your Alias a name and select Amazon S3 as the schema.Ĥ. On the EVO web interface and navigate to the Slingshot > Settings > Aliases card.įor EVO Version 6.x: On the EVO web interface, navigate to the Slingshot > Aliases page.Ģ. Navigate to the B2 Cloud Storage > Buckets menu item, and note the Endpoint URL address for your bucket:įollow the steps outlined below to connect EVO to your Backblaze bucket.ġ. Copy your new application key, which will only appear once.ģ. The Application Key needs Read and Write access for the intended bucket.Ģ. Log in to the Backblaze account and navigate to My Account > App Keys to generate an Application Key for the bucket EVO should access (or refer to your existing key information, which is only displayed at time of creation). To use this product with Backblaze, please follow the instructions below.ġ. Backblaze has been validated for use with EVO. EVO shared storage by SNS enables a collaborative edit workflow for all major NLEs, as well as asset management and file automation tools to organize and ensure safety of data.

B2 cloud