Help Center>
Server Migration Service>
FAQs>
Product Consultation>
How Do I Create a Target Server that Meets the SMS Requirements?
Updated on 2024-03-29 GMT+08:00
How Do I Create a Target Server that Meets the SMS Requirements?
When you use SMS to migrate a server, you can prepare a target server on Huawei Cloud to receive data from your source server.
SMS supports migration to ECSs, DeHs, and DeCs.
Target Server Environment Requirements
- A target server must run the same type of OS as the source server. For details, see Can the Target Server Run a Different Type of OS from the Source Server? Otherwise, there will be a server name conflict or other problems.
- A target server running Windows must have at least 2 GB of memory.
- A target server must use the same type of firmware as the source server. Otherwise, the system will warn you the firmware type of the target server is different from that of the source server, or the firmware type of the source server is unknown. For details, see How Do I Check the Firmware Type of a Source Server?
- Target Server Disk Requirements
- A target server must have at least as many disks as the source server. Otherwise, the error "Insufficient disks on the Target Server" will be reported. To resolve this error, see How Do I Resolve Error "Insufficient disks on the Target ECS"?
- Each target server disk must be at least as large as the paired source server disk, or the migration cannot continue.
In such a case, see How Do I Resolve Error "Some disks on the target server are smaller than those on the source server. Select another target server" When I Configure the Target Server?
- The required ports are enabled in a security group the target server belongs to.
- Windows: TCP ports 8899, 8900, and 22
- Linux: TCP port 22 for file-level migration, and ports 8900 and 22 for block-level migration
- For security purposes, you are advised to open these ports only to the source server.
- The firewall of the target server must allow traffic to these ports.
How to Create a Target Server
Method 1: Create a target server before the migration
Create an ECS, DeH, or DeC that meets the requirements in advance.
When you configure the target server on the SMS console, set Server to Use existing and select the server you created.
Method 2: Create a target server during the migration
When you configure the target server on the SMS console, set Server to Create during migration.
For details, see step 7 in Configuring the Target Server.
Parent topic: Product Consultation
Product Consultation FAQs
- Can I Migrate Physical Servers and VMs 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?
- 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 Create an AK/SK Pair for a Huawei Cloud Account?
- How Do I Create 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 the 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 Services on the Source Server?
- Can the Target Server Run a Different Type of OS from the Source Server?
- What Determines the Specifications of a Target Server?
- Which Download Option Should I Choose When I Download the Windows Agent?
- 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 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 SMS Migrate Self-built Databases, Big Data Services, or Websites Deployed on a Source Server?
- Can the AK/SK of a Federated User (Virtual IAM User) Be Used for Authentication During the SMS-Agent Startup?
- How Do I Synchronize Files 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 My Windows OS and Paid Software After the Migration?
- Why Does the Target Server Not Synchronize the Clocks on the Source 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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
