Server Migration Service - HUAWEI CLOUD1.2 What Are Supported Source Server OSs and Migration Restrictions? Supported source server OSs Table 1-3 Supported source server OSs OS Type

Server Migration Service

FAQs

Issue 07

Date 2020-02-01

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without priorwritten 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 respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin 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, guaranteesor 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 thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Issue 07 (2020-02-01) Copyright © Huawei Technologies Co., Ltd. i

Contents

1 Common.....................................................................................................................................11.1 What Kind of Information About Source Servers Are Collected by SMS?........................................................... 11.2 What Are Supported Source Server OSs and Migration Restrictions?.................................................................. 41.3 What Are the Important Statements of SMS?............................................................................................................101.4 What Is the Block-Level Migration?............................................................................................................................... 111.5 What are Valid Data Blocks?............................................................................................................................................ 11

2 Before Migration................................................................................................................... 122.1 How Can I Configure Network Security for SMS?..................................................................................................... 122.2 What Should I Do on the Target ECSs Before Creating a Server Migration Task?.........................................132.3 How Can I Configure the Security Group Rules for Target ECSs?........................................................................ 142.4 How Do I Obtain the AK and SK of an IAM User?....................................................................................................152.5 How Do I Obtain the AK and SK of an Account?...................................................................................................... 202.6 How Do I Create an ECS?................................................................................................................................................... 212.7 How Do I Compress the Disk Partitions of the Source Server Running a Windows OS?............................ 222.8 What Do I Do If I/O Monitoring Fails to Be Started During Agent Startup?................................................... 252.9 How Do I Migrate an ECS from Account A to Account B?..................................................................................... 262.10 How Do I Migrate Data from One Region to Another?........................................................................................272.11 What Can I Do If Message "The target ECS is not booted with UEFI. Create an ECS using the imagewhose boot mode is UEFI." Is Displayed During Migration Task Creation?............................................................ 27

3 Installing the Migration Agent.......................................................................................... 293.1 What Should I Do If the Source Server Information Is Not Displayed on the Source ManagementPage?................................................................................................................................................................................................ 293.2 How Do I Verify the Software Integrity of the Migration Agent?....................................................................... 293.3 How Can I Install the Migration Agent on Source Servers?...................................................................................303.4 How Do I Reestablish a Connection Between the Migration Agent and the SMS Service?....................... 303.5 What Can I Do If the Linux Agent Cannot Start After the Installation?............................................................323.6 What Can I Do If the Migration Agent AK/SK Authentication Fails?..................................................................36

4 During Migration...................................................................................................................374.1 How Can I Select a Target ECS?.......................................................................................................................................374.2 How Can I Speed Up Migration?..................................................................................................................................... 374.3 How Can I Test the Network with iPerf?...................................................................................................................... 384.4 How Long Does the Migration Take?............................................................................................................................ 414.5 What Do I Do If New Data is Generated on the Source Server During the Migration?.............................. 44

Server Migration ServiceFAQs Contents

Issue 07 (2020-02-01) Copyright © Huawei Technologies Co., Ltd. ii

4.6 What Can I Do If the System Disk on the Target Server Is Still a Temporary Mirror Disk After a Task IsDeleted?.......................................................................................................................................................................................... 444.7 How Do I Modify Configurations to Disable Snapshots?........................................................................................45

5 After Migration...................................................................................................................... 475.1 What Are the Differences Between Target ECSs and Source Servers After the Migration?........................475.2 What Are the Changes of Target ECS Authentication After the Migration?.................................................... 495.3 How Can I Configure and Optimize My Target ECSs Running a Windows OS After the Migration?......495.4 How Do I Activate the Target ECS Running a Windows OS After the Migration?.........................................505.5 Why Is the Used Space of C Drive on the Target Windows ECS Greater Than That on the SourceServer After the Migration?...................................................................................................................................................... 535.6 How Do I Uninstall the SMS-Agent on the Source and Target ECSs Running Windows OSs After theMigration?...................................................................................................................................................................................... 545.7 How Do I Uninstall the SMS-Agent on the Source and Target ECSs Running Linux OSs After theMigration?...................................................................................................................................................................................... 555.8 How Do I Configure the Yum Repository After the Migration?............................................................................555.9 Why Are the File Sizes Before and After the Migration Different?..................................................................... 565.10 Why Are Data Disks not Displayed on the Target ECS After a Windows Server is Migrated?................ 575.11 How Do I Expand the Capacity of a Windows System Disk After the Migration?...................................... 595.12 How Do I Load the NIC Driver for a Windows Server 2003 or 2003 R2 Server After the Migration?............................................................................................................................................................................................................ 625.13 What Can I Do If the Server Cannot Be Started After Migration Due to an Earlier GRUB Version?.... 64

6 Change History...................................................................................................................... 66

Server Migration ServiceFAQs Contents

Issue 07 (2020-02-01) Copyright © Huawei Technologies Co., Ltd. iii

1 Common

1.1 What Kind of Information About Source Servers AreCollected by SMS?

SMS uses the migration Agent to collect information about source servers toevaluate the migration feasibility and provide required data for selecting andconfiguring target ECSs. Table 1-1 lists the information to be collected for aWindows OS. Table 1-2 lists the information to be collected for a Linux OS. Allcollected data is used for data migration only.

Table 1-1 Information about the source server that runs a Windows OS

Item Parameter Objective

Environment checkinformation

OS Version Used for migration feasibilityevaluation: Only source servers withOSs included in Table 1-3 can bemigrated.

Firmware Type Used for migration feasibilityevaluation: The source server can bebooted from BIOS or UEFI.

CPU Used for selecting the target ECS: Thenumber of vCPUs of the target ECScannot be less than that of the sourceserver.

Memory Used for selecting the target ECS: Thememory of the target ECSs cannot beless than that of the source servers.

System Directory Used for configuring target ECSs: Afterthe migration is complete, restore theregistry.

Server Migration ServiceFAQs 1 Common

Issue 07 (2020-02-01) Copyright © Huawei Technologies Co., Ltd. 1


Disk Partition Format Used for configuring target ECSs: Beforethe migration, the disk of the targetECS must be formatted to be the sameas that of the source server.

File System Used for migration feasibilityevaluation: Only the source servers withNew Technology File System (NTFS) filesystem can be migrated.

Available Space Used for migration feasibilityevaluation: If the available space on thesource server partition is insufficient,the migration may fail.

OEM System Check Used for migration feasibilityevaluation: If the system is an OEMsystem, the OS needs to be reactivatedafter the migration.

Driver files Used for migration feasibilityevaluation: The source server musthave a basic disk drive.

System services Used for migration feasibilityevaluation: The Volume Shadow CopyService (VSS) must be available on thesource server.

User permissions Used for migration feasibilityevaluation: You must have theadministrator permissions to run themigration Agent.

NICInformation

● NIC Name● MTU

Used for distinguishing different sourceservers

DiskInformation

● Disk Name● Disk Partition

Format● Disk Size● Used Space

Used for checking whether the diskspecifications of target ECSs meet themigration requirements



Table 1-2 Information about the source server that runs a Linux OS


Environment checkinformation

OS Version Used for migration feasibilityevaluation: Only source servers withOSs included in Table 1-3 can bemigrated.

CPU Used for selecting the target ECS: Thenumber of vCPUs of the target ECScannot be less than that of the sourceserver.

Memory Used for selecting the target ECS: Thememory of the target ECSs cannot beless than that of the source servers.

Paravirtualization Check Used for evaluating migrationfeasibility: The SMS service does notsupport migration of paravirtualizedsource servers.

Firmware Type Used for migration feasibilityevaluation: The source server can bebooted from BIOS or UEFI.

Boot Mode Used for migration feasibilityevaluation: The source server must bebooted from BIOS.

Rsync ComponentCheck

Used for evaluating synchronizationfeasibility: The SMS synchronizationfunction depends on the Rsynccomponent on the source server.

Raw Equipment Check Used for migration feasibilityevaluation: The source servers to bemigrated cannot contain raw devices.

Disk PartitionInformation

Used for migration feasibilityevaluation. The disk type of the sourceserver must be Main Boot Record(MBR) or GUID Partition Table (GPT).

Disk Partition Format Used for configuring target ECSs: Beforethe migration, the disk of the targetECS must be formatted to be the sameas that of the source server.

File System Used for migration feasibilityevaluation: The file system type of thesource server must be ext2, ext3, ext4,VFAT, XFS, Reiserfs, swap, orlvm2_member.




NICInformation

● NIC Name● MTU

Used for distinguishing different sourceservers

DiskInformation

● Disk Name● Disk Partition

Format● Disk Size● Used Space

Used for checking whether the diskspecifications of target ECSs meet themigration requirements

1.2 What Are Supported Source Server OSs andMigration Restrictions?

● Supported source server OSs

Table 1-3 Supported source server OSs

OSType

OS Version Bit UEFI Remarks

Windows

Windows Server 2003(risky)

32/64 No ● Windows Server 2003and 2003 R2 may havesecurity vulnerabilities,and no patch isreleased. After themigration, the systemmay be attacked andbecome abnormal.Therefore, you need toconfigure firewalls orsecurity groups torestrict accesses.

● After a Windows Server2003 or 2003 R2 serveris migrated, the NICdriver may not beautomatically loaded.You need to load theNIC driver. For details,see How Do I Load theNIC Driver for aWindows Server 2003or 2003 R2 ServerAfter the Migration?

Windows Server 2003R2 (risky)

32/64 No

Windows Server 2008 32/64 No A Windows Server 2008 or2008 R2 server cannot bebooted in UEFI mode.



https://support.huaweicloud.com/intl/en-us/sms_faq/sms_faq_0042.html





OSType


Windows Server 2008R2

64 No

Windows Server 2012 64 Yes N/A

Windows Server 2012R2

64 Yes

Windows Server 2016 64 Yes

Windows Server 2019 64 Yes

Windows 7 32/64 No

Windows 10 32/64 32-bitversion:No64-bitversion:Yes

RedHat

Red Hat EnterpriseLinux 6.0 (supportsonly the KVMplatform.)

64 No

Red Hat EnterpriseLinux 6.1

64 No


64 No


64 No


64 No


64 No


64 No


64 No


64 No



OSType



64 No


64 No


64 Yes


64 Yes


64 Yes


64 Yes


64 Yes


64 Yes


64 Yes

CentOS

CentOS 6.0 (supportsonly the KVMplatform.)

64 No

CentOS 6.1 64 No

CentOS 6.2 64 No

CentOS 6.3 64 No

CentOS 6.4 64 No

CentOS 6.5 64 No

CentOS 6.6 64 No

CentOS 6.7 64 No

CentOS 6.8 64 No

CentOS 6.9 64 No

CentOS 6.10 64 No

CentOS 7.0 64 Yes

CentOS 7.1 64 Yes

CentOS 7.2 64 Yes



OSType


CentOS 7.3 64 Yes

CentOS 7.4 64 Yes

CentOS 7.5 64 Yes

CentOS 7.6 64 Yes

CentOS 7.7 64 Yes

Oracle

Oracle Linux 6.1 64 Yes


Oracle Linux 6.3 32/64 No






Oracle Linux 6.9 64 No

Oracle Linux 6.10 64 No








SUSE SUSE Linux EnterpriseServer 11 SP2

32/64 No



OSType


SUSE Linux EnterpriseServer 11 SP3

32/64 32-bitversion:No64-bitversion:Yes


32/64 No


64 Yes


64 No


64 No


64 No

Ubuntu

Ubuntu Server 12.04 64 No

Ubuntu Server 12.10 64 NO



Ubuntu Server 14.04 64 Yes








Debian

Debian GNU/Linux8.2.0

64 No


64 No



OSType



64 No


64 No


64 No


64 No


64 No


64 No


64 No


64 No


64 No


64 No

Debian GNU/Linux10.0

64 No

● Migration constraints and limitations

Table 1-4 Constraints and limitations on source servers

Source Server Type Description

OS ● Only the operating systems (OSs) included inTable 1-3 are supported by SMS.

● Migrations of servers that run multiple OSs arenot supported.

Available disk space ● For Windows: Migrations will fail in both of thefollowing two scenarios: The partition size isgreater than 600 MB, but the available partitionspace is less than 320 MB. The partition size andthe available partition space are less than 600MB and 40 MB, respectively.

● For Linux: Migrations will fail if the availableroot partition space is less than 200 MB.



Source Server Type Description

File System ● For Windows: Only NTFS is supported.● For Linux: Only ext2, ext3, ext4, VFAT, XFS, and

ReiserFS file systems are supported.

Shared file system Only files on the local disk are migrated. Files inthe shared file systems, such as Network FileSystem and Common Internet File System, cannotbe migrated.

Encrypted files OSs that contain protected folders and encryptedvolumes cannot be migrated.

Database and ActiveDirectory Domain (ADDS) application

Server Migration Service (SMS) does not supportthe AD and multi-node database migration.

Applications bound tohardware

Migrations of OSs that contain applications boundto hardware are not supported.

Dynamic disk In Windows OSs, dynamic disks are migrated asbasic disks. After the migration is complete, thetarget ECS does not have dynamic disks.

Servers added to adomain

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

1.3 What Are the Important Statements of SMS?● Source server data collection statement

After the migration Agent is installed and configured on the source server, themigration Agent sends the source server information to SMS for evaluation.For details about the source server information to be collected, see WhatKind of Information About Source Servers Are Collected by SMS? Thecollected information is used only for migration feasibility evaluation. To useSMS, you need to allow SMS to collect source server information.

● License invalidity statement

After OSs, applications, and files on source servers are migrated to targetECSs, the SID and MAC address of the server are changed. As a result, licensesof OSs and applications become invalid. SMS is not responsible for this type ofproblems. For Windows OS licenses, you can use the HUAWEI CLOUD licenseserver to obtain a new license. For application licenses, you need to preparethem at your own cost.

● Target ECS disk formatting description

During the migration, disks on the target ECS are formatted and partitionedagain. As a result, all data on the target ECS will be lost. Before the migration,back up data on the disk of the target ECS and ensure that the disk can beformatted. 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 problems can be resolved because there are alot of possible causes for this kind of problems.The possible causes of the failure to start the target ECS are as follows:– The source server cannot be restarted.– The source server has non-standard OS configurations.– The source server has drivers or software that are incompatible with

HUAWEI CLOUD installed.● To adapt source server to HUAWEI CLOUD, SMS modifies the system

configuration of the target ECSs. For details about the modifications, seeWhat Are the Differences Between Target ECSs and Source Servers Afterthe Migration? SMS can ensure data consistency before and after themigration but cannot ensure that your services can run properly after themigration. You need to modify related service configurations.

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

In block-level migrations, a block refers to a disk block. A disk block is theminimum logical unit of the file system for managing disk partitions. Disk blocksare similar to clusters in Windows OSs.

A block is also the minimum unit of the disk used by OSs and software. As logicunits, blocks are of great significance for OSs and software. The smallest unit fordisk read or write is a sector. A sector is a physical area on the disk. The read andwrite operations to disk blocks are performed in sectors. Generally, a file is storedin 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 thenetwork is interrupted during the migration, only impacted blocks need to bemigrated again after the network recovery. If files are modified during themigration, only modified blocks need to be synchronized after the migration.

In file-level migrations, tools or TAR commands and SSH or other transmissionchannels are used for remote replication. Therefore, the migration fails if files arechanged during decompression or the network is interrupted during migration. Inaddition, if the file is changed during incremental data synchronization, the fileneeds to be synchronized again. In this case, all the blocks of the file must besynchronized. So, the synchronization efficiency is low.

1.5 What are Valid Data Blocks?Valid data blocks are blocks that are allocated or used by a file system, forexample, EXT. SMS migrates only valid data blocks. For data blocks that are notallocated or used can be allocated by the system, SMS does not migrate themduring migration. So, the data volume to be migrated is reduced, and migrationefficiency is improved.





2 Before Migration

2.1 How Can I Configure Network Security for SMS?

ScenariosYou need to install the Agent on the source server to be migrated. During themigration, the source server needs to communicate with the SMS service and thedestination server.

Source Server Network Requirements● SMS depends on some HUAWEI CLOUD services. During the migration, ensure

that the Agent on the source server can call the APIs of the services that SMSdepends on in the region where the target ECS is located. You can view theURLs of the dependent services in the cloud-region.json file in the SMS-Agent/config directory. Figure 2-1 lists the URLs to be opened when thetarget ECS is located in the CN North-Beijing1 region.

Figure 2-1 URLs of the dependent services

● If DNS cannot be configured for the source ECS, you need to enable the IPaddress corresponding to the URL. The IP address of each API can be obtainedby running the ping url command. Figure 2-2 shows an example of openingthe IP address.

Server Migration ServiceFAQs 2 Before Migration


Figure 2-2 Opening the IP address

Target Server Network Requirements● If the target ECS runs a Windows OS, enable ports 8899 and 8900. If the

target ECS runs a Linux OS, enable port 22.● If a network ACL is configured for the target ECS, and the network ACL is

associated with the subnet where the destination ECS resides, you need toenable the corresponding ports in the network ACL.

For details about how to configure the security group rules for a VPC, see HowCan I Configure the Security Group Rules for Target ECSs?

Figure 2-3 SMS networking principle

2.2 What Should I Do on the Target ECSs BeforeCreating a Server Migration Task?

Before creating a migration task, you need to make the following preparations:

Step 1 ECSs that meet the requirements listed in How Can I Select a Target ECS? areavailable 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 iscorrectly configured.



The security group rules for the VPC to which target ECSs belong must beconfigured to enable TCP ports 8899 and 8900 for Windows OSs and enable port22 for Linux OSs.

For details about how to configure the security group rules for a VPC, see HowCan I Configure the Security Group Rules for Target ECSs?

----End

2.3 How Can I Configure the Security Group Rules forTarget ECSs?

1. Log in to the management console.

2. Click in the upper left corner and select the desired region and project.3. Under Computing, click Elastic Cloud Server.4. In the ECS list, click the name of the target ECS.

The page providing details about the ECS is displayed.5. Click the Security Group tab and view security group rules.6. Click the security group ID.

The system switches to the Security Group page.7. Under Inbound Rules, click Add Rule to configure the access rule for the

inbound direction.– For an ECS running a Windows OS, set Protocol/Application to TCP and

Port to 8899.

Figure 2-4 Security group rule

– For an ECS running a Windows OS, set Protocol/Application to TCP andPort to 8900.




– For an ECS running a Linux OS, set Protocol/Application to TCP andPort to 22.


– Set Source IP Address to the IP address segment containing the IPaddresses that you want to allow to access the ECS over the Internet.

The default source IP address 0.0.0.0/0 indicates that all IP addresses can accessECSs in the security group.

8. Click OK to complete the security rule configuration.

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

ScenariosWhen creating a migration task, you need to enter the AK and SK forauthentication. To safeguard the resources in your account on a cloud serviceplatform, you are advised to create a username in the account and grantpermissions to the username to create AKs and SKs. This section describes how tocreate access credentials (AKs and SKs).

ProcedureCreating user groups and granting permissions to the user groups



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. Enter a user group name for User Group.6. (Optional) Set Description.7. Click OK.

The user group list is displayed, including the newly created user group.8. Locate the newly created user group, and click Configure Permission under

More in the Operation column.9. On the displayed page, click the User Group Permission tab, locate the row

where Region is Global service and Project Name is Global, click ConfigurePolicy in the Operation column.The Configure Policy dialog box is displayed.

10. In the displayed Configure Policy dialog box, select Tenant Administrator inthe Available Policies area.

11. Click OK.12. Under the User Group Permission tab, locate the row where Region is

Global service and Project Name is OBS, click Configure Policy in theOperation column.The Configure Policy dialog box is displayed.

13. In the displayed Configure Policy dialog box, select Tenant Administrator inthe Available Policies area.

14. Click OK.15. On the User Group Permissions tab, locate the row where the target ECS

locates and click Configure Policy in the Operation column.The Configure Policy dialog box is displayed.

16. In the displayed Configure Policy dialog box, select Server Administratorand IMS Administrator in the Available Policies area.

17. Click OK.

Creating a user and adding the user to the 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.4. On the Users page, click Create User.5. On the Create User page, enter Username.6. Specify Credential Type.



CredentialType

Application Scenario

Password ● Used to log in to the management console● Used to enable development tools (such as APIs, CLIs,

and SDKs) that can access cloud services throughpassword authentication

Access Key Used to enable development tools (such as APIs, CLIs, andSDKs) that can access cloud services through keyauthentication

7. Select a user group which you want to add the user from the drop-down list

box in the User Groups area.

● You can also enter a keyword to quickly find the target user group.● A user can be added to multiple user groups.

Perform one of the following based on the credential type you selected in 6.

Credential Type Follow-up Operation

Password Perform 8.

Access Key Click OK. Download the generatedkey. User creation is complete.NOTE

Access keys are credentials for identityauthentication in IAM. You can onlyobtain an access key by downloading it.If the user needs to use an access keyfor authentication in IAM but it has notbeen downloaded, you must generate anew access key.

8. Click Next.9. Specify Password Type.

Password Type Description Follow-up Operation

Set at first login The system will sendyou a one-time loginlink through email. Youneed to use this link toset a password beforeyou log in to themanagement console.

1. Set Email Used forreceiving the loginlink.

2. (Optional) SetMobile Number.



Password Type Description Follow-up Operation

Automaticallygenerated

The system randomlygenerates a 10-character password.This option enablesdevelopment tools(such as APIs, CLIs, andSDKs) that can accesscloud services throughpasswordauthentication.

1. (Optional) SetEmail.


Set manually Users set their ownpasswords.

1. (Optional) SetEmail.


3. Set New Passwordand ConfirmPassword.NOTE

The password mustmeet the followingrequirements:● Must contain 6 to

32 characters.● It must contain at

least 2 of thefollowingcharacter types:uppercase letters,lowercase letters,digits, spaces, andfollowing specialcharacters: !"#$%&'()*+,-./:;<=>?@[]^`{_|}~

● It cannot containthe user's mobilenumber or emailaddress.

10. Select Require Password Reset to ensure that the security administrator is

forced to change the password the first time the administrator logs in. TheRequire Password Reset option is selected by default. It is recommended thatyou retain the default setting to ensure that the security administratoraccount password is set by the security administrator, preventing passwordleakage.

11. Click OK.The user is created successfully.

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.

If login authentication is enabled, you need to enter an authentication code from avirtual MFA device, an SMS verification code, or an email verification code on theLogin Verification page.

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 Add Access Key under the Access Keys tab page.The Add Access Key dialog box is displayed.

8. Enter the password in the Login Password field. If a mobile number or anemail address is bound, click Get Code to obtain the code, then enter thecode in the SMS Verification Code or Email Verification Code field forverification, and click OK.After the verification is successful, the Download Access Key dialog box isdisplayed.

9. In the displayed dialog box, click OK. Download and save the added accesskey as prompted.

To prevent the access key from being leaked, keep it secure. If you click Cancel in theDownload Access Key dialog box, the access key will not be downloaded and cannotbe downloaded later. You must delete the access key and create one later.

Subsequent Operations

If an access key has a problem (for example, it is lost or leaked) or will not beused any longer, delete the access key by performing the following operations orcontact 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 APIPassword, and click Log In.

If login authentication is enabled, you need to enter an authentication code from a virtualMFA device, an SMS verification code, or an email verification code on the LoginVerification page.

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 MyCredentials.

The My Credentials page is displayed.

Step 7 Locate the row where the access key to be deleted locates under the Access Keystab and click Delete in the Operation column.

Step 8 Suppose that an email address has been bound. Enter the password in the LoginPassword field, click Get Code, enter the code in the Email Verification Codefield, and click OK.

After the access key is deleted, it will be permanently deleted and cannot be restored.

----End

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

Scenarios

When creating a migration task, you need to enter the AK and SK forauthentication. If you need to use an account to migrate servers, you need toobtain the AK and SK of your HUAWEI CLOUD account.

Procedure1. Log in to the management console.2. In the upper right corner of the page, click the username and choose My

Credentials.The My Credentials page is displayed.

3. Click Add Access Key under the Access Keys tab page.The Add Access Key dialog box is displayed.

4. Enter the password in the Login Password field. If a mobile number or anemail address is bound, click Get Code to obtain the code, then enter thecode in the SMS Verification Code or Email Verification Code field forverification, and click OK.After the verification is successful, the Download Access Key dialog box isdisplayed.

5. In the displayed dialog box, click OK. Download and save the added accesskey as prompted.

To prevent the access key from being leaked, keep it secure. If you click Cancel in theDownload Access Key dialog box, the access key will not be downloaded and cannotbe downloaded later. You must delete the access key and create one later.



Subsequent Operations

If an access key has a problem (for example, it is lost or leaked) or will not beused any longer, delete the access key by performing the following operations orcontact the administrator to reset the access key.

Step 1 Log in to the management console.

Step 2 In the upper right corner of the page, click the username and choose MyCredentials.

The My Credentials page is displayed.

Step 3 Locate the row where the access key to be deleted locates under the Access Keystab and click Delete in the Operation column.

Step 4 Suppose that an email address has been bound. Enter the password in the LoginPassword field, click Get Code, enter the code in the Email Verification Codefield, and click OK.

After the access key is deleted, it will be permanently deleted and cannot be restored.

----End

2.6 How Do I Create an ECS?

Scenarios

Source servers are migrated to ECSs on HUAWEI CLOUD. Therefore, you need tocreate 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.

● The memory size of the target ECS running a Windows OS cannot be less than 2 GB.

● Specify Image to be the same as the OS type of the source server.

● When you specify the Disk parameter, the number of disks on the target ECS must begreater than or equal to the number of disks on the source server. The disk size on thetarget ECS must be greater than or equal to that on the source server.



https://support.huaweicloud.com/intl/en-us/qs-ecs/ecs_02_0009.html

Figure 2-7 Purchasing an ECS

Step 5 After configuring the parameters, click Create Now.

After the purchase is successful, the new ECS is displayed in the ECS list.

----End

2.7 How Do I Compress the Disk Partitions of theSource Server Running a Windows OS?

SymptomWhen using SMS to migrate the source server running a Windows OS, ensure thatthe disk size of the target ECS is not less than the size recommended on theSource Management page. Otherwise, the migration may fail. If you have createdthe target ECS running a Windows OS, and the disk size of the target ECS is lessthan the recommended specifications, you can adjust the recommended



specifications of the source server to be less than or equal to the disk size of thetarget ECS. For details, see the following content.

Possible CausesFor a source server running a Windows OS, the recommended specifications onthe Source Management page are the sum of the size of all the partitions on thedisk. For example, if 35 GB of space is partitioned on a disk of 40 GB, therecommended specification is 36 GB. Therefore, you only need to compress thedisk partitions on the source server and report the information about the sourceserver to SMS. In this way, the recommended specifications on the SourceManagement page are less than or equal to the disk size of the target ECS.

Procedure1. Choose Start, enter diskmgmt.msc in the search box.

The Disk Management page is displayed.2. Right-click the last partition of the disk to be compressed and choose Shrink

Volume.The Shrink Volume page is displayed.

3. Enter the size to be compressed in the Enter the amount of space to shrinkin (MB) text box.



4. Click Shrink.An unallocated partition of the corresponding size is displayed for the disk tobe compressed.

Figure 2-8 Disk partition After compression

5. Log in to the management console.6. Click Service List. Under Migration, click Server Migration Service.

The Server Migration Service page is displayed.7. In the navigation pane on the left, choose Source Management.

The Source Management page is displayed.8. On the Source Management page, locate the row where the information

about the source server resides, click Delete in the Operation column.The Delete dialog box is displayed.

9. In the Delete dialog box, confirm information about the source server to bedeleted and click OK.

10. Report the information about the source server to SMS again.– If you have uninstalled the migration Agent on the source server, install

the migration Agent again. For details, see Installing the WindowsAgent.

– If the migration Agent has been installed on your source server, restartthe migration Agent. After the migration Agent is restarted, it uploadsthe source server information to SMS.



https://support.huaweicloud.com/intl/en-us/qs-sms/sms_02_0003.html


2.8 What Do I Do If I/O Monitoring Fails to Be StartedDuring Agent Startup?

If Failed to start I/O monitoring. is displayed when you start the migration Agenton the source server, you need to perform the following operations:

1. Uninstall the Agent and re-install it.

a. After the Agent of Python 3 version is installed, enter the AK and SK asprompted.

b. After the Agent of Python 2 version is installed, Figure 2-9 is displayed.(If Figure 2-9 is not displayed, double-click start.bat in the installationdirectory.) Enter the AK and SK as prompted.

Figure 2-9 Entering the AK and SK

c. You can also switch to the Agent installation directory on the command-line interface (CLI) and run SMSAgentDeploy.exe ak sk.

Figure 2-10 Starting SMSAgentDeploy.exe

2. Check whether antivirus software is installed on the source server.

a. If antivirus or security software is installed, or the firewall is enabled, apop-up window is displayed indicating the I/O monitoring driver isblocked. Allow the system to run the I/O monitoring process.



b. If the interception window is not displayed and the driver is blocked, youneed to manually start the I/O monitoring driver. Add C:\Windows\System32\drivers\HwDiskMon.sys to the trusted zone of the antivirussoftware and restart the Agent. If the problem persists, uninstall theantivirus software.

Some antivirus software has a persisted security protection process. Simplydisabling the process may fail to stop it blocking the driver.

3. Modify the configuration file to disable I/O monitoring.If you do not need to synchronize data, you can modify the configuration fileto disable I/O monitoring.Change the value of enablesync to False in the property.cfg file in theconfig directory under the Agent installation directory, and then restart theAgent.

Figure 2-11 Modifying the property.cfg file

2.9 How Do I Migrate an ECS from Account A toAccount B?

If you need to migrate an ECS under account A to account B, perform thefollowing operations:

1. Install the Agent on the ECS of account A and enter the AK/SK of account Bwhen starting the Agent. For details about how to install the Agent, seeInstalling the Windows Agent or Installing the Linux Agent.Log in to the management console as account B, Viewing Check Results, andCreating and Starting a Migration Task.

For details about how to migrate an ECS from one region to another under the sameaccount, see How Do I Migrate Data from One Region to Another?.







2.10 How Do I Migrate Data from One Region toAnother?

If you need to migrate an ECS from one region to another, for example, from CNSouth-Guangzhou to CN North-Beijing1, you need to install the Agent on theECS in CN South-Guangzhou. When creating a migration task, select CN North-Beijing1 as the destination region.

For details about how to migrate ECSs under account A to account B, see How Do IMigrate an ECS from Account A to Account B?.

2.11 What Can I Do If Message "The target ECS is notbooted with UEFI. Create an ECS using the imagewhose boot mode is UEFI." Is Displayed DuringMigration Task Creation?

Symptom

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

Causes

The target ECS is created using the BIOS image and cannot be started after themigration. You must select an ECS created using the image whose boot mode isUEFI.

Procedure

Step 1 Download the target UEFI image file. If the image file exists in your OBS bucket,go to Step 3.

● Empty Windows image file

● Empty Linux image file

Step 2 Upload the image file to the OBS bucket.

Step 3 Create a private image.

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.



https://sms-proxy.obs.cn-north-1.myhuaweicloud.com/empty-image/Windows.vhd

https://sms-proxy.obs.cn-north-1.myhuaweicloud.com/empty-image/Linux.vhd

For details, see Creating a Windows System Disk Image from an ExternalImage File or Creating a Linux System Disk Image from an External ImageFile.

----End



https://support.huaweicloud.com/intl/en-us/usermanual-ims/ims_01_0203.html




3 Installing the Migration Agent

3.1 What Should I Do If the Source Server InformationIs Not Displayed on the Source Management Page?

If the migration Agent is installed and configured on the source server, but thesource server information is not displayed on the Source Management page onthe SMS console. You need to perform the following operations:

Step 1 Check whether the source server can access HUAWEI CLOUD using the followingmethod:

For source servers that run a Windows OS, use a browser to access HUAWEICLOUD.

For source servers that run a Linux OS, use Wget or Curl commands to performthe check.

Step 2 If the network connection is normal, check the status of the migration Agent onthe source server.

If the system displays a message indicating that the authentication fails, check theAK and SK.

If the Agent displays a message indicating that the AK or SK is incorrect, check theAK and SK or generate a new AK and SK by performing steps provided in How DoI Obtain the AK and SK of an IAM User? or How Do I Obtain the AK and SK ofan Account? and enter the new ones.

----End

3.2 How Do I Verify the Software Integrity of theMigration Agent?

Step 1 Log in to the management console and go to the Server Migration Service page.

Server Migration ServiceFAQs 3 Installing the Migration Agent


Step 2 In the navigation pane on the left, choose Migration Agent page. ClickDownload sha256 in the pane of the Agent version you need to save the filecontaining the hash value to a local directory.

Step 3 Run the following commands to obtain the hash value of the migration Agent youhave downloaded:

● Windows Agent:

certutil -hashfile SMS-Agent-PyN.exe SHA256

SMS-Agent-PyN.exe indicates 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 theyare the same, the integrity verification is successful.

----End

3.3 How Can I Install the Migration Agent on SourceServers?

● If the source server runs a Windows OS, install the migration Agent byreferring to Installing the Windows Agent.

● If the source server runs a Linux OS, install the migration Agent by referringto Installing the Linux Agent.

3.4 How Do I Reestablish a Connection Between theMigration Agent and the SMS Service?

Source Servers Running Windows Server 2012 and 2016

Step 1 On the source server, open the Agent GUI and click Start.

Step 2 After 30s, log in to the management console.

Step 3 Click Service List. Under Migration, click Server Migration Service.

The Server Migration Service page is displayed.

Step 4 In the navigation pane on the left, choose Source Management.

The Source Management page is displayed.

Step 5 On the Source Management page, check the status of the connection betweenthe source server and SMS.

----End





Source Server that Run Windows Server 2003 and 2008

Step 1 On the source server, go to the SMS-Agent installation directory and run theagent-cli.exe command to enter the interactive mode.

Step 2 Enter connect to reconnect the source server to SMS.

If the value of Connected between sms agent and sms server displayed in thecommand output is True, the connection between the source server and SMS isrestored.






Step 6 On the Source Management page, check the status of connection between thesource server and SMS service.

----End

Source Servers that Run Linux OSs

Step 1 Use PuTTY or an SSH client to log in to the source server to be migrated.

Step 2 Run the following command to switch to the SMS-Agent directory on the sourceserver:

cd SMS-Agent

Step 3 Run the following command to go to the SMS-Agent interaction mode:

./agent-cli

Step 4 Enter connect to reconnect the source server to SMS.

If the value of Connected between sms agent and sms server displayed in thecommand output is True, the connection between the source server and SMS isrestored.



Figure 3-1 Reconnecting the source server to the SMS service






Step 8 On the Source Management page, check the status of connection between thesource server and SMS service.

----End

3.5 What Can I Do If the Linux Agent Cannot StartAfter the Installation?

Symptom

If error messages shown in Figure 3-2 are displayed after you enter AK/SK andstart the Linux Agent, the rsync component is not installed on the source server.You need to install the rsync component and then restart the migration Agent.

Figure 3-2 Error messages

Handling Method

If the OSs on the source servers are different, perform different operations asrequired:



If the source server OS is CentOS or Red Hat, perform the followingoperations:

1. Use PuTTY or an SSH client to log in to the source server to be migrated asuser root:

2. Run the following command to install the rsync component:yum install rsync

3. Enter y and press Enter.

4. Run the following command to query the information about the rsynccomponent:rsync --versionIf the following information is displayed, the rsync component is successfullyinstalled:

5. Run the following command to start the migration Agent:./startup.sh

6. Read the displayed information carefully, enter y, and press Enter.

7. Enter the AK and SK of the HUAWEI CLOUD account to which the target ECSbelongs as prompted.When the following information is displayed, the Linux SMS-Agent startssuccessfully. SMS-Agent starts sending source server information to SMS.



If the source server OS is a SUSE OS, perform the following operations:


2. Run the following command to install the rsync component:zypper install rsync

3. Enter y and press Enter.

4. Run the following command to query the information about the rsynccomponent:rsync --versionIf the following information is displayed, the rsync component is successfullyinstalled:

5. Run the following command to start the migration Agent:./startup.sh


7. Enter the AK and SK of the HUAWEI CLOUD account to which the target ECSbelongs as prompted.When the following information is displayed, the Linux SMS-Agent startssuccessfully. SMS-Agent starts sending source server information to SMS.



If the source server OS is a Ubuntu OS, perform the following operations:


2. Run the following command to install the rsync component:

apt-get install rsync

3. Run the following command to query the information about the rsynccomponent:

rsync --version

If the following information is displayed, the rsync component is successfullyinstalled:

4. Run the following command to start the migration Agent:

./startup.sh


6. Enter the AK and SK of the HUAWEI CLOUD account to which the target ECSbelongs as prompted.

When the following information is displayed, the Linux SMS-Agent startssuccessfully. SMS-Agent starts sending source server information to SMS.



3.6 What Can I Do If the Migration Agent AK/SKAuthentication Fails?

SymptomAfter the AK/SK of HUAWEI CLOUD is entered in the migration Agent, the AK/SKauthentication fails.

● The error message for Windows OSs: AK and SK authentication failed.● The error message for Linux OSs: Failed to start agent! Please check access

key and secret key or check if local time matches standard Time!".

Handling Method1. Check whether the entered HUAWEI CLOUD AK and SK are correct.

– If yes, go to 2.– If no, enter the correct HUAWEI CLOUD AK/SK again.

▪ If the authentication succeeds, no further action is required.

▪ If the authentication fails, go to 2.

2. Check whether the system time of the source server is consistent with thestandard time of the time zone where the source server is located. If not, theAK/SK check fails during the Agent migration.In this case, change the system time of the source server to the standard timeof the time zone where the source server resides, and then enter the HUAWEICLOUD AK/SK for authentication again.



4 During Migration

4.1 How Can I Select a Target ECS?

Currently, the source servers can be migrated to pay-per-use or yearly/monthly ECSs. Youcan select ECSs of a specific billing mode as required.

The selected target ECSs must meet the following requirements. If therequirements are not met, you are required to create an ECS by performing stepsprovided in How Do I Create an ECS?

● The memory size of the target ECS running a Windows OS cannot be lessthan 2 GB.

● Ensure that the number of disks on the target ECS cannot be less than thenumber of disks on the source server. The size of each disk on the target ECScannot be less than that on the source server.

● The image class of a target ECS must be the same as the OS type of thesource server. Otherwise, the actual OS type of the target ECS is differentfrom the image class of the ECS.

Figure 4-1 Image types of ECSs to be purchased

4.2 How Can I Speed Up Migration?● You need to improve your network speed. You can test the network

performance from the source server to the target ECSs on HUAWEI CLOUD byreferring to How Can I Test the Network with iPerf? If the network speed islower than 500 Kbit/s, check the following items:

Server Migration ServiceFAQs 4 During Migration


– If the source server is in a data center, check whether the bandwidth,switching devices, routing devices, security devices (such as firewalls),network lines, and protocol network factors between the source serverand the Internet are limited or incorrect. If any problem occurs, contactnetwork engineers to rectify the fault. It is recommended that the speedof the network from the source server to HUAWEI CLOUD is greater than10 Mbit/s.

– If source servers are ECSs on public clouds, adjust the bandwidth of theelastic IP addresses bound to source servers to improve the migrationspeed.

– Ensure that the OS settings of the source and target ECSs are correct. ForWindows OSs, you can run the perfmon command to invoke the resourcemonitor to monitor the network. For Linux OSs, you are advised to usethe sar tool to monitor the network. You can also use the /proc/net/devto monitor the NIC speed. If the network speed is slow, the OSconfiguration may be incorrect. Note that your OS services and processescannot limit the NIC speed.

● If you have a large number of files (for example, 500,000 files, 100 KB ofeach) on the source server, and these files are not needed anymore, deletethem before migration.

● Check the I/O read/write performance and CPU performance of the sourceserver. For Windows OSs, you can run the perfmon command to invoke theResource Monitor to monitor the read and write performance of the CPU andI/O. For Linux OSs, you can use top/ps and iostat/iotop to monitor the CPUand I/O performance. If the I/O and CPU performance of your source server ispoor, you are advised to increase the I/O and CPU resources or reduce theworkloads on the source server.

4.3 How Can I Test the Network with iPerf?

Prerequisites● Ensure that the networks between source servers and target ECSs are

connected, and the security group rule configured for target ECSs enables portused for the iPerf test. For details about how to configure a security grouprule, see How Can I Configure the Security Group Rules for Target ECSs?

● This test must be performed before the migration. Otherwise, the test data isinaccurate. This test almost has no impact on services running on the sourceserver.

Procedure

Step 1 Download iPerf of the required version based on the OS type of the sourceserver.

Step 2 Decompress the iPerf software package in a directory on the source server andtarget ECS (or other ECSs in the same region as that of the target ECS). Forexample, the iPerf software package for Windows OSs is as follows:



https://iperf.fr/iperf-download.php

Step 3 Start iPerf in server mode by running a command on the command line interface(CLI) on the target ECS. Use a Windows OS as an example.

1. Run the following command to switch to the iperf directory:cd /d pathIn the preceding command, path indicates the path on the target ECS forstoring the decompressed iPerf tool.

2. Run the following command to run iPerf on SMS:iperf3 -p port -sIn the preceding command, port indicates the SMS listening port for the iPerftool. It is recommended that port 8900 be used for Windows OSs and port 22for Linux OSs. Ports 8900 and 22 are data transmission ports used by thetarget ECS. You can also use other ports during the test, but ensure that theTCP or UDP port can be opened for the security group rule configured for thetarget ECS.For details about parameters, run the iperf -h command.Assume that port 8900 is used for a Windows OS. If Server listening on 8900is displayed in the command output, iPerf in server mode is running properly.

Step 4 Start iPerf in client mode on CLI on the source server to test the TCP bandwidth,UDP jitter, packet loss rate, and bandwidth. Use a Windows OS as an example.

1. Run the following command to switch to the iperf directory:cd /d pathIn the preceding command, path indicates the path on the source server forstoring the decompressed iPerf tool.

2. Run the following command to run iPerf to test the TCP bandwidth:iperf3 -c target_IP -p port -t timeIn the preceding command, -c indicates that iPerf is running on the sourceserver (client).– target_IP indicates the IP address of the target ECS, which is the server

that runs iPerf in server mode.– port: indicates the port number for connecting to the target ECS, that is,

the iPerf listening port in Step 3.2.– time indicates the total test time. The default unit is second.



Assume that port 8900 is used for a Windows OS. After the iPerf client issuccessfully connected to the iPerf server, the bandwidth is tested. After thetest is complete, check the result.

3. Run the following command to start iPerf to test the UDP jitter, packet lossrate, and bandwidth.iperf3 -c target_IP -p port -u -t time-u indicates the UDP jitter, packet loss rate, and bandwidth.– target_IP indicates the IP address of the target ECS, which is the server

that runs iPerf in server mode.– port: indicates the port number for connecting to the target ECS, that is,

the iPerf listening port in Step 3.2.– time indicates the total test time. The default unit is second.Assume that port 8900 is used for a Windows OS. After the iPerf client isconnected to the iPerf server, the UDP jitter, Lost/Total Datagrame, andbandwidth are tested. After the test is complete, check the result.

4. To test the network delay, run the following ping command:ping target_iP



target_IP indicates the IP address of the target ECS, which is the server thatruns iPerf in server mode.Configure the security group rule for the VPC to which the target ECSs belongto 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 officialwebsite.

iperf3 -h

----End

4.4 How Long Does the Migration Take?1. Pre-Migration Evaluation

Test the TCP connection speed from the source and target ECSs. For detailsabout the test method, see How Can I Test the Network with iPerf?

Where:– T indicates the migration time in hours.– C indicates the amount of data used by the source server, in GB.– S indicates the TCP speed from the source server to the target ECS, that

is, the TCP speed obtained in Step 4.2. The unit is Mbit/s.– U indicates 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 data volume used by the migration source server is 100GB, the TCP speed tested by iPerf is 100 Mbit/s, and the network usage is70%, the migration time is calculated as follows:Migration time T = 100 GB x 1000 x 8 / 100 Mbit/s / 3600 / 70% = 3.17 hoursAssume that the network usage U is 70%, you can refer to Table 4-1 aboutthe migration time T corresponding to the data volume C and the TCP speedS of different source servers.

Table 4-1 Migration time

Total VolumeSource ServerData C (GB)

TCP speed S(Mbit/s)

Migration Time T (Hour)

10 GB 0.5 Mbit/s SMS is not recommended.

1 Mbit/s SMS is not recommended.

5 Mbit/s 6.34 hours

10 Mbit/s 3.17 hours

100 Mbit/s 0.317 hour (about 19 minutes)



https://iperf.fr/iperf-doc.php


TCP speed S(Mbit/s)



















1 Mbit/s

5 Mbit/s

10 Mbit/s


500 Mbit/s 0.634 hour

1000 Mbit/s 0.317 hour


1 Mbit/s

5 Mbit/s

10 Mbit/s






TCP speed S(Mbit/s)



1 TB 0.5 Mbit/s SMS is not recommended.

1 Mbit/s

5 Mbit/s

10 Mbit/s

100 Mbit/s



Greater than 1TB

N/A SMS is not recommended.

2. Evaluation during migration (remaining time)

Remaining time T (hour) = data volume of source server C (GB) x 1000 / (80 -Current transmission progress P) / 60 / Migration speed S (Mbit/s) / 3600– The data volume of source servers C refers to the total data volume of

the source servers.– The current data transmission progress P% can be viewed on the SMS

console. If the progress P is larger than 80, the data transmission iscomplete and you do not need to evaluate the remaining time.

– The migration speed S cannot be tested with iPerf, because the test isinaccurate. Use either of the following methods to obtain the accuratemigration speed:

▪ You can choose Windows Task Manager > Performance > ResourceMonitor to view the migration speed S for Windows OSs.



▪ You are advised to use the sar tool or run the /proc/net/devcommand to monitor the network interface card speed for Linux OSs.

For example, the data volume of the migration source server is 100 GB andthe progress is 70%. If the migration speed is 5 Mbit/s, the remainingmigration time is calculated as follows:Migration time T = 100 GB x 1000 / (80-70) / 60 / 5 (Mbit/s) / 3600 = 0.93hour

4.5 What Do I Do If New Data is Generated on theSource Server During the Migration?

To synchronize the incremental data to the target ECS, click Synchronize in theOperation column of the task after the migration is complete.

4.6 What Can I Do If the System Disk on the TargetServer Is Still a Temporary Mirror Disk After a Task IsDeleted?

SymptomDuring the migration, if you delete the migration task when the source server isdisconnected, the temporary mirror disk on the target server is still attached, andthe original system disk on the target server cannot be attached as the systemdisk.

ProcedureThe following uses the Linux OS as an example to describe how to handle thisproblem.

1. Run the ./agent-cli command in the SMS-Agent directory on the sourceserver, enter connect, and press Enter to bring the source server online.



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

4.7 How Do I Modify Configurations to DisableSnapshots?

Before data migration from servers running the Windows OS, the VSS module isused to create snapshots to ensure that data on the source server and thedestination server is at the same time point. If the VSS module on the sourceserver 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. Forthe 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 4-2 Modify the configuration parameter

If you skip snapshot creation, data on the destination server and the source server may beat different time points during migration, and services on the destination server may fail tobe started. You can stop the software on the source server when no service is running onthe source server, and then perform data synchronization to ensure that the data on thesource and target servers is at the same time point.

----End



5 After Migration

5.1 What Are the Differences Between Target ECSs andSource Servers After the Migration?

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

Parameter Change Target ECS Remarks

Server SID Changed The SID of thetarget ECS isused.

The SID of Windows OS is ahardware attribute, which isdifferent on each server andcannot be migrated. Therefore, ifthe source server is added to thedomain for management, the SIDwill become invalid after beingmigrated to the target ECS andthe target ECS needs to be addedto the domain again.

Server Name Possiblychanged

The systemmay updatethe servername.

Services bound to the servername may be affected.

OS Type Unchanged

The OS type ofthe target ECSmay be thesame as theOS of thesource server.

The original OS of the target ECSis overwritten.

MAC Address Changed Specifies theMAC addressof the targetECS.

The MAC address is an inherentattribute of a NIC. The MACaddress is determined when thetarget ECS is created.

Server Migration ServiceFAQs 5 After Migration



NIC Name Possiblychanged

The NIC nameof the targetECS isdetermined bytheconfigurationfile of the NICof the sourceserver.

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

IP Changed The IP addressof the targetECS is used.

If the network segment of theVPC is the same as that of thesource IP address segment, retainthe IP address.

DNS Possiblychanged

The DNS ofthe target ECSis determinedby the DNSconfigurationon the sourceserver.

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

Disk Name Possiblychanged

The disk nameof thedestinationEVS diskdepends onthevirtualizationtype of thetarget ECS.

Services are not affected.

Username Unchanged

The usernameof the targetECS is thesame as thatof the sourceserver.

N/A

Password(Certificate)

Unchanged

The username,certificate, andpassword ofthe target ECSare the sameas those of thesource server.

N/A

Registry andstartup items

Changed Modify theparametervalue asrequired.

SMS modifies the registry andstartup items to adapt toHUAWEI CLOUD.




Other data Unchanged

Other data,including files,applications,andconfigurations,must beconsistent withthose onsource servers.

N/A

5.2 What Are the Changes of Target ECSAuthentication After the Migration?

After the migration, the changes of the target ECS authentication are as follows:

● Select an existing server when selecting a target ECS during the taskmigration. The authentication mode of the destination server is the same asthat of the source server, namely the username, certificate, and password ofthe destination server is the same as those of the source server.

● Select Create during migration when selecting a target ECS during the taskmigration. After the migration is complete, the password is in the 1 + firsteight characters of the target SK + ! format. For example, if the first eightcharacters of the SK are RgybsdPP, the password is 1RgybsdPP!.

5.3 How Can I Configure and Optimize My Target ECSsRunning a Windows OS After the Migration?

Scenarios

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

Procedure1. Log in to the management console.

2. Click in the upper left corner and select the desired region and project.

3. Click Service List and choose Computing > Elastic Cloud Server.

4. 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 size of the ECStype. D specifies the ratio of memory to vCPUs expressed in a digit. For detailsabout ECS flavors, see ECS Types.



https://support.huaweicloud.com/intl/en-us/productdesc-ecs/en-us_topic_0035470096.html

– If the type ID B of your target ECS flavor is 1, for example, s1.small.2, thetarget ECS is of Xen virtualization. In this case, you need to install PVdriver.

– If the type ID B of your target ECS flavor is not 1, for example, s2.small.3,the target ECS is of KVM virtualization. In this case, you need to installUVP VMTools.

5. Check whether the PV driver Tools or UVP VMTools software package existson the target ECS based on the target ECS virtualization type queried in 4.

– If yes, go to 8.

– If no, go to 6.

6. Download the PV driver Tools or UVP VMTools software package from thesource server based on the target ECS virtualization type queried in 4. Fordetails about how to obtain the software package, see Obtaining RequiredSoftware Packages.

7. Synchronize the PV driver Tools or UVP VMTools software package on thesource server to the target ECS. For details, see Synchronizing Data After aMigration Task Is Complete. Then, go to 8.

8. Install the driver on the target ECS based on the target ECS virtualization typequeried in 4.

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,

5.4 How Do I Activate the Target ECS Running aWindows OS After the Migration?

Symptom

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

Prerequisites

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

Handling Method1. On the target ECS, choose Start and enter cmd.

2. Run the following command to check whether the IP address of the KMSserver is correct:

slmgr -dli

– If the obtained IP address is the same as that shown in the red box ofFigure 5-1, the IP address of the KMS server is correct.





https://support.huaweicloud.com/intl/en-us/usermanual-sms/sms_03_0011.html

https://support.huaweicloud.com/intl/en-us/usermanual-sms/sms_03_0011.html



– If the obtained IP address is different from that shown in the red box ofFigure 5-1, the IP address of the KMS server is incorrect. In this case, runthe following command to register the ECS with the KMS server:slmgr –skms 100.125.1.2

Figure 5-1 IP address of the KMS server

– If the check result shown in Figure 5-2 is displayed, the KMS serveraddress has not been set for the target ECS. Run the following commandto register the ECS with the KMS server:slmgr –skms 100.125.1.2

Figure 5-2 KMS server address not configured

3. Run the following command to check whether the ECS has been activated:slmgr -atoIf error 0xC004F074 occurs, the ECS cannot be activated. activating the ECSfailed. 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 rangeconfigured 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 ECSagain:ipconfig /renew

v. Run the following command to check whether the ECS has beenactivated:slmgr -ato

b. Verify that the time in the ECS is the same as the standard time. If thetime is significantly different, the ECS cannot be activated.

c. Run the following command on the ECS to check whether the linkbetween the ECS and the activated server port is reachable:telnet 100.125.1.2 1688On 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 asSafeDog are disabled, or that the data on TCP port 1688 can bypasson the internal ECS firewall.

▪ Verify that the data on port 1688 can bypass the security group inthe outbound direction.

The Windows client must periodically communicate with the KMS server.Therefore, ensure that the data on port 1688 can bypass the security groupin the outbound direction. If the network communication is interrupted, theWindows client automatically enters the inactive state.

d. Run the following command to check whether the ECS has beenactivated:slmgr -atoThe system displays a message indicating that the ECS has beenactivated.



5.5 Why Is the Used Space of C Drive on the TargetWindows ECS Greater Than That on the Source ServerAfter the Migration?Symptom

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

Possible CausesThis is a normal phenomenon. 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 page 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.



4. Log in to the target ECS and perform 2 and 3.5. Compare the size of the virtual memory file pagefile.sys in the Local Disk

(C:) of the source and target ECSs.The size of the pagefile.sys file on the target ECS is greater than the size ofthe pagefile.sys file on the source server.Differences between the size of the pagefile.sys file on the target ECS andsource server is equal to the differences between the used space of local diskC on the target ECS and source server.

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 ECS uses Automatically manage paging file sizefor all drives. That is, the size of the virtual memory file pagefile.sys on thetarget ECS is equal to the size of the Installed Memory (RAM) on the targetECS.If the size of Installed Memory (RAM) file on the target ECS is different fromthat on the source server, the used space of C drive on the target ECS isinconsistent with that on the source server.

5.6 How Do I Uninstall the SMS-Agent on the Sourceand Target ECSs Running Windows OSs After theMigration?

Symptom

After the migration is complete, you can perform the following operations touninstall the SMS-Agent on the source and target servers of Windows OSs.

Troubleshooting● 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 uninst.exe.

e. In the SMS-Agent-1.0.0 Uninstall dialog box, click Yes.

5.7 How Do I Uninstall the SMS-Agent on the Sourceand Target ECSs Running Linux OSs After theMigration?

Symptom

After the migration is complete, you can perform the following operations touninstall the SMS-Agent on the source and target ECSs of Linux OSs.

Troubleshooting1. 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:

./stopAgent.sh

4. Run the following command to return to the parent directory.

cd ..

5. Run the following command to delete the SMS-Agent installation directory:

rm -rf SMS-Agent

5.8 How Do I Configure the Yum Repository After theMigration?

Scenarios

The yum repository URL on Alibaba Cloud is an intranet DNS server address. Afteran Alibaba Cloud server is migrated to HUAWEI CLOUD, the yum repositorycannot be used for the ECS that is not in the Alibaba Cloud intranet. You need tochange the yum repository to a HUAWEI CLOUD yum repository.

Constraints● Make sure that the intranet 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 HUAWEICLOUD DNS?

● The operations described in this section apply to ECSs deployed on x86_64servers.



https://support.huaweicloud.com/intl/en-us/dns_faq/dns_faq_002.html

https://support.huaweicloud.com/intl/en-us/dns_faq/dns_faq_002.html

Procedure1. 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. Select a suitable curl command according to the CentOS image sourceversion, run the command to download the CentOS-Base.repo file, and savethe 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 7curl -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 cache:yum makecache

5.9 Why Are the File Sizes Before and After theMigration Different?

Symptom● After the migration, the used disk partition space on the target ECS is

different from that on the source host.● After the migration, the file size on the target ECS is different from that on

the source server.

Causes

If sparse files exist on the source server, the total size of the migrated files on thetarget ECS may be smaller than that on the source. This is because Rsyncautomatically processes sparse files during the transmission: The file systemtransparently converts metadata representing empty blocks into "real" blocksfilled with null bytes at runtime.

You can check whether the files before and after the migration are consistent. Fordetails, see Procedure.

In the Unix file system, when the file displacement is greater than the file length, the nextwrite operation extends the file length, creating a sparse file. This is achieved by writingbrief 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 writtento disk as the actual size only when the block contains "real" (non-empty) data.



Procedure1. 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.imgfile: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 5-3 Checking the file size

2. After the migration is complete, check the size of the migrated file on thetarget ECS. Figure 5-4 shows that the used disk space decreases after themigration.

Figure 5-4 Checking target ECS file size

3. Run the following command on the source server and target ECS to obtainthe 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 5-5 Obtaining the sha256 value

5.10 Why Are Data Disks not Displayed on the TargetECS After a Windows Server is Migrated?

CausesIf the disk policy of the source server is shared disk offline or offline, data diskswill become offline after migration.

Procedure1. Click Start > Run.2. Enter diskmgmt.msc and press Enter. The Disk Management dialog box is

displayed.



The data disk is in the Offline state.

Figure 5-6 Offline

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

Figure 5-7 Bringing the disk online



5.11 How Do I Expand the Capacity of a WindowsSystem Disk After the Migration?

CausesIf the size of the source server disks is smaller than that of the target ECS disks,the partitions of the source and target disks will become same after the migration.As a result, some space of the target ECS disks is not allocated.

Procedure1. Click 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.

Figure 5-8 Expanding volumes

4. In the displayed dialog box, click Next.



Figure 5-9 Extend Volume Wizard

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

Figure 5-10 Expanding the disk

6. In the displayed dialog box, click Finish.



Figure 5-11 Completing the expansion

7. Check the expanded capacity.

Figure 5-12 After the expansion



5.12 How Do I Load the NIC Driver for a WindowsServer 2003 or 2003 R2 Server After the Migration?

ScenariosAfter a Windows Server 2003 server is migrated, the system may notautomatically load the NIC driver. You can load the NIC driver by followingoperations provided in Procedure.

Procedure1. Click Start > Run.2. Enter devmgmt.msc and press Enter to open the device manager.

Figure 5-13 Device manager

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



Figure 5-14 Updating the driver software

4. In the Hardware Update Wizard, select the specified driver file C:\Windows\System32\drivers\netkvm.sys.

Figure 5-15 Selecting a driver file

5. If the NIC driver is displayed as shown in Figure 5-16, the driver issuccessfully loaded.



Figure 5-16 Loaded NIC driver

5.13 What Can I Do If the Server Cannot Be StartedAfter Migration Due to an Earlier GRUB Version?

SymptomThe server cannot be started after the migration.

Figure 5-17 Failed to start



Causes

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

Procedure

Step 1 Log in to the source server as user root and run the grub2-install command toinstall 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 5-18 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. Checkwhether GRUB is successfully upgraded by comparing the version numbers inFigure 5-18 and Figure 5-19.

rpm -qa |grep grub2

Figure 5-19 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



6 Change History

Released On Description

2020-02-01 This issue is the seventh official release, whichincorporates the following change:Added What Can I Do If Message "The target ECS isnot booted with UEFI. Create an ECS using theimage whose boot mode is UEFI." Is DisplayedDuring Migration Task Creation?.

2020-2-11 This issue is the sixth official release, whichincorporates the following changes:● Added How Do I Migrate an ECS from Account A

to Account B?● Added How Do I Migrate Data from One Region

to Another?● Added What Can I Do If the Server Cannot Be

Started After Migration Due to an Earlier GRUBVersion?

2019-12-10 This issue is the fifth official release, which incorporatesthe following change:Added What Can I Do If the System Disk on theTarget Server Is Still a Temporary Mirror Disk Aftera Task Is Deleted?

2019-09-12 This issue is the fourth official release, whichincorporates the following change:Added How Do I Load the NIC Driver for a WindowsServer 2003 or 2003 R2 Server After the Migration?

Server Migration ServiceFAQs 6 Change History


Released On Description

2019-08-30 This issue is the third official release, whichincorporates the following changes:Added Why Are the File Sizes Before and After theMigration Different?Added Why Are Data Disks not Displayed on theTarget ECS After a Windows Server is Migrated?Added How Do I Expand the Capacity of a WindowsSystem Disk After the Migration?

2019-07-18 This issue is the second official release, whichincorporates the following change:Updated Table 1-3 in What Are Supported SourceServer OSs and Migration Restrictions?

2019-03-30 The issue is the first official release.

Server Migration ServiceFAQs 6 Change History


Documents

Server Migration Service - HUAWEI CLOUD1.2 What Are Supported Source Server OSs and Migration Restrictions? Supported source server OSs Table 1-3 Supported source server OSs OS Type