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

These operations depend on the type of the migration job. You can manage different types of migration jobs by performing the following steps.

Manage full migration and incremental migration jobs

  • View the status of a full or incremental migration job
    After a full or incremental migration job is created, it enters one of the following states:
    • Migrating. This state indicates that data is being migrated. Wait until the migration job is completed.
    • Create Failed. This state indicates that the migration job has failed to be created. You can view the cause of failure and create a migration job again.
    • Completed. This state indicates that the migration job is completed. You can view the migration report.
    • Failed. This state indicates that the migration job has failed. You can view the migration report and migrate the files again.
  • Modify the throttling settings of a migration job
    During migration, you can modify the throttling settings of a migration job based on your needs.
    1. In the Data Transport console, choose Data Online Migration > Migration Jobs. On the Migration Jobs page, find the migration job and click Manage.
    2. Click Stop and confirm that the job is stopped.
    3. On the Flow Control Time Schedule chart, click Reset.
      • To add a throttling setting, select an appropriate time range and maximum flow, and then click Add.
      • To delete a throttling setting, click abcd next to the throttling setting.
      • To modify a throttling setting, you must delete the current setting. Then, you can add a new throttling setting.
    4. Click OK and then click Start to restart the job.
  • View a migration report
    1. On the Migration Jobs page, find the migration job and click Manage.
    2. Click Generate Migration Report. After a report is generated, click Export to export the report.
      In a migration report, the following files appear in the File lists section:
      • The file whose name ends with _total_list. This file lists all files that need to be migrated.
      • The file whose name ends with _completed_list. This file lists the files that are migrated.
      • The file whose name ends with _error_list. This file lists the files that have failed to be migrated.
    3. In the Object Storage Service console, find the generated folder aliyun_mgw_import_report/. The folder includes the three files listed in the migration report. You can download the files and view the detailed list included in each file. We recommend that you use the ossbrowser tool to view these files.
      The file formats are described as follows:
      • For the file whose name ends with _total_list, the four columns of the file list include the source data address, file name, file size (measured in bytes), and time when a file is last modified. The format of a source data address: <vendor>://<bucketName>/<prefix>/<objectName>. Example: oss://bucket-test1022/myprefix/testfile.txt.
      • For the file whose name ends with _completed_list, the four columns of the file list include the file name, file size (measured in bytes), CRC-64 checksum, and time when a migration job is completed.
      • For the file whose name ends with _error_list, the four columns of the file list include the file name, time when a migration job starts, time when the migration job ends, and error description.
  • Retry a job after a migration failure

    If a migration job fails, you can check the generated file whose name ends in _error_list to identify the cause of failure and resolve the issue. On the Migration Jobs page, find the failed job, click Manage, and click Retry to migrate the files of the job again. For more information, see Common causes of a migration failure and solutions.

Manage synchronization jobs

  • View the status of a migration job
    A migration job enters one of the following states after being created:
    • Migrating. This state indicates that the migration job is in progress.
    • Stopped. If you click Manage next to a job and then click Stop on the Migration Report page, the status of the job changes to Stopped. This state indicates that the job stops after the current files are synchronized.
    • Create Failed. This state indicates that the migration job fails to be created. You can view the cause of failure and create a migration job again.
  • Manage migration jobs
    • View the details of a migration job: On the Migration Jobs page, click Manage to view the job details in the Basic, Schedule, and Flow Control Time Schedule sections.
    • Stop or start a migration job: On the Migration Report page, you can stop or start a migration job at any time.
    • View the history of a job: On the Migration Jobs page, find the job and click Check History to view the job history.
      After a migration job is completed, it enters one of the following states:
      • Scanning. This state indicates that the files of the source data address are being scanned. The number of scanned files is displayed in the File Count column.
      • Scan Finished. This state indicates that a scan is complete. The total number and size of files are displayed in the File Count and File Size columns.
      • Success. This state indicates that a synchronization job is completed. The number of synchronized files is displayed. You can click next to Download the report to download the list of files that have been synchronized.
      • Failed: An error may occur when you run a synchronization job. Click Retry to synchronize the files that fail to be synchronized again. You can click Download the report1 next to Failed to download the list of files that failed to be synchronized. You can view the details of the files and identify the failure cause. For example, one or more source files were deleted or lost during synchronization.