Amazon S3 to Backblaze B2 storage migration
Backblaze has recently released their support for the S3 protocol to access and work with their B2 storage offering that was previously only accessible via their proprietary access protocol. Due to these changes it has opened Backblaze B2 up to the world and enabled their customers to work with their data using the versatile protocol S3. These changes are a positive step in the right direction for Backblaze which has led to an opportunity to compete with the others in the storage market.
When moving into a cost-effective solution such as Backblaze, it can provide difficult to migrate your large sums of data, as you can’t easily simply ‘sync’ it up or drag and drop into your new bucket.
To migrate into Backblaze B2 there are solutions out there such as Rclone that has been favoured by many engineers over the years to move and sync data between storage platforms. As easy, simple and free as Rclone is, it does have its limitations, such as; no reporting or error handling, no ability to significantly improve performance or on-demand support, as well you lack the granular control and visibility that dedicated tools provide.
When you want more control and that extra oomph, this is when Movebot comes into play. Fully cloud native, that you can set up and walk away, as well increase performance, get support and operate without the hassle of a command line tool. Compared to Rclone Movebot does charge per GB, however due to Backblaze’s affordable rates, the savings will make migrating from S3 will be paid off in only a few months.
Ignore Movebot’s website pricing as when it comes to object storage migrations, their pricing is heavily reduced and has the ability to remove egress costs when migrating from Amazon, Azure or Google Cloud. Pricing for Object Storage migrations start from 12 cents per GB and can scale down to only a few cents with volume. Contact the team for a quote.
Movebot provides full logging, governance and reporting on your data so you know what makes it across, and what doesn’t and why. As well you can see a breakdown of the data and its structure.
Migrating from Amazon (AWS) S3 to Backblaze B2 is straightforward and can be up and going in less than a minute. Below we will do a quick guide on how to migrate to Backblaze B2 using Movebot.
Once you have created a Movebot account and you are at the dashboard, click on create in the top right corner (you can user the project manager for multiple bucket migrations).
You’ll be taken to configure Amazon S3 (or another provider) as your source platform. You’ll just need your API keys, you can enter your specific Amazon S3 bucket if you like. If you don’t enter a bucket you will be able to choose a bucket under folders. Click Next Step
Now select Backblaze B2 from the dropdown. Work through the configuration requirements (your Key ID, Master Key and Bucket ID) then click Next Step.
You can now select specific folders if you would prefer or to move everything across (one to one), don’t tick anything. Simply tick the bucket within the source and click Next Step.
You now have the additional settings where you can enable the migration as a delta, increase compute nodes and choose the region you want the migration to take place. When ready you can either Save and Kickoff or kick off a preflight scan under the menu button at the bottom.
The migration will work through the calculating stage (finding out how much data you have), the transferring stage and the post-migration stage which will finalize your data and check all is well.
For a more detailed migration guide and other guides on and information on Movebot features and cloud data migrations, head to community.movebot.io
Related Posts
Originally published at https://www.movebot.io.
