This topic describes the procedure for creating a migration job and the considerations.

Considerations

When you create a migration job, you must note the following considerations:

  • A migration job occupies the network resources of the source data address and destination data address. To ensure business continuity, we recommend that you specify a speed limit for a migration job or perform the migration job during off-peak hours.
  • Before a migration job is performed, files at the source data address and the destination data address are checked. The files at the destination data address are overwritten if the source files have the same name as the destination files and have a later modification time. If two files have the same name but different content, you must change the name of one file or back up the files.
  • Each migration job only allows you to migrate data from all versions of a single bucket. You cannot migrate all data in your account at a time. Data migration for each version is uniquely identified by the file name and version number.

Step 1: Create a source data address

  1. Log on to the Data Transport console.
  2. Choose Data Online Migration > Data Address, and click Create Data Address.
  3. In the Create Data Address dialog box, configure the parameters and click OK.
    Parameter Required Description
    Data Type Yes Select AWS S3.
    Data Name Yes A data name must be 3 to 63 characters in length. Special characters are not supported, except for hyphens (-) and underscores (_).
    Endpoint Yes Enter the region where the source address is located. For more information, see Regions and endpoints.
    Bucket Yes Enter the name of an AWS Simple Storage Service (AWS S3) bucket.

    The bucket name cannot contain invalid characters such as space, line feed, and tab.

    Prefix Yes
    • Migrate all data: indicates that all data in a bucket is migrated.

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

    • Migrate partial data: indicates that only files in a specified directory (directory prefix) are migrated. A prefix cannot start with a forward slash (/) and must end with a forward slash (/), for example, docs/.
    Access Key Id and Secret Access Key Yes Enter the AccessKey pair that is used to migrate data. Delete the pair after the migration.
    Use VPC Yes When Virtual Private Cloud (VPC) is used, a private IP address within the VPC network is occupied.
  4. You must apply for whitelist permissions because this feature is in the public preview phase. Click Application.
  5. Enter the required information and submit the application for using this feature. After the application is approved, you will receive a short message service (SMS) notification.

Step 2: Create a destination data address

  1. Choose Data Online Migration > Data Address, and click Create Data Address.
  2. In the Create Data Address dialog box, configure the parameters and click OK.
    Parameter Required Description
    Data Type Yes Select OSS.
    Data Region Yes Select the region where the destination data address is located.
    Data Name Yes A data name must be 3 to 63 characters in length. Special characters are not supported, except for hyphens (-) and underscores (_).
    OSS Endpoint Yes
    Select an endpoint based on the region where your data is located.
    • You can use the following HTTP-based endpoint to access OSS from the Internet: http://oss-cn-endpoint.aliyuncs.com.
    • You can also use the following HTTPS-based endpoint to access OSS from the Internet: https://oss-cn-endpoint.aliyuncs.com.
    For more information about OSS endpoints, see Regions and endpoints.
    Note When migrating third-party data to OSS, you can only access OSS from an Internet endpoint.
    AccessKeyId and AccessKeySecret Yes Enter the AccessKey pair that is used to migrate data. For more information, see Create an AccessKey pair.
    OSS Bucket Yes Select a bucket to store the migrated data.
    OSS Prefix No An OSS prefix cannot start with a forward slash (/) and must end with a forward slash (/), for example, data/to/oss/. Do not specify the parameter if you want to migrate data to the root directory of a bucket.
    Notice If the name of a source file starts with a forward slash (/), you must specify an OSS prefix. If no OSS prefix is specified, the migration job will fail. Assume that the name of a file to be migrated is /test/test.png. You must specify an OSS prefix, for 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. Choose Data Online Migration > Migration Jobs, and click Create Job.
  2. In the Create Job dialog box, read the Terms of Migration Service, select I understand the above terms and conditions, and apply for opening data migration service, and then click Next.
    Then, the Fee Reminder dialog box appears.OSS_billing request
  3. In the Create Job dialog box, configure the parameters and click Next.
    Parameter Required Description
    Job Name Yes A job name must be 3 to 63 characters in length and can contain lowercase letters, digits, and hyphens (-). It cannot start or end with a hyphen (-).
    Source Data Address Yes Select the source data address that you have created.
    Destination Data Address Yes Select the destination data address that you have created.
    Notice If the source data address and the destination data address are located in different countries or regions, you must submit a ticket to request permissions to create a cross-country or cross-region migration job. You must ensure that your business is legitimate, data transit conforms to local rules and regulations, and data does not include illegal information.
    Specified Directory No
    • Do not filter: All data at the source data address is migrated.
    • Exclude: The files and subdirectories in the excluded directories are not migrated.
    • Contain: Only the files and subdirectories in the specified directories are migrated.
    Note
    • A directory 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 size.
    • A directory must end with a forward slash (/), for example, docs/.
    • You can specify a maximum of 20 directories of the Exclude or Contain type.
    Migration Type Yes
    • Full: You can specify the Start Time Point of File parameter. Files with the last modification time later than the specified start time point will be migrated. After the files are migrated, the migration job is closed. When you repeat a full migration job, each migration job only migrates files that have been changed.
    • Incremental: You must specify the Migration Interval and Migration Times parameters to perform an incremental migration job. You must specify the Start Point Time of File parameter. Files with the last modification time later than the specified start time point are migrated during the first migration. After the first migration is complete, an incremental migration is performed based on the migration interval. An incremental migration job only migrates files that are created or modified after the previous migration started and before this migration starts. Assume that you specify N for Migration Times. Full migration is performed once. Incremental migration will be performed (N - 1) times. For example, you can set the migration interval to 1, the migration times to 5, and the start time point to 2019/03/05 08:00. The present time is 2019/03/10 08:00. When the first migration starts, each migration job migrates files that are modified between 2019/03/05 08:00 and 2019/03/10 08:00. Assume that the first migration requires one hour to complete. The second migration starts at 2019/03/10 10:00. The two hours include the amount of time it takes to complete the first migration (1 hour) and the migration interval (1 hour). During the second migration, if the last modification time of files is between 2019/03/10 08:00 and 2019/03/10 10:00, these files are migrated. The migration job includes a full migration and four incremental migrations.
    Notice Before a full migration job or an incremental migration job starts, each migration job compares files of the source data address with those of 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 types of the source file and the destination file are different.
    • The source file is updated after the previous migration.
    • The size of the source file is different from that of the destination file.
    Multi-version Migration Yes
    • Do not use: Keep single-version migration (default value).
    • Use: Use multi-version migration.
      After you enable multi-version migration, the following dialog box appears, asking you to enable multi-version migration for the destination data address.Enable multi-version migration
    Start Time Point of File Yes
    • All: All files are migrated.
    • Assign: Files that are created or modified after the specified time are migrated. For example, if you set the start time point to 2018/11/01 08:00:00, only files that are created or modified after 2018/11/01 08:00:00 are migrated. Files that are created or modified before the specified time are skipped.
    Migration Interval Yes (only for incremental migration) The default value is 1 hour and the maximum value is 24 hours.
    Migration Times Yes (only for incremental migration) The default value is 1 and the maximum value is 30.
  4. On the Performance tab, navigate to the Data Prediction section and specify the Data Size and File Count parameters.
    Note An accurate estimation of the data size helps you migrate data as expected. For more information, see Estimate the amount of data to be migrated.
  5. Optional. On the Performance tab, navigate to the Flow Control section, specify the Time Range and Max Flow parameters, and then click Add.
    Note To ensure business continuity, we recommend that you specify the Time Range and Max Flow parameters based on the fluctuation of workloads.
  6. Click Create and wait until the migration job is complete.