- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
-
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
- Network Configurations for Different Migration Scenarios
- Using MgC to Migrate Servers Without Internet Access over Private Lines
- Downsizing Disks on Linux
-
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 Source Server Information
- Updating the Migration Task Status of a Source Server
- Deleting a Source Server Record
- Querying Details About a Source Server
- Obtaining the Summary of Source Servers
- 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
- SDK Reference
-
FAQs
- Question Summary
-
Product Consultation
- 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?
- How Do I Migrate an ECS from One Region to Another Using SMS?
- How Do I Migrate a Linux Source Server as a Non-root User?
- 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?
- How Does SMS Differ from IMS in the Migration Scenario?
- What Are the Snapshots of a Target Server Used for?
- How Many Source Resources Will Be Used for a Linux Block-Level Migration?
- Do I Need to Activate the Windows OS and Paid Software After the Migration Is Complete?
- Which Directories Are Not Synchronized by Default During Incremental Synchronization on a Linux Server?
- Why Can't the Create new Option Be Selected When I Configure a Migration Task for a Windows Source Server?
- Billing
- OS Compatibility and Migration Restrictions
-
Source Servers
- Can I Migrate Servers from Other Clouds to Huawei Cloud?
- Will My Services on the Source Server Be Interrupted During Migration?
- What Information Does SMS Collect About Source Servers?
- Can I Migrate Only Some Workloads from a Source Server?
- Can I Migrate a Source Server If There Is No Corresponding Image Available on Huawei Cloud?
- Can I Use SMS to Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Will the Migration Be Affected If the SSH Service Does Not Use Default Port on the Source Server?
-
Agent Installation and Startup
- How Do I Download the SMS-Agent for Windows and the SHA256 Verification File?
- 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?
- How Do I Resolve Error "SMS.5109 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 %s" 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?
-
Target Server Consultation
- Can I Migrate Workloads to FlexusL and FlexusX Instances, DeHs, DeCs, Kunpeng ECSs, or BMSs Using SMS?
- What ECS Types Are Supported by SMS?
- What Are the Differences Between Target and Source Servers After the Migration?
- What Determines the Specifications of a Target Server?
- How Will the Authentication of a Target Server Change After the Migration?
- Why Is the File System Size Inconsistent Before and After the Migration?
- Will an Incremental Synchronization Overwrite Existing Data on a Launched Target Server?
- How Do I Create a Target Server That Meets the SMS Requirements?
- What Do I Do If the Linux Source Server's Clocks Are Not Synchronized to the Target Server?
- Why Can't I See Data Disks on a Windows 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?
- After the Migration Is Complete, Will Deleting the Target Server Configuration or Server Record Affect the Source or Target Server?
- 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?
- Why Is My Target Server Locked During the Migration?
- How Do I Unlock a Target Server Manually?
-
Target Server Configuration
- How Do I Select a Target Server?
- How Do I Configure Data Compression for a Linux Block-Level Migration?
- How Do I Limit Resource Allocation for the Agent in a Linux Migration?
- How Do I Set the Number of Concurrent Processes for Linux File-Level Migrations?
- How Do I Configure the Yum Repository for the Target Server After the Migration Is Complete?
- How Do I Fix Error "SMS.0601 ECS creation failed?"
- Why Can't I Save the Migration Configuration as a Template?
- How Do I Resolve Error "Inconsistent firmware type. Source: UEFI, Target: BIOS" When I Create a Migration Task?
-
Target Server Launch
- How Do I Optimize a Windows Target Server After the Migration Is Complete?
- 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?
- 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?
- 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 Is the Usable Memory (RAM) Less Than the Total Installed Memory on a Target Server Running 64-bit Windows?
- 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?
- What Configuration Items Do I Need to Modify for the Target Server After the Migration Is Complete?
- Data Consistency
-
Credentials
- 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?
- Can I Use an AK/SK Pair of a Federated User (Virtual IAM User) for Authentication During the SMS-Agent Startup?
- How Do I Obtain the SMS Domain Name Required for Starting the SMS-Agent?
- Can I Use a Temporary AK/SK Pair for Migration?
-
Migration Network
- How Do I Set Up a Secure Migration Network for Using SMS?
- What Are the Network Requirements for Existing Target Servers?
- 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?
-
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
-
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.0208 Failed to Send Your Service Statement Confirmation to SMS
- SMS.0210 Failed to Create File on Target Server
- SMS.0212 Agent Restarted
- SMS.0303 Unable to Access Domain Name
- SMS.0304 SSL/TLS Authentication Failed
- 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.1113 Failed to Reconfigure Partition Details on the Target Server
- 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.3803 The Connection to the Port 22 of Target Server Failed, Because an Error Occurred During the Public Key Verification on the Target Server
- SMS.3804 The Connection to the Port 22 of Target Server Failed Due to Invalid Connection Credential
- SMS.3805 The Connection to the Port 22 of Target Server Timed Out
- SMS.3806 The Connection to the Port 22 of Target Server was Rejected
- 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
- MS.5112: Agent Main Program linuxmain Could Not Run
- SMS.5113 Check %s on Linux Timed Out
- 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
- SMS.9007 Migration Task Paused. Rate Limit Not Applied. Rate Exceeded Limit Multiple Times
- Videos
- Glossary
-
More Documents
-
User Guide(ME-Abu Dhabi Region)
- Service Overview
- Getting Started
-
User Guide
- Permissions Management
-
Server Management
- Configuring a Target Server
- Starting a Full Replication
- (Optional) Cloning a Target Server
- Launching a Target Server
- Viewing a Server Details
- Synchronizing Incremental Data
- Deleting the Target Server Configuration
- (Optional) Deleting a Cloned Server
- Deleting a Server
- Setting the Migration Rate
- Unlocking a Target Server
- Template Management
- Viewing CTS Traces
-
FAQs
-
Product Consulting
- Can I Migrate Physical Servers and VMs from Other Clouds to the Cloud Platform Using SMS?
- Can I Migrate ECSs to an On-premises Environment or Another Cloud Using SMS?
- Can I Ask the Technical Support to Help Me Move Servers?
- Can I Migrate Workloads to a DeH, or DeC Using SMS?
- Does SMS Support Resumable Data Transfer?
- How Do I Migrate an ECS from One Account to Another?
- 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 Create an AK/SK Pair for an Account?
- How Do I Create 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 the Block-Level Migration?
- What are Valid Data Blocks?
- 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 Task Is Complete?
- Can I Migrate Only Some Services on the Source Server?
- Can the Target Server Run a Different Type of OS from the Source Server?
- What Determines the Specifications of a Target Server?
- Which Download Option Should I Choose When I Download the Windows Agent?
- 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?
- In a Linux File-Level Migration, How Do I Exclude Directories from Migration and Synchronization?
- Will an Incremental Synchronization Overwrite the Existing Data on a Launched Target Server?
- How Do I Create a Target Server that Meets the SMS Requirements?
- Can SMS Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Can the AK/SK of a Federated User (Virtual IAM User) Be Used for Authentication During the SMS-Agent Startup?
- How Do I Synchronize Files in Specific Directories After a Linux File-Level Migration Is Complete?
- 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 Disable Data Compression When the CPU Usage Is Too High During a Linux Block-Level Migration?
- Do I Need to Activate My Windows OS and Paid Software After the Migration?
- 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?
-
OS Compatibility and Migration Restrictions
- What Source Server OSs Are Supported by SMS and Are There Any Restrictions on Using SMS?
- What Are the Important Statements of SMS?
- How Many Servers Can I Migrate Concurrently Using SMS?
- How Do I Resolve the Error "Inconsistent firmware type. Source: UEFI, Target: BIOS" When I Create a Migration Task?
- How Do I Resolve Error "Incompatible file system of the source server"?
- How Do I Resolve Error "Insufficient permissions. Add corresponding fine-grained permissions"?
- How Do Resolve the Error "Source server lacks driver files"?
- How Do I Resolve Error "VSS not installed on the source server"?
- 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 Resolve the Error "Failed to establish an SSH connection with the target ECS"?
- How Do I Fix the Error "Failed to connect to the target ECS. Check whether its IP address is reachable and confirm that port XX is enabled"?
- How Do I Fix a Connection Failure Between the Source Server and API Gateway Due to a Busy Network?
- 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?
- Can I Release or Change the Target Server EIP During the Migration?
- How Do I Resolve the Error "SMS.0302 Failed to resolve domain name xxx"?
- How Do I Resolve the Error "SMS.0303 Unable to access domain name xxx"?
- How Do I Measure the Network Performance Before the Migration?
-
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 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 in 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 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 Find and Modify the Agent Configuration Files?
- 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 the "No such file or directory: 'rsync':'rsync" Error When I Start the Linux Agent?
- 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 "Failed to start the I/O monitoring module" When I Start the Agent?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Resolve Error "AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct" 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 Resolve Error "Failed to load wmi" During the Agent Startup?
- How Do I Fix the Agent Startup Failures Due to Agent Files Write or Read Failures?
- 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 "Agent startup failed because the noexec permission is not allowed on /tmp for SMS Agent. Please remount /tmp without noexec" When I Start the Linux Agent?
- How Do I Resolve Error "Only servers with x86 architecture can be migrated"?
- 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 "SMS.1901, Agent cannot read disk information" When I Start the Agent Installed on a Windows 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 the Google Cloud?
- How Do I Fix Error "SMS.0410: Failed to obtain NicName/IPAddress information of source server " When I Start the Agent on a Linux Server?
- What Do I Do If the SMS-Agent Fails to Start and Error "SMS.0609 An earlier version of Agent is detected. Please exit the old Agent, uninstall the old Agent completely, and install the latest version" Is Displayed?
- How Do I Fix Error "SMS.5103: Agent startup failed." When I Fail to Start the Agent on a Linux Source Server? Folder /tmp is missing
- How Do I Fix Error "SMS.1353: Bind mount or repeated mount detected on /xxx of the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.1352: Unknown physical volumes detected on the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "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" When I Fail to Start the Agent on a Linux Source Server?
-
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 Resolve Error "Disk info in source server has changed, task fail, please delete the task and then restart the agent"?
- How Do I Resize Partitions and Disks When I Migrate a Windows Source Server?
- How Do I Shrink the Disk Partitions on a Source Server Running Windows?
- How Do I Exclude a Partition from Migration in Windows?
- How Do I Fix Error "Failed to modify the configuration files of the target server"?
- How Do I Fix Error "Failed to create snapshot"?
- How Do I Fix Error "Failed to mount partition xxx to directory xxx"?
- How Do I Troubleshoot a Failed Migration or Synchronization of a Partition?
- How Do I Fix Error "Failed to create a file on the source server. Cause: /bin/sh: line 0: echo: write error: No space left on device"?
- How Do I Fix Error "Failed to read /etc/fstab on the source server"?
- How Do I Resolve Error "Insufficient disks on the Target ECS"?
- How Do I Resolve Error "SMS.1105 Disk creation failed"?
- How Do I Resolve Error "Failed to execute df -TH"?
- 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?
- 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 Detach the Temporary System Disk from My Target Server and Re-attach the Original Disk?
- Why Is There Less Data on the Target Server After the Migration Than There Was on the Source Server?
- How Do I Merge Disks During a Linux Migration?
- How Do I Split a Disk During a Linux Migration?
-
Migration or Synchronization Failures
- After the Migration Is Complete, How Do I Replicate Any New Data from the Source Server to the Target Server?
- How Do I Fix the Error "The migration module stops abnormally and cannot synchronize data"?
- What Do I Do If the SMS-Agent Exits Suddenly and Disconnects a Windows Source Server from the SMS Console During a Migration?
-
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?
- 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 Was 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?
- 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 Migration?
- Why Can't a Windows Target Server Access the Internet After the Migration?
- Why Is the System Recovery Options Window Displayed When the Target Server Is Started?
- How Do I Expand the Capacity of a Windows System Disk After the Migration?
- 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 Do the Agent Plug-ins from the Source Cloud Service Provider Exist 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?
- How Do I Fix Error "Failed to execute boot loader on the target ECS" When I Launch the Target Server?
- After the Migration Is Complete, Will Deleting the Target Server Configuration or Server Record Affects 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 Replication After the Full Migration Is Complete, Will the New Password Be Synchronized to the Target Server?
-
Product Consulting
- Change History
-
API Reference(ME-Abu Dhabi Region)
- Before You Start
- API Overview
- Calling APIs
-
APIs V3.0
-
Source Server Management
- Listing Failed Source Servers
- Registering a Source Server with SMS
- Listing Source Servers
- Batch Deleting Source Server Records
- Modifying Source Server Information
- Updating the Migration Task Status of a Source Server
- Deleting a Source Server Record
- Querying Details About a Source Server
- Obtaining the Summary of Source Servers
- 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
- Command Management
- Template Management
- Migration Project Management
-
Source Server Management
- Appendix
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Getting Started
-
User Guide
- Permissions Management
-
Server Management
- Configuring a Target Server
- Starting a Full Replication
- (Optional) Cloning a Target Server
- Launching a Target Server
- Viewing a Server Details
- Synchronizing Incremental Data
- Deleting the Target Server Configuration
- (Optional) Deleting a Cloned Server
- Deleting a Server
- Setting the Migration Rate
- Unlocking a Target Server
- Template Management
- Viewing CTS Traces
-
FAQs
-
Product Consulting
- Can I Migrate Physical Servers and VMs from Other Clouds to the Cloud Platform Using SMS?
- Can I Migrate ECSs to an On-premises Environment or Another Cloud Using SMS?
- Can I Ask the Technical Support to Help Me Move Servers?
- Can I Migrate Workloads to a DeH, or DeC Using SMS?
- Does SMS Support Resumable Data Transfer?
- How Do I Migrate an ECS from One Account to Another?
- 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 Create an AK/SK Pair for an Account?
- How Do I Create 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 the Block-Level Migration?
- What are Valid Data Blocks?
- 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 Task Is Complete?
- Can I Migrate Only Some Services on the Source Server?
- Can the Target Server Run a Different Type of OS from the Source Server?
- What Determines the Specifications of a Target Server?
- Which Download Option Should I Choose When I Download the Windows Agent?
- 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?
- In a Linux File-Level Migration, How Do I Exclude Directories from Migration and Synchronization?
- Will an Incremental Synchronization Overwrite the Existing Data on a Launched Target Server?
- How Do I Create a Target Server that Meets the SMS Requirements?
- Can SMS Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Can the AK/SK of a Federated User (Virtual IAM User) Be Used for Authentication During the SMS-Agent Startup?
- How Do I Synchronize Files in Specific Directories After a Linux File-Level Migration Is Complete?
- 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 Disable Data Compression When the CPU Usage Is Too High During a Linux Block-Level Migration?
- Do I Need to Activate My Windows OS and Paid Software After the Migration?
- 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?
-
OS Compatibility and Migration Restrictions
- What Source Server OSs Are Supported by SMS and Are There Any Restrictions on Using SMS?
- What Are the Important Statements of SMS?
- How Many Servers Can I Migrate Concurrently Using SMS?
- How Do I Resolve the Error "Inconsistent firmware type. Source: UEFI, Target: BIOS" When I Create a Migration Task?
- How Do I Resolve Error "Incompatible file system of the source server"?
- How Do I Resolve Error "Insufficient permissions. Add corresponding fine-grained permissions"?
- How Do Resolve the Error "Source server lacks driver files"?
- How Do I Resolve Error "VSS not installed on the source server"?
- 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 Resolve the Error "Failed to establish an SSH connection with the target ECS"?
- How Do I Fix the Error "Failed to connect to the target ECS. Check whether its IP address is reachable and confirm that port XX is enabled"?
- How Do I Fix a Connection Failure Between the Source Server and API Gateway Due to a Busy Network?
- 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?
- Can I Release or Change the Target Server EIP During the Migration?
- How Do I Resolve the Error "SMS.0302 Failed to resolve domain name xxx"?
- How Do I Resolve the Error "SMS.0303 Unable to access domain name xxx"?
- How Do I Measure the Network Performance Before the Migration?
-
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 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 in 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 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 Find and Modify the Agent Configuration Files?
- 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 the "No such file or directory: 'rsync':'rsync" Error When I Start the Linux Agent?
- 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 "Failed to start the I/O monitoring module" When I Start the Agent?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Resolve Error "AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct" 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 Resolve Error "Failed to load wmi" During the Agent Startup?
- How Do I Fix the Agent Startup Failures Due to Agent Files Write or Read Failures?
- 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 "Agent startup failed because the noexec permission is not allowed on /tmp for SMS Agent. Please remount /tmp without noexec" When I Start the Linux Agent?
- How Do I Resolve Error "Only servers with x86 architecture can be migrated"?
- 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 "SMS.1901, Agent cannot read disk information" When I Start the Agent Installed on a Windows 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 the Google Cloud?
- How Do I Fix Error "SMS.0410: Failed to obtain NicName/IPAddress information of source server " When I Start the Agent on a Linux Server?
- What Do I Do If the SMS-Agent Fails to Start and Error "SMS.0609 An earlier version of Agent is detected. Please exit the old Agent, uninstall the old Agent completely, and install the latest version" Is Displayed?
- How Do I Fix Error "SMS.5103: Agent startup failed." When I Fail to Start the Agent on a Linux Source Server? Folder /tmp is missing
- How Do I Fix Error "SMS.1353: Bind mount or repeated mount detected on /xxx of the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.1352: Unknown physical volumes detected on the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "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" When I Fail to Start the Agent on a Linux Source Server?
-
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 Resolve Error "Disk info in source server has changed, task fail, please delete the task and then restart the agent"?
- How Do I Resize Partitions and Disks When I Migrate a Windows Source Server?
- How Do I Shrink the Disk Partitions on a Source Server Running Windows?
- How Do I Exclude a Partition from Migration in Windows?
- How Do I Fix Error "Failed to modify the configuration files of the target server"?
- How Do I Fix Error "Failed to create snapshot"?
- How Do I Fix Error "Failed to mount partition xxx to directory xxx"?
- How Do I Troubleshoot a Failed Migration or Synchronization of a Partition?
- How Do I Fix Error "Failed to create a file on the source server. Cause: /bin/sh: line 0: echo: write error: No space left on device"?
- How Do I Fix Error "Failed to read /etc/fstab on the source server"?
- How Do I Resolve Error "Insufficient disks on the Target ECS"?
- How Do I Resolve Error "SMS.1105 Disk creation failed"?
- How Do I Resolve Error "Failed to execute df -TH"?
- 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?
- 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 Detach the Temporary System Disk from My Target Server and Re-attach the Original Disk?
- Why Is There Less Data on the Target Server After the Migration Than There Was on the Source Server?
- How Do I Merge Disks During a Linux Migration?
- How Do I Split a Disk During a Linux Migration?
-
Migration or Synchronization Failures
- After the Migration Is Complete, How Do I Replicate Any New Data from the Source Server to the Target Server?
- How Do I Fix the Error "The migration module stops abnormally and cannot synchronize data"?
- What Do I Do If the SMS-Agent Exits Suddenly and Disconnects a Windows Source Server from the SMS Console During a Migration?
-
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?
- 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 Was 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?
- 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 Migration?
- Why Can't a Windows Target Server Access the Internet After the Migration?
- Why Is the System Recovery Options Window Displayed When the Target Server Is Started?
- How Do I Expand the Capacity of a Windows System Disk After the Migration?
- 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 Do the Agent Plug-ins from the Source Cloud Service Provider Exist 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?
- How Do I Fix Error "Failed to execute boot loader on the target ECS" When I Launch the Target Server?
- After the Migration Is Complete, Will Deleting the Target Server Configuration or Server Record Affects 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 Replication After the Full Migration Is Complete, Will the New Password Be Synchronized to the Target Server?
-
Product Consulting
- Change History
-
API Reference (Kuala Lumpur Region)
- Before You Start
- API Overview
- Calling APIs
-
APIs V3.0
-
Source Server Management
- Listing Failed Source Servers
- Registering a Source Server with SMS
- Listing Source Servers
- Batch Deleting Source Server Records
- Modifying Source Server Information
- Updating the Migration Task Status of a Source Server
- Deleting a Source Server Record
- Querying Details About a Source Server
- Obtaining the Summary of Source Servers
- 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
- Command Management
- Template Management
- Migration Project Management
-
Source Server Management
- Appendix
-
User Guide(ME-Abu Dhabi Region)
- General Reference
- Notes
- Constraints
- Enabling Data Consistency Verification When You Configure the Target Server
- Enabling Data Consistency Verification When You Initiate an Incremental Synchronization
- Modifying the Default Excluded Paths
- Skipping Consistency Verification
- Viewing Verification Results
- Estimating Verification Time
Show all
Copied.
How Do I Verify Data Consistency Between the Source and Target Servers?
SMS gives you the capability to verify data consistency before and after the migration. You can enable the verification option when you configure the target server or initiate an incremental synchronization.
Notes
- Before enabling the verification option, you are advised to stop services (and databases if any) on the source server. If they are not stopped, data on the source server keeps changing, which will affect the consistency.
NOTE:
It is normal for some directories on the source and target servers to have slight differences. For instance, there are directories on the source server where data is always changing, such as the directory where SMS-Agent was installed and the /var/log directory where stores system logs.
- The time required for consistency verification depends on the number and size of files to be verified. If consistency verification takes a long time during the final incremental synchronization, the time required for service cutover will also increase. Evaluate the impacts on your services.
- Consistency verification occupies significant source disk I/O resources. Evaluate the potential impacts on your source services.
- You can specify which paths should be included in the verification. If a parent and its child paths are included, only the parent path and its contents will be verified. The system will not re-verify the child paths.
For example, if you specify the following paths for consistency verification:
/path,/path/test
The system will verify all contents of /path and will not verify /path/test separately.
Constraints
- Consistency verification is not recommended when you choose to resize disks or partitions for the target server. Since paths between the source and target servers may not align perfectly, the verification results may be inaccurate.
- It is not applicable to verification of cross-file system files or shared folders.
- To prevent your services on the source server from being affected, a maximum of 1 million files can be verified in a single directory.
- To prevent excessive memory usage, only paths that are shorter than 1024 bytes are verified.
- Windows paths with non-ASCII characters (like Chinese or Japanese) cannot be verified and will be skipped during the process.
Enabling Data Consistency Verification When You Configure the Target Server
If you enable consistency verification when you configure the target server, data consistency will be verified after the full replication is complete. For details, see Configuring a Target Server.
Enabling Data Consistency Verification When You Initiate an Incremental Synchronization
- Open the Sync Incremental Data page by referring to Synchronizing Incremental Data.
- Select Verify Data consistency. This is a quick verification, and only the file size and modification time will be compared.
Figure 1 Enabling data consistency verificationConfigure the verification policy based on the following table and your actual requirements.
Parameter
Description
Enable Hash Verification
If this option is enabled, the system will generate and compare hash values for each file to be verified. Hash verification is recommended when individual files are large and important. Enabling this option will increase CPU and disk I/O overheads for the source server and extend the verification time.
CAUTION:- Hash values cannot be calculated for files in use, so these files will be skipped during the verification.
- Enabling this option requires you to specify the verification scope, and only files in the specified scope will be verified.
Verification Scope
- Under Exclude paths, enter the paths you want to exclude from the verification. A maximum of 30 paths can be entered. Use commas (,) to separate the paths. For example, /root/data,/var. Leaving it empty will initiate a full verification.
- Under Include paths, enter the paths you want to verify.
NOTICE:- If the entered paths are incorrect or empty, 0 will be displayed for them in the verification results.
- The more data you need to verify, the longer the consistency check will take. It is wise to focus on verifying only key paths.
- The following paths will be excluded from consistency verification by default:
- Linux: /bin, /boot, /dev, /home, /etc, /lib, /media, /proc, /sbin, /selinux, /sys, /usr, /var, /run, and /tmp
- Windows: top-level directories of partitions, for example, C:\ and D:\
If you want to verify some of the excluded paths, see Modifying the Default Excluded Paths.
Verify Inconsistencies
This option can only be enabled after at least one consistency verification is complete.
- Click OK to synchronize incremental data and verify consistency. After the synchronization and verification are complete, you can view the verification results by referring to Viewing Verification Results.
Modifying the Default Excluded Paths
- Log in to the source server.
- Open the g-property.cfg configuration file of the SMS-Agent.
- Linux: .../SMS-Agent/agent/config/g-property.cfg
- Windows: C:\SMS-Agent-Py*\config\g-property.cfg
- Modify the [consistency_check] configuration item to fit your requirements. Use commas (,) to separate paths and do not end with a comma. The following is an example:
- Linux: list_dir_illegal_linux = /bin,/boot,/dev,/home,/etc,/lib,...
- Windows: list_dir_illegal_windows = C:\SMS-Agent-Py3,C:\SMS-Agent-Py2,...
- Save the configuration file.
Skipping Consistency Verification
If you want to skip consistency verification after the incremental synchronization starts, perform the following steps:
- In the server list, click the server name. The task details show up on the right.
- On the Task Progress tab, locate the Verify data consistency subtask and click Skip Verification under the progress bar. In this displayed window, click OK.
Figure 2 Skipping consistency verification
NOTICE:
Consistency verification can be skipped only when the progress is between 5% and 95%.
Viewing Verification Results

If 0 is displayed in the Files Verified column, it means the specified directory could not be found or is empty.
All files verified to be inconsistent are recorded in the log file sms_cmp_result.log in the SMS-Agent installation directory (*/SmsAgent/agent/Logs/ on Linux and C://SMS-Agent-Py*/Logs on Windows) on the source server.
Estimating Verification Time
The following table lists the verification time tested on servers where only the migration process runs but is for reference only.
OS |
Specifications |
Disk Performance |
Verification Time (per 100 GB) |
---|---|---|---|
Windows |
2 vCPUs and 4 GB of memory |
5,000 IOPS/150 MB/s |
About 17 minutes |
Linux |
2 vCPUs and 4 GB of memory |
5,000 IOPS/150 MB/s |
About 13 minutes |
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.
Chatbot