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

Subsequent operations vary with the types of migration jobs. You can manage migration jobs of different types as follows.

Manage full migration and incremental migration jobs

  • View the status of a migration job
    After you create a migration job, one of the following states is displayed for the job:
    • 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 failed to be created. You can view the cause of the failure and create a new migration job.
    • Completed. This state indicates that the migration job is completed. You can view the migration report.
    • Failed. This state indicates that a migration job fails. You can view the migration report and remigrate the files that failed to be migrated.
  • Modify flow control settings
    During migration, you can modify flow control settings at any time based on your needs.
    1. In the Data Transport console, choose Data Online Migration > Migration Jobs. On the Migration Jobs page, find a migration job and click Manage.
    2. Click Stop and ensure that the job is stopped.
    3. On the Flow Control Time Schedule chart, click Reset.
      • To add a flow control setting, select an appropriate time range and maximum flow, and click Add.
      • To delete a flow control setting, click Delete next to the flow control setting.
      • To modify a flow control setting, you must delete the previous setting and add a new flow control setting.
    4. Click OK and click Start to restart the job.
  • View a migration report
    1. On the Migration Jobs page, find the required 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 contains a list of all files that need to be migrated.
      • The file whose name ends with _completed_list. This file contains a list of files that are migrated.
      • The file whose name ends with _error_list. This file contains a list of files that failed to be migrated.
    3. In the OSS console, find the generated folder aliyun_mgw_import_report/. The folder includes the three files that appear 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 failed migration job

    If a migration job failed, you can view the generated file whose name ends with _error_list to identify the cause of the failure and troubleshoot the issue. On the Migration Jobs page, find the failed job, click Manage, and click Retry to remigrate the files that failed to be migrated. For more information about FAQ for migration failures, see Common causes of a migration failure and solutions.

Manage synchronization jobs

  • View the status of a synchronization job
    After you create a synchronization job, one of the following states is displayed for the job:
    • Migrating. This state indicates that the synchronization job is in progress.
    • Stopped. If you click Manage next to a job to enter the Migration Report page and then click Stop, the status of the job changes to Stopped. This state indicates that the job stops after the synchronization of the current files is complete.
    • Create Failed. This state indicates that you failed to create the synchronization job. You can view the cause of the failure and create a new synchronization job.
  • Manage synchronization jobs
    • View the details of a synchronization 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 synchronization job: On the Migration Report page, you can stop or start a synchronization job at any time.
    • View the history of a job: On the Migration Jobs page, find the required job and click Check History to view the job history.
      After a synchronization job is completed, one of the following states is displayed for the job:
      • 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, respectively.
      • Success. This state indicates that a synchronization job is completed. The number of synchronized files is displayed. You can click Download the report next to Completed to download the list of files that have been synchronized.
      • Failed: An error may occur when you run a synchronization job. Click Retry to resynchronize the files that failed to be synchronized. You can click Download the report 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 causes of the failure. For example, source files are deleted or lost during migration.