You need to enable JavaScript to run this app.
Server Migration Center

Server Migration Center

Copy page
Download PDF
Step 2: Create and launch the migration job
Operating system migration tasks
Copy page
Download PDF
Operating system migration tasks
After the migration source information is imported, the SMC console will automatically generate a migration source record. You can create and start an operating system migration task for the migration source in the console to migrate the operating system of your VolcanoEngine instance to veLinux 1.0/2.0 CentOS Compatible while retaining all system volume data.​
This topic describes how to create and start a migration task.​
Prerequisites​
  • Make sure that the VolcanoEngine instance with the operating system to be migrated complies with the operating system migration specifications.​
Usage notes​
  • Currently, only the following operating systems are supported for migration.​
  • ​
    Source operating system​
    Target OS​
    ​
    ​
    veLinux 1.0 CentOS Compatible​
    veLinux 2.0 CentOS Compatible​
    CentOS Stream 8​
    ×​
    ✓​
    CentOS 7​
    ✓​
    ✓​
    ​
  • The 5.x kernel used by veLinux is incompatible with the 3.10 kernel used by CentOS 7. If your instance runs workloads that depend on kernel interface programming, such as kernel out-of-tree (OOT) module development and hardware enablement, evaluate compatibility in advance to avoid service malfunctions after operating system migration.​
  • Before the operating system of the ECS instance is migrated, SMC will automatically create a whole image (naming format: SMC_Backup_Image__$Migration task ID$) and a snapshot consistency group (naming format: create from $Target resource ID$) for data backup, facilitating subsequent data recovery. The image and snapshots will not be automatically deleted by the resource cleanup feature after the migration. You can delete them manually based on your needs. For details, refer to Clearing tasks resources.​
  • During the migration process, do not perform operations on the source ECS instance. For example, do not stop or restart the source ECS instance.​
  • Do not shut down the migration Agent during the migration. Doing so will cause migration failure and may even damage the operating system of the source ECS instance. In case of unexpected incidents, restore the system using the whole image automatically created by SMC before the migration. For details, refer to Purchasing ECS instances with whole images.​
Procedure​
After you import the migration source information using the migration Agent, the ECS console will display the corresponding migration source information. You can create a migration task to migrate the source to VolcanoEngine.​
  1. Log in to the ECS console.​
  1. In the left directory tree under any region, select "Server Migration Center > Migration source" to enter the migration source list page.​
  1. (Optional) If you have already enabled the snapshot service, skip this step. Otherwise, hover the mouse over the "Create migration task" button. In the pop-up window, check the box next to "Click to activate, indicating that you are aware and agree Service-Specific Terms for VolcanoEngine Elastic Compute Service", and then click the "Confirm" button.​
  1. After the snapshot service is enabled, click the "Create migration task" button in the "Actions" column of the target migration source.​
  • ​​​
  1. On the "Create migration task" page, enter the following information based on the page instructions.​
  • ​
    Parameter​​
    Description​
    Sample value​
    Migration type​
    Select the migration task type. In this topic, "OS migration" is selected.​
    OS migration​
    Task name​
    Enter the name of the current migration task.​
    Migration task 1​
    Current OS​
    By default, the source server operating system version is displayed. You cannot modify this parameter.​
    CentOS 7​
    Target OS​
    Select the new operating system version for the source server after migration.​
    veLinux 1.0 CentOS Compatible​
    Project name (optional)​
    Select the project to which the migration task belongs.​
    • After a project is selected, the migration task can only be viewed and used by users with permissions for that project.​
    • If no project is available in the drop-down list, you can follow the guidelines to create a project. For more information, see Creating projects.​
    tip​
    A project is a collection of resources. You can add migration tasks to a project, categorize and manage them by project, and control user and role permissions for migration tasks within the project. For more details, refer to Resource management.​
    project-1​
    Tag (optional)​
    A tag is a key-value pair used to identify cloud resources. Tags help you categorize cloud resources with similar attributes based on different dimensions, such as purpose, owner, or environment. This allows you to search and aggregate your cloud resources for easy management.​
    Click the "+ Add tag" button, and enter the tag key and tag value to add a tag to the migration task. For more information, see Tag overview.​
    Key:Value​
    ​
  1. After you configure the parameters, click the "Confirm" button.​
  1. Once the task is created, it will start immediately.​
  • You can view the execution progress, result, and logs of the migration task. You can also modify the auto incremental synchronization rules. For details, see Managing migration tasks.​
  • You can go to the "Event monitoring" page in the ECS console or the "Event Center" in the Cloud Monitor console to query migration task event information. For details, see Querying and handling ECS events. For the complete list of Server Migration Center event types, see Status change event.​
  1. After the migration is completed, you can go to the ECS console or log in to the source server to check whether the operating system is migrated.​
  • ​
    ECS console
    Inside the instance
    ​
    1. Log in to the ECS console.​
    1. In the top menu bar, select the region and project where the target instance resides.​
    1. If the image column of the target instance is updated to veLinux, the migration is successful.​
    ​
Related documents​
Last updated: 2026.01.26 14:49:52