How Do I Display the OS Name of a Target Server on the ECS Console?
Symptom
On the ECS console, you found that the OS name of your target server was different from the actual OS name of the server.
This is a normal event resulting from a limitation of the ECS console.
Possible Causes
The ECS console displays the image name of an ECS, not the OS name. The two names may be different. When you configure the target server:
- If you choose to automatically create an ECS as the target server, an SMS-defined image name will be displayed for the new ECS on the ECS console, such as LinuxServer or WindowsServer.
- If you choose to use an existing ECS as the target server, the image name of the existing ECS is displayed on the ECS console.
Solution
To display the actual OS name of your target server on the ECS console, perform the following steps:
- Obtain an image file based on the source server OS.
- Upload the image file to an OBS bucket.
- Use the image file to create a private image.
- Log in to the management console and click Image Management Service under Compute.
- On the Image Management Service page, click Create Image.
- Set Type to Import Image and Image Type to System disk image.
- Select the image file uploaded to your OBS bucket.
- Select ECS system disk image for Function and x86 for Architecture. Set Boot Mode to the actual boot mode of the source server.
You can see the boot mode of the source server on the SMS console. For more information, see Checking the Firmware Type of a Source Server.
- Set OS to the source server OS. If the source server OS is not an available option, select Other from the drop-down list.
- Set System Disk based on the system disk of the source server. If the source system disk is smaller than 40 GB, set System Disk to 40 GB.
- Set Name to the source server OS. The name you specified here will be displayed on the ECS console.
- Select an enterprise project for the target server. If no other enterprise projects are available, select Default.
- Confirm the configuration details, select I have read and agree to the Statement of Commitment to Image Creation and Image Disclaimer, and click Next. On the Resource Details page that is displayed, click Submit. Wait for the image creation to complete.
- If you have an ECS suitable as a target server, use this image to change the OS of the ECS. If you have no suitable ECS available, use this image to create one.
- When configuring the target server on the SMS console, select the one you prepared above. For more details, see Configuring the Target Server.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore