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

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. The migration process takes a while.
  • Create Failed. This state indicates that you failed to create the migration job. You can view the cause of the failure and create a new migration job.
  • Completed. This state indicates that the migration job is complete. You can view the migration report.
  • Failed. This state indicates that the migration job fails. You can view the migration report and migrate 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. Log on to the Data Transport console.
  2. Choose Data Online Migration > Migration Jobs. On the Migration Jobs page, find a migration job and click Manage.
  3. Click Stop and ensure that the job is stopped.
  4. 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 next to the flow control setting.
    • To modify a flow control setting, you must first delete the previous setting and add a new flow control setting.
  5. Click OK and click Start to restart the job.

View a migration report

  1. On the Migration Jobs page, find a 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 successfully 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.
    Each list consists of four columns. The description of four columns is provided as follows:
    • For the file whose name ends with _total_list, the four columns include the source data address, name, size (measured in Bytes), and last modification time of each file that needs to be migrated. The format of the data source address: <vendor>://<bucketName>/<prefix>/<objectName>. Example: oss://bucket-test1022/myprefix/testfile.txt.
    • For the file whose name ends with _completed_list, the four columns include the name, size (measured in Bytes), CRC-64 checksum, and completion time of each migrated file.
    • For the file whose name ends with _error_list, the four columns include the name, start time, completion time, and error description of each file that failed to be migrated.

Retry after a migration failure

If a migration job fails, you can view the file whose name ends with _error_list to find the causes of the failure and troubleshoot the issue. On the Migration Jobs page, find the failed job, click Manage, and click Retry to migrate the files that failed to be migrated.

References