Migration to Huawei Cloud

Module 6: Using and Migrating

Compute Services
 Objectives
⚫ Upon completion of this course, you will:
 Understand Huawei Cloud compute services.
 Know how to migrate servers from data centers to Huawei Cloud ECS.
 Be able to perform hands-on exercises.

3
 Contents
1. Introduction to Elastic Cloud Server (ECS)

2. Introduction to Server Migration Service (SMS)

3. Getting Started with SMS

4
 Do you know ECS features and
what do you think of them?

Elastic Cloud Server

(ECS)
 ECS Features
 You can use an ECS just like a
regular server.
 You have full permissions for your
ECS.
 You only need to note the upper-
Elastic Cloud Server
layer configurations above the OS.
(ECS)
 On-demand elasticity: Resources can
be added or deleted dynamically to
meet changing demand.
6
 What Are the Benefits of On-Demand Elasticity?

Scalable to meet Easy-to-obtain Used in red-black and

changing demand for resources to help blue-green iterations
compute resources innovation during agile deployment

7
 Creating an ECS
Configure Configure Configure
Confirm
Basic Settings Network Advanced Settings

Billing mode VPC and subnet ECS name

Region and AZ Security group Server backup

Instance type EIP and traffic ECS group

Image Advanced options

Disk

8
 How Do I Select an Instance Type?

1. Instance type

General computing, memory-optimized,

and more

C6.8xLarge.4 2. Instance generation

Generally, the later the generation,

12 3 4
the more cost-effective the instance

is.

3. Instance size (number of vCPUs)

4. Memory size (GiB) for each vCPU

9
  General computing
 General computing-basic
 Large-memory
 Disk-intensive
Which instance type should I choose?
 GPU-accelerated
 FPGA-accelerated
 Kunpeng memory-
optimized
 Kunpeng ultra-high I/O
 ......

10
 Tips for Selecting an Instance Type
Select an instance type based on the module Optimizing instance types is not a one-time
features. job. You can:
• Evaluate resource consumption and select • Optimize instance types based on
proper specifications. monitoring metrics.
• Check whether all key resources are
fully utilized.
Do not worry if you pick an inappropriate instance • Change the instance type if resources
type. You can: are being wasted.
• Change the instance type easily. • Keep monitoring and find more
• Purchase a new ECS. opportunities for optimization.

11
 Which specifications should I select?

12
 Comparison of ECS Specifications

Max: 80 persons Max: 40 persons

Elasticity
50 50 25 25 25 25
Cost: persons persons cost:

2 OSs and 2 EVS disks VS 4 OSs and 4 EVS disks

VS
Max: 80 persons Max: 40 persons

Disaster 50 100 33 33 34 25
radius: persons persons

Select specifications based on your service scale.

13
 Contents
1. Introduction to Elastic Cloud Server (ECS)

2. Introduction to Server Migration Service (SMS)

3. Getting Started with SMS

14
 SMS Characteristics

 SMS moves source servers as-is to Huawei Cloud.

 SMS requires that you have full permissions for source

servers.

You need to install and run the Agent on source servers

SMS
as an administrator.

 SMS requires that source server OSs be compatible with

target server hardware.

15
 SMS Overview
SMS helps you migrate
Target Server
applications and data from x86 Source Server
physical servers or virtual OS OS
machines (VMs) on-premises or
Disks Disks
in private or public clouds to
SMS App
ECSs on Huawei Cloud. App

Scenario 2: Application Scenario 3: Database

Scenario 1: OS migration migration migration To migrate
SMS lifts and shifts all data to
SMS migrates OSs as-is. applications and data in SMS can migrate single- cloud
No additional source server disks, so node databases and data databases,
configurations are you do not have to files. you can use
required. manually redeploy DRS.
applications.

16
 SMS Compatibility
⚫ SMS can migrate x86 physical servers and VMs on VMware, Hyper-V, XenServer,
OpenStack, and FusionSphere from IDCs, private, or public clouds to Huawei Cloud.
⚫ SMS supports popular public clouds (such as AWS, Azure, Google Cloud, Alibaba Cloud,
Tencent Cloud, and Huawei Cloud) and jointly-operated clouds (such as Tianyi Cloud,
Open Telekom Cloud, Orange Flexible Engine, and Open Telefonica Cloud).
⚫ SMS supports most of the popular OS distributions and releases. For details, see SMS
documentation.

17
 How SMS Works

/ /boot /data
/tmp / /
Linux
migration /boot /data File- or block-level migration: SMS /boot /data
replicates source data by file or by
block.

Source (Linux) Target (Linux)

1 1

2 5 4 3 1
Windows migration
6 Block-level migration: SMS identifies and 3
3
replicates valid blocks from the source server to
the target server.
Suppose that blocks 2 and 6 on the source server 5 4
5 4
are unused. They will not be replicated to the
Source (Windows) target server. Target (Windows)
18
 Full Migration
Source Target
1 Create a target server. server
1. You create an ECS before creating a migration server User
task, or let SMS create an ECS as the target C D
server during the migration. C D Create a migration task.

Create and attach a Target

Source 2 temporary EVS disk. server
2. SMS uses a hidden public image (Windows Server
server SMS
2008 or CentOS 7.5) to create a temporary EVS
disk and attaches it to the target server. Windows Server D E
C D 2008/CentOS 7.5 C

Source Target
3 Format and partition server
3. SMS formats and partitions disks on the server disks on the target
target server. SMS server.
C D C D E

Target
4. SMS migrates disk data from the source server Source server
to the target server, modifies the registries server 4 Migrate source disk data.
and startup items, and configures the bootable SMS
volume. C D E
C D

Restart the target server. Target

5. SMS deletes the temporary EVS disk, restores Source
server
the disk sequence, and restarts the target server
SMS
server.
C D 5 Delete the temporary EVS disk. C D

19
 Single Incremental Synchronization

Source Target
1 Update the source data. server
1. After a full migration is complete, you server User
update the source data. C
C D Start an incremental synchronization. D

Target server
2. SMS attaches a temporary EVS disk to and Source 2
server SMS
restarts the target server.
C D E
C D

Source Target
3. SMS synchronizes incremental data and 3 server
server
modifies file configurations. SMS
C D C D E

4. After the synchronization is complete, SMS

detaches the temporary EVS disk from the Source 4 Detach the temporary EVS disk after Target
the synchronization is complete. server
target server. server SMS
C D
C D

20
 SMS Functions and Features
SMS automatically checks the migration SMS automatically identifies valid data
feasibility of source servers. Only based on disk partitions and file system
Migration servers that pass the check can be Online structures and then migrates the data
feasibility migrated. migration online.
check
Functions
After the online migration is complete, SMS can create target servers with
you can synchronize incremental data at specifications recommended based on source
Incremental any time, which helps minimize service Automatic VM servers.
synchronization downtime. creation

• Migration feasibility check: Before the migration, the Agent

• Migration agents: GUI-based Windows Agent and CLI-based Linux
collects source server information and checks the migration
Agent
feasibility.
• Block-level migration and synchronization for Windows: The
• File- and block-level migration and synchronization for
Agent identifies valid data in file systems, creates
Linux: The Agent uses rsync to migrate or synchronize data
incremental snapshots, and performs block-level migration and
on Linux servers.
synchronization.
• Secure transmission: SMS uses AK/SK pairs to authenticate the
Features • Migration network: You can use EIP, virtual private network (VPN), Agent. Each new transmission channel is established using new
or Direct Connect for migration and control the migration speed. certificates and encrypted using SSL.

• Target server optimization: After the migration is complete, SMS

• Automatic VM creation: SMS can create target servers during the
optimizes target servers by installing drivers, activating OSs,
migration based on the settings you specified and source server
processing login credentials, controlling server status, and
specifications.
other actions.

• Synchronous rollback: If a synchronization fails, SMS rolls back

• Log upload: If a migration fails, SMS can easily collect and
the target server to the status when the previous full migration
upload logs for troubleshooting.
or synchronization is complete.

21
 Collected Source Server Information (Linux)
Item Sub-Item Usage

OS version Used for migration feasibility check. Only source servers with supported OSs can be migrated.
Used for recommending target server flavors. Target servers must have at least as many vCPUs as
CPU
the source servers.
Used for recommending target server flavors. Target servers must have at least as much memory as
Memory
the corresponding source servers.
Paravirtualization Used for migration feasibility check. Paravirtualized source servers cannot be migrated.
Used for synchronization feasibility check. SMS synchronization depends on rsync on source
Environment rsync
servers.
information
Raw device Used for migration feasibility check. Source servers that contain raw devices cannot be migrated.
Used for migration feasibility check. The disk type of a source server must be main boot record
Disk partition
(MBR) or GUID partition table (GPT).
Used for configuring target servers. Before the migration, the disks of the target server must be
Disk partition style
formatted to be the same as those of the source server.
Used for migration feasibility check. The file systems on a source server must be Ext2, Ext3,
File system
Ext4, VFAT, XFS, or Btrfs.
Disk name
Disk partition style Used for checking whether the disk specifications of target servers meet the migration
Disk information
Disk size requirements.
Used space

For details, see https://support.huaweicloud.com/intl/en-us/sms_faq/sms_faq_0002.html.

22
 Collected Source Server Information (Windows)
Item Sub-Item Usage

OS version Used for migration feasibility check. Only source servers with supported OSs can be migrated.
Used for recommending target server flavors. Target servers must have at least as many vCPUs as the
CPU
corresponding source servers.
Used for recommending target server flavors. Target servers must have at least as much memory as
Memory
the corresponding source servers.
Used for configuring target servers. After the migration is complete, it will be used to restore
System directory
Environment the registry.
information Used for configuring target servers. Before the migration, the disks of the target server must be
Disk partition style
formatted to be the same as those of the source server.
Used for migration feasibility check. Only new technology file system (NTFS) partitions can be
File system
migrated.
Used for migration feasibility check. If there is not enough space on a source server partition,
Available space
the migration may fail.
Used for migration feasibility check. If a system is an OEM system, the OS needs to be reactivated
OEM system
after the migration.
Disk name
Disk partition style Used for checking whether the disk specifications of target servers meet the migration
Disk information
Disk size requirements.
Used space

For details, see https://support.huaweicloud.com/intl/en-us/sms_faq/sms_faq_0002.html.

23
 Migration Constraints
Item Description

Only source servers with supported OSs can be migrated.

OS
A server running multiple OSs cannot be migrated.
Windows:
- At least 320 MB of available space on a partition larger than 600 MB
Available disk space - At least 40 MB of available space on a partition smaller than 600 MB
Linux: At least 200 MB of available space on the root partition

Windows: Only NTFS partitions can be migrated.

File system
Linux: Only Ext2, Ext3, Ext4, VFAT, XFS, and Btrfs file systems can be migrated.
Only files on the local disk can be migrated. SMS cannot migrate files from shared file systems such as network
Shared file system
file systems (NFSs) and common internet file systems (CIFSs).
Encrypted file OSs that contain protected folders and encrypted volumes cannot be migrated.
Raw device Source servers that contain raw devices cannot be migrated.
Paravirtualization Paravirtualized source servers cannot be migrated.
Cluster application OSs that contain cluster applications cannot be migrated.
Database and application Active directories and database applications cannot be migrated. They need their own migration solutions.
Application bound to
OSs that contain applications bound to hardware cannot be migrated.
hardware

For details, see https://support.huaweicloud.com/intl/en-us/sms_faq/sms_faq_0007.html.

24
 Application Scenarios
Source Server SMS Target Server

Windows Red Hat FreeBSD Windows Red Hat FreeBSD

OS migration
CentOS Debian Ubuntu CentOS Debian Ubuntu

IFS IQMS SAP Exchange .NET IFS IQMS SAP Exchange .NET
Application
migration Oracle SQL Server SAP HANA Oracle SQL Server SAP HANA

Database Database
Data
migration File File

25
 IaaS Migration Case
Scenario Analysis
LB ELB • Server migration
During the server migration, you do not need to interrupt or stop your
services. You only need to suspend services briefly before you launch the
target server when the migration is in the Continuous Synchronization
stage. This minimizes your service downtime.
Web server Web server • NAS migration
SMS Typically, scp or rsync is used for NAS migration. However, these two
ECS ECS tools cannot migrate a large number of small files fast. In contrast,
Incremental synchronization rclone supports multi-thread, concurrent migrations, which can greatly
accelerate the migration.
rclone • Object storage migration
App server App server Object Storage Migration Service (OMS) can easily migrate object storage
data from popular private or public clouds. In this example, OMS is
ECS NAS ECS SFS compatible with the source object storage interfaces and can quickly
transmit and encrypt data.
• Advantages
SMS
SMS: ease of use, smooth service switchover, high compatibility and
Middleware layer Middleware layer security, and efficient transmission
Incremental synchronization
·· ·· Rclone: fast transmission of massive small files and verification of data
Redis MQ Redis MQ consistency
· Direct ·
OMS: security authentication, and transmission and storage encryption
Connect • Weaknesses
After the object storage migration is complete, you need to verify data
Data layer Data layer consistency. If there is massive data to be migrated, this will take a
long time. Using rclone will change the UIDs and GIDs of files and
RDS ES RDS ES OBS
directories to those of the user who run rclone commands. You can change
OMS the UIDs and GIDs to the same as those on the source server manually or
Object storage using a script after the migration is complete.
Incremental synchronization
26
 Migration Network
Condition 1: Source servers can connect to Huawei
Cloud API Gateway.
Huawei Cloud ➢ The Agent installed on source servers must
communicate with Huawei Cloud services
Global DMZ
Identity and Access Management (IAM), ECS,
SMS Image Management Service (IMS), EVS, VPC, SMS,
OBS, and Domain Name Service (DNS) during the
Users migration. You must ensure that the Agent can
SMS web server
call the APIs of these services in the region
ECS you are migrating to.
Access Huawei Cloud. Condition 2: Source servers can connect to the
target region.
➢ If you want to migrate over the Internet, you
API Gateway EVS need to purchase and configure an EIP in the
target region.
➢ If you want to migrate over a private network,
VPC (POD)
you need to purchase and configure a Direct
Connect or VPN connection in the target
region.
The source server can access
the target server through an Condition 3: Required ports in the security group
EIP or a Direct Connect EIP of each target server should be opened.
EVS disks
connection. ➢ Windows: ports 8899, 8900, and 22
➢ Linux: ports 8900 and 22
Source VPN Target server ➢ If a network access control list (ACL) is
Windows: ports 8899, 8900, and
server 22 Linux: ports 8900 and 22
configured for the subnet you are migrating
to, you also need to open the required inbound
ports in the ACL.
27
 Migration Time

where
• T: the migration time, in hours
• 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
server
• U: the network usage, which is related to network quality (jitter,
delay, and packet loss). The value is usually between 50% and 80%.

For details, see https://support.huaweicloud.com/intl/en-us/sms_faq/sms_faq_0017.html.

28
 Contents
1. Introduction to Elastic Cloud Server (ECS)

2. Introduction to Server Migration Service (SMS)

3. Getting Started with SMS

29
 Process Flow

30
 Create a Migration Task

31
 Start the Migration Task

32
 Synchronize Incremental Data

33
Thank You.
Copyright©2023 Huawei Technologies Co., Ltd. All Rights Reserved.
The information in this document may contain predictive statements including,
without limitation, statements regarding the future financial and operating
results, future product portfolio, new technology, etc. There are a number of
factors that could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements. Therefore, such
information is provided for reference purpose only and constitutes neither an
offer nor an acceptance. Huawei may change the information at any time
without notice.