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
Help Center/ Server Migration Service/ User Guide(ME-Abu Dhabi Region)/ FAQs/ Migration Duration/ How Is the Migration Rate Displayed on the SMS Console Calculated?

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

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

Metrics

Table 1 Related metrics

Metric

Windows Block-Level

Linux File-Level

Linux Block-Level

Total data

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

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

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

Migrated data

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

Total size of all migrated files.

Total size of all migrated data blocks in the partition.

Elapsed time

Time elapsed after a migration starts.

Remaining time

Remaining time = (Total data – Migrated data) / Migration rate

Migration rate

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

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

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

Windows Block-Level Migration

There are two types of Windows block-level migration rates. One is the rate displayed on the SMS console, which is the average migration rate over the last 5 seconds. The other is the actual NIC throughput for the migration process, which is less than what is displayed on the console because the data is compressed before being transmitted through the NIC

  • Migration rate displayed on the SMS console (before compression)

    The migration rate displayed on the console is the actual amount of data migrated per second, which is the data transmission rate before compression. This rate shown is based on the average amount of data migrated over the last 5 seconds. For example, if 200 MB of data was transmitted over the last 5 seconds, and the amount of data after compression is 50 MB, the rate displayed on the console is 320 Mbit/s (200 MB*8/5s), but the NIC throughput for the migration process is 80 Mbit/s (50 MB*8/5s).

  • Actual NIC throughput (after compression)

    During a Windows block-level migration, the Agent compresses data before transmitting it to the target ECS. The agent on the target ECS decompresses the data and writes the data to disks. The actual NIC throughput is the network bandwidth occupied by the migration process. You can view this rate in the task managers on the source server and target ECS. However, you can view this rate only after the target ECS is unlocked. The following uses Windows Server 2012 as an example.

    CAUTION:
    • You can view the network bandwidth occupied by the migration process in the task manager. Use the migration rate displayed on the SMS console to estimate how long the migration will take.
    • The NIC rate of the source server also includes the bandwidth occupied by applications running on the source server. A more reliable indicator is the migration rate of the migration process. The rate displayed in the task manager is the compressed data transmission rate.
    • A Windows block-level migration rate is more stable because it is not affected by the number or size of files to be migrated.

Linux File-Level Migration

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

However, there is an exception. A Linux file-level migration is inefficient when transferring small files. When migrating a large number of small files, the network bandwidth cannot be fully utilized. In such a scenario, the migration rate is far lower than the available network bandwidth.

Linux Block-Level Migration

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

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