Why Is the Migration Progress Inconsistent Between MgC and SMS?

MgC and SMS have different methods to calculate migration progress. As a result, the migration progress of a source server may appear differently in MgC and SMS. In SMS, a migration task is divided into phases. In MgC, a migration workflow uses a simpler calculation method to estimate the progress.

1. Task configuration: After the migration task is configured, the progress is 21%.
2. Data migration: The progress increases based on the percentage of migrated data and reaches 80% when the data migration is complete.
3. Finalization: After the configurations of the target server are modified and the disk containing the agent image is detached from it, the progress reaches 100%.

MgC Server Workflow Progress

For each source server included in an MgC migration workflow, a migration task is created in SMS. Each SMS migration task consists of several subtasks, and a subtask only starts after the previous one is 100% complete. For example, if the SMS migration task of a source server has six subtasks, the migration task can be considered complete when all six subtasks have reached 100% completion. In the MgC workflow, the migration progress of the source server is calculated as the sum of the completed subtasks' percentages divided by 600%.

Take the SMS migration task in the following figure as an example. The migration progress of the involved source server in MgC would be approximately 63% (380%/600%).

Figure 1 The subtask progress in SMS