Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Help Center/ Server Migration Service/ User Guide(ME-Abu Dhabi Region)/ FAQs/ Product Consulting/ What Information Does SMS Collect About Source Servers?

What Information Does SMS Collect About Source Servers?

Updated on 2024-03-15 GMT+08:00

SMS uses the Agent to collect source server details to evaluate the migration feasibility and provide data required for selecting or configuring target servers. Table 1 lists the data collected from a Windows server. Table 2 lists the data collected from a Linux server. All collected data is used for migration only.

Table 1 Collected Windows server details

Item

Sub-Item

Usage

Environment information

OS version

Used for migration feasibility checks. Only source servers with OSs included in Supported Windows OSs can be migrated.

Firmware type

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

CPU

Used for recommending the target server flavor.

Memory

Used for recommending the target server flavor.

System directory

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

Disk partition style

Used for configuring the target server. Before the migration, the disks of the target server must be formatted to be the same as those of the source server.

File system

Used for migration feasibility check. Only the NTFS partitions can be migrated.

Available space

Used for migration feasibility check. If there is not enough space on a source server partition, the migration may fail.

OEM system check

Used for migration feasibility check. If the system is an OEM system, the OS needs to be reactivated after the migration.

Driver files

Used for migration feasibility check. The source server must have basic disk drivers.

System services

Used for migration feasibility check. Volume Shadow Copy Service (VSS) must be available on the source server.

User permissions

Used for migration feasibility check. You must have the administrator permissions to run the Agent.

Disk information

  • Disk name
  • Disk partition style
  • Disk size
  • Used space

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

Table 2 Collected Linux server details

Item

Sub-Item

Usage

Environment information

OS version

Used for migration feasibility checks. Only source servers with OSs included in Supported Linux OSs can be migrated.

CPU

Used for recommending the target server flavor.

Memory

Used for recommending the target server flavor.

Paravirtualization

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

Firmware type

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

Boot mode

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

rsync

Used for evaluating synchronization feasibility. SMS synchronization depends on rsync on the source server.

Raw device

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

Disk partition

Used for migration feasibility check. The source disk partition style must be Main Boot Record (MBR) or GUID Partition Table (GPT).

Disk partition style

Used for configuring the target server. Before the migration, the disks of the target server must be formatted to be the same as those of the source server.

File system

Used for migration feasibility check. The file systems on the source server must be Ext2, Ext3, Ext4, VFAT, XFS, or Btrfs.

Disk information

  • Disk name
  • Disk partition style
  • Disk size
  • Used space

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

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback