Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
Server Migration Service
Server Migration Service
- What's New
- Function Overview
- Service Overview
-
Getting Started
- Before You Start
- Quick Start
- Preparing for Migration
- Installing the Agent on the Source Server
- (Optional) Creating a Migration Template
- (Optional) Creating a Server Template
- Configuring the Target Server
- Starting the Full Replication
- Launching the Target Server
- Synchronizing Incremental Data
- Change History
-
User Guide
- Permissions Management
-
Migration Management
- Configuring a Target Server
- Starting a Full Replication
- (Optional) Cloning a Target Server
- Launching a Target Server
- Viewing the Details of a Server
- Synchronizing Incremental Data
- Deleting a Target Server Configuration
- (Optional) Deleting a Server Clone
- Deleting a Server Record
- Setting a Migration Rate
- Unlocking a Target Server
- Deleting an EVS Snapshot
- Template Management
- Viewing CTS Traces
- Change History
-
Best Practices
- Moving Huawei Cloud ECSs from Multiple Accounts to a Single Account
- Migrating Physical or Virtual Servers On-Premises or in Other Clouds to Huawei Cloud
- Migrating the System and Data Partitions of a Windows Server to the Separate Disks of a Huawei Cloud ECS
- Migrating a Server into an Enterprise Project
- Migrating Servers Whose OSs Are Not Supported by SMS
- Customizing Agent Images
- Migrating Servers over an IPv6 Network
- Change History
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Application Examples
-
APIs V3.0
- API Version Query
- Agent Running
-
Source Server Management
- Listing Failed Source Servers
- Registering a Source Server with SMS
- Listing Source Servers
- Batch Deleting Source Server Records
- Modifying a Source Server Name
- Updating the Migration Task Status of a Source Server
- Deleting a Source Server Record
- Querying Details About a Source Server
- Obtaining Source Server Overview
- Updating Disk Information
-
Task Management
- Creating a Migration Task
- Listing Migration Tasks
- Batch Deleting Migration Tasks
- Deleting a Migration Task
- Querying Details About a Migration Task
- Updating a Migration Task
- Managing Migration Tasks
- Reporting Migration Progress and Rate
- Querying the Migration Rate Limit Rules of a Migration Task
- Setting Migration Rate Limit Rules for a Migration Task
- Unlocking a Target Server
- Checking NICs and Security Groups
- Querying a Certificate Passphrase
- Uploading Migration Task Logs
- Obtaining Consistency Verification Results
- Uploading Consistency Verification Results
- Command Management
- Template Management
- Key Management
- Migration Project Management
- Network Measurement Management
- Advanced Migration Options Management
- Privacy Agreement Management
- Appendix
- Change History
- SDK Reference
-
FAQs
- Question Summary
-
Product Consultation
- Can I Migrate Servers from Other Clouds to Huawei Cloud Using SMS?
- Can I Migrate ECSs from Huawei Cloud to On-Premises Environments or Other Clouds Using SMS?
- Can I Ask Huawei Cloud Technical Support to Help Me Migrate Services?
- Does SMS Support Resumable Data Transfer?
- How Do I Migrate an ECS from One Account to Another Using SMS?
- How Do I Migrate an ECS from One Region to Another Using SMS?
- Will My Services on the Source Server Be Interrupted During Migration?
- How Do I Obtain an AK/SK Pair for a Huawei Cloud Account?
- How Do I Obtain an AK/SK Pair for an IAM User?
- How Do I Migrate a Linux Source Server as a Non-root User?
- What Information Does SMS Collect About Source Servers?
- How Do I Select a Target Server?
- How Do I Create an ECS?
- What Is Block-Level Migration?
- What are Valid Data Blocks?
- How Does Migration Using SMS Differ from Migration Using IMS?
- Why Is the OS Name of the Target ECS Displayed on the ECS Console Different from That of the Source Server?
- How Do I Determine Whether a Migration Is Complete?
- Can I Migrate Only Some Workloads from a Source Server?
- Can the Target Server Run a Different Type of OS from the Source Server?
- What Determines the Specifications of a Target Server?
- How Do I Download the SMS-Agent for Windows and the SHA256 Verification File?
- Can I Migrate a Source Server If There Is No Corresponding Image Available on Huawei Cloud?
- How Does SMS Differ from IMS in the Migration Scenario?
- How Do I Display the OS Name of a Target Server on the ECS Console?
- What Are the Snapshots of a Target Server Used for?
- Will an Incremental Synchronization Overwrite Existing Data on a Launched Target Server?
- How Do I Create a Target Server That Meets the SMS Requirements?
- Can I Use SMS to Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Can I Use an AK/SK Pair of a Federated User (Virtual IAM User) for Authentication During the SMS-Agent Startup?
- Will the Migration Be Affected If the SSH Service Does Not Use Default Port 22 on the Source Server?
- How Do I Obtain the SMS Domain Name?
- How Many Resources Will Be Used for a Linux Block-Level Migration?
- How Do I Configure Data Compression for a Linux Block-Level Migration?
- Do I Need to Activate the Windows OS and Paid Software After the Migration Is Complete?
- What Do I Do If the Source Server's Clocks Are Not Synchronized to the Target Server?
- How Do I Set the Number of Concurrent Processes for Linux File-Level Migrations?
- Which Directories Are Not Synchronized by Default During Incremental Synchronization on a Linux Server?
- How Do I Verify Data Consistency Between the Source and Target Servers?
- Can I Use a Temporary AK/SK Pair for Migration?
- Why Can't the Create new Option Be Selected When I Configure a Migration Task for a Windows Source Server?
-
OS Compatibility and Migration Restrictions
- What OSs Can Be Migrated by and What Are the Restrictions on Using SMS?
- What Are the Important Statements of SMS?
- How Many Servers Can I Migrate Concurrently Using SMS?
- How Do I Resolve Error "Inconsistent firmware type. Source: UEFI, Target: BIOS" When I Create a Migration Task?
- How Do I Check the Firmware Type of a Source Server?
- Why Can't I Save the Migration Configuration as a Template?
- How Do I Set Resource Limits for SMS-Agent During a Linux Server Migration?
-
Migration Network
- How Do I Set Up a Secure Migration Network for Using SMS?
- How Do I Prepare a Target Server Before the Migration?
- How Do I Configure Security Group Rules for Target Servers?
- How Do I Restore the Connection Between the Agent and SMS?
- Why the Migration Progress Is Suspended or Slow?
- Does a Source Server Have to Connect to the Internet?
- How Do I Configure a Source Server to Access Huawei Cloud Through a Proxy?
- Can I Release or Change the Target Server EIP During the Migration?
- How Do I Measure the Network Performance Before the Migration?
- Can I Set a Rate Limit for a Migration?
- How Do I Configure Automatic Recovery?
-
Migration Duration
- How Long Does a Migration Take?
- How Do I View the Remaining Migration Time?
- How Is the Migration Rate Displayed on the SMS Console Calculated?
- How Do I Speed Up Migration?
- Why Does the Migration Speed Fluctuate?
- How Do I Test the Network Bandwidth Between the Source and Target Servers Using iPerf?
- Why Isn't the Increased Bandwidth Being Used During the Migration?
- Is the Migration Speed Determined by the Source Bandwidth or the Target Bandwidth?
- Why Does the Migration Stay at a Stage for a Long Time?
- What Factors Affect the Migration Speed?
- Why Is the Linux Block-Level Migration Very Slow?
-
Agent Installation and Startup
- How Do I Download and Install the Agent on Source Servers?
- What Can I Do If I Fail to Download the Agent Installation File?
- How Do I Verify the Integrity of the Agent Installation File?
- Why Wasn't My Source Server Added to the SMS Console After I Configured the Agent?
- How Do I Configure Certificate Verification in the SMS-Agent Configuration File?
- Where Can I Find the Agent Run Logs?
- Why Is My Target Server Locked During the Migration?
- How Do I Unlock a Target Server Manually?
- How Do I Resolve Error "The application cannot be started due to incorrect parallel configuration" When I Start the Agent?
- Why Does the Agent Not Start the First Time I Launch It?
- Why Does the Windows Agent Executable Not Run When I Double-Click It?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Troubleshoot Failures of Pasting the AK/SK Pair When I Start the Agent (Python 2)?
- How Do I Resolve Error "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" When I Start the Agent?
- How Do I Restart the Agent?
- How Do I Fix Agent Startup Failures Due to Insufficient Space in /tmp on a Linux Source Server?
- How Do I Fix Error "Failed to start sms agent! disks" When I Start the Agent on a Linux Source Server?
- How Do I Fix Error "Failed to obtain information about disk X" When I Start the Agent on a Linux Source Server?
- How Do I Choose When the System Asks Whether to Disable the Google Services Detected on My Source Server on Google Cloud?
-
Disk Management
- Why Was a 40 GB EVS Disk Added to the Target Server During the Migration?
- Why Can't I Attach the Original System Disk Back to a Target Server?
- How Do I Resize Partitions and Disks When I Migrate a Windows Source Server?
- How Do I Shrink the Disk Partitions on a Windows Source Server?
- How Do I Exclude a Partition from Migration in Windows?
- How Do I Resolve Error "Target server has fewer disks than source server. Select another target server" When I Configure the Target Server?
- What Are the Requirements on Disks on a Target Server?
- How Can I Migrate a Source Server with a Large System Disk?
- How Do I Resolve Error "Some disks on the target server are smaller than those on the source server. Select another target server" When I Configure the Target Server?
- Can SMS Migrate Local Disks on a Source Server?
- When I Migrate a Windows Source Server from Alibaba Cloud, Why Do I Need to Choose a Target Disk at Least 1 GB Larger than the Paired GPT Source Disk?
- Why Can't I Specify Whether to Migrate a Physical Volume When I Resize Disk Partitions in Linux?
- Why Can't I Specify Whether to Migrate a Logical Volume When I Resize Disk Partitions in Linux?
- What Are the Rules for Resizing Volume Groups, Disks, and Partitions?
- How Do I Migrate a Server with a System Disk Larger Than 1 TB?
- How Do I Manually Detach the Temporary System Disk from My Target Server and Re-attach the Original System Disk?
- Why Is the Amount of Migrated Data Less Than the Total Amount of Data to Be Migrated After the Migration Is Complete?
- How Do I Merge Disks During a Linux Migration?
- How Do I Split a Disk During a Linux Migration?
- How Do I Detach the Temporary System Disk from My Target Server and Re-attach the Original System Disk using SMS-Agent?
- Migration or Synchronization Failures
-
Target Server Configuration and Launch
- What Are the Differences Between Target and Source Servers After the Migration?
- How Will the Authentication of a Target Server Change After the Migration?
- How Do I Optimize a Windows Target Server After the Migration Is Complete?
- How Do I Fix the Error "SMS.1113 Failed to reconfigure partition details on the target server" When I Launch the Target Server?
- After a Windows Server Is Migrated, Why Is the Used Space of C: Drive Increased?
- How Do I Uninstall the SMS-Agent from the Source and Target Servers After the Migration Is Complete?
- How Do I Configure the Yum Repository for the Target Server After the Migration Is Complete?
- Why Is the File System Size Inconsistent Before and After the Migration?
- Why Can't I See Data Disks on a Windows Target Server After the Migration Is Complete?
- Why Can't a Windows Target Server Access the Internet After the Migration Is Complete?
- Why Is the System Recovery Options Window Displayed When the Target Server Is Started?
- How Do I Fix a GRUB Error Because an XFS Volume Is Mounted to the /boot Partition?
- What Do I Do If a Target Server Fails to Be Created?
- How Do I Troubleshoot a MySQL Startup Failure on the Target Server After the Migration?
- How Do I Resolve Error "SELinux targeted" When I Start a Linux Target Server After the Migration Is Complete?
- Why Are the Agent Plug-ins from the Source Cloud Service Provider Retained on the Target Server After the Migration Is Complete?
- Why Is the Usable Memory (RAM) Less Than the Total Installed Memory on a Target Server Running 64-bit Windows?
- After the Migration Is Complete, Will Deleting the Target Server Configuration or Server Record Affect the Source or Target Server?
- How Do I Fix BSOD Errors When I Start a Windows Target Server After the Migration?
- How Do I Fix Startup Failures of a Windows Target Server After the Migration?
- If I Change the Password of the Source Server and Perform an Incremental Synchronization After the Full Migration Is Complete, Will the New Password Be Synchronized to the Target Server?
- What ECS Types Are Supported by SMS?
-
Known Errors and Solutions
- SMS.0202 AK/SK Authentication Failed. Ensure that the AK and SK Are Correct
- SMS.0203 Connection from Source Server to API Gateway Timed Out
- SMS.0204 Insufficient Permissions. Obtain the Required Fine-Grained Permissions
- SMS.0205 Incorrect System Time or Time Zone On Source Server
- SMS.0206 Only x86 Servers Can Be Migrated
- SMS.0210 Failed to Create File on Target Server
- SMS.0303 Unable to Access Domain Name
- SMS.0410 Failed to Obtain NIC Information
- SMS.0412 Target Server Does Not Exist
- SMS.0515 Migration Failed. Source Disk Information Has Changed. Delete Target Server Configuration and Restart the Agent
- SMS.0609 An Older Version of Agent Is Detected. Please Exit The Current Program, Uninstall the Old Agent Completely, and Install the Newest One
- SMS.0805 Failed to Migrate Partition to Target Server
- SMS.0806 Failed to Synchronize Partition to Target Server
- SMS.1104 Failed to Detach disk xx
- SMS.1105 Disk Creation Failed
- SMS.1106 Failed to Delete Disk XX
- SMS.1204 Failed to Create File on Source Server
- SMS.1205 Failed to Load WMI
- SMS.1351: Mount Point /xxx Detected on the Source Server, Which Has No Free Space. Ensure that There Is at Least 1 MB of Space
- SMS.1352: Unknown Physical Volumes Detected on the Source Server
- SMS.1353: Bind Mount or Repeated Mount Detected on /xxx of the Source Server
- SMS.1402 SSH Client Not Installed
- SMS.1414 The Migration Module Stopped Abnormally and Cannot Synchronize Data
- SMS.1807 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Confirm that Port 8900 Is Enabled
- SMS.1901 Agent Could Not Read Disk Information
- SMS.1902 Failed to Start the I/O Monitoring Module
- SMS.1904 Failed to Create a Snapshot for the Windows Server
- SMS.2802 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Port 8899 Is Enabled
- SMS.3205 Failed to Mount Partition XXX to Directory XXX
- SMS.3802 Failed to Establish an SSH Connection with the Target Server
- SMS.5102 Agent Startup Failed Because the noexec Permission Is Unavailable on /tmp in Linux
- SMS.5105 Agent Startup Failed. Insufficient Permissions to Add Files to or Delete Files from xxx
- SMS.5108 Failed to Execute df -TH
- SMS.6303 The Installed Agent Is of an Earlier Version. Download the Latest Version
- SMS.6509 Incompatible File System of the Source Server
- SMS.6511 The Source Server Lacks Driver Files
- SMS.6517 rsync Not Installed on the Source Server
- SMS.6528 Complete Real-name Authentication to Invoke SMS APIs
- SMS.6533 VSS Not Installed on the Source Server
- SMS.6537 SMS Cannot Migrate System Disks Larger Than 1 TB
- SMS.6562: Component i386-pc Not Found on Source Server For solution, see SMS API Reference
- SMS.6563: File initrd or initramfs of the xxxx version Not Found Under /boot Directory For solution, see SMS API Reference
- SMS.6616 The Current OS Does Not Support Block-level Migration/SMS.6617 The Current Kernel Version Does Not Support Block-level Migration
- Change History
On this page
Show all
Help Center/
Server Migration Service/
FAQs/
Known Errors and Solutions/
SMS.1414 The Migration Module Stopped Abnormally and Cannot Synchronize Data
SMS.1414 The Migration Module Stopped Abnormally and Cannot Synchronize Data
Updated on 2024-08-15 GMT+08:00
Symptom
During continuous synchronization, the message "SMS.1414 The migration module stops abnormally and cannot synchronize data" was displayed.
Possible Causes
The Agent or the source server has been restarted.
NOTE:
On the source server, there is a process that monitors disk changes and synchronizes the incremental data from the source server to the target server. If the source server or the Agent is restarted, this process is stopped, and the incremental synchronization cannot be performed.
Solution
Delete the task and create a migration task for the source server again. To prevent this issue from happening, take care to avoid restarting the source server or Agent during migration.
Parent topic: Known Errors and Solutions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
