All Products
Search
Document Center

Data Online Migration:BIlling of the new version

Last Updated:Nov 27, 2023

This topic describes the billing of the new version of Data Online Migration.

Billable items

Overview

The following table describes the billable items of different source and destination types in different scenarios.

Important
  • If the data addresses are in the same region as the Data Online Migration console, you can use an internal or public endpoint.

  • If the data addresses and the Data Online Migration console are in different regions, you can use only an internal endpoint.

Migration type

Scenario

Traffic consumed to download data from the source data address

API requests sent to the source data address

API requests sent to the destination data address

Transfer acceleration

Alibaba Cloud Object Storage Service (OSS) to OSS

The source and destination data addresses are in the same region as the Data Online Migration console.

N/A

Charged

Charged

N/A

Only the source data address is in the same region as the Data Online Migration console.

N/A

Charged

Charged

Charged (only when enabled)

Only the destination data address is in the same region as the Data Online Migration console.

Charged

Charged

Charged

Charged (only when enabled)

The source and destination data addresses and the Data Online Migration console are in different regions.

Charged

Charged

Charged

Charged (only when enabled)

OSS to OSS across regions (We recommend that you enable transfer acceleration for the destination OSS bucket.)

N/A

Charged

Charged

Charged (only when enabled)

Note

You are charged for transfer acceleration only if data is migrated between OSS buckets across regions and transfer acceleration is enabled. In this case, you are charged by the destination OSS bucket.

Third-party storage service to OSS

Amazon Simple Storage Service (Amazon S3) to OSS

Charged

Charged

Charged

N/A

Qiniu Cloud Object Storage (KODO) to OSS

Charged

Charged

Charged

N/A

Tencent Cloud Object Storage (COS) to OSS

Charged

Charged

Charged

N/A

Other data sources to OSS

HTTP or HTTPS server to OSS

Charged

Charged

Charged

N/A

Billing scenarios

Migrate data between Alibaba Cloud OSS buckets

The following figure shows the billable items for data migration between Alibaba Cloud OSS buckets.1

Migrate data from HTTP or HTTPS servers to OSS

The following figure shows the billable items for data migration from HTTP or HTTPS servers to OSS.

image.png

Migrate data from third-party storage services to OSS

The following figure shows the billable item of migrating a third-party storage service to OSS. 1

Fees for API requests

API requests are sent when Data Online Migration compares the files at the source and destination data addresses, migrates data to the destination data address, and checks data integrity. The number of API requests varies based on the scenarios. This section describes how the number of API requests is calculated when a single file is migrated.

Important

The following rules for calculating the number of API requests apply only if your migration is successful.

The following API requests are sent to migrate a file that exists at the source data address but does not exist at the destination data address:

  • Source data address

    • A HeadObject request is sent to compare data before data is migrated.

    • A GetObject request is sent to obtain data.

  • Destination data address

    • A HeadObject request is sent to compare data before data is migrated.

    • A PutObject request is sent to upload data.

    • Important

      If the size of a file to be migrated is larger than or equal to 150 MB, the file is split into multiple parts before it is uploaded. The size of each part is 50 MB. The number of API requests that are required to upload the file is equal to the number of parts into which the file is split. For example, if you want to upload a file of 150 MB, three PutObject requests are sent because the file is split into three parts.

    • A HeadObject request is sent to check data integrity after data is migrated.

The following API requests are sent to migrate a file that has the same name at the source and destination data addresses:

  • Source data address

    • A HeadObject request is sent to compare data before data is migrated.

    • A GetObject request is sent to obtain data.

  • Destination data address

    • A HeadObject request is sent to compare data before data is migrated.

    • A PutObject request is sent to upload data.

    • Important

      If the size of a file to be migrated is larger than or equal to 150 MB, the file is split into multiple parts before it is uploaded. The size of each part is 50 MB. The number of API requests that are required to upload the file is equal to the number of parts into which the file is split. For example, if you want to upload a file of 150 MB, three PutObject requests are sent because the file is split into three parts.

    • A HeadObject request is sent to check data integrity after data is migrated.

The following API requests are sent to skip the migration of a file that has the same name at the source and destination data addresses:

  • Source data address

    A HeadObject request is sent to compare data before data is migrated.

  • Destination data address

    • A HeadObject request is sent to compare data before data is migrated.

    • A HeadObject request is sent to check data integrity after data is migrated.

Billing examples

For example, you want to create a migration task to migrate 1,000 files. The size of each file is smaller than 150 MB. Among the 1,000 files, 500 files have a unique name both at the source and destination data addresses and need to be migrated, 300 files have the same names at the source and destination data addresses and need to be migrated, and 200 files have the same names at the source and destination data addresses and do not need to be migrated. If the migration task succeeds, the following formulas are used to calculate the total number of API requests sent to the source data address and the total number of API requests sent to the destination data address:

  • Source data address: 500 × 2 + 300 × 2 + 200 × 1 = 1800

  • Destination data address: 500 × 3 + 300 × 3 + 200 × 2 = 2800

Note

You are charged for API requests based on the pricing of storage service providers. For more information about billing methods and billable items of OSS, see Billing overview.

Fees for restoring and retrieving data

Before you create a migration task to migrate data of the Archive storage class, you must manually restore the data. Take note of the following items when you restore the data:

  • Before you create a source data address and a migration task, make sure that data of the Archive storage class is restored.

  • Specify the number of days during which the restored data remains in the restored state based on the amount of data that you want to migrate. This can prevent data from entering the archived state during data migration.

  • You may be charged for the restoration operation. The fee may be relatively high. For more information about the billing methods, contact the service provider that offers the source bucket.

Note

Data Online Migration does not restore data in archived files at the source data address during data migration. The files that are not restored or are being restored cannot be migrated.

Fees for the traffic generated by data downloads and uploads

You are charged for the traffic that is generated when data is downloaded from the source data address and uploaded to OSS. The fees for the traffic that is consumed to download and upload the data vary based on the scenario.

Important

The following rules apply only if your migration is successful.

Migrate data from a third-party storage service

You are charged for downloading data from the source data address. The consumed traffic depends on the amount of data that you download. You are charged by the storage service provider that owns the source data address. You are not charged for uploading data to an OSS bucket within a specific bandwidth range. For more information, see Limits.

Migrate data from an OSS bucket to another OSS bucket within the same region

By default, data is migrated over an Alibaba Cloud internal network. You are not charged for downloading or uploading data.

Migrate data from an OSS bucket to an OSS bucket across regions

In this case, data is downloaded over an Alibaba Cloud internal network and uploaded over the Internet. You are not charged for downloading or uploading data.