FAQs Server Migration Service - FAQs

FAQs

Huawei Technologies Co., Ltd.

Server Migration Service

On the displayed Volume Shadow Copy Properties window, change the Startup type to Manual. Click OK. Figure 3-8 Changing the startup mode ...

Server Migration Service - FAQs - Huawei Cloud

2022-06-22 — 6.10 How Do I Resolve Error "The application cannot be started due to incorrect parallel configuration". When I Start the Agent?

Google Docs
Google Drive
Download [pdf]

File Info : application/pdf, 121 Pages, 2.43MB

sms-faq

Server Migration Service
FAQs

Issue Date

11 2021-01-08

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Issue 11 (2021-01-08)

Server Migration Service FAQs

Contents

1 Question Summary................................................................................................................. 1
2 Product Consultation.............................................................................................................. 4
2.1 Can I Migrate Physical Servers and VMs on Other Clouds to HUAWEI CLOUD Using SMS?.......................4 2.2 Can I Migrate HUAWEI CLOUD ECSs to Local or Other Cloud Environments Using SMS?...........................4 2.3 Can I Ask HUAWEI CLOUD Technical Support to Help Me Migrate Services?.................................................. 4 2.4 Can I Migrate Data to a DeH, DeC, or Kunpeng ECS Using SMS?......................................................................... 5 2.5 Does SMS Support Resumable Data Transfer?............................................................................................................. 5 2.6 How Do I Migrate an ECS from One Account to Another?...................................................................................... 5 2.7 How Do I Migrate an ECS from One Region to Another?........................................................................................ 5 2.8 Will My Services Running on the Source Server Go Down During Migration?................................................. 6 2.9 How Do I Obtain the AK and SK of an Account?.........................................................................................................6 2.10 How Do I Obtain the AK and SK of an IAM User?....................................................................................................7 2.11 How Do I Migrate a Server as a Non-root Linux User?........................................................................................ 10 2.12 What Kind of Information About Source Servers Does SMS Collects?............................................................ 11 2.13 How Do I Select a Target ECS?...................................................................................................................................... 14 2.14 How Do I Create an ECS?................................................................................................................................................ 14 2.15 What Is the Block-Level Migration?............................................................................................................................. 15 2.16 What are Valid Data Blocks?.......................................................................................................................................... 16 2.17 What Are the Differences Between the New and Old SMS Versions?.............................................................16 2.18 How Does Migration Using SMS Differ from Migration Using IMS?............................................................... 17
3 OS Compatibility and Migration Restrictions................................................................ 19
3.1 What Are Supported Source Server OSs and Migration Restrictions?................................................................19 3.2 What Are the Important Statements of SMS?............................................................................................................26 3.3 How Many Servers Can I Migrate Concurrently Using SMS?................................................................................ 27 3.4 What Can I Do If Message "The source server runs Windows 2003. Network may be unavailable after migration." Is Displayed?........................................................................................................................................................... 27 3.5 What Should I Do If Message "The target ECS is not booted with UEFI. Create an ECS using the image whose boot mode is UEFI." Is Displayed During Migration Task Creation?............................................................ 32 3.6 What Should I Do If Message "Incompatible file system of the source server" Is Displayed?.................. 34 3.7 What Should I Do If the Source Server Lacks a Necessary Driver File?.............................................................34 3.8 What Should I Do If the VSS Service Is Not Installed on the Source Server?.................................................. 35
4 Migration Network............................................................................................................... 39
4.1 How Do I Configure Network Security for SMS?....................................................................................................... 39

Issue 11 (2021-01-08)

Server Migration Service FAQs

Contents

4.2 What Should I Do on the Target ECS Before Creating a Server Migration Task?...........................................41 4.3 How Do I Configure the Security Group Rules for Target ECSs?.......................................................................... 42 4.4 What Should I Do If the SSH Connection to the Target ECS Fails to Be Established?..................................43 4.5 What Should I Do If the Target ECS Cannot Be Accessed?.................................................................................... 45 4.6 What Should I Do If the Source Server Fails to Connect to an API Gateway Due to a Busy Network? ............................................................................................................................................................................................................ 47 4.7 How Do I Restore the Connection Between the Agent and SMS?...................................................................... 48 4.8 What Should I Do If the Migration Progress Is Suspended or Slow?..................................................................52
5 Migration Duration............................................................................................................... 53
5.1 How Long Does a Migration Take?................................................................................................................................ 53 5.2 How Do I View the Remaining Migration Time?....................................................................................................... 56 5.3 How Is the Migration Rate Displayed on the SMS Console Calculated?...........................................................57 5.4 How Do I Speed Up Migration?....................................................................................................................................... 60 5.5 Why Does the Migration Speed Fluctuate?................................................................................................................. 60 5.6 How Do I Test the Network with iPerf?........................................................................................................................ 60
6 Agent Installation and Startup.......................................................................................... 64
6.1 How Do I Install the Agent on Source Servers?......................................................................................................... 64 6.2 What Should I Do If The Agent Package Fails to Be Downloaded?....................................................................64 6.3 How Do I Verify the Software Integrity of the Migration Agent?....................................................................... 65 6.4 Why There Is No Record for My Source Server on the SMS Console After the Agent Is Configured?....65 6.5 How Do I Find and Modify the SMS-Agent Configuration Files?........................................................................ 66 6.6 Why Is My Target ECS Locked During the Migration?............................................................................................. 67 6.7 How Do I Unlock the Target ECS?...................................................................................................................................67 6.8 What Should I Do If Message "No such file or directory: 'rsync':'rsync" Is Displayed During the Linux Agent Startup?.............................................................................................................................................................................. 68 6.9 What Can I Do If the System Displays a Message Indicating That the Application Cannot Be Started Due to Incorrect Parallel Configuration?............................................................................................................................. 71 6.10 What Can I Do If the Agent Does Not Start The First Time I Launch?........................................................... 71 6.11 What Can I Do If I/O Monitoring Does Not Start At Agent Startup?.............................................................. 72 6.12 What Should I Do If Message "INTERNAL ERROR: cannot create temporary directory!" Is Displayed During the Agent Startup?........................................................................................................................................................74 6.13 What Should I Do If the Migration Agent Displays a Message Indicating that AK and SK Authentication Fails?.................................................................................................................................................................. 74 6.14 What Should I Do If the AK or SK Cannot Be Pasted During the Startup of the Agent on a Source Server Running Windows 2003 or 2008?.............................................................................................................................75 6.15 What Should I Do If the Message "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" Is Displayed During the Agent Startup?.........................................................................................76 6.16 What Should I Do If the WMI Module Fails to Be Loaded During the Agent Startup?.............................77 6.17 What Should I Do If the Agent Fails to Be Installed?............................................................................................ 78 6.18 What Should I Do If the Agent Fails to Be Started Due to Insufficient Space in /tmp on the Source Server Running Linux?................................................................................................................................................................ 79 6.19 What Should I Do If the Agent Fails to Be Started on My Source Server Running Linux?.......................80 6.20 What Can I Do If the System Displays a Message Indicating That Only x86 Servers Can Be Migrated? ............................................................................................................................................................................................................ 80

Issue 11 (2021-01-08)

iii

Server Migration Service FAQs

Contents

7 Disks......................................................................................................................................... 82
7.1 Why Was a 40 GB EVS Disk Added to the Target ECS During the Migration?................................................82 7.2 What Should I Do If a System Disk Cannot Be Attached to the Target ECS?..................................................82 7.3 What Should I Do If the Migration Task Failed Because the Disks on the Source Server Had Changed? ............................................................................................................................................................................................................ 83 7.4 How Do I Move a Partition to Another Disk in Windows?.................................................................................... 84 7.5 How Do I Shrink the Disk Partitions on My Source Server Running Windows?............................................. 85 7.6 How Do I Exclude Specified Disk Partitions for Migration on Windows?......................................................... 87 7.7 What Can I Do If I Failed to Modify the Configuration Files of the Target Server?...................................... 87 7.8 What Should I Do If Snapshot Creation Failed?.........................................................................................................88 7.9 What Should I Do If a Partition Fails to Be Mounted?............................................................................................ 89 7.10 What Should I Do If Partitions Fail to Be Migrated or Synchronized to the Target ECS?......................... 90 7.11 What Should I Do If /etc/fstab on the Source Server Cannot Be Read?......................................................... 91 7.12 What Should I Do If There Are Not Enough Disks on the Target ECS?........................................................... 91
8 Migration or Synchronization Failures............................................................................. 93
8.1 What Should I Do If New Data Is Generated on the Source Server During the Migration?...................... 93 8.2 What Should I Do If the Migration Module Stops Abnormally and Cannot Synchronize Data?.............. 93
9 Target ECS Configuration and Startup............................................................................. 95
9.1 What Are the Differences Between Target ECSs and Source Servers After the Migration?........................95 9.2 What Are the Changes of Target ECS Authentication After the Migration?.................................................... 97 9.3 How Do I Configure and Optimize My Target ECSs Running Windows After the Migration?.................. 98 9.4 How Do I Activate the Target ECS Running Windows After the Migration?....................................................99 9.5 Why Is the Used Space of C: Drive on the Target Windows ECS Greater Than That on the Source Server After the Migration?................................................................................................................................................... 100 9.6 How Do I Uninstall the SMS-Agent from the Source Server and Target ECS After the Migration?......102 9.7 How Do I Configure the Yum Repository After Migration?................................................................................. 102 9.8 Why Are the File Sizes Before and After the Migration Different?................................................................... 103 9.9 Why Are Data Disks Not Displayed on the Target ECS After a Windows Server is Migrated?............... 105 9.10 What Can I Do If the Target ECS Corresponding to My Source Server Running Windows Cannot Access the Internet?.................................................................................................................................................................. 107 9.11 How Do I Expand the Capacity of a Windows System Disk After the Migration?....................................108 9.12 What Can I Do If the Server Cannot Be Started After Migration Because the GRUB Version Is Too Old?................................................................................................................................................................................................ 111 9.13 What Do I Do If a GRUB Error Occur Because the XFS File System Volume Is Mounted to the /boot Partition?...................................................................................................................................................................................... 113
10 Change History.................................................................................................................. 115

Issue 11 (2021-01-08)

Server Migration Service FAQs

1 Question Summary

Product Consultation
Can I Migrate Physical Servers and VMs on Other Clouds to HUAWEI CLOUD Using SMS?
Can I Ask HUAWEI CLOUD Technical Support to Help Me Migrate Services?
How Do I Migrate an ECS from One Account to Another? How Do I Migrate an ECS from One Region to Another? Can I Migrate Data to a DeH, DeC, or Kunpeng ECS Using SMS? Can I Migrate HUAWEI CLOUD ECSs to Local or Other Cloud Environments
Using SMS? How Do I Obtain the AK and SK of an Account? How Do I Obtain the AK and SK of an IAM User? Does SMS Support Resumable Data Transfer?

Billing

How Is SMS Billed?

OS Compatibility and Migration Restrictions
What Are Supported Source Server OSs and Migration Restrictions?
What Can I Do If Message "The source server runs Windows 2003. Network may be unavailable after migration." Is Displayed?
What Should I Do If Message "The target ECS is not booted with UEFI. Create an ECS using the image whose boot mode is UEFI." Is Displayed During Migration Task Creation?
What Should I Do If Message "Incompatible file system of the source server" Is Displayed?
What Should I Do If the Source Server Lacks a Necessary Driver File?
What Should I Do If the VSS Service Is Not Installed on the Source Server?

Issue 11 (2021-01-08)

Server Migration Service FAQs

1 Question Summary

Migration Duration
How Do I View the Remaining Migration Time? How Long Does a Migration Take? How Do I Speed Up Migration? Why Does the Migration Speed Fluctuate? How Do I Test the Network with iPerf?

Migration Network
What Should I Do If the SSH Connection to the Target ECS Fails to Be Established?
What Should I Do If the Target ECS Cannot Be Accessed? What Should I Do If the Source Server Fails to Connect to an API Gateway
Due to a Busy Network? How Do I Restore the Connection Between the Agent and SMS? What Should I Do If the Migration Progress Is Suspended or Slow? How Do I Configure Network Security for SMS? What Should I Do on the Target ECS Before Creating a Server Migration
Task? How Do I Configure the Security Group Rules for Target ECSs?

Agent Installation and Startup
How Do I Install the Agent on Source Servers?
What Should I Do If The Agent Package Fails to Be Downloaded?
Why Is My Target ECS Locked During the Migration?
How Do I Unlock the Target ECS?
What Should I Do If Message "No such file or directory: 'rsync':'rsync" Is Displayed During the Linux Agent Startup?
What Can I Do If the Agent Does Not Start The First Time I Launch?
What Can I Do If I/O Monitoring Does Not Start At Agent Startup?
What Should I Do If the Message "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" Is Displayed During the Agent Startup?
What Should I Do If the WMI Module Fails to Be Loaded During the Agent Startup?
What Should I Do If the Agent Fails to Be Started Due to Insufficient Space in /tmp on the Source Server Running Linux?
What Should I Do If the Migration Agent Displays a Message Indicating that AK and SK Authentication Fails?
What Should I Do If Message "INTERNAL ERROR: cannot create temporary directory!" Is Displayed During the Agent Startup?
What Should I Do If the Agent Fails to Be Installed?
What Should I Do If the Agent Fails to Be Started on My Source Server Running Linux?

Issue 11 (2021-01-08)

Server Migration Service FAQs

1 Question Summary

Disks

Why Was a 40 GB EVS Disk Added to the Target ECS During the Migration?
What Should I Do If a System Disk Cannot Be Attached to the Target ECS?
What Should I Do If the Migration Task Failed Because the Disks on the Source Server Had Changed?
How Do I Move a Partition to Another Disk in Windows?
How Do I Shrink the Disk Partitions on My Source Server Running Windows?
What Should I Do If Snapshot Creation Failed?
What Should I Do If a Partition Fails to Be Mounted?
What Should I Do If Partitions Fail to Be Migrated or Synchronized to the Target ECS?
What Should I Do If /etc/fstab on the Source Server Cannot Be Read?
What Should I Do If There Are Not Enough Disks on the Target ECS?

Migration and Synchronization Failures
What Should I Do If New Data Is Generated on the Source Server During the Migration?
What Should I Do If the Migration Module Stops Abnormally and Cannot Synchronize Data?

Target ECS Configuration and Startup
What Are the Differences Between Target ECSs and Source Servers After the Migration?
What Are the Changes of Target ECS Authentication After the Migration?
How Do I Activate the Target ECS Running Windows After the Migration?
Why Is the Used Space of C: Drive on the Target Windows ECS Greater Than That on the Source Server After the Migration?
Why Are the File Sizes Before and After the Migration Different?
Why Are Data Disks Not Displayed on the Target ECS After a Windows Server is Migrated?
What Can I Do If the Server Cannot Be Started After Migration Because the GRUB Version Is Too Old?

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

2.1 Can I Migrate Physical Servers and VMs on Other Clouds to HUAWEI CLOUD Using SMS?
Yes.
SMS makes it easy to migrate physical servers in data centers and VMs on various popular private and public clouds to ECSs and HECSs on HUAWEI CLOUD. In principle, all x86 servers can be migrated to HUAWEI CLOUD using SMS.
For details about the supported OSs, see What Are Supported Source Server OSs and Migration Restrictions?
2.2 Can I Migrate HUAWEI CLOUD ECSs to Local or Other Cloud Environments Using SMS?
SMS does not support the direct migration of HUAWEI CLOUD ECSs to local or other cloud environments. However, you can export an ECS image to your physical servers and then upload it to VMs on other clouds. For details, see Exporting Images.
2.3 Can I Ask HUAWEI CLOUD Technical Support to Help Me Migrate Services?
SMS does not directly migrate your services. For details, go to SMS Documentation.
If you need professional migration solutions and tools, Cloud Migration Service on HUAWEI CLOUD is available for you. It helps you smoothly migrate services, reducing the time needed for migration, so you can stay focused on service development.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

2.4 Can I Migrate Data to a DeH, DeC, or Kunpeng ECS Using SMS?

DeH

Yes. Before the migration, purchase a DeH. For details, see Buying DeHs. When configuring the target server, select the DeH that you purchased.

Dedicated Cloud
Yes. Before the migration, purchase a DeC. For details, see Enabling a DeC. When configuring the target server, select the enabled DeC.
Kunpeng ECS
No.

2.5 Does SMS Support Resumable Data Transfer?
Yes. However, the Agent or source server cannot be restarted during Windows migration. This is because the address corresponding to the incremental data is stored in the memory. If the Agent is restarted, incremental synchronization cannot be performed.

2.6 How Do I Migrate an ECS from One Account to Another?
If you need to migrate an ECS under account A to account B, perform the following operations:
1. Install the Agent on the ECS under account A and enter the AK/SK of account B when starting the Agent. For details about how to install the Agent, see Installing the Windows Agent or Installing the Linux Agent. Log in to the management console using account B, set the target server, start server replication, and start the target server.
NOTE
For details about how to migrate an ECS from one region to another, see How Do I Migrate an ECS from One Region to Another?

2.7 How Do I Migrate an ECS from One Region to Another?
If you need to migrate an ECS from one region to another, for example, from CN South-Guangzhou to CN North-Beijing1, you need to install the Agent on the

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

ECS in CN South-Guangzhou. When creating a migration task, select CN NorthBeijing1 as the target region.
NOTE
For details about how to migrate ECSs under account A to account B, see How Do I Migrate an ECS from One Account to Another?

2.8 Will My Services Running on the Source Server Go Down During Migration?
No. During migration, SMS mainly affects the network of the source server, and has little impact on other resources such as the CPU and memory.
Because the amount of data to be migrated is large, bandwidth resources are consumed. Before the migration, you are advised to evaluate the current bandwidth and the bandwidth occupied by services running on the source server. Based on the evaluation result, allocate proper bandwidth resources to SMS.

2.9 How Do I Obtain the AK and SK of an Account?

Scenarios

An access key comprises an access key ID (AK) and secret access key (SK). It is a long-term identity credential for you on HUAWEI CLOUD. You can use an AK/SK to sign requests for calling HUAWEI CLOUD APIs. AK is used together with SK to sign requests cryptographically, ensuring that the requests are secret, complete, and correct.
When creating a migration task, you need to enter an AK and SK for authentication. If you use an account to migrate servers, you need to obtain the AK and SK of your HUAWEI CLOUD account.

CAUTION During the migration, do not delete the AK/SK. Otherwise, the migration task will fail.
Procedure
Step 1 Log in to the management console. Step 2 Hover over the username in the upper right corner and choose My Credentials
from the drop-down list.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

Step 3 Choose Access Keys from the navigation pane. Step 4 Click Create Access Key, and enter the verification code.

Step 5 Click OK to generate and download the access key. NOTE
Open the CSV file displayed, or open this file by choosing Downloads in the upper right corner of the browser.
----End

2.10 How Do I Obtain the AK and SK of an IAM User?

Scenarios

When creating a migration task, you need to enter the AK and SK for authentication. To safeguard the resources in your account on a cloud service platform, you are advised to create a username in the account and grant permissions to the username to create AKs and SKs. This section describes how to create access credentials (AKs and SKs).

Procedure

Creating a User Group and Assigning Permissions
1. Log in to the management console. 2. In the upper right corner of the page, click the username and choose Identify
and Access Management. 3. In the navigation pane on the left, choose User Groups. 4. On the User Groups page, click Create User Group. 5. (Optional) Enter the user group name and description, and click OK.
The user group list is displayed, including the newly created user group.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

6. Locate the newly created user group, and click Manage Permissions under More in the Operation column.
7. On the Permission tab page, click Assign Permissions.
8. Select Global service project for Scope, and select SMS Administrator and OBS OperateAccess for Permissions. Select Region-specific projects, and select ECS FullAccess for Permissions.
Creating a User and Adding the User to a User Group
1. Log in to the management console.
2. Click the username in the upper right corner and select Identity and Access Management from the drop-down list.
3. In the navigation pane on the left, choose Users. Click Create User in the upper right corner.
4. On the Create User page, set user information and click Next.
Username: Used for logging in to HUAWEI CLOUD, in this example we will use James.
Credential Type: The type of credential to be used to access HUAWEI CLOUD.
Password: The password that is used to log in to the console or
when calling APIs.
Access key: A credential used for APIs requiring access.
(Optional) User Groups: Add the user to a user group and the user will inherit the permissions granted to the user group. If no user group is created and the user is not the administrator, skip this step.
(Optional) Description: A description of the user.
5. Set the following parameters:
Password Type
Set by user: Select this option if you yourself are not using user
James. Enter James's email and mobile number, and then James will be sent a one-time link to log in to HUAWEI CLOUD and set his own password.
Automatically generated: The system automatically generates a
random 10-digit password. If you access HUAWEI CLOUD through an API, CLI, or SDK, you are advised to select this option. If you select this mode, click OK, download the password file provided by HUAWEI CLOUD, and send it to the IAM user.
Set now: Select this option if you are the entity using user James.
Then set a password for login.
Password Reset: If this option is selected, after a user enters the username and initial password to log in to the system, the Change Password Upon First Login page is displayed. For security reason, the user needs to create a new password. This option is enabled by default. Keep it enabled for security purposes.
6. Click OK.
The created IAM user is displayed in the user list.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

7. Click Next, add the user to the user group (optional), and click Create.
Creating an AK/SK
1. On the homepage of the system, click Log In in the upper right corner. 2. Click IAM User Login in the lower right corner of the page. 3. Set Domain name, User name/Email address/Mobile number, and API
Password, and click Log In.
NOTE
If MFA authentication is enabled, you will need to enter an authentication code from a virtual MFA device, an SMS verification code, or an email verification code.
4. On the Login Verification page, click OK. 5. In the upper right corner of the displayed page, click Console.
The management console page is displayed. 6. In the upper right corner of the page, click the username and choose My
Credentials. The My Credentials page is displayed. 7. Click Create Access Key under the Access Keys tab page. The Create Access Key dialog box is displayed. 8. Enter the password in the Login Password field. If a mobile number or an email address is bound, click Get Code to obtain the code, then enter the code in the SMS Verification Code or Email Verification Code field for verification, and click OK. After the verification is successful, the Download Access Key dialog box is displayed. 9. In the displayed dialog box, click OK. Download and save the added access key as prompted.
NOTE
Anyone who possesses your access keys can decrypt your login information. Therefore, keep your access keys somewhere secure. If you click Cancel in the Download Access Key dialog box, the access key will not be downloaded and cannot be downloaded later. You will have to delete the access key and create a new one later.

Subsequent Operations
If there is something wrong with an access key, for example, it is lost or stolen, or for some other reason will not be used any longer, delete the key, or contact the administrator to reset the access key.
Step 1 On the homepage of the system, click Log In in the upper right corner.
Step 2 Click IAM User Login in the lower right corner of the page.
Step 3 Set Domain name, User name/Email address/Mobile number, and API Password, and click Log In.
NOTE
If MFA authentication is enabled, you will need to enter an authentication code from a virtual MFA device, an SMS verification code, or an email verification code.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

Step 4 On the Login Verification page, click OK.
Step 5 In the upper right corner of the displayed page, click Console.
The management console page is displayed.
Step 6 In the upper right corner of the page, click the username and choose My Credentials.
The My Credentials page is displayed.
Step 7 Locate the row containing the target access key under the Access Keys tab and click Delete in the Operation column.
Step 8 Suppose that an email address has been bound. Enter the password in the Login Password field, click Get Code, enter the code in the Email Verification Code field, and click OK. NOTE
After the access key is deleted, it will be permanently deleted and cannot be restored.
----End

2.11 How Do I Migrate a Server as a Non-root Linux User?

Scenarios

If you must use a non-root user to perform migration, ensure that the user has the required permissions before creating a Linux migration task.

Procedure
Step 1 For a hypothetical user, test, check whether the user is included in /etc/passwd. If it is not, run the following two commands to add the user and set the password:
If it is, confirm that user test has a /home directory. If the use does not has a home direcory, add one.
useradd -m test passwd test
Step 2 Modify the /etc/sudoers file.
1. Add the following information to the end of the /etc/sudoers file based on the OS version:
Debian and Ubuntu:
test ALL=(ALL:ALL) ALL test ALL=(ALL:ALL) NOPASSWD:ALL
Other distributions:
test ALL=(ALL) ALL test ALL=(ALL) NOPASSWD:ALL
2. If Defaults requiretty is in the /etc/sudoers file, comment out it.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

CAUTION
These modifications to the sudoers file grant the user the ability to execute administrator level command without entering a password. After the migration is completed, you need to remove the added lines, or an exception occurs.

Step 3 After the permissions are configured, switch to a regular account and run the following command to start the Agent:
sudo ./startup.sh
----End

2.12 What Kind of Information About Source Servers Does SMS Collects?
SMS uses the Agent to collect source servers details to evaluate the migration feasibility and provide data required for selecting and configuring target ECSs. Table 2-1 lists the data collected from Windows servers. Table 2-2 lists the data collected from Linux servers. All collected data is used for data migration only.

Table 2-1 Window server details to be collected

Item

Parameter

Objective

Environme Windows Version nt check information

Used for migration feasibility evaluation. Only source servers with OSs included in Table 3-1 can be migrated.

Firmware Type

Used for migration feasibility evaluation. The source server can be booted from BIOS or UEFI.

CPU

Used for selecting the target ECS.

Target ECSs must have at least as many

vCPUs as the corresponding source

servers.

Memory

Used for selecting the target ECS. Target ECSs must have at least a much memory as the corresponding source servers.

System Directory

Used for configuring the target ECS. After the migration is complete, it will be used to restore the registry.

Disk Partition Format

Used for configuring the target ECS. Before the migration, the disk of the target ECS must be formatted to be the same as that of the source server.

Issue 11 (2021-01-08)

Server Migration Service FAQs
Item

Parameter File System
Available Space

OEM System Check

Driver files System services

User permissions

Disk information

Disk Name Disk Partition
Format Disk Size Used Space

2 Product Consultation
Objective
Used for migration feasibility evaluation. Only source servers with the NTFS file system can be migrated.
Used for migration feasibility evaluation. If there is not enough space on the source server partition, the migration may fail.
Used for migration feasibility evaluation. If the system is an OEM system, the OS needs to be reactivated after the migration.
Used for migration feasibility evaluation. The source server must have basic disk drivers.
Used for migration feasibility evaluation. Volume Shadow Copy Service (VSS) must be available on the source server.
Used for migration feasibility evaluation. You must have the administrator permissions to run the Agent.
Used for checking whether the disk specifications of the target ECS meet the migration requirements.

Table 2-2 Linux server details to be collected

Item

Parameter

Objective

Environme OS Version nt check information

Used for migration feasibility evaluation. Only source servers with OSs included in Table 3-1 can be migrated.

CPU

Used for selecting the target ECS.

Target ECSs must have at least as many

vCPUs as the corresponding source

servers.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

Item

Parameter

Objective

Memory

Used for selecting the target ECS. Target ECSs must have at least a much memory as the corresponding source servers.

Paravirtualization Check

Used for evaluating migration feasibility. SMS does not support migration of paravirtualized source servers.

Firmware Type

Used for migration feasibility evaluation. The source server can be booted from BIOS or UEFI.

Boot Mode

Used for migration feasibility evaluation. The source server must be booted from BIOS.

Rsync Component Check

Used for evaluating synchronization feasibility. The SMS synchronization function depends on the Rsync component on the source server.

Raw Equipment Check

Used for migration feasibility evaluation. The source servers to be migrated cannot contain raw devices.

Disk Partition Information

Used for migration feasibility evaluation. The disk type of the source server must be Main Boot Record (MBR) or GUID Partition Table (GPT).

Disk Partition Format

Used for configuring the target ECS. Before the migration, the disk of the target ECS must be formatted to be the same as that of the source server.

File System

Used for migration feasibility evaluation. The file system type of the source server must be ext2, ext3, ext4, VFAT, XFS, or Btrfs.

Disk information

Disk Name Disk Partition
Format Disk Size Used Space

Used for checking whether the disk specifications of the target ECS meet the migration requirements.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

2.13 How Do I Select a Target ECS?
NOTE
Currently, the source servers can be migrated to pay-per-use or yearly/monthly ECSs. You can select whichever billing mode best suits your needs.
The selected target ECSs must meet the following requirements. If the requirements are not met, you are required to create an ECS by performing steps provided in "How Do I Create an ECS?" in Elastic Cloud Server User Guide. A target ECS running Windows must have at least 2 GB of memory. The number of disks on the target ECS cannot be less than the number of
disks on the source server. The size of each disk on the target ECS cannot be less than that on the source server. The image type of a target ECS must be the same as the OS type of the source server. Otherwise, the actual OS type of the target ECS is different from the image type of the ECS.
Figure 2-1 Image types of ECSs

2.14 How Do I Create an ECS?

Scenarios

Source servers are migrated to the ECSs on HUAWEI CLOUD. You need to create one or more ECSs on HUAWEI CLOUD before the migration.

Procedure
Step 1 Log in to the management console.
Step 2 Click in the upper left corner and select the desired region and project. Step 3 Click Service List and choose Computing > Elastic Cloud Server.
The Elastic Cloud Server page is displayed. Step 4 Click Buy ECS and configure basic parameters on the displayed page.
For details about the parameters, see Purchasing an ECS.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

NOTE
A target ECS running Windows must have at least 2 GB of memory. Image must be set the same as the OS type of the source server. When you set System Disk, there has to be at least as many disks on the target ECS as
on the source server, and the disks much each be at least as large as the source server disks they correspond to.
Figure 2-2 Purchasing an ECS

Step 5 Click Next. After successful purchase, the new ECS is displayed in the ECS list. ----End

2.15 What Is the Block-Level Migration?
What Is a Block?

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

In block-level migrations, a block refers to a disk block. A disk block is the minimum logical unit of the file system for managing disk partitions. Disk blocks are similar to clusters in Windows.
A block is also the minimum logic unit of the disk used by OSs and the software. The smallest unit for disk read or write is a sector. A sector is a physical area on the disk. The read and write operations to disk blocks are performed in sectors. Generally, a file is stored in several blocks, and one block maps to several physical sectors.
What Is the Block-Level Migration?
In block-level migrations, the file system is migrated by blocks. Therefore, if the network is interrupted during the migration, only impacted blocks need to be migrated again after the network is recovered. If files are modified during the migration, only modified blocks need to be synchronized after the migration.
In file-level migrations, various tools like TAR and SSH or other transmission protocols are used for remote replication. Therefore, if the file is changed during decompression or the network is interrupted during migration, the migration fails. In addition, if the file is changed during incremental data synchronization, the file needs to be synchronized again. In this case, all the blocks of the file must be synchronized. So, the synchronization efficiency is low.

2.16 What are Valid Data Blocks?
Valid data blocks are blocks that are allocated or used by a file system, for example, EXT. SMS migrates only valid data blocks. For data blocks that are not allocated or used and can be allocated by the system, SMS does not migrate them during migration. Therefore, the data volume to be migrated is reduced, and migration efficiency is improved.

2.17 What Are the Differences Between the New and Old SMS Versions?
The following functions have been added to the new version:
Continuous synchronization: If you enable this function, after full replication is complete, SMS automatically performs continuous synchronization, reducing the amount of manual operations required to complete a server migration.
Cloning target ECSs: Before launching the target ECS, you can clone the target ECS for service testing, and then only launch the target ECS after tests confirm there are no issues.
Project management: You can manage your source servers by migration project.
Locking target ECSs: After the migration starts, the target ECS is automatically locked. If the target ECS is operated on during the migration, the migration fails.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

CAUTION
Data is not shared between the new and old versions of SMS console. If you install the old Agent, go to the old SMS console. If you install the new Agent, go to the new SMS console.

2.18 How Does Migration Using SMS Differ from Migration Using IMS?

SMS

You can use SMS to migrate applications and data from on-premises x86 physical servers or VMs on private or public clouds to HUAWEI CLOUD ECSs.
Advantages
Ease of use You only need to install and configure the Agent on the source server. You can then configure the target ECS and start the migration on the SMS management console. SMS takes care of the remaining work automatically.
Seamless migration Your services do not have to go down during the migration. If the network is interrupted during migration, SMS allows you to restart the migration and continue transferring data from where it left off.
High security SMS authenticates the Agent using an AK/SK pair. SMS uses a dynamically generated SSL certificate and key pair to encrypt the transmission channel for data security.
Constraints
For details, see What Are Supported Source Server OSs and Migration Restrictions?

Migration Using IMS
If you want to migrate a server using IMS, you need to create an image of the server to be migrated, perform initial configuration (configuring network and installing a Xen or KVM driver), import the image to the IMS console, and use the image to create an ECS.
Advantages
IMS enables you to create images (in VHD, VMDK, QCOW2, or RAW format) of existing servers and import the images to the cloud platform.
You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converted before being imported. The open-source tool qemu-img is provided for you to convert image file formats.

Issue 11 (2021-01-08)

Server Migration Service FAQs

2 Product Consultation

You can create image of many popular OSs, such as SUSE, Oracle Linux, Red Hat, Ubuntu, openSUSE, CentOS, Debian, Fedora, and EulerOS.
IMS provides image sharing and cross-region image replication for you to migrate ECSs between accounts and regions.
IMS enables you to create system and data disk images and reuse these images on the cloud platform for batch deployment.
Constraints
Local storage space is occupied and only image files no larger than 1 TB can be used.

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

3 OS Compatibility and Migration Restrictions
3.1 What Are Supported Source Server OSs and Migration Restrictions?
Table 3-1 lists the source server OSs supported by SMS. If you need to migrate a source server whose OS is not included in Table 3-1 to HUAWEI CLOUD, use any of the following methods: Use Image Management Service (IMS) to create an image of the source
system disk, import the image to the cloud platform, and use the imported image to create an ECS. For details, see Creating a Windows System Disk Image from an External Image File or Creating a Linux System Disk Image from an External Image File. Use a public image from IMS to create ECSs and deploy server applications on the newly created ECSs. With this method, there is no need for you to migrate source servers. Use the Cloud Migration Service on HUAWEI CLOUD. Supported Source Server OSs

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

Table 3-1 Supported source server OSs

OS OS Type

Bit

UEFI Remarks

Wind ows

Windows Server 2003 (risky)

32/64 No

Supported by the old version only.

You are advised to select an S or SN series ECS as the target server since network exceptions may occur on ECSs of other series after migration.

Windows Server 2003 R2 32/64 No (risky)
Supported by the old version only.
You are advised to select an S or SN series ECS as the target server since network exceptions may occur on ECSs of other series after migration.

Windows Server 2003 and 2003 R2 may have security vulnerabilities that there is no patch for. After the migration, the system may be vulnerable to attack. You will need to configure firewalls or security groups to restrict accesses.
When a Windows Server 2003 or 2003 R2 server is migrated, the NIC driver may not be automatically loaded. You need to load the NIC driver. For details, see How Do I Load the NIC Driver for a Windows Server 2003 or 2003 R2 Server After the Migration?

Windows Server 2008

32/64 No

Windows Server 2008 R2 64

A Windows Server 2008 or 2008 R2 server cannot be booted in UEFI mode.

Windows Server 2012

Yes N/A

Windows Server 2012 R2 64

Yes

Windows Server 2016

Yes

Windows Server 2019

Yes

Windows 7

32/64 No

Windows 8.1

32/64 No

Windows 10

32/64

32bit versio n: No
64bit versio n: Yes

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

OS Type
Red Hat

Bit

Red Hat Enterprise Linux 64 6.0 (supports only the KVM platform.)
Red Hat Enterprise Linux 64 6.1
Red Hat Enterprise Linux 64 6.2
Red Hat Enterprise Linux 64 6.3
Red Hat Enterprise Linux 64 6.4
Red Hat Enterprise Linux 64 6.5
Red Hat Enterprise Linux 64 6.6
Red Hat Enterprise Linux 64 6.7
Red Hat Enterprise Linux 64 6.8
Red Hat Enterprise Linux 64 6.9
Red Hat Enterprise Linux 64 6.10
Red Hat Enterprise Linux 64 7.0
Red Hat Enterprise Linux 64 7.1
Red Hat Enterprise Linux 64 7.2
Red Hat Enterprise Linux 64 7.3
Red Hat Enterprise Linux 64 7.4
Red Hat Enterprise Linux 64 7.5
Red Hat Enterprise Linux 64 7.6

UEFI Remarks No
No No No No No No No No No No Yes Yes Yes Yes Yes Yes Yes

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

OS Type
Cent OS

Bit

Red Hat Enterprise Linux 64 7.7

Red Hat Enterprise Linux 64 7.8

Red Hat Enterprise Linux 64 7.9

Red Hat Enterprise Linux 64 8.0

Red Hat Enterprise Linux 64 8.1

Red Hat Enterprise Linux 64 8.2

CentOS 6.0 (supports

only the KVM platform.)

CentOS 6.1

CentOS 6.2

CentOS 6.3

CentOS 6.4

CentOS 6.5

CentOS 6.6

CentOS 6.7

CentOS 6.8

CentOS 6.9

CentOS 6.10

CentOS 7.0

CentOS 7.1

CentOS 7.2

CentOS 7.3

CentOS 7.4

CentOS 7.5

CentOS 7.6

CentOS 7.7

UEFI Remarks
Yes
Yes
Yes
Yes
Yes
Yes
No
No No No No No No No No No No Yes Yes Yes Yes Yes Yes Yes Yes

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

OS OS Type
CentOS 7.8 CentOS 7.9 CentOS 8.0 CentOS 8.1 CentOS 8.2 Oracl Oracle Linux 6.1 e Oracle Linux 6.2 Oracle Linux 6.3 Oracle Linux 6.4 Oracle Linux 6.5 Oracle Linux 6.6 Oracle Linux 6.7 Oracle Linux 6.8 Oracle Linux 6.9 Oracle Linux 6.10 Oracle Linux 7.0 Oracle Linux 7.1 Oracle Linux 7.2 Oracle Linux 7.3 Oracle Linux 7.4 Oracle Linux 7.5 Oracle Linux 7.6 Oracle Linux 7.7 Oracle Linux 7.8 Oracle Linux 7.9 Oracle Linux 8.0 SUSE SUSE Linux Enterprise Server 11 SP2

Bit

UEFI Remarks

Yes

32/64 No

Yes

32/64 No

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

OS OS Type

Bit

UEFI Remarks

SUSE Linux Enterprise Server 11 SP3

32/64

32bit versio n: No
64bit versio n: Yes

SUSE Linux Enterprise Server 11 SP4

32/64 No

SUSE Linux Enterprise 64

Yes

Server 12 SP1

SUSE Linux Enterprise 64

Server 12 SP2

SUSE Linux Enterprise 64

Server 12 SP3

SUSE Linux Enterprise 64

Server 12 SP4

SUSE Linux Enterprise 64

Server 12 SP5

Ubun Ubuntu Server 12.04 tu
Ubuntu Server 12.10

Ubuntu Server 13.04

Ubuntu Server 13.10

Ubuntu Server 14.04

Yes

Ubuntu Server 14.10

Yes

Ubuntu Server 15.04

Ubuntu Server 16.04

Yes

Ubuntu Server 16.10

Yes

Ubuntu Server 17.04

Ubuntu Server 18.04

Yes

Ubuntu Server 19.04

Debia Debian GNU/Linux 8.2.0 64

Debian GNU/Linux 8.4.0 64

Debian GNU/Linux 8.5.0 64

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

OS OS

Bit

Type

Debian GNU/Linux 8.6.0 64

Debian GNU/Linux 8.7.0 64

Debian GNU/Linux 8.8.0 64

Debian GNU/Linux 9.0.0 64

Debian GNU/Linux 9.3.0 64

Debian GNU/Linux 9.5.0 64

Debian GNU/Linux 9.6.0 64

Debian GNU/Linux 9.8.0 64

Debian GNU/Linux 9.9.0 64

Debian GNU/Linux 10.0 64

Euler EulerOS 2.2

EulerOS 2.3

EulerOS 2.5

Amaz Amazon Linux 2.0

Linux Amazon Linux 2018.3

UEFI Remarks
No No No No No No No No No No No No No No No

Migration constraints and limitations

Table 3-2 Constraints and limitations on source servers

Source Server Type Description

Only the OSs included in Table 3-1 are

supported by SMS.

Migrations of servers running multiple OSs are not supported.

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

Source Server Type Description

Available disk space

Migrations will fail in both of the following scenarios:
Windows
There is a partition greater than 600 MB, but the available space is less than 320 MB.
There is a partition smaller than 600 MB, but the available space is less than 40 MB.
Linux There is less than 200 MB of available space on the root partition space is less than 200 MB.

File system

Windows: Only NTFS is supported.
Linux: Only ext2, ext3, ext4, VFAT, XFS, Btrfs, and ReiserFS file systems are supported.

Shared file system

Only files on the local disk can be migrated. Files in the shared file systems, such as NFS and CIFS file systems, cannot be migrated.

Encrypted files

OSs that contain protected folders and encrypted volumes cannot be migrated.

Database and Active SMS does not support AD and multi-node Directory Domain (AD database migration. DS) application

Applications bound to Migrations of OSs that contain applications bound

hardware

to hardware are not supported.

Dynamic disk

In Windows OSs, dynamic disks are migrated as basic disks. After the migration is complete, the target ECS will not have dynamic disks.

Servers added to a domain

If a server added to a domain is migrated, the target ECS must be added to the domain after the migration is complete.

3.2 What Are the Important Statements of SMS?
Source server data collection statement
After the Agent is installed and configured on the source server, it automatically reports the source server information to SMS only for a migration feasibility check. For details about the source server information that are collected, see What Kind of Information About Source Servers Are Collected by SMS? To use SMS, you need to allow SMS to collect source server information.
License invalidity statement

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

After OSs, applications, and files on source servers are migrated to target ECSs, the SIDs and MAC addresses of the servers will be different. This means that some OS or application licenses may be invalidated. SMS is not responsible for this type of issue. For Windows OS licenses, you can use the license server on HUAWEI CLOUD to obtain a new license. For application licenses, you will need to update or obtain them at your own expense.
Target ECS disk formatting description
During the migration, disks on the target ECS are formatted and repartitioned. Any existing data on the target ECS will be lost. Before the migration, make sure you back up any data on the target ECS that you need to save and ensure that the disk can be formatted. Otherwise, SMS is not responsible for any data loss incurred.
If your target ECSs on HUAWEI CLOUD cannot be started after the migration, HUAWEI CLOUD can provide technical support to help you solve the problem, but does not promise that the all possible problems can be resolved. There are many possible reasons that the ECS may be unable to start, for example:
The source server could not be restarted.
The source server has a non-standard OS configuration.
The source server has drivers or software that is incompatible with HUAWEI CLOUD.
To adapt source servers to HUAWEI CLOUD, SMS modifies the system configuration of the target ECSs. For details about the modifications, see What Are the Differences Between Target ECSs and Source Servers After the Migration? SMS can ensure data consistency before and after the migration but cannot ensure that your services can run properly after the migration. You need to modify related service configurations.

3.3 How Many Servers Can I Migrate Concurrently Using SMS?
You can migrate a maximum of 1,000 servers at a time. If you need to migrate more than 1000 servers, delete the migrated servers from the server list timely so that other servers can continue to be migrated.

3.4 What Can I Do If Message "The source server runs Windows 2003. Network may be unavailable after migration." Is Displayed?

Scenario

Currently, the NIC driver for Windows Server 2003 is compatible only with S3 ECSs, SN3 ECSs, and HECSs. If your target ECS has other specifications, the ECS may be unable to access the Internet after the migration since the system may not automatically load the NIC driver. You can, however, manually load the NIC driver. For details, see Solutions.

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

CAUTION
It is recommended that you select an S or SN series ECS as the target server since network exceptions may occur on ECSs of other series after migration.
Possible Causes
Microsoft no longer provides official support for Windows Server 2003. The KVM NIC driver provided by Microsoft for Windows Server 2003 has the following compatibility issues: The NIC driver may be incompatible with your ECS. The NIC driver may not have been loaded after the target ECS was started.

CAUTION
Microsoft no longer provides security updates for Windows Server 2003. Windows Server 2003 is vulnerable to network attacks. You are advised to upgrade Windows Server 2003 to Windows Server 2012 or later.

Solutions

Solution 1: Select a S3 ECS, SN3 ECS, or HECS as the target server. Solution 2: 1. Click Start > Run. 2. Enter devmgmt.msc and press Enter to open the device manager.
Figure 3-1 Device Manager

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

3. Right-click Network adapters and choose Update Driver Software from the shortcut menu.

Figure 3-2 Updating the driver software

4. In the displayed Hardware Update Wizard dialog box, perform operations according to the following figures.

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

5. In the Install From Disk dialog box, select the specified driver file C: \Windows\System32\drivers\netkvm.sys. Figure 3-3 Selecting a driver file
6. Check whether the driver was successfully loaded. If the NIC driver is displayed as shown in Figure 3-4, the driver is successfully loaded.

Issue 11 (2021-01-08)

Server Migration Service FAQs
Figure 3-4 Loaded NIC driver

3 OS Compatibility and Migration Restrictions

3.5 What Should I Do If Message "The target ECS is not booted with UEFI. Create an ECS using the image whose boot mode is UEFI." Is Displayed During Migration Task Creation?

Symptom

If the source server is booted with UEFI, message "The target ECS is not booted with UEFI. Create an ECS using the image whose boot mode is UEFI." is displayed when you create a migration task.

Possible Causes
The target ECS was created using a BIOS image and cannot be started after the migration. You must select an ECS created using the image whose boot mode is UEFI.

Solution Using the Management Console
Step 1 Download the target UEFI image file. If the image file is in your OBS bucket, go to Step 3. Windows image file Linux image file
Step 2 Upload the image file to the OBS bucket.
Step 3 Create a private image.

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

1. Set Source to the image file uploaded. 2. In the Image Information area, set Boot Mode to UEFI.

Step 4 Use the private image created in Step 3 to create an ECS.
For details, see Creating a Windows System Disk Image from an External Image File or Creating a Linux System Disk Image from an External Image File.
----End

Solution Using API
Step 1 If the current region does not support changing the boot mode to UEFI using the management console, perform the following operations:
Call the API to update the image attributes and change the value of hw_firmware_type to uefi.
API URI: PATCH /v2/cloudimages/{image_id}
For details about how to call the API, see Updating Image Information.
[ { "op": "add", "path": "/hw_firmware_type", "value": "uefi" }
]
Step 2 Use the updated image to create an ECS again.
----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

3.6 What Should I Do If Message "Incompatible file system of the source server" Is Displayed?

Symptom

After the migration feasibility check is complete, the system displays a message indicating that the source file system is incompatible.

Possible Causes
The file system on the source server is not supported by SMS.

Solution

Currently, SMS supports ext2, ext3, ext4, XFS, VFAT, and Btrfs.
For unsupported file systems such as ReiserFS, you can copy files to other file systems, uninstall the unsupported file systems, and then perform the migration.
If this is not allowed on the source server, you can:
Use Image Management Service (IMS) to create an image of the source system disk and import the image as an external image file. For details, see Creating a Windows System Disk Image from an External Image File or Creating a Linux System Disk Image from an External Image File.
Use a public image from IMS to create ECSs and deploy server applications on the newly created ECSs. With this method, there is actually no server migration involved
Use the Cloud Migration Service on HUAWEI CLOUD.

3.7 What Should I Do If the Source Server Lacks a Necessary Driver File?

Symptom

After you start the Agent, the source server does not pass the migration feasibility check, and an error message is displayed on the SMS management console, as shown in the following figure.

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

Possible Causes
After the Agent is started, it will verify the driver files on the source server. If any necessary driver files are missing, the preceding error is reported. The following files will be verified: * C:\Windows\system32\DRIVERS\atapi.sys * C:\Windows\system32\DRIVERS\pciidex.sys * C:\Windows\system32\DRIVERS\intelide.sys

Solution

Check whether the preceding files are there in the preceding paths on the source server. If any of them are missing, use the driver repair tool to repair the file or copy the file from another server.

3.8 What Should I Do If the VSS Service Is Not Installed on the Source Server?

Symptom

After the Agent is started, your source server running Windows does not pass the migration feasibility check, and the message "VSS not installed on the source server" is displayed on the SMS management console.

Issue 11 (2021-01-08)

Server Migration Service FAQs
Figure 3-5 Error message

3 OS Compatibility and Migration Restrictions

Possible Causes
The possible causes are as follows: 1. The VSS service was not installed on the source server. 2. The VSS service was disabled on the source server.

Solution

1. Open the Task Manager and check whether the VSS service is available. If it is, go to 2. If it is not, go to 3.

Figure 3-6 Checking whether VSS is available

Issue 11 (2021-01-08)

Server Migration Service FAQs

3 OS Compatibility and Migration Restrictions

2. Modify the configuration file to disable I/O monitoring.
If you do not need to synchronize data, you can modify the configuration file to disable I/O monitoring.
In the Agent installation directory config, change the value of enablesync to False in the g-property.cfg file, and then restart the Agent.

Figure 3-7 Modifying the g-property.cfg file

3. Check VSS status. If its status is Stopped, right-click the service and choose Open Services from the shortcut menu. Locate and right-click Volume Shadow Copy, and choose Properties from the shortcut menu. On the displayed Volume Shadow Copy Properties window, change the Startup type to Manual. Click OK.
Figure 3-8 Changing the startup mode of VSS

4. Go back to the Task Manager window, locate and right-click VSS, and choose Start from the shortcut menu.

Issue 11 (2021-01-08)

Server Migration Service FAQs
Figure 3-9 Starting VSS

3 OS Compatibility and Migration Restrictions

5. Log in to the SMS management console, locate the row that contains the source server to be migrated, and in the Operation column, choose More > Delete This Server. After the deletion is complete, restart the Agent.
Figure 3-10 Delete This Server

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

4.1 How Do I Configure Network Security for SMS?

Scenarios

You need to install the Agent on the source server to be migrated. During the migration, the source server needs to communicate with SMS and the target ECS.

Figure 4-1 SMS networking

Connecting Source Servers to HUAWEI CLOUD API Gateway
SMS-Agent depends on the following HUAWEI CLOUD services: IAM, ECS, EVS, IMS, VPC, SMS, OBS, and DNS. During the migration, ensure that the

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Agent on the source server can call the APIs of these services in the region where the target ECS is located.
IAM and SMS are global-level services and need to connect to iam.myhuaweicloud.com and sms.apsoutheast-1.myhuaweicloud.com.
ECS, EVS, IMS, VPC, and DNS are region-level services and need to connect to the endpoints of the region where the target ECS is located. For details about service endpoints, see Endpoints.
OBS needs to connect to both obs.cn-north-1.myhuaweicloud.com and the endpoint of the region where the target ECS is located.
Table 4-1 lists the corresponding endpoints when the target ECS is located in the CN South-Guangzhou region.

Table 4-1 Dependent services and bucket addresses

Service/Bucket Endpoint Address

IAM

iam.myhuaweicloud.com

SMS

sms.apsoutheast-1.myhuaweicloud.com

OBS

obs.cn-north-1.myhuaweicloud.com

ECS

ecs.cn-south-1.myhuaweicloud.com

EVS

evs.cn-south-1.myhuaweicloud.com

VPC

vpc.cn-south-1.myhuaweicloud.com

IMS

ims.cn-south-1.myhuaweicloud.com

OBS

obs.cn-south-1.myhuaweicloud.com

DNS

dns.cn-south-1.myhuaweicloud.com

agent.bucket.en sms-agent-2-0.obs.ap-

dpoint

southeast-1.myhuaweicloud.com

agent.conf.bucke sms-agent-config-inter.obs.ap-

t.endpoint

southeast-1.myhuaweicloud.com

Description Global-level services
Region-level services
Bucket addresses

NOTE
Retain the default values of agent.bucket.endpoint and agent.conf.bucket.endpoint (sms-agent-2-0.obs.apsoutheast-1.myhuaweicloud.com and sms-agent-config-inter.obs.apsoutheast-1.myhuaweicloud.com). The URLs of other dependent services depend on the region where the target ECS is located.
If the DNS server address cannot be set on the source server, you need to configure the IP address corresponding to the URL in the local DNS configuration file (C:\Windows\System32\drivers\etc\hosts for Windows and /etc/hosts for Linux) to ensure that the URL can be properly resolved. The

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

IP address of each API can be obtained by running the ping url command. Figure 4-2 shows an example of opening the IP address.

Figure 4-2 Opening the IP address

Connecting Source Servers to Target ECSs
If you want to use an EIP to connect the source server to the target ECS, you need to purchase and configure an EIP for the target ECS in advance.
If you want to use Direct Connect or VPN, you need to purchase and configure Direct Connect or VPN connections in advance.
Ports to Be Enabled in the Security Groups of Target ECSs
If the target ECS runs Windows, enable ports 8899 and 8900. If the target ECS runs Linux, enable ports 8900 and 22.
If a network ACL is configured for the target ECS and is associated with the subnet where the target ECS resides, you need to enable the corresponding ports in the network ACL.
For details, see How Do I Configure the Security Group Rules for Target ECSs?
4.2 What Should I Do on the Target ECS Before Creating a Server Migration Task?
Before the migration, if you want to migrate servers to an existing server, make the following preparations:
Step 1 Ensure that ECSs that meet the requirements listed in How Do I Select a Target ECS? are available on HUAWEI CLOUD.
Step 2 Ensure that source servers can access the target ECSs. Elastic IP addresses, VPNs, or Direct Connect connections must be available.
Step 3 Ensure that the security group of the VPC to which your target ECSs belong is correctly configured.
The security group rules for the VPC that the target ECSs belong to must be configured to enable TCP ports 8899 and 8900 for Windows and ports 8900 and 22 for Linux.
For details about how to configure the security group rules for a VPC, see How Do I Configure the Security Group Rules for Target ECSs?

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

CAUTION
During the migration, do not perform any operations on the target ECS, such as stopping or restarting the ECS, attaching or detaching a disk, or changing the password, or the migration will fail.
----End
4.3 How Do I Configure the Security Group Rules for Target ECSs?
1. Log in to the management console. 2. Under Computing, click Elastic Cloud Server. 3. In the ECS list, click the name of the target ECS.
The page providing details about the ECS is displayed. 4. Click the Security Groups tab and view security group rules. 5. Click Modify Security Group Rule.
The Summary page of the security group is displayed. 6. Select the Inbound Rules tab, click Add Rule to configure an access rule for
the inbound direction. For an ECS running Windows, set Protocol & Port to TCP and Port to
8899 and 8900.
Figure 4-3 Add Inbound Rule

To remotely access a Linux ECS, set Protocol to TCP and Port Range to 8900 and 22.

Issue 11 (2021-01-08)

Server Migration Service FAQs
Figure 4-4 Add Inbound Rule

4 Migration Network

Set Source IP address to the IP address segment containing the IP addresses that you want to allow to access the target ECS over the Internet.
NOTE
Default source IP address 0.0.0.0/0 indicates that all IP addresses can access the ECSs in the security group.
7. Click OK.

4.4 What Should I Do If the SSH Connection to the Target ECS Fails to Be Established?

Symptom

The migration task fails to be executed, and the system display a message indicating that the SSH connection to the target ECS fails to be established.

Figure 4-5 SSH connection failure

Possible Causes
During a Linux file-level migration, an SSH connection is established between the source server and the target ECS. If the SSH connection is not set up, the preceding error message is displayed. You are advised to perform the operations described here to locate the cause of the SSH connection failure.
Checking Whether the Target ECS is Stopped

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Checking Whether Port 22 Is Allowed in the Security Group of the Target ECS And Whether the Source IP Address Is Specified
Checking Whether the Source Server Can Connect To the Target ECS Checking Whether the SSH Client Has Been Installed on the Source Server Checking the Status of the sshd Service on the Target ECS or Whether the
Listening Port is 22 Checking Whether the VPC or IP address of the Target ECS Is Changed
During the Migration
Checking Whether the Target ECS is Stopped
Step 1 Log in to the management console.
Step 2 Under Computing, click Elastic Cloud Server. Locate the target ECS and view its status. If the ECS is in the Stopped state, choose More > Start in the Operation column.
----End
Checking Whether Port 22 Is Allowed in the Security Group of the Target ECS And Whether the Source IP Address Is Specified
Step 1 Log in to the management console.
Step 2 On the ECS list page, click the name of the target ECS.
Step 3 On the ECS details page, click the Security Groups tab. Check whether port 22 is allowed in the security group of the target ECS and whether the source IP address is specified correctly.
If port 22 is not allowed in the inbound rules, add an inbound rule for port 22. If such inbound rule exists but the source IP address is not the IP address of the source server and is not 0.0.0.0/0, change the source IP address to 0.0.0.0/0.
For details, see How Do I Configure the Security Group Rules for Target ECSs?
----End
Checking Whether the Source Server Can Connect To the Target ECS
Step 1 Log in to the source server.
Step 2 Ping the EIP of the target ECS from the source server. If the EIP cannot be pinged, check the configurations of DNSs, firewalls, security groups, and local networks of the source and target servers. For details, see Why Cannot an EIP Be Pinged?
----End
Checking Whether the SSH Client Has Been Installed on the Source Server
Step 1 Log in to the source server as user root.
Step 2 Run the following command to check whether the SSH client is installed.
If the SSH path shown in the following figure is not returned, install the SSH client.

Issue 11 (2021-01-08)

Server Migration Service FAQs
command -v ssh

4 Migration Network

----End
Checking the Status of the sshd Service on the Target ECS or Whether the Listening Port is 22
Step 1 Log in to the source server as user root. You can try to use the login password of the target ECS or 1 + first eight characters of the target SK + !.
Step 2 Run serviec sshd status to view the sshd service status.
If the status is not active (running), restart the sshd service. If the listening port is not 22, change the listening port to 22.

----End
Checking Whether the VPC or IP address of the Target ECS Is Changed During the Migration
Check whether the VPC or IP address of the target ECS is changed during the migration. If the VPC or IP address is changed, change it back to the original VPC or IP address. Otherwise, you need to perform the migration again.

4.5 What Should I Do If the Target ECS Cannot Be Accessed?

Symptom

The target ECS cannot be accessed, and either of the following messages is displayed:
Failed to connect to the target ECS. Check whether its IP address is reachable and confirm that port 8900 is enabled.
Failed to connect to the target ECS. Check whether its IP address is reachable and confirm that port 8899 is enabled.

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Possible Causes
During a Windows migration, ports 8899 and 8900 should be enabled on the target ECS for communicating with SMS and the source server. If communication cannot be established, this error occurs. You are advised to perform the operations described here in this section to locate the cause.
Checking Whether the Source Server Can Connect To the Target ECS Checking Whether Ports 8899 and 8900 Are Enabled in the Security Group
of the Target ECS Checking Whether Ports 8899 and 8900 Are Allowed in the Network ACL
of the Target ECS
Checking Whether the Source Server Can Connect To the Target ECS
Step 1 Log in to the source server.
Step 2 Ping the EIP of the target ECS from the source server. If the EIP cannot be pinged, check the configurations of DNSs, firewalls, security groups, and local networks of the source and target servers. For details, see Why Cannot an EIP Be Pinged?
----End
Checking Whether Ports 8899 and 8900 Are Enabled in the Security Group of the Target ECS
Step 1 Log in to the management console.
Step 2 On the ECS list page, click the name of the target ECS.
Step 3 On the ECS details page, click the Security Groups tab. Check whether ports 8899 and 8900 are allowed in the security group of the target ECS and whether the source IP address is specified correctly.
If port 22 is not allowed in the inbound rules, add inbound rule for ports 8899 and 8900. If such rules exist but the IP address in the Source column is not 0.0.0.0/0 or the IP address of the source server, change IP address to 0.0.0.0/0.
For details, see How Do I Configure the Security Group Rules for Target ECSs?
----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Checking Whether Ports 8899 and 8900 Are Allowed in the Network ACL of the Target ECS
Step 1 Log in to the management console.
Step 2 Check whether the subnet of the ECS has been associated with a network ACL.
If you have created a network ACL and associated it with the subnet where the target ECS resides and the inbound rules of the network ACL contain ports 8899 and 8900 as shown in the following figure, change the policy to Allow.
For details, see Modifying a Network ACL Rule.

----End

4.6 What Should I Do If the Source Server Fails to Connect to an API Gateway Due to a Busy Network?

Symptom

The Agent cannot be started, and the either of the following messages is displayed:
Linux: SMS.0201 Failed to start sms agent! Please check the network connection with below commands!
Windows: SMS.0201 Network busy. The source server failed to connect to API Gateway.

Possible Causes
The source server is not connected to the Internet and cannot communicate with IAM or SMS.

Solution
Step 1 Log in to the source server.
Step 2 Run the following commands on the source server:
curl -v https://iam.myhuaweicloud.com:443
curl -v https://sms.cn-north-1.myhuaweicloud.com:443
If curl fail to be executed (for example, if there is a network timeout), the source server cannot access the IAM or SMS management console.
Step 3 Check whether the source server can access the Internet. If it cannot, rectify the fault and restart the Agent. Check the configurations of DNSs, firewalls, security groups, and local networks of the source and target servers. For details, see Why Cannot an EIP Be Pinged?

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Step 4 If a proxy server is used, check whether the proxy server is running properly.
Common proxy problems are incorrect login credentials, network disconnections, and firewall or various software restrictions.
----End

4.7 How Do I Restore the Connection Between the Agent and SMS?

Symptom

The real-time migration status of your server is disconnected, so most operations cannot be performed.

Figure 4-6 Disconnection

Possible Causes
The Agent on the source server is not running. If no operations have been on the Agent for a long time (30 days by default,
but this can be changed using the heartmonitorday parameter in the config/g-property.cfg file), the Agent proactively disconnects from SMS. The network connection between the source server and the Agent is abnormal.
Windows Server 2019/2016/2012 and Windows 10/8.1
Step 1 Log in to the source server, search for the Agent icon in the lower right corner, and check whether the Agent is running properly. If the Agent has exited, restart the Agent. If the Agent is running properly, go to Step 2.
Step 2 On the Agent operation page, check whether the Start button can be clicked. If it can be clicked, the Agent has proactively disconnected from SMS. Click Start to reconnect to it. If it cannot be clicked, go to Step 3.

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Step 3 In the cmd window, run telnet sms.ap-southeast-1.myhuaweicloud.com 443 to check the connection between the source server and the SMS API.
If the connection is unavailable, check whether the DNS and the firewall of the source server are correctly configured.
If the connection is available and data is being transmitted, check whether the outbound bandwidth of the source server is lower than 10 Mbit/s. If yes, the data transmission may occupy all the bandwidth. As a result, the connection between the Agent and SMS times out. In this case, increase the outbound bandwidth of the source server to more than 10 Mbit/s, and then continue the migration.

Step 4 Wait for about a minute and log in to the HUAWEI CLOUD management console. Step 5 Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed. Step 6 In the navigation pane on the left, choose Servers.
In the Real-time Migration Status column, view the connection status of the source server. ----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Windows Server 2008 and Windows 7
Step 1 Log in to the source server, search for the SMSAgentDeploy.exe process, and check whether the Agent is running properly.
If the SMSAgentDeploy.exe process does not exist, restart the Agent and go to Step 2.
Step 2 Go to the SMS-Agent installation directory, run the agent-cli.exe command, and run the status command to check the Agent connection status. If the status is True, go to 4. If the status is False, the Agent has proactively disconnected from SMS. In this case, go to Step 3.

Step 3 Enter connect to reconnect the source server to SMS.
If the value of Connected between sms agent and sms server displayed in the command output is True, the connection between the source server and SMS has been restored.
Step 4 In the cmd window, run the telnet sms.ap-southeast-1.myhuaweicloud.com 443 command to check the connection between the source server and the SMS API.
If the connection is unavailable, check whether the DNS and the firewall of the source server are correctly configured.
If the connection is available and data is being transmitted, check whether the outbound bandwidth of the source server is lower than 10 Mbit/s. If it is, the data transmission may be using up all the bandwidth, which can cause the connection between the Agent and SMS to time out. In this case, increase the outbound bandwidth of the source server to more than 10 Mbit/s, and then continue the migration.

Step 5 Wait for about a minute and log in to the HUAWEI CLOUD management console. Step 6 Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed.

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

Step 7 In the navigation pane on the left, choose Servers.
In the Real-time Migration Status column, view the connection status of the source server.
----End

Linux
Step 1 Use PuTTY or an SSH client to log in to the source server to be migrated.
Step 2 Run the ps -ef | grep -v grep | grep linuxmain command to check whether the Agent is running properly. If the linuxmain process is not running, restart the Agent. If the linuxmain process is running, go to Step 3.

Step 3 Run the ./agent-cli.sh command in the SMS-Agent directory to go to the agentcli page, and run the status command to check the Agent connection status. If the status is True, go to Step 5. If the status is False, the Agent has proactively disconnected from SMS. In this case, go to Step 4.
Step 4 Enter connect to reconnect the source server to SMS.
If the value of Connected between sms agent and sms server displayed in the command output is True, the connection between the source server and SMS has been restored.
Figure 4-7 Reconnecting the source server to SMS

Step 5 In the cmd window, run telnet sms.ap-southeast-1.myhuaweicloud.com 443 to check the connection between the source server and the SMS API.
If the connection is unavailable, check whether the DNS and the firewall of the source server are correctly configured.
If the connection is available and data is being transmitted, check whether the outbound bandwidth of the source server is lower than 10 Mbit/s. If it is, the

Issue 11 (2021-01-08)

Server Migration Service FAQs

4 Migration Network

data transmission may be using up all the bandwidth, which can cause the connection between the Agent and SMS to time out. In this case, increase the outbound bandwidth of the source server to more than 10 Mbit/s, and then continue the migration.

Step 6 Wait for about a minute and log in to the HUAWEI CLOUD management console. Step 7 Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed. Step 8 In the navigation pane on the left, choose Servers.
In the Real-time Migration Status column, view the connection status of the source server. ----End

4.8 What Should I Do If the Migration Progress Is Suspended or Slow?

Symptom

During the migration, the progress bar changes slowly or does not change.

Possible Causes
This problem may be caused by multiple factors, such as the network bandwidth, a large number of small files on the source end, and difference comparison during the data synchronization of a Linux file-level migration.

Procedure

Check the bandwidths of the source and target servers. Provide sufficient bandwidth for the migration process without affecting services.
Check whether there are a large number of small files on the source server. If there are, delete as many unnecessary files as possible.
During the data synchronization of a Linux file-level migration, if the synchronization progress stays at 5% for a long time, be patient. The migration process is comparing and synchronizing the differences between the source and target servers.
Check whether Real-time Migration Status is Disconnected on the SMS console. If the connection is normal, be patient. If the connection fails, see How Do I Restore the Connection Between the Agent and SMS?

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

5.1 How Long Does a Migration Take?
1. Pre-migration evaluation Test the TCP speed from the source server to the target ECS. For details, see How Do I Test the Network with iPerf?

where
T: the migration time, in hour
C: the total data volume of the source server, in GB
S: the TCP speed (in Mbit/s) from the source server to the target ECS, that is, the TCP speed obtained in Step 4.2
U: the network usage, which is related to network quality (jitter, delay, and packet loss). The value is usually between 50% and 80%.
For example, if the total data volume of the source server is 100 GB, the TCP speed tested by iPerf is 100 Mbit/s, and the network usage is 70%, the migration time is calculated as follows:
Migration time T = 100 GB x 1000 x 8 / 100 Mbit/s / 3600 / 70% 3.17 hours
You can refer to Table 5-1 to view the migration time of source servers of different data volumes and TCP speeds assuming that the network usage U is 70%.

Table 5-1 Migration time

Total Data Volume on Source Server C (GB)

TCP Speed S (Mbit/s)

10 GB

0.5 Mbit/s

Migration Time T (Hour)
NOTE For migration time T, if the unit is hour, two digits are retained after the decimal point. If the unit is min, the value is an integer.
SMS is not recommended.

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

Total Data Volume on Source Server C (GB)

TCP Speed S (Mbit/s)

30 GB 50 GB 100 GB

1 Mbit/s 5 Mbit/s 10 Mbit/s 100 Mbit/s 500 Mbit/s 1000 Mbit/s 0.5 Mbit/s 1 Mbit/s 5 Mbit/s 10 Mbit/s 100 Mbit/s 500 Mbit/s 1000 Mbit/s 0.5 Mbit/s 1 Mbit/s 5 Mbit/s 10 Mbit/s 100 Mbit/s 500 Mbit/s 1000 Mbit/s 0.5 Mbit/s 1 Mbit/s 5 Mbit/s 10 Mbit/s 100 Mbit/s 500 Mbit/s 1000 Mbit/s

Migration Time T (Hour)
NOTE For migration time T, if the unit is hour, two digits are retained after the decimal point. If the unit is min, the value is an integer.
SMS is not recommended. 6.35 hours 3.17 hours 0.32 hour (about 19 minutes) 0.06 hour (about 4 minutes) 0.03 hour (about 2 minutes) SMS is not recommended. SMS is not recommended. 19.04 hours 9.52 hours 0.95 hour (about 57 minutes) 0.19 hour (about 11 minutes) 0.10 hour (about 6 minutes) SMS is not recommended. SMS is not recommended. SMS is not recommended. 15.87 hours 1.59 hours 0.32 hour (about 19 minutes) 0.16 hour (about 10 minutes) SMS is not recommended.
3.17 hours 0.63 hours (about 38 minutes) 0.32 hour (about 19 minutes)

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

Total Data Volume on Source Server C (GB)

TCP Speed S (Mbit/s)

500 GB
1 TB
Greater than 1 TB

0.5 Mbit/s 1 Mbit/s 5 Mbit/s 10 Mbit/s 100 Mbit/s 500 Mbit/s 1000 Mbit/s 0.5 Mbit/s 1 Mbit/s 5 Mbit/s 10 Mbit/s 100 Mbit/s 500 Mbit/s 1000 Mbit/s N/A

2. Evaluation during migration (remaining time)
T = C x 1000 x 8 x (80% - P) / 60% / S / 3600
T: the time required, in hours
C: the total data volume of the source servers
P: the transmission progress. P can be viewed on the SMS console. If P is larger than 80%, the data transmission is complete and you do not need to evaluate the remaining time.

S: the migration speed in Mbit/s. S cannot be tested accurately with iPerf. To obtain the accurate migration speed:

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

Windows: Choose Windows Task Manager > Performance >
Resource Monitor to view the migration speed S for Windows OSs.

Linux: You are advised to use the sar tool or use /proc/net/dev to
monitor the NIC speed. Take an example where there is 100 GB to be migrated (C), the progress (P) is 70%, and the migration speed (S) is 100 Mbit/s, for our formula, T = C x 1000 x 8 x (80% - P) / 60% / S / 3600 If we plug in the numbers, we get: T = 100 x 1000 x 8 x (80% - 70%) / 60% / 100 / 3600 = 0.37 hour
5.2 How Do I View the Remaining Migration Time?
The remaining migration time depends on how much data is left to be migrated and on how fast it is being migrated. Because the migration rate changes over time, the remaining time shown on the SMS management console is only an estimate. You can perform the following operations to view the remaining migration time:
Step 1 Log in to the HUAWEI CLOUD management console.
Step 2 Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed.
Step 3 In the navigation pane on the left, choose Servers.
The server list is displayed.
Step 4 Locate the target source server, hover over the icon corresponding to Full Replication in the Migration Stage > Real-Time Status, and view the remaining migration time.
Figure 5-1 Remaining time

----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

5.3 How Is the Migration Rate Displayed on the SMS Console Calculated?

Metrics

Table 5-2 Related metrics

Metric

Windows BlockLevel

Linux File-Level

Linux Block-Level

Total data

Total used space of all partitions to be migrated. You can right-click a partition and choose Properties from the shortcut menu. On the General tab, you see details about partition usage.

Total used space of all partitions to be migrated. You can run the df -TH command to view the used and available space on each partition.

Total size of all partitions to be migrated. You can run the fdisk -lu command to view the size of all the partitions.

Migrated data

Total size of all migrated data blocks that are located in the used partition space.

Total size of all migrated files.

Total size of all migrated data blocks in the partition.

Elapsed time

Time elapsed after a migration starts.

Remainin Remaining time = (Total data Migrated data)/Migration rate g time

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

Metric

Windows BlockLevel

Linux File-Level

Linux Block-Level

Migration rate

Calculated using the amount of data migrated over the last 5 seconds. For example, if 200 MB data was migrated over the last 5 seconds, the migration rate is calculated as 320 Mbit/s (200 MB x 8/5s). The migration rate is not the same as the NIC rate because the data is compressed before being transmitted through NICs. For details, see Windows Block-Level Migration.

Actual migration speed, which is the NIC rate of the target ECS.

Calculated using the amount of data migrated over the last 5 seconds. For example, if 200 MB data was migrated over the last 5 seconds, the migration rate is calculated as 320 Mbit/s (200 MB*8/5s). The migration rate is not the same as the NIC rate because the data is compressed before being transmitted through the NIC. For details, see Linux Block-Level Migration.

Windows Block-Level Migration
Windows block-level migration rates are classified into two types. One is the rate displayed on the SMS console, which is the average migration rate over the last 5 seconds. The other is the actual NIC throughput for the migration process, which is less than what is displayed on the console because the data is compressed before being transmitted through the NIC
Migration rate displayed on the SMS console (before compression)
The migration rate displayed on the console is the actual amount of data migrated per second, which is the data transmission rate before compression. This rate shown is based on the average amount of data migrated over the last 5 seconds. For example, if 200 MB of data was transmitted over the last 5 seconds, and the amount of data after compression is 50 MB, the rate displayed on the console is 320 Mbit/s (200 MB*8/5s), but the NIC throughput for the migration process is 80 Mbit/s (50 MB*8/5s).

Actual NIC throughput (after compression)
During a Windows block-level migration, the Agent compresses data before transmitting it to the target ECS. The agent on the target ECS decompresses

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

the data and writes the data to disks. The actual NIC throughput is the network bandwidth occupied by the migration process. You can view this rate in the task managers on the source server and target ECS. However, you can view this rate only after the target ECS is unlocked. The following uses Windows Server 2012 as an example.

CAUTION
You can view the network bandwidth occupied by the migration process in the task manager. Use the migration rate displayed on the SMS console to estimate the migration duration.
The NIC rate of the source server also includes the bandwidth occupied by applications running on the source server. Therefore, you need to check the migration rate of the migration process. The rate displayed in the task manager is the compressed data transmission rate.
A Windows block-level migration rate is stable because it is not affected by the number or size of files to be migrated.
Linux File-Level Migration
During a Linux file-level migration, data is not compressed, so the migration rate displayed on the console and the NIC throughput should match.
However, there is an exception. A Linux file-level migration is inefficient in transferring small files. When migrating a large number of small files, the network bandwidth cannot be fully utilized. In such a scenario, the migration rate is far lower than the available network bandwidth.

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

Linux Block-Level Migration
During a Linux file-level migration, data is not compressed, so the migration rate displayed on the console and the NIC throughput should match.

5.4 How Do I Speed Up Migration?
Improve your network speed. You can test the network performance from the source server to the target ECSs on HUAWEI CLOUD. For details, see How Do I Test the Network with iPerf? If the network speed is less than 500 Kbit/s, check the following items:
If the source server is in a data center, check the bandwidth, switching devices, routing devices, security devices (such as firewalls), network lines, and network protocols between the source server and the Internet for issues. If there are any issues, contact network engineers to rectify the fault. It is recommended that the speed of the network from the source server to HUAWEI CLOUD be at least 10 Mbit/s.
If the source servers are ECSs on public clouds, adjust the bandwidth of the elastic IP addresses bound to source servers to improve the migration speed.
Check that the OS settings of the source servers and target ECSs. On Windows, you can run perfmon to invoke Performance Monitor to monitor the network. On Linux, you are advised to use the sar tool to monitor the network and use /proc/net/dev to monitor the NIC speed. If the network speed is slow, the OS configuration may be incorrect. Note that your OS services and processes cannot limit the NIC speed.
Delete any files you no longer need from the source server before migration.
Check the I/O read and write performance and CPU performance of the source server. On Windows, you can run perfmon to invoke Performance Monitor to monitor the CPU and I/O read and write performance. On Linux , you can use top or ps to monitor the CPU, and use iostat or iotop to monitor the I/O performance. If the I/O and CPU performance of your source server is poor, you are advised to increase the I/O and CPU resources or reduce the workloads on the source server.

5.5 Why Does the Migration Speed Fluctuate?
During the migration, operations such as module initialization, backup, and clearing are performed. It is difficult to accurately estimate the duration of these operations. Speed fluctuation is a normal phenomenon.

5.6 How Do I Test the Network with iPerf?

Prerequisites
Ensure that the networks between the source servers and the target ECSs are connected, and the security group rules configured for the target ECSs on HUAWEI CLOUD allow the ports used for the iPerf test.For details about how to configure

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

security group rules, see How Do I Configure the Security Group Rules for Target ECSs?
This test must be performed before the migration, or the results will be inaccurate. This test almost has no impact on services running on the source server.
Procedure
Step 1 Download iPerf based on the OS type of the source server.
Step 2 Decompress the iPerf software package in a directory on the source server and target ECS (or other ECSs in the same region as that of the target ECS). On a Windows server, the iPerf installation package looks like:

Step 3 Start iPerf in server mode by running a command on the command line interface (CLI) on the target ECS. Use Windows as an example.
1. Run the following command to switch to the iperf directory:
cd /d path
In the preceding command, path indicates the path where on the target ECS you wish to decompress iPerf to.
2. Run the following command to run iPerf on SMS:
iperf3 -p port -s
In the preceding command, port indicates the SMS listening port for the iPerf tool. It is recommended that port 8900 be used for Windows and port 22 for Linux. Ports 8900 and 22 are data transmission ports used by the target ECS. You can also use other ports during the test, but ensure that the TCP or UDP port can be opened for the security group rule configured for the target ECS.
For details about parameters, run the iperf -h command.
Assume that port 8900 is used for Windows. If Server listening on 8900 is displayed in the command output, iPerf in server mode is running properly.

Step 4 To test the TCP bandwidth, UDP jitter, packet loss rate, and bandwidth, use a CLI to start iPerf in client mode on the source server. For Windows:
1. Run the following command to switch to the iperf directory: cd /d path In the preceding command, path indicates the path on the source server for storing the decompressed iPerf tool.

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

2. Run the following command to run iPerf to test the TCP bandwidth:
iperf3 -c target_IP -p port -t time
In the preceding command, -c indicates that iPerf is running on the source server (client).
target_IP is the IP address of the target ECS, which is the server that runs iPerf in server mode.
port is the port for connecting to the target ECS, that is, the iPerf listening port in Step 3.2.
time is the total test time. The default unit is second.
Assume that port 8900 is used for Windows. After the iPerf client is successfully connected to the iPerf server, the bandwidth is tested. After the test is complete, check the result.

3. Run the following command to start iPerf to test the UDP jitter, packet loss rate, and bandwidth.
iperf3 -c target_IP -p port -u -t time
-u is the UDP jitter, packet loss rate, and bandwidth.
target_IP is the IP address of the target ECS, which is the server that runs iPerf in server mode.
port is the port for connecting to the target ECS, that is, the iPerf listening port in Step 3.2.
time is the total test time. The default unit is second.
Assume that port 8900 is used for Windows. After the iPerf client is connected to the iPerf server, UDP jitter, lost/total datagrame, and bandwidth are tested. After the test is complete, check the result.

Issue 11 (2021-01-08)

Server Migration Service FAQs

5 Migration Duration

4. To test the network delay, run the following ping command: ping target_iP target_IP is the IP address of the target ECS, which is the server that runs iPerf in server mode. Configure the security group rule for the VPC to which the target ECSs belong to allow Internet Control Message Protocol (ICMP) packets to pass through.
Step 5 Run the following command to obtain more online help of the iPerf tool. Alternatively, you can obtain the help information about iPerf on its official website.
iperf3 -h
----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

6 Agent Installation and Startup
6.1 How Do I Install the Agent on Source Servers?
If the source server runs Windows, install the migration Agent by referring to Installing the Windows Agent.
If the source server runs Linux, install the Agent by referring to Installing the Linux Agent.
6.2 What Should I Do If The Agent Package Fails to Be Downloaded?
Step 1 Ensure that your computer can access the Internet. Then, run the following command in the cmd window to check whether the IP address shown in the following figure is displayed:
nslookup sms-agent-2-0.obs.ap-southeast-1.myhuaweicloud.com

Step 2 If the IP address is not displayed, add the following record to the hosts file, and download the package again:
100.125.100.2 sms-agent-2-0.obs.ap-southeast-1.myhuaweicloud.com
NOTE
In Windows, the hosts file is stored in the C:\Windows\System32\drivers\etc directory and requires an administrator account to edit. In Linux, the hosts file is stored in the /etc directory.
Step 3 If an IP address is parsed, check whether the hosts file contains a record of the domain name. If it does, delete the record and download the package again.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

Step 4 If the download still fails after you have performed the preceding steps, you are advised to use another computer to download the package and upload it to the source server.
----End

6.3 How Do I Verify the Software Integrity of the Migration Agent?
Step 1 Log in to the management console and go to the SMS console.
Step 2 In the navigation pane on the left, choose Migration Agents. Click Download sha256 in the pane of the Agent version you need to save the file containing the hash value to a local directory.
Step 3 Run the following commands to obtain the hash value of the migration Agent you have downloaded: Windows Agent certutil -hashfile SMS-Agent-PyN.exe SHA256 SMS-Agent-PyN.exe is the migration Agent name. Linux Agent sha256sum SMS-Agent.tar.gz SHA256
Step 4 Compare the hash value obtained in Step 2 with that obtained in Step 3.
If they are the same, the integrity verification is successful.
----End

6.4 Why There Is No Record for My Source Server on the SMS Console After the Agent Is Configured?
After the Agent is installed and configured on the source server, the source server information is not displayed on the Source Management page on the SMS management console. In this case, you need to perform the following operations:
Step 1 Check whether the source server has been registered with SMS. When the source server is registered with SMS successfully, message "Upload success. Waiting for the SMS instruction" will be displayed on the CLIs of Windows Agent Phthon2 and Linux Agent, and message "sms agent start up successfully" will be displayed in the GUI of Windows Agent Python3.
Step 2 Currently, there are two versions of the SMS console. The source server information is not shared between two versions.
Old version
Cick Source Management to view the record about the source server. If you are currently viewing the new version, click Back to Old Version in the navigation pane on the left to access the old version.
New version

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

Click Servers to view the record about the source server. If you are currently viewing the old version, click Go To New Edition (NEW) in the navigation pane on the left to access the new version.
Step 3 Check whether the login account and the entered AK and SK are correct.
Step 4 If the source server has been successfully registered with the SMS service, and the console version matches the Agent version, but no records are displayed, wait for about a minute and refresh the page.
----End

6.5 How Do I Find and Modify the SMS-Agent Configuration Files?
The configuration files of the SMS-Agent are stored in the installation directory of the Agent. For details, see SMS-Agent configuration files.

Table 6-1 SMS-Agent configuration files

SMSAgent Configura tion File

Location

auth.cfg
cloudregion.json

Windows: C:\SMS-AgentPy3\config or C:\SMS-AgentPy2\config
Linux: ../SMS-Agent/agent/ config
NOTE ../ indicates the download path of the SMS-Agent.

disk.cfg

gproperty.cf g

Description
Modify this configuration file when an HTTPS proxy server is used for migration. You do not need to modify this file when a public network is used for migration.
You do not need to modify this file.
Modify this configuration file when you want to migrate a partition on the source server running Windows to a specified disk on the target server.
It is recommended that you do not modify this main configuration file. If you need to modify this file, modify it under the guidance of professional personnel.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

6.6 Why Is My Target ECS Locked During the Migration?
During the migration, operations on the target ECS may cause migration failures. To ensure a smooth migration, the target ECS will be automatically locked during the migration and unlocked after the migration. For details about how to manually unlock the target ECS, see How Do I Unlock the Target ECS?

6.7 How Do I Unlock the Target ECS?

Symptom

After the migration is complete, the target ECS should be automatically unlocked. However, the target ECS may fail to be unlocked for some reasons. For instance, there may be insufficient permissions or network issues. In this case, you can unlock the target ECS manually by performing the operations described in this section.

Possible Causes
The most typical reasons are as follows: The token is invalid or the network is faulty Account permissions are insufficient.

Solution

1. Check whether the corresponding migration record still exists. If the record has not been deleted, in the Operation column, choose More > Unlock Target Server to unlock the target ECS.
If the system displays a message indicating that you do not have the permission to unlock the target ECS, use an account with the required permission and try again.

Figure 6-1 Unlocking a target server

2. If the migration record has been deleted, unlock the ECS by following the instructions provided in Unlocking an ECS.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

6.8 What Should I Do If Message "No such file or directory: 'rsync':'rsync" Is Displayed During the Linux Agent Startup?

Symptom

If this error message is displayed after you enter the AK and SK and start the Linux Agent, rsync is not installed on the source server. You need to install rsync and restart the Agent.

Figure 6-2 Error message

Possible Causes
Linux migration depends on rsync. If rsync is not installed on the source server, the Agent cannot be started.

Solutions

The operations for different OSs are as follows:
CentOS and Red Hat 1. Use PuTTY or an SSH client to log in to the source server as user root. 2. Run the following command to install rsync:
yum install rsync

3. Enter y and press Enter.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

4. Run the following command to query the information about rsync: rsync --version If the following information is displayed, rsync has been successfully installed:

5. Run the following command to start the migration Agent: ./startup.sh
6. Read the displayed information carefully, enter y, and press Enter. Figure 6-3 Confirmation
7. Enter the AK and SK of the HUAWEI CLOUD account to which the target ECS belongs. When the following information is displayed, the Linux SMS-Agent has been started successfully. SMS-Agent will start sending source server information to SMS.
SUSE 1. Use PuTTY or an SSH client to log in to the source server as user root. 2. Run the following command to install rsync:
zypper install rsync

3. Enter y and press Enter.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

4. Run the following command to display rsync details: rsync --version If the following information is displayed, rsync has been installed:

5. Run the following command to start the migration Agent: ./startup.sh
6. Read the displayed information carefully, enter y, and press Enter. Figure 6-4 Confirmation
7. Enter the AK and SK of the HUAWEI CLOUD account to which the target ECS belongs. When the following information is displayed, the Linux SMS-Agent has been started successfully. SMS-Agent will start sending source server information to SMS.
Ubuntu 1. Use PuTTY or an SSH client to log in to the source server as user root. 2. Run the following command to install rsync:
apt-get install rsync

3. Run the following command to display rsync details: rsync --version

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

If the following information is displayed, rsync has been installed:

4. Run the following command to start the migration Agent: ./startup.sh
5. Read the displayed information carefully, enter y, and press Enter.
6. Enter the AK and SK of the HUAWEI CLOUD account to which the target ECS belongs. When the following information is displayed, the Linux SMS-Agent has been started successfully. SMS-Agent will start sending source server information to SMS.

6.9 What Can I Do If the System Displays a Message Indicating That the Application Cannot Be Started Due to Incorrect Parallel Configuration?

Symptom Solution

After the Agent (Python2) for Windows 2003 and 2008 is installed, the Agent cannot be started. The system displays a message indicating that the application cannot be started due to incorrect parallel configuration.
For details, see What Can I Do If the Agent Does Not Start The First Time I Launch?

6.10 What Can I Do If the Agent Does Not Start The First Time I Launch?
Due to the permission structure on some Windows machines, the Agent cannot be started the first time you launch it. If this happens:

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

1. Right-click the Start menu.
2. Click Run and enter cmd.
3. Enter cd C:\SMS-Agent-Py2 to switch to the Agent installation directory. Run SMSAgentDeploy.exe and enter your AK and SK.

Figure 6-5 Starting SMSAgentDeploy.exe

NOTE
You must have a valid AK and SK. For details about how to obtain the AK and SK, see How Do I Obtain the AK and SK of an Account? and How Do I Obtain the AK and SK of an IAM User?
If the error message "[401:{"error_msg": " Incorrrect IAM authentication in formation: xxx xxx not exist","error_code":"APIGW.0301","request_id":"xxx"} "]" is displayed during the execution, check whether the entered AK and SK are correct.

6.11 What Can I Do If I/O Monitoring Does Not Start At Agent Startup?

Symptom

When the Agent is being started, the error message "SMS.1902 Failed to start I/O monitoring" is displayed.

Procedure

If Failed to start I/O monitoring is displayed when you start the migration Agent on the source server:
1. Uninstall the Agent and re-install it.
a. If the Agent (Python 3) is installed, enter the AK and SK when prompted. b. If the Agent (Python 2) is installed, the Figure 6-6 is displayed. (If Figure
6-6 is not displayed, double-click start.bat in the installation directory.) Enter the AK and SK when prompted.

Issue 11 (2021-01-08)

Server Migration Service FAQs
Figure 6-6 Entering the AK and SK

6 Agent Installation and Startup

2. Check whether antivirus software is installed on the source server. If antivirus or security software is installed, or the firewall is enabled, a pop-up window may be displayed indicating the I/O monitoring driver was blocked. Allow the system to run the I/O monitoring process. If there is no pop-up warning, but the driver is blocked, you need to start the I/O monitoring driver manually. Add C:\Windows\System32\drivers \HwDiskMon.sys to the trusted zone of the antivirus software and restart the Agent.If the problem persists, uninstall the antivirus software.
NOTE
Some antivirus software has a persisted blocking functions and may block the driver even if disabled.
3. Modify the configuration file to disable I/O monitoring. If you do not need to synchronize data, you can modify the configuration file to disable I/O monitoring. In the Agent installation directory config, change the value of enablesync to False in the g-property.cfg file, and then restart the Agent.
Figure 6-7 Modifying the g-property.cfg file

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

6.12 What Should I Do If Message "INTERNAL ERROR: cannot create temporary directory!" Is Displayed During the Agent Startup?

Symptom

After SMS-Agent-Py2 is installed, the Agent fails to be started and the error message "INTERNAL ERROR: cannot create temporary directory!" is displayed.

Possible Causes
Some files will be generated in a temp directory of the C: dirve when you install the Agent. This error accurs if the available space of the C: drive is insufficient or if you do not have the permission to create a temp directory there.

Solutions

Check the available space of C: drive. If the space is not enough, clean up the drive.
Check whether you can create a temp directory on the C: drive. You may need to obtain write permissions.

6.13 What Should I Do If the Migration Agent Displays a Message Indicating that AK and SK Authentication Fails?

Symptom

After the AK and SK of HUAWEI CLOUD are entered in the Agent, the AK and SK authentication fails. The specific error message depends on the OS.
Windows: AK/SK authentication failed. Linux: AK/SK authentication failed. Ensure that the system time is consistent
with the standard time and the AK and SK are correct.
NOTE
For details about how to obtain the AK and SK, see How Do I Obtain the AK and SK of an Account? or How Do I Obtain the AK and SK of an IAM User?

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

Possible Causes
The entered AK or SK is incorrect. The system time of the source server is consistent with standard time. The time zone of the source server is configured incorrectly. The AK and SK have been deleted or disabled.

Procedure
Step 1 Check whether the entered HUAWEI CLOUD account AK and SK are correct, especially whether spaces are copied or characters are missing during the copy. If yes, go to Step 2. If no, enter the correct HUAWEI CLOUD account AK and SK. If the authentication succeeds, no further action is required. If the authentication fails, go to Step 2.
Step 2 Check whether the system time of the source server is consistent with the standard time of the time zone where the source server is located.
If not, change the system time of the source server to the standard time of the time zone where the source server resides, and enter the HUAWEI CLOUD account AK and SK for authentication again.

CAUTION
If services on the source server depend on the system time, check whether the time can be changed to avoid impact on services.

Step 3 Change the time zone of the source server so that the system time plus the time zone is equal to the standard UTC time. For details, see Changing the Time Zone.
Step 4 Choose My Credential > Access Keys to check whether the AK is in the list. If no, change or create an AK. If yes, check whether it is disabled. If the AK is disabled, enable it.
----End

6.14 What Should I Do If the AK or SK Cannot Be Pasted During the Startup of the Agent on a Source Server Running Windows 2003 or 2008?

Symptom

During the startup of SMS-Agent-Py2, when you right-click the command window, the shortcut menu is not displayed. As a result, you cannot paste the AK and SK.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

Prerequisites
You have obtained the AK and SK. For details about how to obtain the AK and SK, see How Do I Obtain the AK and SK of an Account? or How Do I Obtain the AK and SK of an IAM User?

Solution
Step 1 Log in to the source server.
Step 2 Go to the Agent installation directory C:\SMS-Agent-Py2 and double-click agentstart.exe.
Step 3 Copy the AK, click the icon in the upper left corner of the window, choose Edit > Paste from the displayed menu, and press Enter.
Step 4 Copy the SK, click the icon in the upper left corner of the window, choose Edit > Paste from the displayed menu, and press Enter.

----End

6.15 What Should I Do If the Message "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" Is Displayed During the Agent Startup?

Symptom

In Linux, after you run ./startup.sh or bash startup.sh to start the Agent, the following message is displayed: "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte".

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

Possible Causes
The character set of the source system is incorrect and is incompatible with SMS. As a result, the Agent fails to be started.
Handling Method
1. Log in to the source server. 2. Run the following command to set the character set:
export LANG="en_US.UTF-8"
3. Restart the Agent. If the problem persists, run the following command to set the character set:
export LC_ALL="en_US.UTF-8" export LANG="en_US.UTF-8"
Impact Scope
Setting the character set affects only the current shell and applications in the shell. It does not affect your files or other applications.

6.16 What Should I Do If the WMI Module Fails to Be Loaded During the Agent Startup?

Symptom

When you start the Agent, the message "SMS.1205 Failed to load wmi" is displayed.
Figure 6-8 WMI loading failure

Possible Causes
Windows Management Instrumentation (WMI)-related files are missing or damaged. In Windows, the Agent uses the WMI module to collect source server information, such as CPU, memory, and disks details. The missing or damaged WMI-related files need to be restored.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

CAUTION
WMI will be stopped during the restoration. Confirm that stopping WMI will not affect services on the source server. The restoration will also change the files on the source server, which may involve certain risks. It is recommended that you perform the operations on a cloned source server first.
If the issue persists, you can create an ECS by following the instructions provided in Creating a Windows ECS from an Image.

Restoring WMI
Step 1 Right-click This Computer in the navigation pane on the left in your file explorer and choose Manage from the shortcut menu.
Step 2 On the Computer Management page, choose Services and Applications > Services. Stop Windows Management Instrumentation.
Step 3 Change C:\Windows\System32\wbem\repository to C:\Windows \System32\wbem\repository_old.
Step 4 Start Windows Management Instrumentation. Step 5 Open the cmd window as administrator. Step 6 Run the following command to go to the C:\Windows\System32\wbem\
directory: cd C:\Windows\System32\wbem\ Step 7 Run the following commands to restore WMI: for /f %s in ('dir /b *.mof') do mofcomp %s for /f %s in ('dir /b en-us\*.mfl') do mofcomp en-us\%s Step 8 Restart the Agent.
----End

6.17 What Should I Do If the Agent Fails to Be Installed?

Symptom

When you install the Agent on a source server running Windows, the system displays a message indicating that the Agent cloud not be installed because Agent files cloud not be written or opened for writing.

Possible Causes
If a message indicating a write failure is displayed, it may be that there is not enough space on the system disk of the source server.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

If a message indicating a read failure is displayed, the possible cases are as follows:
a. Role permissions are insufficient. b. Antivirus software is blocking access to the files.

Agent Files Write Failure
Windows The partition size is greater than 600 MB, but the available space is less than 320 MB. The partition size is smaller than 600 MB, and the available space is less than 40 MB.
Linux The available space on the root partition is less than 200 MB.

Agent Files Read Failure
1. Install the Agent as an administrator. 2. Disable the antivirus software and try again. If the error persists, uninstall the
antivirus software and try again.

6.18 What Should I Do If the Agent Fails to Be Started Due to Insufficient Space in /tmp on the Source Server Running Linux?

Symptom

When you run the sh startup.sh command to start the SMS Agent, the following message is displayed:
Failed to write all bytes for cffibackend.cpython-36m-x86_64-linux.gnu.so fwrite: No space left on device

Possible Causes
When the Agent is being started, directories and files are generated in the /tmp directory on the source server. These files will occupy about 40 MB of space. You need to reserve more than 100 MB space for the /tmp directory.

Solution
Step 1 Log in to the source server.
Step 2 Run the df -lh command to check whether there is a volume mounted to the /tmp directory. If there, check the available space for that volume.
Step 3 If there is not enough space available, delete unnecessary files or expand the volume.
----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

6.19 What Should I Do If the Agent Fails to Be Started on My Source Server Running Linux?

Symptom

When you run sh startup.sh to start the SMS Agent, the system displays the message "SMS.5102 Agent startup failed because the noexec permission is not allowed on /tmp for SMS Agent. Please remount /tmp without noexec."

Possible Causes
This problem occurs because a block device is mounted to the /tmp directory, but the exec permission was not assigned or the noexec permission was assigned during the mounting.

Solution
Step 1 Log in to the source server.
Step 2 Run the mount -l | grep /tmp command. If information similar to the following is displayed, the noexec permission is assigned:
/dev/vdb1 on /tmp type ext4 (rw, noexec, relatime, data=ordered)
Step 3 Remount the block device to the /tmp directory. Do not assign the noexec permission during the mounting. Alternatively, run the mount -o remount exec /tmp command to assign the exec permission.
Step 4 Run the mount -l | grep /tmp command again. If information similar to the following is displayed, restart the Agent.
/dev/vdb1 on /tmp type ext4 (rw, relatime, data=ordered)
----End

6.20 What Can I Do If the System Displays a Message Indicating That Only x86 Servers Can Be Migrated?

Symptom

When you start the Agent, the error message shown in the following figure is displayed.

Possible Cause
SMS can migrate only x86 servers.

Issue 11 (2021-01-08)

Server Migration Service FAQs

6 Agent Installation and Startup

Solution

If your source server is based on the ARM architecture, Kunpeng Professional Services on HUAWEI CLOUD can help you.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

7.1 Why Was a 40 GB EVS Disk Added to the Target ECS During the Migration?
During the migration, SMS temporarily creates and attaches a 40 GB EVS disk to the target ECS. The disk will be automatically deleted after the migration is complete. Do not delete this EVS disk during the migration, or the migration will fail.

7.2 What Should I Do If a System Disk Cannot Be Attached to the Target ECS?

Symptom

After the migration fails, the system disk of the target ECS is a temporary disk with the disk name starting with sms. As a result, the original system disk of the target ECS cannot be attached back.

Possible Causes
The temporary image was not uninstalled during the migration. As a result, the system disk of the target ECS is still the temporary disk created by SMS. You need to manually uninstall the temporary disk.

Procedure

The following uses a Linux server as an example to describe how to handle this problem.
1. To connect the source server to the Agent, run the ./agent-cli command in the SMS-Agent directory on the source server, enter connect, and press Enter.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

2. Run the clear command in the CLI of agent-cli.
After about a minute, the temporary mirror disk on the target server is detached and deleted, and the original system disk is attached again.

7.3 What Should I Do If the Migration Task Failed Because the Disks on the Source Server Had Changed?

Symptom

When you start the migration, the message shown in the following figure is displayed.

Possible Causes
The Agent collects information about the disks on the source server every two hours. This error will occur if the source server disks are changed during the period from the last collection to the start of migration. Possible changes in source server disks include:
Disks or partitions were attached or detached to the source server.
The capacity of a source partition may have been expanded, and now the target disk space is insufficient.
A large amount of data was written to a source partition, and now the target partition space is insufficient.
The file system type of the source partition was changed.

Solution
Step 1 Log in to the HUAWEI CLOUD management console. Step 2 Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

Step 3 In the navigation pane on the left, choose Servers.
Locate the row that contains the source server, and in the Operation column, choose More > Delete This Server.
Step 4 Log in to the source server and restart the Agent. The Agent automatically reports changed source disk information to SMS.
Step 5 Reconfigure the target ECS and start the migration. For details, see Configuring the Target ECS, Starting Replication, and Launching the Target ECS.
----End

7.4 How Do I Move a Partition to Another Disk in Windows?

Scenario

The system disk of the source server is 1.1 TB and has two partitions (disk C: 100 GB and disk D: 1024 GB). You want to divide the system disk into two disks after the migration: one 100 GB and one 1024 GB.

Procedure

1. Go to the Agent configuration directory on the source server.
For the Agent of Python3 version, the directory is C:\SMS-Agent-Py3\config. For the Agent of Python2 version, the directory is C:\SMS-Agent-Py2\config.
2. Modify the disk.cfg file and save it.
[volmap] D = 2
NOTE
D = 2 indicates that migrate data in disk D to the second disk on the target ECS.
If the source server has multiple partitions and you want to split them into multiple disks after the migration, modify the disk.cfg file as follows: D=2, E=3, F=4...
3. On the SMS console, delete the source server on the Source Management page.
4. Restart the migration Agent. The partition location in the source server details is changed.

CAUTION
The system partition and boot partition on the source server can be migrated only to the first disk. Therefore, this method cannot be used for the system partition and boot partition.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

7.5 How Do I Shrink the Disk Partitions on My Source Server Running Windows?

Symptom

When you use SMS to migrate a source server running Windows, the disk size of the target ECS should be at least as large as the size recommended on the Source Management page. Otherwise, the migration may fail. If you have created a target ECS running Windows, and the disk size of the target ECS is too small, you can reduce the size of the source server to be no larger than the target ECS.

Possible Causes
For a migration to be successful, the target server must be at least as large as the source. If it is not, you need to either scale up the target ECS or shrink the source server. On a Windows server, you can shrink disk partitions of the source server using the Windows Disk Management tool.

Procedure

1. Choose Start, enter diskmgmt.msc in the search box. The Disk Management tool is displayed.
2. Right-click the partition of the disk you want to shrink and choose Shrink Volume. The Shrink Volume dialog box is displayed.

3. Enter the amount you wish to shrink the partition by in the Enter the amount of space to shrink in MB text box.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

4. Click Shrink. The new space available is displayed as unallocated space.
Figure 7-1 Disk partition after shrink
5. Log in to the HUAWEI CLOUD management console. 6. Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed. 7. In the navigation pane on the left, choose Servers.
The server list is displayed. 8. Locate the source server to be deleted, and in the Operation column, click
More > Delete This Server. Alternatively, select the target source server and choose More > Delete This Server in the upper left corner of the server list. 9. In the displayed Delete This Server dialog box, click Yes. 10. Report the information about the source server to SMS again. If you have uninstalled the Agent from the source server, install the Agent
again. For details, see Installing the Windows Agent. If the Agent has been installed on your source server, restart the Agent to
upload the source server information to SMS.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

7.6 How Do I Exclude Specified Disk Partitions for Migration on Windows?
Procedure
Step 1 Go to the Agent configuration directory on the source server. For the Agent (Python3), the directory is C:\SMS-Agent-Py3\config. For the Agent (Python2), the directory is C:\SMS-Agent-Py2\config.
Step 2 Modify the disk.cfg file as follows and save it. [volmap] D = -1
NOTE
D = -1 indicates that disk D will not be migrated.
Step 3 Restart the Agent. You will see that disk D is not displayed in the source server details. If drive D is still displayed in the source server details, delete the source server record and register the source server with SMS again. NOTE
This method can be used only before the migration. During the migration, restarting the Agent will cause a migration failure.
----End

7.7 What Can I Do If I Failed to Modify the Configuration Files of the Target Server?

Symptom

The error message SMS.3101 Failed to modify the configuration files of the target server" is displayed when you modify the configuration files of the corresponding destination server of a source server running Linux.

Possible Causes
The possible cause for the error is as follows: The /etc/hosts file is configured incorrectly.

Solution

If the error is caused by incorrectly configured /etc/hosts:
Possible cause: The content of the /boot/grub2/grub.cfg file is written to the /etc/default/grub file.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

Handling method: On HUAWEI CLOUD, create an ECS running the same or similar OS as the source server, copy the /etc/default/grub file of the new ECS to overwrite that file of the faulty ECS, and try again.

7.8 What Should I Do If Snapshot Creation Failed?

Symptom

The error message "SMS.1904 Failed to create snapshot." is displayed during the migration.

Possible Causes
Before data migration from servers running Windows, the VSS module is used to create snapshots to ensure that data on the source and target servers is from the same point in time. If the VSS module on the source server is faulty, the snapshot creation will fail.

Procedure
Step 1 Go to the Agent configuration directory on the source server. For the Agent of Python3 version, the directory is C:\SMS-Agent-Py3\config. For the Agent of Python2 version, the directory is C:\SMS-Agent-Py2\config.
Step 2 Open the g-property.cfg file and change the value of enablesnapshot to False. Restart the migration task. In this way, the migration task skips snapshot creation.

Figure 7-2 Modifying the configuration parameter

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

NOTE
If you skip snapshot creation, data on the target server and the source server may be from different points in time during migration, and services on the target server may fail to be started. If this happens, you can stop the software on the source server when no services are running, and then perform a new data synchronization to ensure that the data on the source and target servers is from the same point in time.
----End

7.9 What Should I Do If a Partition Fails to Be Mounted?

Symptom

A Linux file-level migration fails, and the message "SMS.3205 Failed to mount partition /dev/vdc1 to directory /mnt/vdc1." is displayed.

Possible Causes
The file system on the source server is not supported by SMS.

Solution

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

7.10 What Should I Do If Partitions Fail to Be Migrated or Synchronized to the Target ECS?

Symptom

During the migration, the system displays a message indicating that a partition failed to be migrated or synchronized to the target ECS.

Possible Causes
The possible causes are as follows:
The network from the source server to the target ECS is disconnected. There is not enough space on the target ECS disk that the partition is
migrated or synchronized to. The disk is detached from the target ECS. The TAR processes exit.

Solutions

1. Check whether the fault was caused by a network disconnection. If it was, rectify the network fault by referring to What Should I Do If the SSH Connection to the Target ECS Fails to Be Established?
2. Check whether there is enough space on the target ECS disk.
If there is not enough space, delete any unnecessary files on the partition on the target ECS or the source server, make sure there is enough space, and try again.
3. Check whether the disk which the partition is migrated or synchronized to is detached from the target ECS.
If the disk was not attached, attach the disk to the target ECS again. Log in to the SMS console, choose Servers in the navigation pane on the left, locate the source server, and click Start in the Operation column.
4. Check whether there are ongoing TAR processes on the source server or target ECS.
If there are not, it was terminated. Restart the TAR process. Log in to the SMS console, choose Servers in the navigation pane on the left, locate the source server, and click Start in the Operation column.

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

7.11 What Should I Do If /etc/fstab on the Source Server Cannot Be Read?

Symptom

When the target ECS is being started, the message "SMS.3104 Failed to read /etc/ fstab on the source server." is displayed.

Possible Causes
The source server does not have an fstab file. If this is the case, an error is reported when the system attempts to read the file during configuration modification.

Solution

1. Log in to the source server and restore the /etc/fstab file.
2. Log in to the SMS console and click Servers in the navigation pane on the left.
3. Locate the target source server and click Start in the Operation to start the migration again.

7.12 What Should I Do If There Are Not Enough Disks on the Target ECS?

Symptom

When you configure or start the target ECS, the message "SMS.1311 Insufficient disks on the Target ECS." is displayed.

Possible Causes
During the configuration of the target ECS, SMS checks whether the number of disks on the target ECS is the same as that on the source server. When this

Issue 11 (2021-01-08)

Server Migration Service FAQs

7 Disks

error occurs, check whether the number of disks on the target ECS is less than that on the source server, or whether the disks on the target ECS have been manually deleted or detached. In this case, perform the operations described in Checking the Number of Disks on the Target ECS and Source Server.
After the Agent is started, disk addition to or deletion from the source server will make the Agent fail to identify the disk changes. In this case, perform the operations described in Checking Whether a Disk Was Added To or Deleted From the Source Server.

Checking the Number of Disks on the Target ECS and Source Server
Step 1 Click Service List. Under Migration, click Server Migration Service. Step 2 The SMS console is displayed. Step 3 In the navigation pane on the left, choose Servers. Step 4 The server list is displayed. Step 5 Locate the target source server, choose More > Delete Target ECS Config. Step 6 Attach disks to the target ECS again to ensure that the number of disks on the ECS
is no less than that of disks on the source server. Step 7 Go back to the server list page, click Configure in the Target ECS column of the
target server. Reconfigure the target ECS and start the migration task again.
----End

Checking Whether a Disk Was Added To or Deleted From the Source Server
Step 1 Click Service List. Under Migration, click Server Migration Service. The SMS console is displayed.
Step 2 In the navigation pane on the left, choose Servers. The server list is displayed.
Step 3 Locate the target source server, choose More > Delete This Server. Step 4 Attach disks to the target ECS again to ensure that the number of disks on the ECS
is no less than that of disks on the source server. Step 5 Go back to the server list page, click Configure in the Target ECS column of the
target server. Reconfigure the target ECS and start the migration task again.
----End

Issue 11 (2021-01-08)

Server Migration Service FAQs

8 Migration or Synchronization Failures

8.1 What Should I Do If New Data Is Generated on the Source Server During the Migration?
To synchronize the incremental data to the started target ECS, click Start in the Operation column that contains the source server to start incremental replication. When the migration status becomes Continuous Synchronization, click Launch Target ECS. When the real-time migration status becomes Completed, the new data has been synchronized to the target ECS.

8.2 What Should I Do If the Migration Module Stops Abnormally and Cannot Synchronize Data?

Symptom

The message "SMS.1414 The migration module stops abnormally and cannot synchronize data." is displayed during continuous synchronization.

Possible Causes
The migration Agent or the source server has been restarted.

Issue 11 (2021-01-08)

Server Migration Service FAQs

8 Migration or Synchronization Failures

Solution

NOTE
The source server has a process that monitors disk changes and synchronizes the incremental data from the source server to the target ECS. If the source server is restarted, this process is stopped. As a result, changes on the source server cannot be correctly synchronized to the target ECS.
In this case, the migration task cannot continue. Delete the task and create a new migration task. To prevent this issue from happening, take care to avoid restarting the source server or Agent during migration.

Issue 11 (2021-01-08)

Server Migration Service FAQs

9 Target ECS Configuration and Startup

9.1 What Are the Differences Between Target ECSs and Source Servers After the Migration?

Table 9-1 Differences between target ECSs and source servers after the migration

Parameter Change Target ECS

Remarks

Server SID

Changed

The SID of the target ECS is used.

The SID of Windows OS is a hardware attribute, which is different on each server and cannot be migrated. Therefore, if the source server is added to the domain for management, the SID will become invalid after being migrated to the target ECS and the target ECS needs to be added to the domain again.

Server Name Possibly changed

The system may update the server name.

Services bound to the server name may be affected.

OS Type

Unchange d

The OS of the target ECS is the same as the OS of the source server.

The original OS of the target ECS is overwritten.

MAC Address Changed

Specifies the MAC address of the target ECS.

The MAC address is an inherent attribute of a NIC, and is determined when the target ECS is created.

Issue 11 (2021-01-08)

Server Migration Service FAQs

9 Target ECS Configuration and Startup

Parameter NIC Name
IP address
DNS
Disk Name
Username Password (Certificate)

Change Possibly changed
Changed
Possibly changed
Possibly changed
Unchange d
Unchange d

Target ECS

Remarks

The NIC name of the target ECS is determined by the NIC configuration file on the source server.

You can modify the NIC name after the migration. Otherwise, services may be affected.

The IP address of the target ECS is used.

The IP address of the source server changes to the IP address of the target ECS after the migration. If the network segment of the VPC to which target ECSs belong contains the private IP address of the source server, the private IP address can remain unchanged.

The DNS of the target ECS is determined by the DNS configuration on the source server.

After the migration is complete, you can modify the DNS.

The name of the target EVS disk depends on the virtualization type of the target ECS.

Services are not affected.

The username N/A of the target ECS is the same as that of the source server.

The username, N/A certificate, and password of the target ECS are the same as those of the source server.

Issue 11 (2021-01-08)

Server Migration Service FAQs

9 Target ECS Configuration and Startup

Parameter Change
Registry and Changed startup items

Other data

Unchange d

Target ECS

Remarks

Modify the parameter value as required.

SMS modifies the registry and startup items to adapt to HUAWEI CLOUD.

Other data,

N/A

including files,

applications,

and

configurations,

must be

consistent with

those on the

source server.

9.2 What Are the Changes of Target ECS Authentication After the Migration?
After the migration, the changes of the target ECS authentication are as follows:
After the migration is complete, the authentication mode of the target server must be the same as that of the source server, namely the username, certificate, and password of the target ECS must be same as those of the source server.
If the migration is not complete, the disk on the target ECS is a temporary disk whose name starts with sms. If Use existing is selected, the password of the agent image is the original password of the target ECS. If Create during migration is selected, the password of the target ECS is in the 1 + first eight characters of the target SK + ! format. For example, if the first eight characters of the SK are RgybsdPP, the password is 1RgybsdPP!.
CAUTION
If the password is incorrect, reset the password by following the instructions provided in Password Reset.

Issue 11 (2021-01-08)

Server Migration Service FAQs

9 Target ECS Configuration and Startup

9.3 How Do I Configure and Optimize My Target ECSs Running Windows After the Migration?

Scenarios

You need to manually install drivers on the target ECSs to solve the compatibility issues between the source servers running Windows OSs and the target ECSs.

Procedure

1. Log in to the management console.
2. Under Computing, click Elastic Cloud Server.
3. In the ECS list, view the flavors of the target ECS.
The ECS flavors are named in the format of AB.C.D, for example, m2.8xlarge.8.
A specifies the ECS type. B specifies the type ID. C specifies the flavor size. D specifies the ratio of memory to vCPUs expressed in a digit. For details about ECS flavors, see ECS Types.
If B of your target ECS is 1, for example, s1.small.2, the target ECS is of Xen virtualization. In this case, you need to install PV driver Tools.
If B of your target ECS is not 1, for example, s2.small.3, the target ECS is of KVM virtualization. In this case, you need to install UVP VMTools.
4. Check whether the PV driver Tools or UVP VMTools software package exists on the target ECS based on the target ECS virtualization type queried in 3.
If it is, go to 7.
If it is not, go to 5.
5. Download the PV driver Tools or UVP VMTools software package from the source server based on the target ECS virtualization type queried in 3. For details about how to obtain the software package, see Obtaining Required Software Packages.
6. Synchronize the PV driver Tools or UVP VMTools software package on the source server to the target ECS. For details, see Synchronizing Data After a Migration Task Is Complete. Then, go to 7.
7. Install the driver on the target ECS based on the target ECS virtualization type queried in 3.
a. If the target ECS is of KVM virtualization, install UVP VMTools. For details, see Installing UVP VMTools.
b. If the target ECS is of XEN virtualization, install the PV driver. For details, see Installing the PV Driver,

Issue 11 (2021-01-08)

Server Migration Service FAQs

9 Target ECS Configuration and Startup

9.4 How Do I Activate the Target ECS Running Windows After the Migration?

Symptom

After a source server running Windows is migrated to an ECS on HUAWEI CLOUD through SMS, you need to reactivate the license of the target ECS using the license server of HUAWEI CLOUD.

Prerequisites
The IP address of the DNS server on HUAWEI CLOUD has been configured.

Procedure

1. On the target ECS, choose Start and enter cmd. 2. Run the following command to register the ECS with the KMS server:
slmgr -skms 100.125.1.2 3. Run the following command to check whether the ECS has been activated:
slmgr -ato If error 0xC004F074 occurs, the ECS cannot be activated. In this event, go to 4. 4. Identify the cause of the ECS activation failure.
a. Check whether the private IP address of the ECS is correct.
i. Run the following command to obtain the private IP address: ipconfig
ii. Check whether this IP address is within the denied IP address range configured on the management console. If yes, go to 4.b. If no, go to 4.a.iii.
iii. Run the following command to release the private IP address: ipconfig /release
iv. Run the following command to assign an IP address to the ECS again: ipconfig /renew
v. Run the following command to check whether the ECS has been activated: slmgr -ato
b. Check whether the ECS time is the same as the standard time. If the time is significantly different, the ECS cannot be activated.
c. Run the following command on the ECS to check whether the link between the ECS and the activated server port is reachable: telnet 100.125.1.2 1688

Issue 11 (2021-01-08)

Server Migration Service FAQs

9 Target ECS Configuration and Startup

On the ECS, test the link to the activated server port. If the link failed, perform the following operations:
Verify that the internal ECS firewall and security software such as
SafeDog are disabled, or that the data on TCP port 1688 can bypass the internal ECS firewall.
Verify that the data on port 1688 can bypass the security group rule
in the outbound direction.
NOTE
The Windows client must periodically communicate with the KMS server. Therefore, ensure that the data on port 1688 can bypass the security group in the outbound direction. If the network communication is interrupted, the Windows client automatically enters the inactive state.
d. Run the following command to check whether the ECS has been activated:
slmgr -ato
The system displays a message indicating that the ECS has been activated.

9.5 Why Is the Used Space of C: Drive on the Target Windows ECS Greater Than That on the Source Server After the Migration?

Symptom

In a Windows migration, after the source server is migrated to HUAWEI CLOUD, the used space of C drive on the target ECS will be at least one GB larger than the used space of C drive on the source server. Is that normal?

Possible Causes
This is a normal phenomenon resulting from the fact that the size of paging file, used for virtual memory, tends to be larger on the destination server. You can perform the following steps to adjust the size of the paging file: Perform the following steps to locate the cause:
1. Log in to the source server. 2. Choose Start > Control Panel > Folder Options.
The Folder Options dialog box is displayed. 3. Click the View tab. In the Advanced settings area, perform the following
operations: Deselect Hide protected operating system files (Recommended). Select Show hidden files, folders, and drives and click Apply.

Issue 11 (2021-01-08)

100

Server Migration Service FAQs

9 Target ECS Configuration and Startup

4. Log in to the target ECS and repeat 2 and 3.
5. Compare the size of the virtual memory file pagefile.sys in the Local Disk (C:) on the source and target ECSs.
The size of the pagefile.sys file on the target ECS is greater than that on the source server.
The differences in the sizes of pagefile.sys on the two servers should account for the difference in used space.
6. On the target ECS, click Start.
7. Choose Control Panel > System > Advanced system settings.
The System Properties dialog box is displayed.
8. Click the Advanced tab, click Settings in the Performance area.
The Performance Options page is displayed.
9. Click the Advanced tab, click Change in the Virtual memory area.
The Virtual Memory is displayed.
You can see that the target server uses Automatically manage paging file size for all drives. That is, the size of virtual memory file pagefile.sys on the target ECS is equal to the size of file Installed Memory (RAM) on the target ECS.
If the size of file Installed Memory (RAM) on the target ECS is different from that on the source server, the used space of C drive on the target ECS is inconsistent with that on the source server.

Issue 11 (2021-01-08)

101

Server Migration Service FAQs

9 Target ECS Configuration and Startup

9.6 How Do I Uninstall the SMS-Agent from the Source Server and Target ECS After the Migration?

Symptom

After the migration is complete, you can perform the following operations to uninstall the SMS-Agent from the source server and target ECS.

Windows

Method 1
a. Log in to the server where the SMS-Agent is to be uninstalled. b. Choose Start > All Programs. c. In the All Programs panel, click the SMS-Agent folder. d. Click Uninstall in the SMS-Agent file. e. In the SMS-Agent-1.0.0 Uninstall dialog box, click Yes. Method 2
a. Log in to the server where the SMS-Agent is to be uninstalled. b. Click Start, and then select Computer. c. Go to the C:\Program Files (x86)\SMS-Agent directory. d. Double-click Uninstall.exe. e. In the SMS-Agent-1.0.0 Uninstall dialog box, click Yes.

Linux

1. Log in to the server where SMS-Agent is to be uninstalled as user root. 2. Go to the SMS-Agent installation directory. 3. Run the following command to stop the SMS-Agent:
shutdown.sh 4. Run the following command to go to the parent directory:
cd .. 5. Run the following command to delete the SMS-Agent installation directory:
rm -rf SMS-Agent

9.7 How Do I Configure the Yum Repository After Migration?

Scenarios

If you are migrating servers to HUAWEI CLOUD from Alibaba Cloud, note that the yum repository used on Alibaba Cloud is not a public server address. Therefore, after the server is migrated to HUAWEI CLOUD, the originally configured

Issue 11 (2021-01-08)

102

Server Migration Service FAQs

9 Target ECS Configuration and Startup

repository will be unavailable for your ECS. You will need to change the repository settings to make it available to HUAWEI CLOUD ECSs.

Constraints
Make sure that the DNS server provided by HUAWEI CLOUD has been configured. For instructions about how to obtain an intranet DNS server, see What Are the Private DNS Server Addresses Provided by HUAWEI CLOUD DNS?
The operations described in this section apply to ECSs deployed on x86_64 servers.

Procedure

1. Log in to the ECS as user root. 2. Run the following commands to back up the CentOS-Base.repo file:
mkdir -p /etc/yum.repos.d/repo_bak/ mv /etc/yum.repos.d/*.repo /etc/yum.repos.d/repo_bak/ 3. Use curl to download the CentOS-Base.repo file, and save the file into /etc/ yum.repos.d/: CentOS 6
curl -o /etc/yum.repos.d/CentOS-Base.repo http:// mirrors.myhuaweicloud.com/repo/CentOS-Base-6.repo CentOS 7 curl -o /etc/yum.repos.d/CentOS-Base.repo http:// mirrors.myhuaweicloud.com/repo/CentOS-Base-7.repo 4. Run the following command to clear the original yum cache: yum clean all 5. Run the following command to generate a new cache: yum makecache

9.8 Why Are the File Sizes Before and After the Migration Different?

Symptom

After the migration, the used disk partition space on the target ECS is different from that on the source server.
After the migration, a particular file size on the target ECS is different from that on the source server.

Possible Causes
If there are sparse files on the source server, the total size of the migrated files on the target ECS may be smaller than that on the source server. This is because rsync automatically truncates sparse files during the transmission. The file system

Issue 11 (2021-01-08)

103

Server Migration Service FAQs

9 Target ECS Configuration and Startup

transparently converts metadata representing empty blocks into "real" blocks filled with null bytes at runtime.
You can check whether the files before and after the migration are consistent. For details, see Procedure.
NOTE
In a UNIX file system, when the file displacement is greater than the file length, the next write operation extends the file length, creating a sparse file. This is achieved by writing brief information (metadata) representing the empty blocks to disk instead of the actual "empty" space which makes up the block, using less disk space. The full block size is written to disk as the actual size only when the block contains "real" (non-empty) data.

Procedure

1. Check the size of the file on the source server and the used disk space. The /tmp/test-data.img file is used as an example.
a. Run the following command to check the size of the /tmp/test-data.img file:
ll /tmp/test-data.img
b. Run the following command to check the disk space occupied by /tmp/ test-data.img:
du -sh /tmp/test-data.img

Figure 9-1 Checking the file size

2. After the migration is complete, check the size of the migrated file on the target ECS. Figure 9-2 shows that the used disk space decreases after the migration.
Figure 9-2 Checking target ECS file size

3. Run the following command on the source server and target ECS to obtain the sha256 values of the files to determine whether the files are the same. If the sha256 values of the files are the same, the file content is consistent. sha256sum /tmp/test-data.img
Figure 9-3 Obtaining the sha256 value

Issue 11 (2021-01-08)

104

Server Migration Service FAQs

9 Target ECS Configuration and Startup

9.9 Why Are Data Disks Not Displayed on the Target ECS After a Windows Server is Migrated?
Possible Causes
If the disk policy of the source server is shared disk offline or offline, data disks will become offline after migration.
Solutions
Solution 1 Step 1 Click Start > Run. Step 2 Enter diskmgmt.msc and press Enter. The Disk Management dialog box is
displayed. The data disk is in the Offline state.
Figure 9-4 Offline

Step 3 Right-click the offline data disk and click online.

Issue 11 (2021-01-08)

105

Server Migration Service FAQs
Figure 9-5 Bringing the disk online

9 Target ECS Configuration and Startup

----End Solution 2 Step 1 Right-click the Start menu. Step 2 Click Run and enter cmd. Step 3 Run diskpart to start the disk management tool. Step 4 Run the list disk command to query all disks on the current server. As shown in the following figure, disk 0 is online and disk 1 is offline.

Step 5 Run the select disk 1 command to select the offline disk. Step 6 Run the online disk command to bring the selected offline disk online.

Issue 11 (2021-01-08)

106

Server Migration Service FAQs

9 Target ECS Configuration and Startup

Step 7 If the disk is read-only after it goes online, run the attribute disk clear readonly command to remove the write protection on the disk.
----End

9.10 What Can I Do If the Target ECS Corresponding to My Source Server Running Windows Cannot Access the Internet?

Symptom

After the source server running Windows is migrated successfully, the corresponding target ECS cannot access the Internet.

Possible Causes
The possible causes are as follows:
The network adapter driver of the target ECS is abnormal. The network configuration on the target ECS is incorrect. The NIC drivers of target ECSs running Windows Server 2003 are
incompatible.

Solutions

If the network adapter driver of the target ECS is abnormal, you need to:
1. Search for abnormal network devices in the device manager and use the automatic search function to update the driver. Then restart the target ECS.

Issue 11 (2021-01-08)

107

Server Migration Service FAQs

9 Target ECS Configuration and Startup

2. If the problem persists, disable the driver and enable it, and restart the target ECS.
3. If the problem persists, download VMTools from another server that is in the same AZ as the target ECS. Transfer the downloaded VMTools package to the target ECS and install it on the ECS. Then restart the target ECS.
If the network configuration on the target ECS is incorrect, you need to:
1. In the cmd window, run the ipconfig command to check whether the IP address of the target ECS is the same as that displayed on the ECS management console. If they are different, a static IP address may be set for the target ECS. In this case, change the IP address obtaining mode to DHCP.
2. If the EIP of the ECS can be pinged, but the external domain name cannot be pinged, see Configuring DNS.
If the source server runs Windows Server 2003, see What Can I Do If Message "The source server runs Windows 2003. Network may be unavailable after migration." Is Displayed?

9.11 How Do I Expand the Capacity of a Windows System Disk After the Migration?

Causes

The partitions of the source and target disks will be same after the migration, but if the source server disks was smaller than the target ECS disks, there will be unallocated space left over on the target disk. You can expand the new partition to take advantage of the unallocated space.

Procedure

1. Choose Start > Run. 2. Enter diskmgmt.msc and press Enter.
The Disk Management dialog box is displayed. 3. Right-click partition (C:) and choose Expand Volume.

Issue 11 (2021-01-08)

108

Server Migration Service FAQs
Figure 9-6 Expanding volumes

9 Target ECS Configuration and Startup

4. In the displayed dialog box, click Next. Figure 9-7 Extend Volume Wizard

5. Add the available space to the C partition and click Next.

Issue 11 (2021-01-08)

109

Server Migration Service FAQs
Figure 9-8 Expanding the disk

9 Target ECS Configuration and Startup

6. In the displayed dialog box, click Finish. Figure 9-9 Completing the expansion

7. Check the expanded capacity.

Issue 11 (2021-01-08)

110

Server Migration Service FAQs

9 Target ECS Configuration and Startup

Figure 9-10 Checking the expanded capacity

9.12 What Can I Do If the Server Cannot Be Started After Migration Because the GRUB Version Is Too Old?

Symptom

The server cannot be started after the migration.

Figure 9-11 Failed to start

Issue 11 (2021-01-08)

111

Server Migration Service FAQs

9 Target ECS Configuration and Startup

Possible Causes
The GRUB2 version of the source server is old and has bugs that are not fixed. (The bugs do not affect the system operations, but GRUB fails to be reinstalled.)

Procedure
Step 1 Log in to the source server as user root and run grub2-install to install GRUB2. If the error message "not a correct XFS inode" is displayed during the installation, GRUB fails to be installed.
Step 2 Run the following command to check the installed GRUB2 version: rpm -qa |grep grub2

Figure 9-12 Checking the GRUB2 version

Step 3 Run the following command to upgrade the GRUB2 version: yum update grub2
Step 4 Run the following command to check the upgraded GRUB2 version. Check whether GRUB was successfully upgraded by comparing the version numbers in Figure 9-12 and Figure 9-13. rpm -qa |grep grub2
Figure 9-13 Checking the upgraded GRUB2 version

Step 5 After GRUB2 is installed on the source server, perform the migration task again. After the migration is complete, the server can be started properly. ----End

Issue 11 (2021-01-08)

112

Server Migration Service FAQs

9 Target ECS Configuration and Startup

9.13 What Do I Do If a GRUB Error Occur Because the XFS File System Volume Is Mounted to the /boot Partition?

Symptom

On a source server running CentOS 7.1, the XFS file system volume is mounted to the /boot partition. After the source server is migrated to HUAWEI CLOUD, the corresponding target server fails to be started.

Possible Causes
The XFS file system volume is mounted to the /boot partition, causing a GRUB error. According to the available limited tests, only CentOS 7.1 is affected.

Solutions

Solution 1
Detach the system disk from the target ECS that failed to be started, and attach it to another Linux ECS (for example, CentOS7.6). After the system disk is successfully attached, detach the disk and attach it back to the original ECS.
Solution 2
Edit the GRUB installation script file vi SMS-Agent/agent/linux/resources/ shell/installGrub2.sh on the source server, locate the install_grub2 function, and add the two lines of code in the red box in the following figure. Then restart the Agent for migration.

Issue 11 (2021-01-08)

113

Server Migration Service FAQs

9 Target ECS Configuration and Startup

Figure 9-14 Editing the GRUB installation script file

Solution 3 Upgrade GRUB on the source server. For details, see What Can I Do If the Server Cannot Be Started After Migration Due to an Earlier GRUB Version?
NOTE
Upgrading GRUB on the source server may pose risks to the source server. Exercise caution when performing the upgrade.

Issue 11 (2021-01-08)

114

Server Migration Service FAQs

10 Change History

Released On 2021-01-08
2020-11-05
2020-10-31 2020-10-14

Description
This issue is the eleventh official release. Optimized What Can I Do If the Target ECS
Corresponding to My Source Server Running Windows Cannot Access the Internet? Optimized How Do I Exclude Specified Disk Partitions for Migration on Windows? Added How Do I Find and Modify the SMS-Agent Configuration Files? Added What Can I Do If I Failed to Modify the Configuration Files of the Target Server? Added What Do I Do If a GRUB Error Occur Because the XFS File System Volume Is Mounted to the /boot Partition?
This is the tenth official release. Added What Should I Do If the Source Server
Lacks a Necessary Driver File? Added What Should I Do If the VSS Service Is Not
Installed on the Source Server? Added What Should I Do If the Agent Fails to Be
Started on My Source Server Running Linux? Added Why Is My Target ECS Locked During the
Migration? Added How Do I Unlock the Target ECS?
This issue is the ninth official release. Added What Should I Do If the Migration Task Failed Because the Disks on the Source Server Had Changed?
This issue is the eighth official release. Optimized the structure of section "FAQs."

Issue 11 (2021-01-08)

115

Server Migration Service FAQs
Released On 2020-02-01
2020-2-11
2019-12-10 2019-09-12 2019-08-30
2019-07-18 2019-03-30

10 Change History
Description
This issue is the seventh official release. Added What Should I Do If Message "The target ECS is not booted with UEFI. Create an ECS using the image whose boot mode is UEFI." Is Displayed During Migration Task Creation?
This issue is the sixth official release. Added How Do I Migrate an ECS from One
Account to Another? Added How Do I Migrate an ECS from One Region
to Another? Added What Can I Do If the Server Cannot Be
Started After Migration Because the GRUB Version Is Too Old?
This issue is the fifth official release. Added What Should I Do If a System Disk Cannot Be Attached to the Target ECS?
This issue is the fourth official release. Added What Can I Do If Message "The source server runs Windows 2003. Network may be unavailable after migration." Is Displayed?
This issue is the third official release. Added Why Are the File Sizes Before and After the Migration Different? Added Why Are Data Disks Not Displayed on the Target ECS After a Windows Server is Migrated? Added How Do I Expand the Capacity of a Windows System Disk After the Migration?
This issue is the second official release. Updated Table 3-1 in What Are Supported Source Server OSs and Migration Restrictions?
This issue is the first official release.

Issue 11 (2021-01-08)

116

AH Formatter V6.2 MR8 for Windows : 6.2.10.20473 (2015/04/14 10:00JST) Antenna House PDF Output Library 6.2.680 (Windows)