All Products
Search

This Product

    Data Online Migration:Subsequent operations

    Document Center

    Data Online Migration:Subsequent operations

    Last Updated:Jan 17, 2024

    This topic describes the operations that you can perform after you create a migration task.

    View the status of a migration task

    After you create a migration task, one of the following states is displayed for the task:

    • Created: The migration task is created. You can manually start the migration task or wait until the system starts the migration task at the specified start time.

    • Started: The migration task is created and started. The task is waiting to be scheduled.

    • Preparing: The data is being preprocessed.

    • Migrating: The data is being migrated. Wait until the migration task is complete.

    • Deleting: The migration task is being deleted. After the migration task is deleted, the task is removed from the task list.

    • Paused: The migration task is paused.

    • Closed: The migration task is being closed. After the migration task is closed, the task enters the Finished state.

    • Finished: The migration task is complete.

    View migration logs

    You can view the logs of finished migration tasks in the Simple Log Service console. You can use filter conditions such as the task name, task ID, Alibaba Cloud account ID, or file name to search for logs of migration tasks.

    Important

    The logs of a migration task are pushed to Simple Log Service only if you set the Migration Logs parameter to Push or Push only file error logs when you create the migration task. If you set the Migration Logs parameter to Do not push when you create a migration task, the logs of the migration task are not pushed to Simple Log Service.

    Data Online Migration creates projects in Simple Log Service to store migration logs. The name of a project is in the aliyun-oss-import-log-Alibaba Cloud account ID-ID of the region selected in the Data Transport console format. Example: aliyun-oss-import-log-137918634953****-cn-hangzhou. You can view the logs of migration tasks in the corresponding project. The following two types of logs are stored:

    • drs_import_success_log: the logs about files that are migrated.

    • drs_import_fail_log: the logs about files that failed to be migrated.

    The following table describes the fields in migration logs.

    Field

    Description

    JobName

    The name of the migration task.

    JobId

    The ID of the migration task.

    Region

    The region that is selected in the Data Transport console.

    Status

    The status of the file. Valid values:

    • succeed: The file is migrated.

    • skipped: The file is skipped.

      Note

      In one of the two following scenarios, a file is skipped:

      • The source file does not exist because it has been deleted.

      • The system skips the file based on the overwrite policy.

    • failed: The file failed to be migrated.

    UserId

    The ID of the user.

    ExecuteId

    The ID of the execution record.

    StartTime

    The time when the migration started.

    EndTime

    The time when the migration finished.

    ListTime

    The time when the file was scanned.

    Time

    The current time.

    SrcObjectName

    The name of the source file. The fields whose names start with Src are the fields about the source file.

    Note

    The file name is URL-encoded. Example: docs%2Fmy.docir%2Fexample.log.

    SrcObjectSize

    The size of the source file.

    DestObjectName

    The name of the destination file. The fields whose names start with Dest are the fields about the destination file.

    Note

    The file name is URL-encoded. Example: docs%2Fmy.docir%2Fexample.log.

    DestObjectSize

    The size of the destination file.

    Modify the throttling settings

    During data migration, you can modify the throttling settings of a migration task based on your business requirements.

    1. Log on to the Data Transport console.

    2. In the top navigation bar, select the region in which your migration task is created.

    3. In the left-side navigation pane, choose Data Online Migration > Migration Tasks.

    4. On the Migration Tasks page, find the migration task for which you want to modify the throttling settings and click Manage in the Actions column to go to the task details page.

    5. In the Configurations section, click Reset next to Maximum Migration Bandwidth.

    6. In the dialog box that appears, modify the maximum migration bandwidth.

      • Default: By default, the maximum bandwidth is 1 Gbit/s. The actual speed is based on the file size and the number of files.

      • Specify an upper limit: Specify the maximum bandwidth, which can be up to 2 Gbit/s.

    7. Click OK.

    Modify the maximum number of files to be migrated per second

    During data migration, you can modify the maximum number of files to be migrated per second based on your business requirements.

    1. Log on to the Data Transport console.

    2. In the top navigation bar, select the region in which your migration task is created.

    3. In the left-side navigation pane, choose Data Online Migration > Migration Tasks.

    4. On the Migration Tasks page, find the migration task for which you want to modify the maximum number of files to be migrated per second and click Manage in the Actions column to go to the task details page.

    5. In the Configurations section, click Reset next to Maximum Files That Can Be Migrated Per Second.

    6. In the dialog box that appears, modify the maximum number of files to be migrated per second.

      • Default: By default, 1,000 files are migrated per second. The actual speed is based on the file size and the number of files.

      • Specify an upper limit: Specify the maximum number of files to be migrated per second, which can be up to 2,000 files per second. If you want to migrate more files per second, contact technical support.

    7. Click OK.

    Migrate incremental files

    You can perform the following steps to migrate incremental files:

    1. Log on to the Data Transport console.

    2. In the top navigation bar, select the region in which your migration task is created.

    3. In the left-side navigation pane, choose Data Online Migration > Migration Tasks.

    4. On the Migration Tasks page, find the migration task that you want to start and click Started in the Actions column to start the migration task.

      You can also click Manage in the Actions column to go to the task details page. In the History section, click Started in the Actions column of the migration task to start the migration task.

    Rerun a failed migration task

    If some files fail to be migrated in a migration task, you can migrate the failed files again.

    1. Log on to the Data Transport console.

    2. In the top navigation bar, select the region in which your migration task is created.

    3. In the left-side navigation pane, choose Data Online Migration > Migration Tasks.

    4. On the Migration Tasks page, find the migration task for which you want to migrate the failed files and click Manage in the Actions column to go to the task details page.

    5. In the History section, click Retry in the Actions column of the migration task to rerun the migration task.

    6. Modify the name of the subtask and click Next.

    7. After you confirm the settings of parameters such as Migration Bandwidth, Files Migrated per Second, and Overwrite Mode, click Next.

    8. Click OK. The subtask is started and the failed files are migrated again.