Approaches and tools for migration

Migrating data from other cloud providers to IDrive® e2 cloud object storage platform is quite easy. The storage is S3 compatible hence you can use it with your existing tool or process without any additional software.

In the following sections we will explain the processes and the considerations you must make before selecting an approach that suits best for your budget.

Methods:

You can select from any of the following options for data migration:

  • All-Cloud Migration using a cloud-based migration tool.
  • Self-hosted Cloud Migration by connecting your current cloud provider to IDrive® e2 via a tool that is hosted by your organization.
  • Source Data Migration by moving data directly to e2 storage from the source, without involving your current cloud provider.
idrive e2

Migrate cloud data using rclone

Read related steps to transfer cloud data to IDrive® e2

Costs

The two major factors to be considered when selecting the migration approach are egress charges and cost of the migration tool.

Egress charges or limit - is levied on outbound data from your cloud i.e., fees for downloading or extracting data. Your current service provider may charge you some amount at their end for each GB of data you transfer out or they may have a per-day or per-month data egress limit.

Migration tool cost - This can be a one-time license fee, subscription-based fee, or a "consumption-based" fee for the amount of data flowing through the tool in addition to egress charges.

Considerations while planning your storage costs

1. Costs of moving data out from your current storage provider

Before deciding on which tool is best for you, how much will it cost to extract your data from your current cloud provider? Most public cloud object storage providers such as AWS, GCP, and Azure will charge you a fee (typically between $.01 and $.09 per GB) to extract (download or egress) data from their cloud. Run the numbers to know your budget estimate for this approach.

If the cost of downloading data from your current cloud provider is too high, you may want to consider uploading your source data to IDrive® e2 from the original data source (application or system), rather than through your current cloud provider. From a performance perspective, this can potentially take a long time depending on the size of the data set and your network connection to IDrive® e2, but you would avoid egress fees from your current cloud provider.

If you are trying to move data from a cloud storage provider that does not charge an egress fee, you should also make sure that this provider does not have a per-day or per-month data egress limit (some do). Check the fine print for all outbound traffic from your current cloud provider.

2. Evaluate the cost of using the migration tool itself

Certain migration tools operate on the cloud. They are hosted in a public cloud compute and you are not required to install the tool on your own hardware. The providers of these tools cover their compute and bandwidth costs and support their business by charging some sort of per-GB or per-TB transfer fees. These fees are calculated in addition to the cost of extracting the data from your current cloud provider.

If the cost of using a cloud-based tool is not feasible because of metered transfer fees, you could consider a self-hosted tool that you can deploy in your own environment. You may have to pay a license fee for access to the tool, but you can avoid the compute and bandwidth costs that factor into the cloud-based
tool fees.

To summarize, the following illustrations shed light on the cost points associated with migration from one cloud provider or a source data system to IDrive® e2. All approaches are valid ways to migrate data, the choice comes down to the one that meets your budget and the amount of time and effort it will take to move
the data.

All-Cloud Migration

IDrive e2

Self-hosted Cloud Migration

IDrive e2

Source Data Migration

IDrive e2

Solutions

You can consider the following approaches to select the right fit for your business needs. Please note that these suggestions are not universally applicable and may not be suited for you.

  • If the egress charges are too high, you may choose Source Data Migration instead of All-Cloud or Self-hosted Cloud Migration. This process will help you avoid high transfer fees but may be more time consuming depending on the size of data set and network connectivity.
  • If the migration tool is expensive, you can deploy a self-hosted tool to mitigate the compute and bandwidth costs associated with most cloud-based tools.

Supported migration tools

This section provides a list of common migration tools that can be used with IDrive® e2

Cloud hosted tools

  • Flexify.io
  • Couchdrop
  • Cloudflyer
  • CloudFuze
  • Cloudsfer

Self hosted tools

  • AWS CLI
  • Datadobi DobiMigrate
  • NetApp CloudSync
  • Nodeum
  • Scality Zenko
  • S3cmd