This topic describes the usage notes and procedure for data migration.

Usage notes

When you perform an online migration job, take note of the following items:
  • A migration job occupies the network resources of the source and destination data addresses. To ensure business continuity, we recommend that you specify a rate limit for your migration job or run your migration job during off-peak hours.
  • Before an online migration job starts, the system checks the files at the source data address and the destination data address. If the source and destination have files with the same name, and the last modification time of the source file is later than the last modification time of the destination file, the destination file is overwritten. If both files are important and contain different information, we recommend that you change the name of one file or back up the destination file.
  • Data Online Migration allows you to migrate only the data of a single bucket per job. You cannot migrate all data that belongs to your account at a time.

Step 1: Create a source data address

  1. Log on to the Alibaba Cloud Data Transport console.
  2. In the left-side navigation pane, choose Data Online Migration > Data Address. On the page that appears, click Create Data Address.
  3. In the Create Data Address panel, configure the parameters and click OK. The following table describes the parameters.
    Parameter Required Description
    Data Type Yes Select QI NIU.
    Data Name Yes Enter a name. The name must be 3 to 63 characters in length. The name cannot contain special characters, except for hyphens (-) and underscores (_).
    Endpoint Yes Specify an endpoint that corresponds to the region where the specified bucket resides. The endpoint is in the http://<a Qiniu Cloud Integrated CDN (FUSION) test domain name> or http://<a custom FUSION accelerated domain name> format.

    To view the endpoint, perform the following steps: Log on to the Qiniu Cloud console. On the Object Storage page, find the bucket, and view the endpoint in the Test Domain column or the Accelerated Domain column.

    Notice A daily flow limit of 10 GB is set for FUSION test domains. If the size of data to be migrated exceeds 10 GB, we recommend that you migrate the data in batches or use FUSION accelerated domains. For more information, see Limits on test domains.
    Bucket Yes The name of the Qiniu Cloud Object Storage (KODO) bucket. Enter the custom name of the bucket. For example, if the bucket name is tony-1234567890, enter tony in the field.
    Prefix Yes
    • Migrate All Data: All data in the bucket is migrated.

      When you migrate all data, you do not need to specify a prefix.

    • Migrate Partial Data: Only the files in the directory that is specified by the prefix are migrated. The prefix must end with a forward slash (/). For example, you can specify data/to/oss/ as a prefix.
    Access Key and Secret Key Yes Specify the cloud API key that you want to use to migrate data. We recommend that you create an API key for the data migration job and delete the API key after the migration job is complete.
  4. Optional:If the system prompts that this feature is in public preview, click Application to apply to use this feature.
  5. Optional:Enter the required information and submit the application for the feature in public preview. After the application is approved, the system sends a text message to notify you.

Step 2: Create a destination data address

  1. In the left-side navigation pane, choose Data Online Migration > Data Address. On the page that appears, click Create Data Address.
  2. In the Create Data Address panel, configure the parameters and click OK. The following table describes the parameters.
    Parameter Required Description
    Data Type Yes Select OSS.
    Data Name Yes Enter a name. The name must be 3 to 63 characters in length. The name cannot contain special characters, except for hyphens (-) and underscores (_).
    Data Region Yes Select the region where the destination data address resides.
    Enable Transfer Acceleration No Before Data Online Migration uses the transfer acceleration feature provided by OSS, enable the transfer acceleration feature for OSS buckets. After you enable the transfer acceleration feature, the feature takes effect in 30 minutes. After the feature is enabled, wait for 30 minutes before you create a migration job.
    Notice If you use the transfer acceleration feature to access your OSS buckets, you are charged additional transfer acceleration fees. For more information, see Transfer acceleration.
    OSS Endpoint Yes
    Select an endpoint based on the region where your data is stored.
    • http://oss-cn-endpoint.aliyuncs.com: indicates that you use an HTTP-based endpoint to access OSS over the Internet.
    • https://oss-cn-endpoint.aliyuncs.com: indicates that you use an HTTPS-based endpoint to access OSS over the Internet.
    For more information, see Regions and endpoints.
    Note When you migrate data from third-party services to OSS, you must access OSS from an Internet endpoint.
    Access Key Id and Access Key Secret Yes Specify the AccessKey pair that you want to use to migrate data. For more information, see Prepare for a migration job.
    OSS Bucket Yes Select a bucket to store the migrated data.
    OSS Prefix No The OSS prefix cannot start with a forward slash (/), but must end with a forward slash (/). For example, you can specify data/to/oss/ as an OSS prefix. Do not configure this parameter if you want to migrate data to the root directory of the specified bucket.
    Notice If the name of a source file starts with a forward slash (/), you must specify an OSS prefix when you configure the destination data address. If no OSS prefix is specified, the migration job fails. For example, the name of a file to be migrated is /test/test.png. You must specify an OSS prefix. Example: oss/. After the migration job is complete, the name of the OSS file changes from /test/test.png to oss//test/test.png.

Step 3: Create a migration job

  1. In the left-side navigation pane, choose Data Online Migration > Migration Jobs. On the page that appears, click Create Job.
  2. In the Create Job panel, read the terms of the migration service and select I understand the above terms and conditions, and apply for opening data migration service. Then, click Next.
  3. In the Fee Reminder dialog box, click Yes, Go Ahead.
  4. In the Job Config step, configure the parameters and click Next. The following table describes the parameters.
    Parameter Required Description
    Job Name Yes Enter a job name. The name must be 3 to 63 characters in length and can contain only lowercase letters, digits, and hyphens (-). It cannot start or end with a hyphen (-).
    Source Data Address Yes Select the source data address that you created.
    Destination Data Address Yes Select the destination data address that you created.
    Specified Directory No Specify directories in which the files and subdirectories are migrated or not migrated.
    • Do not filter: All data from the source data address is migrated.
    • Exclude: The files and subdirectories in the specified directories are not migrated.
    • Contain: Only the files and subdirectories in the specified directories are migrated.
    Note
    • Before you configure the Specified Directory parameter, you must configure a whitelist. For more information, see Advanced features.
    • A directory name cannot start with a forward slash (/) or a backslash (\), and cannot contain double slashes (//), double periods (..), or double quotation marks ("). The character string that consists of all the specified directory names cannot exceed 10 KB in length.
    • A directory name must end with a forward slash (/). For example, you can specify docs/ as the directory name.
    • You can specify up to 20 directories of the Exclude or Contain type.
    Migration Type Yes Select the data migration mode.
    • Full: The system migrates all data from the source data address to the destination data address. You must configure the Start Time Point of File parameter. The system migrates all data whose last modification time is later than the specified time. After all data is migrated, the migration job ends.

      If you change the data at the source data address after the migration job is completed, you can submit another job to migrate all data. In this case, the system migrates only the changed data.

    • Incremental: The system runs a migration job based on the values that you specified for the Migration Interval and Migration Times parameters.
      • You must configure the Start Time Point of File parameter. During the first migration, the system migrates all data whose last modification time is later than the specified time. After the first migration job is completed, incremental migration jobs are performed based on the value that you specified for the Migration Interval parameter. For each incremental migration, the system migrates only the data that is created or modified after the previous migration starts and before the current migration starts.
      • If you set the Migration Times parameter to N, full migration is performed once and then incremental migration is performed (N - 1) times.

        For example, the current time is 08:00, March 10, 2019 and you set the Migration Interval parameter to 1, the Migration Times parameter to 5, and the Start Time Point of File parameter to 08:00, March 5, 2019. When the first migration starts, the system migrates all files whose last modification time is between 08:00, March 5, 2019 and 08:00, March 10, 2019. In this example, the first migration requires one hour to complete and the second migration starts at 10:00, March 10, 2019. The duration from 08:00 to 10:00 consists of one hour for the first migration process and one hour for the migration interval. During the second migration, the system migrates the files whose last modification time is between 08:00, March 10, 2019 and 10:00, March 10, 2019. The migration job consists of one full migration and four incremental migrations.

    Notice Before you start a full or incremental migration job, the system compares the files at the source data address with the files at the destination data address. If a source file has the same name as a destination file, the destination file is overwritten when one of the following conditions is met:
    • The Content-Type values of the source file and the destination file are different.
    • The last modification time of the source file is later than that of the destination file.
    • The size of the source file is different from that of the destination file.
    Start Time Point of File Yes Specify a time to filter data to be migrated. Data will be migrated if it is created or modified after the specified time.
    • All: All files are migrated.
    • Assign: Only the files that are created or modified after the specified time are migrated.

      For example, if you set the time to 08:00:00, November 1, 2018, only the files that are created or modified after 08:00:00, November 1, 2018 are migrated.

    Migration Interval This parameter is required when you set the Migration Type parameter to Incremental. The default value is 1 and the maximum value is 24. Unit: hours.
    Migration Times This parameter is required when you set the Migration Type parameter to Incremental. The default value is 1 and the maximum value is 30.
    File Overwrite Method Yes The method that is used to process the source file whose name is the same as that of a destination file. Valid values:
    • LastModified: If a source file has the same name as a destination file, the system compares the last modification time that is indicated by the LastModified property of the files.
      • If the last modification time of the source file is later than that of the destination file, the source file is migrated and the destination file is overwritten.
      • If the last modification time of the source file is earlier than that of the destination file, the source file is not migrated and the destination file is retained.
      • If the two files have the same last modification time, the system checks the values of the Size and Content-Type properties of the files.

        If the files have the same Size and Content-Type values, the source file is not migrated. If the two files have different values of at least one property, the source file is migrated and the destination file is overwritten.

    • Condition: If a source file has the same name as a destination file, the system compares the values of the LastModified, Size, and Content-Type properties of the two files.
      • If all property values of the two files are the same, the source file is not migrated.
      • If the two files have different values of at least one property, the source file is migrated and the destination file is overwritten.
    • All: If a source file has the same name as a destination file, the system performs no comparison and directly overwrites the destination file with the source file.
    • No: If a source file has the same name as a destination file, the system performs no comparison and directly skips the source file in the migration.
  5. On the Performance tab, go to the Data Prediction section and configure the Data Size and File Count parameters.
    Note To ensure that the migration job is successful, we recommend that you estimate the volume of data that you want to migrate. For more information, see Estimate the volume of data that you want to migrate.
  6. Optional:On the Performance tab, go to the Flow Control section, configure the Time Range and Max Flow(MB/s) parameters, and then click Add.
    Note To ensure service continuity, we recommend that you configure the Time Range and Max Flow parameters based on the workloads during peak hours and off-peak hours.
  7. Click Create and wait until the migration job is complete.

FAQ

What do I do if the migration speed is lower than expected?
  1. Check whether you use a FUSION test domain of Qiniu Cloud. We recommend that you use FUSION accelerated domains instead of test domains to create migration jobs. Test domains have limits on bandwidth and the number of visits from a single IP address.
  2. Check the application scenario of your domain. The available bandwidth varies based on the application scenarios of Qiniu Cloud domains. For example, low bandwidth is allocated if you select websites as the application scenario of a domain. In this scenario, if you specify the domain as the endpoint of the source data address, the transmission speed for data migration is low due to the low bandwidth. Submit a ticket to Qiniu Cloud to change the application scenario of the domain.