What Are the Information Mappings Between MgC and SMS?
The following figure shows the server information mapping between MgC and SMS.
The following table lists the mapping between the server lists on the MgC and SMS consoles.
Server List on MgC |
Server List on SMS |
Description |
---|---|---|
Hostname |
Source Name |
Hostname of a source server |
IP Address |
Source IP Address |
IP address of a source server |
Image |
Source OS |
OS of a source server |
- |
Target |
Name of the paired target server |
Viewing a Server Migration Task Created by MgC on SMS
Viewing the Real-Time Migration Status
Retaining Migration Tasks on SMS
To retain the migration tasks created by MgC on SMS after a server migration workflow is complete, manually add a checkpoint before the step for clearing migration tasks in the workflow, as shown in Figure 5. For details about how to add checkpoints in a workflow and what are the precautions, see Adding a Stage or Step.
Migration Workflows FAQs
- Why the Workflow Status Is Always "Running"?
- How Do I View the Migration Progress When the Migration Workflow Is in the Running State?
- How Do I Fix the Error "Edge is not accessible" When a Step in the Migration Workflow Fails?
- How Do I Fix the Error "server require to bind credential first..." When the Migration Workflow Fails on a Source Server?
- How Do I Handle Resource Exceptions during a Batch Server Migration?
- What Are the Known Errors Related to Server Migration Workflows and How Can I Fix Them?
- What Can I Do If an Error Occurs During the Migration of a VMware Server?
- What Are the Information Mappings Between MgC and SMS?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore