DocsICP FilingConsole
官方文档
首页

Server migration to an ENS instance

更新时间：
复制 MD 格式
产品详情
我的收藏

The edge node migration feature of Server Migration Center (SMC) migrates servers directly to Alibaba Cloud Edge Node Service images. Supported server sources include physical servers, local virtual machines (such as VMware, Xen, KVM, and Hyper-V), servers from other cloud providers (such as AWS, Azure, Google Cloud, and Tencent Cloud), and Alibaba Cloud ECS instances. You can then use these ENS images to create ENS instances, improving migration efficiency.

Use cases

Directly migrate a server into an Alibaba Cloud ENS image

If you have not purchased an Alibaba Cloud Edge Node Service instance, you can migrate a server into an Alibaba Cloud Edge Node Service image. You can then use the ENS image to manually create an ENS instance.

This approach is more efficient than manual migration because it eliminates the need to create an ECS custom image, export the image, and import it as an ENS image.

Migration overview

An ENS instance is the smallest compute unit that Edge Node Service (ENS) provides. SMC migrates the source server into an Alibaba Cloud Edge Node Service (ENS) image. You can then use the ENS image in the Edge Node Service (ENS) console to create an ENS instance to complete the migration.

The following diagram illustrates the service relationships and migration workflow for this feature.

image

  1. Install the SMC client on the source server.

  2. Configure the migration settings and start the migration. SMC automatically creates an ECS custom image, exports it to an intermediate OSS Bucket, and then imports it as an ENS image.

  3. In the Edge Node Service (ENS) console, create an ENS instance from the ENS image to complete the migration.

Note

  • Edge Node Service (ENS) is built on carrier edge nodes and networks. It provides on-demand, elastic, and distributed computing resources that are close to end users and offer global coverage. By processing data closer to end users, ENS optimizes response times, reduces the load on central servers, and lowers overall costs. This lets you deploy applications to carrier-side edge nodes, reducing compute latency and costs.

  • Object Storage Service (OSS) is a scalable, secure, cost-effective, and highly reliable cloud storage service. During migration, an OSS Bucket is used to store and transfer the generated ECS custom images.

Limitations

  • To use this feature, you must activate ENS.

  • This feature relies on the custom image export feature of ECS and the image import feature of ENS. The following limitations apply:

    • Only servers running a Linux operating system can be migrated. You cannot create ENS images from servers that run a Windows Server operating system.

    • A server can have a maximum of four data disks, each not exceeding 500 GiB.

    • Importing ENS images is supported only in the China (Beijing) and Singapore regions.

    • This feature supports only x86-based server instance types.

    • The maximum size for an image imported to ENS is 1 TiB, which is the total compressed size of the system disk and all data disks.

    For more limitations, see Limits on exporting ECS custom images and Notes on importing ENS custom images.

Migration costs

  • SMC is a free service, but you incur charges for the ECS resources used during migration, such as the migration intermediate instance. For billing details, see SMC Billing Items.

  • OSS costs: SMC saves the ECS custom image generated during migration to an OSS bucket.

  • ENS: Importing an ENS image and creating an ENS instance incur charges. For billing details, see ENS Billing Items Overview.

How it works

The SMC service consists of an SMC client and a console. You can use the SMC service to easily migrate a server into an Edge Node Service (ENS) image. The migration process involves the following steps:

  1. Download and install the SMC client on the source server. (If you import a migration source by using the CLI or the automatic import feature in the console, the system automatically downloads and installs the SMC client.)

  2. Run the SMC client on the source server. The SMC client registers the source server and reports its information to the SMC service by using the SMC service domain name.

  3. The SMC service creates a temporary intermediate instance and opens ports 8080 and 8703 in the security group.

  4. The SMC client connects to the intermediate instance over port 8080. It then transfers the cloud disk data to the data disk of the intermediate instance over port 8703.

  5. The SMC service creates an ECS custom image from the cloud disk data of the intermediate instance and uploads the image to your specified Object Storage Service (OSS) bucket.

  6. The SMC service imports the ECS image into Edge Node Service, creating an ENS image.

  7. Go to the Edge Node Service console and use the ENS image to create an ENS instance.

image

Migration impacts

Before you begin, review the migration impacts in the table below.

Affected item

Description

Intermediate instance

Do not interfere with the intermediate instance.

Do not stop, start, restart, or release the intermediate instance, or change its billing method during migration. The intermediate instance is automatically released after migration.

Note

  • For each migration, SMC creates a temporary, pay-as-you-go intermediate instance named No_Delete_SMC_Transition_Instance in your destination Alibaba Cloud account to assist with the migration.

  • If you migrate to a destination instance, that instance serves as the intermediate instance and is not automatically released.

How it works.

Intermediate image

Do not interfere with the intermediate image.

To prevent migration failure, SMC generates a temporary ECS image in the intermediate region during the migration. Do not perform any operations on the intermediate image. The intermediate image is automatically deleted upon task completion or deletion.

Transit bucket

To prevent migration failure, do not interfere with the temporary ECS image that SMC uploads to the specified OSS Bucket. This storage space is automatically released upon task completion or deletion.

Underlying hardware

The migration changes the underlying hardware, which may invalidate application licenses. Verify that your licenses remain valid after the migration.

Prerequisites

  • You have activated Server Migration Center (SMC). If you are using SMC for the first time, you must grant the required permissions, prepare the migration network, and back up your data. For more information, see Prepare for migration.

  • You have activated Object Storage Service (OSS) and created an OSS Bucket. This bucket is used to store the temporary ECS image generated during the migration. For more information, see Prepare for migration.

  • You have activated Edge Node Service (ENS). After the migration is complete, SMC imports the generated custom image to create an ENS image. You can then use this image to create edge node ENS instances.

Migration

Important

An OSS bucket is required to store intermediate images. Before first use, grant ECS access to OSS resources by following the prompts in the SMC console.

Step 1: Import a migration source

A migration source is a physical server, VM, or cloud host from another platform that you want to migrate.

Command-line import (recommended)

Important

  • The source server must have public network access. If the source server is behind a firewall, see What are the SMC endpoints? to obtain the SMC endpoints and ports, and then add them to your firewall allowlist.

  • If your source server cannot access the public network or you want to use a private network for a faster migration, see private network migration.

  1. Go to the Edge Node Migration page in the SMC console.

  2. On the Edge node migration page, click Import the migration source.

  3. Configure the parameters as prompted and copy the activation code command. The following table describes the parameters.

    Parameter

    Description

    Migration Source Type

    Select a type based on your source server:

    • Physical servers/VMs/Cloud servers of other cloud platforms.

    • ECS Instance

    Import Method

    Select Use CLI to Import Server.

    Migration Source Quota

    The number of migration sources that can be activated by the activation code. Valid values: 1 to 1,000. Default value: 200.

    Validity Period

    The validity period of the activation code, in days. Valid values: 1 to 90. Default value: 90.

    Activation Code

    Generate the activation code and copy the command.

    1. Click Generate.

    2. Click the Linux Shell tab.

    3. Click Copy to copy the activation code command.

  4. Log on to the source server and run the copied command with administrator privileges to import it.

    1. Log on to the Linux source server.

    2. Paste and run the copied command with administrator privileges to import the migration source.

      image.png

      If a message similar to Import Source Server [s-bp18x8751kgz2oyh****] Successfully! is displayed, it indicates a successful import.

  5. On the Edge node migration page of the SMC console, check the status of the migration source in the Real-time Migration Status column.

    • If the status of the migration source is Migration source online, the migration source was imported successfully.

    • Any other status indicates a failed import. Use the following methods to troubleshoot the issue, and then re-import the migration source.

      • Check the error message in the console or view the log files in the SMC client directory. The client's default installation directory is /smc.

      • For common issues and solutions, see SMC FAQ and Troubleshooting.

Console import

Important

  1. Go to the Edge Node Migration page in the SMC console.

  2. On the Edge node migration page, click Import the migration source.

  3. Configure the related parameters based on the migration source type.

    Parameter

    Description

    Migration Source Type

    Select ECS Instance.

    Import Method

    Select Import through Console.

    Region

    From the drop-down list, select the source server's region.

    Instance

    Search for and select the ECS instances to migrate in the specified region by instance ID, name, or IP address. You can select and import multiple instances in bulk.

    Tag (Optional)

    Add tag key-value pairs to the migration task to easily find and manage the task. For more information, see Manage migration sources and migration tasks by using tags and Implement fine-grained access control by using tags.

    You can add a maximum of 20 tags to a migration task.

    Resource Group

    To group and manage migration resources by business unit or project, create a resource group.

  4. After configuring the parameters, click Import.

    SMC automatically starts Cloud Assistant to import the migration source. The import process takes about 3 to 10 minutes.

  5. On the Edge node migration page of the SMC console, check the status of the migration source in the Real-time Migration Status column.

    • If the status of the migration source is Migration source online, the migration source was imported successfully.

    • Any other status indicates a failed import. Use the following methods to troubleshoot the issue, and then re-import the migration source.

      • Check the error message in the console or view the log files in the SMC client directory. The client's default installation directory is /smc.

      • For common issues and solutions, see SMC FAQ and Troubleshooting.

SMC client import

For more information about the SMC client, see SMC client user guide.

Important

  • Client-based import requires the SMC client to run on the source server, and public network access is enabled by default. If the source server is behind a firewall, find the required SMC domain names and ports in What are the SMC service domains? and add them to your firewall's allowlist.

  • If your source server cannot access the public network or you want to use a private network to improve migration efficiency, see private network migration to set up a private network connection.

  1. Go to the Edge Node Migration page in the SMC console.

  2. On the Edge node migration page, click Import the migration source.

  3. On the Import Source Servers page, configure the parameters as described in the following table.

    Parameter

    Description

    Migration Source Type

    Physical servers/VMs/Cloud servers of other cloud platforms.

    Import Method

    Select Use Client to Import Server.

    You must manually download and install the SMC client on the source server.

    Description

    1. In the Description section, follow the prompts to download, install, and activate the SMC client that matches the operating system (Linux or Windows) and architecture (32-bit or 64-bit) of your source server.

    2. Click Generate and copy the activation code.

      You must enter the activation code when you install the client.

  4. Import the migration source.

    Important

    Do not close the SMC client during the migration. Otherwise, the migration source will lose its connection to the SMC console and the migration will fail.

    1. Use a remote connection tool that supports file transfer, such as WinSCP, to upload the SMC client to the Linux source server, or run the command provided in the import instructions to download the SMC client directly on the source server.

    2. Remotely connect to the Linux source server and decompress the SMC client package.

      The following command uses the Linux 64-bit General-purpose Edition as an example. If you use a different version of the SMC client, replace the package name in the command with the name of the file you downloaded.

      tar -zxvf go2aliyun_client.tar.gz
      Note

      The Linux 64-bit ARM Edition supports the g6r general-purpose instance family and the c6r compute-optimized instance family. Enterprise-level Arm-based compute instance families.

    3. (Optional) Exclude files or directories from the migration.

      Important

      If you enable block replication for the migration, you cannot exclude files or directories.

    4. Obtain an activation code or an AccessKey pair.

      • (Recommended) Obtain an activation code: In the Description section of the SMC console, click Generate and copy the activation code.

      • Obtain an AccessKey pair: An AccessKey pair consists of an AccessKey ID and an AccessKey secret. If you have not created one, see Create an AccessKey pair.

    5. In the SMC client directory, run the following commands to start the SMC client.

      The go2aliyun_client2.6.5_linux_x86_64 directory is used as an example. The directory name varies based on the client version. Make sure to replace it with the name of the directory created after you download and decompress the package.
      cd go2aliyun_client2.6.5_linux_x86_64
sudo chmod +x go2aliyun_client
sudo ./go2aliyun_client

    6. Enter the activation code or AccessKey pair as prompted. The following example shows how to enter an activation code:adad

      After you enter the activation code or AccessKey pair, the following prompts may appear:

      • If a snapshot driver is not installed on the source system, the SMC client prompts you to install one. You can choose whether to install it based on your migration plan.

        • If you plan to enable block replication when you create the migration task, enter yes to automatically install the snapshot driver.

        • If you do not plan to enable block replication, enter no.

        Important

        If the snapshot driver fails to install, do not enable block replication when you create the migration task. Otherwise, the migration will fail.

        123

      • Most mainstream source systems have rsync installed by default. If rsync is not installed, the SMC client prompts you to install it. Enter yes to automatically install rsync, as shown in the following figure.Install rsync

      • If SELinux is enabled on the source system, the SMC client prompts you to disable it. Enter yes to automatically disable SELinux, as shown in the following figure.Disable SELinux

      If a message similar to Import Source Server [s-bp11npxndknsycqj****] Successfully! is displayed, it indicates a successful import.

      Note

      If the import fails, troubleshoot the issue based on the displayed message. Then, run the following commands in sequence to exit the background process and import the migration source again. For information about common issues and solutions, see SMC FAQ and Troubleshooting.

      sudo ./go2aliyun_client --abort
sudo ./go2aliyun_client

  5. On the Edge node migration page of the SMC console, check the status of the migration source in the Real-time Migration Status column.

    • If the status of the migration source is Migration source online, the migration source was imported successfully.

    • Any other status indicates a failed import. Use the following methods to troubleshoot the issue, and then re-import the migration source.

      • Check the error message in the console or view the log files in the SMC client directory. The client's default installation directory is /smc.

      • For common issues and solutions, see SMC FAQ and Troubleshooting.

Step 2: Migration configuration

  1. In the Actions column of the migration source that you want to manage, click Start Migration.

  2. Configure the parameters and click Start Migration.

    1. Configure basic parameters.

      Parameter

      Description

      Image storage region

      The region where the final ENS image is stored after the migration.

      Image name prefix

      A prefix for the ENS image name for easy identification.

      Transit region

      During the migration, a temporary ECS image is created in this region. Do not perform any operations on the intermediate image. The intermediate image is automatically deleted when the migration job completes or is deleted.

      Transit bucket (OSS Bucket)

      Select an OSS bucket that is in the same region as the custom image.

      The temporary ECS image created during the migration is uploaded to the specified OSS bucket. The OSS storage space occupied by the exported image is automatically released when the migration job completes or is deleted.

      Network Type

      Select the network for transferring migration data to the intermediate instance. By default, data is transferred over the public network. The intermediate instance is created in the selected Virtual Private Cloud (VPC) and vSwitch and is assigned a public IP address.

      Public Network (Default)

      Migration data is transferred to the intermediate instance over the public network. This mode requires the source server to have public internet access. You can choose whether to specify a Virtual Private Cloud (VPC) and vSwitch.

      • Specify a VPC and vSwitch: The migration job creates an intermediate instance in the VPC and vSwitch that you specify.

      • Do not specify a VPC and vSwitch: The migration job creates an intermediate instance in a new VPC and vSwitch that are automatically created by the system.

      VPC

      Migration data is transferred to the intermediate instance over a private connection within a VPC. This mode requires you to connect the source server to the Alibaba Cloud VPC and specify a VPC and vSwitch.

      Note

      If you can directly access a VPC in an Alibaba Cloud region from an on-premises data center (IDC), virtual machine (VM) environment, or cloud host, we recommend that you use this method. Private network transfer is faster and more stable than public network transfer, improving migration efficiency. You can connect the source server to the cloud VPC by using a VPN gateway, an Express Connect circuit, or a Smart Access Gateway. For more information, see Connect a VPC to a data center or another cloud.

    2. (Optional) To set parameters such as transmission speed limit and compression ratio, click More Configurations. The following table describes the advanced parameters.

      Parameter

      Description

      Migration Job Name

      The name of the migration job.

      Job Description

      Enter a description for the migration job.

      Modify Disk Partition

      Select whether to adjust the disk partition structure based on your requirements. Only SMC client versions 2.8.0 and later support this feature. SMC Client User Guide.

      • Disabled: The disk information of the source instance is not shown. SMC automatically reads the source disk information and generates a disk layout. After migration, the destination disk partition structure matches the automatically generated layout by default.

      • Enabled: The disk information of the source instance is displayed. SMC automatically reads the source disk information to generate a disk layout. You can adjust the destination disk partition structure, including the partition size and order, transfer method, and whether to enable LVM.

        The disk partition parameters are as follows:

        Configure disks

        • System Disk: The size of the destination system disk, in GiB. Valid values: 20 to 2,048.

          The destination system disk size must exceed the used space on the source system disk. For example, if the source system disk is 400 GiB and 100 GiB of space is used, the destination system disk size must be greater than 100 GiB.

          Note

          The default value is the size of the source system disk. Unless you need to reduce the system disk size, we recommend that you do not specify a value smaller than the default.

        • Data Disk<N>: The size of the destination data disk after migration, in GiB. Valid values: 1 to 32,768.

          • The <N> variable represents the data disk number. If you are migrating to a destination instance, N is the data disk ID.

          • The destination data disk size must exceed the used space on the source data disk. For example, if the source data disk is 500 GiB and 100 GiB of space is used, the destination data disk size must be greater than 100 GiB.

          • If a Data Disk has no mount target, or if all its mount targets are set to not be migrated, the data disk is not migrated.

        • LVM: Logical Volume Manager (LVM) is a disk partition management system for Linux. LVM offers more flexibility than standard disk partitions and allows for dynamic resizing of disk space.

          You can enable LVM based on your requirements. If enabled, the destination disk is automatically rebuilt with an LVM structure.

          Example:

          For each destination disk with LVM enabled, the system creates one physical volume (PV) and its corresponding volume group (VG). Within this VG, it creates one logical volume (LV) for each mount target. The VG is named vgX by default (where X is the disk sequence number), and the LVs are named lvX by default (where X is the LV sequence number), as shown in the following example:

          image

          Important

          LVM cannot be enabled in the following cases:

          • The source server runs Windows.

          • The system disk does not have a boot partition.

          If you enable LVM, the feature does not take effect in the following scenarios:

          • The source server does not support lvm2, or the lvm2 package is not installed.

          • The source server runs a Debian system with a kernel version of 3.x or earlier and has a disk with an XFS file system mounted.

        Configure mount targets

        • Migrate: Specifies whether to migrate the mount target based on your business requirements.

        • Enable Block Replication: This option is visible only for SMC client versions before 3.2.0. Block replication improves the stability of the transfer speed and ensures that the destination partition structure is identical to the source, but you cannot modify the partition size. SMC determines whether to support block replication based on the status of the source disk partitions.

          • If the source partition does not support Block Replication, this option cannot be enabled. File-level replication is used by default, which allows the partition size to be modified.

          • If the source partition supports Block Replication, this option is enabled by default to perform a partition-level disk migration.

          Note

          • If the source server runs a Windows operating system, block replication is enabled by default and cannot be disabled.

          • If LVM is enabled for the disk and the partition size is not a multiple of 4 MiB, block replication does not take effect. File-level replication is used instead.

        • Set Partition Size: If block replication is disabled, you can set the partition size. The sum of partition sizes cannot exceed the total size of the disk.

          • Windows operating systems: You cannot adjust the partition size.

          • Linux operating systems: You can set the partition size based on your requirements, but the sum of partition sizes cannot exceed the disk size.

            For SMC client versions earlier than 3.2.0, ensure that block replication is disabled.
        Note

        If the disk sizes of the destination instance do not match the source disks, you cannot create the job. In this case, the system automatically adjusts the mount target locations to meet the disk size requirements. If the requirements are still not met after the adjustment, resolve the issue as prompted on the UI.

        You can also manually drag and drop mount targets to meet the disk size requirements. However, you cannot move boot or system partitions. To do this, perform the following steps:

        1. Hover the pointer over the image icon next to the mount target.

        2. Drag the mount target to another disk.

      Transmission Speed Limit

      Limits the data transfer speed, in Mbit/s. If Compression Ratio is set to a value greater than 0, the actual network transfer speed for the compressed data is lower than the speed displayed in Real-time Migration Status.

      Compression Ratio

      Sets the data compression level for migration.

      • In environments with limited bandwidth, a higher compression ratio can increase data transfer speed.

      • In environments with high bandwidth, we recommend that you do not compress data to reduce CPU usage on the source server.

      Valid values: 0 to 10. The default value is 7. A value of 0 indicates that data is not compressed.

      Checksum Verification

      This feature is disabled by default. Enabling it enhances data consistency checks but may decrease transfer speed.

      SSL-Encrypted Transmission

      The default value is Auto. SSL encryption for data transfer improves security and data integrity.

      License Type

      Select a license type.

      • Alibaba Cloud (Default): Only Microsoft Windows Server licenses are supported. After migration, you are charged a license fee when you create an ECS instance from the image in the China (Hong Kong) region or other regions outside the Chinese mainland. The instance is automatically activated. The actual fee is displayed when you create the instance.

      • BYOL: BYOL is supported for operating systems such as Microsoft Windows, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server. After migration, no license fee is charged when you create an ECS instance from the image. You must activate the instance by using your own license.

        Note

        If you have an existing ECS instance, you can purchase software licenses, such as for Red Hat Enterprise Linux and SUSE Linux Enterprise Server, for the instance. Purchase software licenses for an ECS instance.

      Tag

      Add tags (key-value pairs) to the migration job for easier searching and management. Use tags to manage migration sources and jobs. Implement fine-grained permission management by using tags.

      Note

      You can add a maximum of 20 tags to a single migration job.

      Intermediate Instance Type

      You can select an intermediate instance type based on your requirements.

      • If you specify an instance type and it is out of stock, the migration job cannot be created.

      • If you do not specify an instance type, the system selects an instance type in a specific order to create the intermediate instance.

      Important

      To prevent migration errors, do not stop, start, restart, or release the intermediate instance during the migration. The instance is automatically released after the migration is complete.

      Report diagnostic logs

      Automatically uploads SMC client logs to the SMC server for diagnostic analysis. This helps troubleshoot issues if a migration error occurs. This feature is enabled by default.

      SMC client logs are typically stored in the /smc/go2aliyun_client*/Logs directory within the installation path.

    3. In the dialog box that appears, read the migration notice carefully, and then click Got It.

  3. On the Edge node migration page, monitor the real-time migration status.

    Data transfer time depends on factors such as the volume of source data and network bandwidth. Please wait for the migration job to complete.

    Note

    • Speed: The amount of uncompressed migration data transferred per second. If the Compression Ratio for the migration job is greater than 0, the displayed speed is higher than the actual network transfer speed of the compressed data.

    • Time Remaining for Synchronization: Calculated as (Total Data Volume - Transferred Data Volume) / Speed.

    • If the transfer speed is too slow, consider temporarily increasing the fixed bandwidth of the source and destination servers. Estimate migration time and test transfer speed.

    Subscribe to migration error events, and modify or pause the migration

    • To avoid interruptions from migration errors, you can subscribe to SMC job error notifications in CloudMonitor to receive timely SMS and email alerts.

    • While the migration job status is Synchronizing, you can perform the following operations as needed:

      • To edit a migration task, in the Actions column, click Modify Migration Job. You can modify parameters such as transfer throttling, compression ratio, and Checksum verification.

      • Pause the migration job: In the Actions column, click Pause Migration Job to pause the migration.

  4. In the Migration Source ID/Name column for the target migration source, click the migration source ID to view migration details.

    The migration job list at the top of the migration details page displays the job's Status (such as Synchronizing), synchronization progress, and Target region. The Basic information section below displays fields such as Job ID, Job name, Job status, Creation time, Start time, End time, Job progress, Target region, Intermediate instance ID, Tags, and Resource group.

Error handling

If the Real-time Migration Status is Error, the migration job has failed. Troubleshoot the error and retry the job:

  1. In the Actions column, click Troubleshoot Errors and resolve the error based on the provided code and message. For more information, see SMC FAQ and troubleshooting.

  2. After resolving the error, click Retry Migration Job in the Actions column. The migration job resumes from where it left off.

    Important

    If the intermediate instance has been released, you must restart the migration. For instructions, see What do I do if the intermediate instance is accidentally released?.

Create an ENS instance from an ENS image

When the Real-time Migration Status changes to Completed, the migration has created an Alibaba Cloud ENS image.

Go to the Edge Node Service console and create an ENS instance from an ENS image, selecting the ENS image generated from this migration.

Clean up resources

Migrate to an image

During the migration, SMC creates a temporary pay-as-you-go intermediate instance named No_Delete_SMC_Transition_Instance in your destination Alibaba Cloud account to facilitate the migration. The migration result determines whether you need to manually release the instance:

  • Successful migration: SMC automatically releases the intermediate instance. No manual cleanup is required.

  • Migration error: The intermediate instance is not released and continues to incur charges. To avoid unnecessary charges, you can release the instance in one of the following ways:

    • If you no longer need the migration task, click the migration source ID. In the Actions column for the migration task, click Cancel Migration Job to delete the migration task and automatically clean up the intermediate instance.

    • Manually release the intermediate instance.

Migrate to a destination instance

During the migration, SMC creates a temporary pay-as-you-go intermediate disk named SMC_Temp_Disk and attaches it to the destination instance to facilitate the migration. The migration result determines whether you need to manually release the intermediate disk:

  • Successful migration: SMC automatically releases the intermediate disk. No manual cleanup is required.

  • Migration error: The intermediate disk is not released and continues to incur charges. To avoid unnecessary charges, you can release the disk in one of the following ways:

    • If you no longer need the migration task, click the migration source ID. In the Actions column for the migration task, click Cancel Migration Job to delete the migration task and automatically clean up the intermediate disk.

    • Manually release the intermediate disk.

Previous：Containerized migrationNext：Appendix