This topic describes the procedure for data migration.

Notes

When you perform an online migration, take note of the following issues:
  • 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.

Step 1: Create a source data address

  1. Log on to the Alibaba Cloud Data Transport console.
  2. Choose Data Online Migration > Data Address, and click Create Data Address.
  3. In the Create Data Address panel, configure the following parameters and click OK.
    Parameter Required Description
    Data Type Yes Select OSS.
    Data Region Yes Select the region where the source data address is located, such as China (Zhangjiakou).
    Data Name Yes Enter a name that is 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.
    • http://oss-cn-endpoint.aliyuncs.com: indicates that you use an HTTP-based endpoint to access Object Storage Service (OSS) over the Internet.
    • https://oss-cn-endpoint.aliyuncs.com: indicates that you use an HTTPS-based endpoint to access OSS over the Internet.
    • http://oss-cn-qingdao-internal.aliyuncs.com: indicates that you use an internal HTTP-based endpoint to access OSS.
    • https://oss-cn-qingdao-internal.aliyuncs.com: indicates that you use an internal HTTPS-based endpoint to access OSS.
    For more information, see Endpoint.
    Notice Assume that an OSS data address uses an internal endpoint and is used as the source data address when you create a migration job. In this case, the destination data address can only be a Network Attached Storage (NAS) or OSS data address in the same region.
    Access Key Id and Access Key Secret Yes Specify the AccessKey pair that is used to migrate data. For more information, see Create and authorize a RAM user.
    OSS Bucket Yes Select the bucket that stores the data to be migrated.
    OSS Prefix Yes An OSS prefix cannot start with a forward slash (/) and must end with a forward slash (/). For example, you can specify data/to/oss/ as the OSS prefix.
  4. Optional:If the system prompts that this feature is in the public preview, click Application to submit a whitelist permission application.
  5. Enter the required information and submit the application for public preview. 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 panel, configure the parameters and click OK.
    Parameter Required Description
    Data Type Yes Select NAS.
    Data Region Yes Select the region where the NAS file system is located.
    Data Name Yes Enter a name that is 3 to 63 characters in length. Special characters are not supported, except for hyphens (-) and underscores (_).
    NAS Type Yes Select Alibaba Cloud.
    File System Yes Select the corresponding NAS file system.
    Mount Point Yes Select the mount point of the NAS file system.
    Notice You can mount a NAS file system only within a virtual private cloud (VPC). The classic network is not supported.
    Sub Folder Optional Select a subdirectory to store migrated data. If you do not set this parameter, the default value is the root directory (/).
    Notice If you specify a subdirectory, you must make sure that the subdirectory exists on the NAS server. Otherwise, the data address fails to be created.
    Note For more information about the status of a new data address, see Data address status.

Step 3: Create a migration job

  1. Choose Data Online Migration > Migration Jobs, and click Create Job.
  2. In the Create Job panel, read the Terms of Migration Service and select I understand the above terms and conditions, and apply for opening data migration service. Click Next.
    Then, the Fee Reminder dialog box appears.OSS_billing request
  3. On the Job Config tab, configure the parameters and click Next.
    Parameter Required Description
    Job Name Yes Enter a name that is 3 to 63 characters in length. The name 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 have created.
    Destination Data Address Yes Select the destination data address that you have created.
    Notice The source data address may be located in a different country than the destination data address. In this case, before you configure the migration job, you must submit a ticket to request permissions to create cross-country migration jobs. You must commit that your business is legitimate, data transit conforms to local rules and regulations, and your data does not contain illegal information.
    Specified Directory No
    • Do not filter: All the 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, you can specify docs/ as the directory.
    • You can specify a maximum of 20 directories of the Exclude or Contain type.
    Migration Type Yes
    • Full: The system runs a full migration job. You must specify the Start Time Point of File parameter. The system migrates the data whose last modification time is later than the specified start time at one time. After all data is migrated, the migration job is closed. You can submit the job again if the data at the source data address changes. In this case, the system migrates only the data that is changed after the previous job.
    • Incremental: The system runs the migration job based on the specified Migration Interval and Migration Times parameters. You must specify the Start Point Time of File parameter. During the first migration, the system migrates the full data that is modified after the specified start time. After the first migration is complete, incremental migrations are performed based on the specified Migration Interval parameter. For each incremental migration, the system migrates only the data that is created or modified after the previous migration started and before this migration starts. If you set Migration Times to N, full migration is performed once and then incremental migration is performed (N - 1) times. For example, you set Migration Interval to 1 hour, Migration Times to 5, and Start Time Point of File to 08:00, March 5, 2019. The current time is 08:00, March 10, 2019. When the first migration starts, the system migrates the files that are last modified between 08:00, March 5, 2019 and 08:00, March 10, 2019. Assume that the first migration requires 1 hour to complete. In this case, the second migration starts at 10:00, March 10, 2019. The two hours from 8:00 to 10:00 include the 1 hour time that the first migration requires and the migration interval of 1 hour. During the second migration, the system migrates the files that are last modified between 08:00, March 10, 2019 and 10:00, March 10, 2019. The migration job includes one full migration and four incremental migrations.
    • Sync: The system synchronizes the data from the source data address to the destination data address. A synchronization job continues to run based on the specified Job Period parameter until you stop the job. When a synchronization job is performed for the first time, data is synchronized based on the specified Start Time Point of File parameter. After the first synchronization is complete, the system synchronizes the files whose last modification time is later than the start time of the last synchronization each time a synchronization interval ends. Assume that the first synchronization is performed at 08:00, November 01, 2018. For the second synchronization, files that are created or modified after 08:00, November 01, 2018 are synchronized.
    Notice
    • You can select Sync only if the source data address and the destination data address are located in the same region. Otherwise, this option is unavailable.
    • Before you start a migration job of the Full, Incremental, or Sync type, the system compares files at the source data address with those 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 source file has a later last modification time than the destination file.
      • The size of the source file is different from that of the destination file.
    Start Time Point of File Yes (only for full and incremental migrations)
    • 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 start time to 08:00:00, November 01, 2018, only the files that are created or modified after 08:00:00, November 01, 2018 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.
    Start Time Point of File Yes (only for data synchronization)
    • All: All files are synchronized.
    • Assign: Only the files that are created or modified after the specified time are synchronized. For example, if you set the start time to 08:00:00, November 01, 2018, only the files that are created or modified after 08:00:00, November 01, 2018 are synchronized. Files that are created or modified before the specified time are skipped.
    Start Time of Job Yes (only for data synchronization)
    • Immediately: The system synchronizes the data immediately after the migration job is created.
    • Schedule: The system synchronizes the data at the scheduled time.
    Job Period Yes (only for data synchronization) The time interval between two synchronization jobs. A synchronization job starts each time an interval ends. Valid units: hour, day, and week.
    Don't trigger new task if another task running Yes (only for data synchronization) Specify whether to start a new synchronization job if the last synchronization job is still running when the synchronization interval ends. You must use this parameter together with Job Period. Assume that Job Period is set to 1 hour and this parameter is not selected. In this case, the next synchronization job runs regardless of whether the last synchronization job is completed within 1 hour. This parameter is selected by default.
  4. Click Next. The Performance tab appears.
    • If you select Full or Incremental for the job type, specify the Data Size and File Count parameters.
      Note To ensure a successful migration, estimate the amount of data to be migrated as accurately as possible. For more information, see Estimate the amount of data to be migrated..
    • If you select Sync for the job type, specify the Subtask file count and Subtask file size parameters.
      • Subtask file count: A migration job can be divided into multiple subtasks based on the specified Subtask file count parameter. A maximum of 20 subtasks can run at a time. Set an appropriate number of files for each subtask to reduce the amount of time that is required to run a migration job. The default value is 1000. Assume that you need to migrate 10,000 files. If you set the Subtask file count parameter to 500, the migration job is divided into 20 subtasks that run at the same time. If you set the Subtask file count parameter to 100, the migration job is divided into 100 subtasks. Each time the system migrates the files, 20 subtasks run at the same time and the remaining subtasks are queued.
      • Subtask file size: A migration job can be divided into multiple subtasks based on the specified Subtask file size parameter. A maximum of 20 subtasks can run at a time. Set an appropriate size of files for each subtask to reduce the amount of time that is required to run a migration job. The default value is 1 GB. Assume that you need to migrate files with a total size of 40 GB. If you set the Subtask file size parameter to 2 GB, the migration job is divided into 20 subtasks that run at the same time. If you set the Subtask file size parameter to 1 GB, the migration job is divided into 40 subtasks. Each time the system migrates the files, 20 subtasks run at the same time and the remaining subtasks are queued.
      Note Subtasks are generated when the specified Subtask file count or Subtask file size parameter value is reached. If the specified Subtask file count parameter value is reached but the specified Subtask file size parameter value is not reached, subtasks are generated based on the number of files. If the specified Subtask file count parameter value is not reached but the specified Subtask file size parameter value is reached, subtasks are generated based on the file size. Assume that you set the Subtask file count parameter to 1000 and the Subtask file size parameter to 1 GB. If the number of files reaches 1,000 but the file size does not reach 1 GB, subtasks are generated based on the number of files. If the file size reaches 1 GB but the number of files does not reach 1,000, subtasks are generated based on the file size.
  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 workload peaks and troughs.
  6. Click Create and wait until the migration job is completed.

View the status of a data address

After you create a NAS data address, one of the following states is displayed for the data address:
  • Normal: The data address is created.
  • Creating: It takes time to create the first NAS data address. Wait for about 3 minutes. If the state of the data address remains Creating for a long time, you can click Refresh in the upper-right corner to update the status.
  • Invalid: An error has occurred when you create the data address. You can verify the configuration information and check whether Data Online Migration is allowed to access the NAS service. If this issue persists, you can contact Alibaba Cloud technical support.