How Do I Configure Data Compression for a Linux Block-Level Migration?
Scenario
By default, data compression is enabled for Linux block-level migrations. The number of compression threads is automatically configured based on the resource usage of source servers. The number of compressions threads depends on the number of idle CPUs but is limited to 3 at most. This may cause high CPU usage. In this case, you can modify the number of compression threads or disable data compression on the SMS console.
Procedure
- Log in to the SMS console.
- In the server list, locate the source server to be migrated and click Configure Target in the Migration Stage/Status column.
- On the Configure Basic Settings tab page, select Configure now next to Advanced Settings to expand advanced settings.
- At the bottom of the page, select Configure now next to Advanced Options.
- Configure the advanced options listed in the following table.
Parameter
Setting
Data Compression
- Select Yes if you want to enable data compression during the migration. Then Compression Threads will be available for you to configure.
- Select No if you do not want to enable data compression during the migration.
Compression Threads
Configure the maximum number of compression threads that can be launched. If you select auto for this option, the system determines the number automatically. You can also enter an integer from 1 to 3.
Cache Node Size (MB)
Specify the size of a single data cache node. The value must be an integer ranging from 1 to 8. The default value is 4.
Data compression occupies a large amount of CPU resources. If you enable this function, you need to consider the actual resource usage of the source server to prevent services on it from being affected. For details about the default resource usage, see How Many Resources Will Be Used for a Linux Block-Level Migration?
Modifying Advanced Options
You can only modify the advanced migration options if a task has the target server configured but is not started, is paused, or is waiting to execute an incremental synchronization. After locating the task, in the Operation column, choose More > Manage Migration Settings > Configure Advanced Options. Then you can modify the settings of Data Compression, Compression Threads, and Cache Node Size.
Product Consultation FAQs
- Can I Migrate Servers from Other Clouds to Huawei Cloud Using SMS?
- Can I Migrate ECSs from Huawei Cloud to On-Premises Environments or Other Clouds Using SMS?
- Can I Ask Huawei Cloud Technical Support to Help Me Migrate Services?
- Can I Migrate Workloads to a DeH, DeC, Kunpeng ECS, or BMS Using SMS?
- Does SMS Support Resumable Data Transfer?
- How Do I Migrate an ECS from One Account to Another Using SMS?
- How Do I Migrate an ECS from One Region to Another Using SMS?
- Will My Services on the Source Server Be Interrupted During Migration?
- How Do I Obtain an AK/SK Pair for a Huawei Cloud Account?
- How Do I Obtain an AK/SK Pair for an IAM User?
- How Do I Migrate a Linux Source Server as a Non-root User?
- What Information Does SMS Collect About Source Servers?
- How Do I Select a Target Server?
- How Do I Create an ECS?
- What Is Block-Level Migration?
- What are Valid Data Blocks?
- How Does Migration Using SMS Differ from Migration Using IMS?
- Why Is the OS Name of the Target ECS Displayed on the ECS Console Different from That of the Source Server?
- How Do I Determine Whether a Migration Is Complete?
- Can I Migrate Only Some Workloads from a Source Server?
- Can the Target Server Run a Different Type of OS from the Source Server?
- What Determines the Specifications of a Target Server?
- How Do I Download the SMS-Agent for Windows and the SHA256 Verification File?
- Can I Migrate a Source Server If There Is No Corresponding Image Available on Huawei Cloud?
- How Does SMS Differ from IMS in the Migration Scenario?
- How Do I Display the OS Name of a Target Server on the ECS Console?
- What Are the Snapshots of a Target Server Used for?
- In a Linux File-Level Migration, How Do I Exclude Specific Directories from Migration and Synchronization?
- Will an Incremental Synchronization Overwrite Existing Data on a Launched Target Server?
- How Do I Create a Target Server That Meets the SMS Requirements?
- Can I Use SMS to Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Can I Use an AK/SK Pair of a Federated User (Virtual IAM User) for Authentication During the SMS-Agent Startup?
- How Do I Synchronize Data in Specific Directories After a Linux File-Level Migration Is Complete?
- Will the Migration Be Affected If the SSH Service Does Not Use Default Port 22 on the Source Server?
- How Do I Obtain the SMS Domain Name?
- How Many Resources Will Be Used for a Linux Block-Level Migration?
- How Do I Configure Data Compression for a Linux Block-Level Migration?
- Do I Need to Activate the Windows OS and Paid Software After the Migration Is Complete?
- What Do I Do If the Source Server's Clocks Are Not Synchronized to the Target Server?
- How Do I Set the Number of Concurrent Processes for Linux File-Level Migrations?
- Which Directories Are Not Synchronized by Default During Incremental Synchronization on a Linux Server?
- How Do I Verify Data Consistency Between the Source and Target Servers?
- Can I Use a Temporary AK/SK Pair for Migration?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
