This topic describes several subsequent operations 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: Data is being migrated. Wait until the migration job is completed.
  • Create Failed: The migration job has failed to be created. You can view the cause of the failure and create another migration job.
  • Finished: The migration job is completed. You can view the migration report.
  • Failed: The migration job has failed. You can view the migration report and migrate the files that have failed to be migrated.

Modify the throttling settings

During migration, you can modify the throttling settings of a migration job based on your needs.

  1. Log on to the Data Transport console.
  2. Choose Data Online Migration > Migration Jobs. On the migration job list, find a migration job and click Manage.
  3. Click Stop and verify that the job is stopped.
  4. 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 deleteimage next to the throttling setting.
    • To modify a throttling setting, delete the current setting and then add a new throttling setting.
  5. Click Submit and then click Start to rerun the migration job.

View a migration report

  1. On the migration job list, find the migration job and click Manage.
  2. Click Generate Migration Report. After a report is generated, click Export to export the migration 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 to be migrated.
    • The file whose name ends with _completed_list. This file lists the files that have been 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 (OSS) console, find the automatically generated folder aliyun_mgw_import_report/. The folder includes the three files that appear in the migration report. You can download these files and view the detailed list that is included in each file. We recommend that you use the ossbrowser tool to view these files.
    Each list consists of the following columns:
    • The columns of the file whose name ends with _total_list include the source data address, file name, source version ID, and destination version ID. The columns also display whether the job version is the latest at the source data address and whether the job version is deleted at the source data address. The last two columns display the file size (measured in bytes) and the time when the file was last modified. The format of a source data address is <vendor>://<bucketName>/<prefix>/<objectName>. The following string provides an example: oss://bucket-test1022/myprefix/testfile.txt.
    • The columns of the file whose name ends with _completed_list include the file name, the source version ID, and the destination version ID. The columns also display whether the job version is the latest at the source data address and whether the job version is deleted at the source data address. The last four columns display the file size (measured in bytes), CRC-64 checksum, time when the migration job was completed, and whether the migration was skipped.
      Note Skip migration: indicates whether the file that has the same name at the source data address and the destination data address has been skipped during migration. Valid values: 1 and 0. The value 1 indicates that the file has been skipped during migration. The value 0 indicates that the file has not been skipped during migration. The value of this field depends on the value of the File Overwrite Method parameter that you specify when you create the migration job.
    • The columns of the file whose name ends with _error_list include the file name, the source version ID, and the destination version ID. The columns also display whether the job version is the latest at the source data address and whether the job version is deleted at the source data address. The last three columns display the time when the migration job started, the time when the migration job ended, and the error description.
      Note The following four fields apply only if multi-version migration is enabled:
      • Source version ID: the version ID of the file at the source data address.
      • Destination version ID: the version ID of the file at the destination data address.
      • Latest at source data address: indicates whether the current version is the latest version of the file at the source data address. Valid values: true and false.
      • Deleted at source data address: indicates whether the current version is deleted at the source data address. Valid values: true and false.

Rerun a failed migration job

If a migration job fails, you can check the generated file whose name ends with _error_list to identify the cause of the failure and resolve the issue. Then, on the migration job list, find the failed migration job, click Manage, and click Retry to migrate the failed files.