This topic describes the 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: Data is being migrated. Wait until the migration job is complete.
Create Failed: The migration job fails to be created. You can view the cause of the failure and create another migration job.
Finished: The migration job is complete. You can view the migration report.
Failed: The migration job fails. You can view the migration report and migrate the files that fail to be migrated.
Modify the throttling settings
During migration, you can modify the throttling settings of a migration job based on your business requirements. The modified throttling settings take effect after a specific period of time.
Log on to the Data Online Migration console.
In the left-side navigation pane, choose .
On the File Sync Management page, find the migration job that you want to manage and click Manage in the Operation column.
On the page that appears, click Stop in the upper-right corner and confirm that the job is stopped.
In the Flow Control Time Schedule chart, click Reset.
To add a throttling setting, select an appropriate time range and the maximum traffic, and then click Add.
To remove a throttling setting, click the
icon next to the throttling setting. To modify a throttling setting, delete the throttling setting and then add a throttling setting.
Click Submit and then click Start to rerun the migration job.
View a migration report
Log on to the Data Online Migration console.
In the left-side navigation pane, choose .
On the File Sync Management page, find the migration job that you want to manage and click Manage in the Operation column.
On the page that appears, click Generate Migration Report in the lower part. After a migration report is generated, click Export to export the migration report.
ImportantBefore a migration job is complete, the migration logs in the generated migration report may be incomplete. To obtain complete migration logs, generate a migration report after your migration job is complete.
The obtained migration logs are for your reference only. The progress of a migration job prevails.
In a migration report, the following files are displayed 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 are migrated.The file whose name ends with
_error_list. This file lists the files that fail to be migrated.
In the Object Storage Service (OSS) console, find the automatically generated directory named aliyun_mgw_import_report/. The directory contains the three files that are displayed in the migration report. You can download the three files to view detailed file lists. 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, and version ID. The columns also display whether the file version is the latest at the source data address and whether the file 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>. Example:oss://bucket-test1022/myprefix/testfile.txt.NoteVersion ID: the version ID of the file at the source data address.
Latest at the 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 the source data address: indicates whether the current version is deleted at the source data address. Valid values: true and false.
The columns of the file whose name ends with _completed_list include the file name and the file size measured in bytes. The last three columns display the CRC-64 checksum, the time when the migration ends, and whether the migration is skipped.
NoteSkip migration: indicates whether the file that has the same name at the source data address and destination data address is skipped during migration. Valid values: 1 and 0. A value of 1 indicates that the file is skipped during migration. A value of 0 indicates that the file is not skipped during migration. The value of this column depends on the value of the File Overwrite Method parameter that you specified when you create the migration job.
The columns of the file whose name ends with _error_list include the file name, the time when the migration starts, the time when the migration stops, and the error description. The last column indicates whether the migration is skipped.
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.
Log on to the Data Online Migration console.
In the left-side navigation pane, choose .
On the File Sync Management page, find the migration job that you want to manage and click Manage in the Operation column.
On the page that appears, click Retry in the upper-right corner to rerun the migration job and migrate the files that fail to be migrated.