<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=348068&amp;fmt=gif">




Simple Object Storage Migrations

Posted by Jayden @ Movebot on Sep 22, 2020 4:58:30 PM
Jayden @ Movebot

Migrating data between object storage platforms is difficult and can take a lot of time. This post will cover how to migrate data between two object storage endpoints, whether it is Amazon S3, Azure Blob, IBM S3, Dell EMC, Wasabi, Cloudian, GCP or anything in between using Movebot. 

 

In reality, if you have your bucket names and API keys ready to go, this will take less than a minute. 

object s3 storage migrations


Step 1: Create a Movebot account

Navigate to https://admin.movebot.io/register and create an account, it'll only take a minute. Once your account is created you will be taken into your Movebot dashboard.

create movebot account

 

 

 

Step 2: Create a migration

Click Create once at the dashboard

Create an object storage migration

 

 

Step 3: Add source platform

Here you can select from the list of available options, if an S3 compatible option isn't displayed, then select S3 Compatible and fill out the required fields.

When you've worked through the fields (bucket name, API keys, etc.) click Next Step.

s3 object storage migration

 

 

Step 4: Add destination platform

Once again you can select from the list of available options, if an S3 compatible option isn't displayed, then select S3 Compatible and fill out the required fields.

When you've worked through the fields (bucket name, API keys, etc.) click Next Step.

amazon s3 migration

 

 

Step 5: Select Buckets/Folders

If working with Amazon S3 and you don't enter a specific bucket name, all buckets become available (see destination side of image below). Otherwise, folders within your buckets are available and can be drilled into further. Click Next Step once you've selected your bucket combination

object storage migration bucket selection

 

 

Step 6: Settings and Advanced Options

Movebot is fully customizable right down to the region the migration is run from and how many worker nodes you wish to run on each individual migration. You can also enable a delta migration or schedule the migration for a replication job.

Either Save and Kickoff when you are ready or click the ellipsis for other options (such as a preflight scan).

s3 migration settings

 

 

Step 7: The Migration

Once you've kicked off the migration it will standup the worker nodes required to begin migrating your data. The process will work through three stages; Calculating, Migrating, Post-Check. You can monitor your migration via logs,  by the dashboard or by the available status screen for the individual migration.

Object storage migration  discovery scan

 

 

Hot Tip

If you need to recreate multiple object storage migration jobs from the same configuration, you can click under the dashboard "copy and edit" and this will clone the job for you to then edit the folders/buckets as required.

configuring s3 object storage migrations

 

 

For any help or assistance, or for more information please don't hesitate to reach out to our Movebot humans, or visit our website and knowledge base.

 

 

Related Posts

 

Topics: Object Storage, Wasabi, Data Lake, Cloud Storage, On-Premise, Backblaze, s3, cloudian, data center, ibm, netapp, dell emc, aws, gcp, azure