Migration drill items

Lists all SMC migration drill and rehearsal items with severity levels, descriptions, and recommended actions to resolve failures.

Migration drill items

Review the migration drill items in the drill report and follow recommended actions to resolve issues.

Source environment checks

SMC checks the migration source for metrics such as CPU utilization, memory utilization, and firewall status.

Linux

Migration drill item	Level	Description	Recommended action
CPU utilization	Warning	CPU utilization exceeds 90%. This may affect the performance of the SMC client.	Stop unnecessary services or processes as needed.
Memory utilization	Warning	Memory utilization exceeds 95%. This may affect the performance of the SMC client.	Stop unnecessary services or processes as needed.
File system type	Warning	The migration source has an unsupported file system type.	No manual action is required. The migration process automatically reformats the partition to ext2, ext3, or ext4.
File system inode utilization	Warning	The inode utilization of the file system exceeds 99%. This may cause the migration to fail.	Delete unnecessary files to free up inodes as needed.
File system space utilization	Warning/Critical	The space utilization of the file system exceeds 99%. This may cause the migration to fail.	Delete unnecessary files to free up space as needed.
Firewall status	Warning	The firewall is enabled, which may cause network connectivity failures.	Verify network connectivity on the migration source. What public IP addresses and ports must my server access for outbound traffic?
Network proxy status	Warning	A network proxy is enabled, which may cause network connectivity failures.	Verify network connectivity on the migration source. What public IP addresses and ports must my server access for outbound traffic?
initramfs file	Warning	The initramfs file is missing from the `/boot` directory. This may prevent the destination instance from starting after migration.	Rebuild the initramfs file.
vmlinuz file	Warning	The vmlinuz file is missing from the `/boot` directory. This may prevent the destination instance from starting after migration.	Rebuild the vmlinuz file.
Grub configuration file rebuild	Warning	Failed to rebuild the Grub configuration file by using grub-mkconfig.	Contact us.
Grub module	Warning/Critical	Required Grub modules are missing.	Install the required Grub modules or contact us.
Docker directory data	Warning	File replication does not support migrating data in the Docker directory.	If block replication is not enabled for the mount point of the Docker directory, the data in the Docker directory is automatically excluded during migration. Check the migration task parameters. If the current task does not support block replication, you can manually push the original Docker images to a container registry and then pull them after the migration is complete.

Windows

Migration drill item	Level	Description	Recommended action
PowerShell version	Warning	The PowerShell version is earlier than 3.0. SMC cannot perform the source environment checks.	To run the source environment checks again, install PowerShell 3.0 or later and recreate the task as needed.
CPU utilization	Warning	CPU utilization exceeds 90%. This may affect the performance of the SMC client.	Stop unnecessary services or processes as needed.
Memory utilization	Warning	Memory utilization exceeds 95%. This may affect the performance of the SMC client.	Stop unnecessary services or processes as needed.
VSS service status	Warning	The VSS service is disabled, which prevents VSS snapshot creation.	Check and change the status of the VSS service.
VSS minimum storage space	Warning	The volume has less than 300 MB of available space, which prevents VSS snapshot creation.	Free up space on the volume or configure the storage location for VSS snapshots to a volume with sufficient space.
VSS usable space limit	Warning	A storage space limit is set for VSS snapshots. If a large amount of data is written to the disk during migration, the storage space for VSS snapshots may be insufficient.	Remove or increase the VSS storage space limit as needed.
VSS usable storage space	Warning	The available space on the volume is less than 5%. If a large amount of data is written to the disk during migration, the storage space for VSS snapshots may be insufficient.	Free up space on the volume or configure the storage location for VSS snapshots to a volume with sufficient space.
Antivirus software	Warning	Antivirus software is running, which may cause migration issues.	Disable or uninstall the antivirus software as needed.
Network proxy status	Warning	A network proxy is enabled, which may cause network connectivity failures.	Check the network proxy status. What public IP addresses and ports must my server access for outbound traffic?
Firewall status	Warning	The firewall is enabled, which may cause network connectivity failures.	Check the firewall status. What public IP addresses and ports must my server access for outbound traffic?
Driver registry status	Warning	The registry is configured to block driver installation, which may prevent the destination instance from starting after migration.	Allow driver installation.
Virtio driver	Warning	The Virtio driver is not installed. This may prevent the destination instance from starting after migration.	Install VirtIO Driver. Important This operation may prevent the instance from starting after installation. Back up your data before you proceed. If you cannot back up your data, do not perform this operation.
Xen driver	Warning	Residual Xen drivers exist, which may prevent the destination instance from starting after migration.	Disable Xen Driver. Important This operation may prevent the instance from starting after the change. Back up your data before you proceed. If you cannot back up your data, do not perform this operation.
System files	Warning	Critical system files are missing, which may affect system operations.	Restore the system files as needed.

Destination environment checks

These checks verify that your Alibaba Cloud account meets migration requirements, including account balance, permissions, and the ECS instance creation environment.

Migrate to an ECS image

Migration drill item	Level	Description	Recommended action
Prepare VPC	Critical	Failed to create a VPC.	Contact us. If Error Details shows QuotaExceeded.Vpc:VPC quota exceeded., check whether the number of VPCs in the current region exceeds the quota.
Prepare vSwitch	Critical	Failed to create a vSwitch.	Contact us.
Prepare security group	Critical	Failed to create a security group.	Check Error Details and the CreateSecurityGroup API documentation.
Create transit instance	Critical	Failed to create the transit instance.	Check Error Details and the CreateInstance API documentation.
Release transit instance	Critical	Failed to release the transit instance.	Check the status of the transit instance.
Release network resources	Critical	Failed to release network resources.	Check the status of the network resources, including the VPC, vSwitch, and security group.
Check client status	Critical	The SMC client on the migration source has not reported its status for a long time. The current drill report may be incomplete.	Check the running status of the SMC client on the migration source. If the client has stopped, delete the current migration task, restart the client, and then create a new migration task with the Migration Drill option enabled to rerun the drill.

Migrate to an ECS instance

Migration drill item	Level	Description	Recommended action
Backup snapshot	Critical	Failed to create a backup snapshot.	Check if a snapshot creation is in progress for the destination instance's disk. If a snapshot is being created, wait until the process is complete and then click Retry Drill on the task list page.
Create security group	Critical	Failed to create the security group.	Check Error Details and CreateSecurityGroup.
Join security group	Critical	Failed to add the instance to the security group.	Check whether the destination instance can be added to the security group.
Replace system disk with transit image	Critical	Failed to replace the system disk with the transit image.	Check whether the operating system of the destination instance can be changed.
Create and attach disk	Critical	Failed to create and attach the disk.	Check whether your account balance is at least CNY 100. If your account balance meets the requirement, see the Error Details and Create a data disk.
Check client status	Critical	The SMC client on the migration source has not reported its status for a long time. The current drill report may be incomplete.	See Manage SMC Client to check the running status of the SMC client on the migration source. If the client has stopped, restart the SMC client and then click Retry Drill on the task list page.
Detach and delete disk	Critical	Failed to detach and delete the disk.	Check whether the disk can be detached from the destination instance.
Roll back destination instance	Critical	Failed to roll back the destination instance.	Check if the destination instance supports OS changes and disk rollbacks.
Delete security group	Critical	Failed to delete the security group.	Check Error Details and DeleteSecurityGroup.

Data sync tests

These tests verify the basic migration workflow, including network connectivity, snapshot creation, and data sync.

Migration drill item	Level	Description	Recommended action
Network connectivity check (transit service)	Critical	Failed to connect to the transit service port (8080) of the transit instance.	Verify that the migration source can access port 8080 on the transit instance's public IP address. For VPC-based internal network migration, verify access to the private IP address. Error S11: A network connection error occurs in the transit service of the destination instance.
Network connectivity check (data sync)	Critical	Failed to connect to the data sync port (8703) of the transit instance.	Verify that the migration source can access port 8703 on the transit instance's public IP address. For VPC-based internal network migration, verify access to the private IP address.
Initialize disk partition	Critical	Failed to initialize the disk partition.	Error S4: Failed to initialize the destination disk partition.
Get block replication transfer key	Warning	Failed to obtain the block replication transfer key.	Error S12: Failed to obtain the data sync key.
Sync disk partition header	Critical	Failed to sync the disk partition header.	Error S9: Failed to sync data in the disk partition header.
Create partition snapshot	Critical	Failed to create the partition snapshot.	Error S6: Failed to create a snapshot for the disk partition.
Block replication test	Critical	Failed to sync the partition with block replication.	Error S3: Failed to sync data of the disk partition.
File replication test	Critical	Failed to sync the partition with file replication.	Error S10: Failed to test file data sync for the disk partition.
Network performance test	Warning	Failed to run the lperf test tool.	Manually estimate migration time and test transfer speed. Estimate Migration Time and Test Transfer Speed.
Disk I/O performance test	Warning	Failed to run the disk I/O test tool.	Contact us.

Migration rehearsal items

Review rehearsal items in the migration rehearsal report and follow recommended actions to resolve issues.

Source environment backup

The backup process for an ECS instance involves creating, rolling back, and deleting snapshots of standard cloud disks.

Rehearsal item	Level	Description	Recommended action
Instance status	Critical	The instance fails to start.	Check the instance status. Ensure the instance starts properly, and then retry the rehearsal.
Create cloud disk snapshot	Critical	Failed to create a cloud disk snapshot.	Check if a snapshot is being created for the current cloud disk. If so, wait for the snapshot creation to complete, and then retry the rehearsal.
Check client status	Critical	The SMC client on the migration source has not reported its status for an extended period. The current rehearsal report may be incomplete.	Check the running status of the SMC client on the migration source. If it has stopped, restart the client and then retry the rehearsal.
Roll back cloud disk snapshot	Critical	Failed to roll back the cloud disk snapshot.	Check if the snapshot used for the rollback was manually deleted. If so, retry the rehearsal without deleting backup snapshots.
Delete snapshot	Critical	Failed to delete the snapshot.	Contact us.

Source environment check

This check verifies that the source environment meets migration tool requirements, such as system architecture and OS version.

Rehearsal item

Level

Description

Recommended action

System architecture

Critical

The current system architecture is not supported for migration.

Migration is supported only for the x86_64 and aarch64 architectures.

Run the uname -m command to check the current system architecture.

Operating system migration (Linux).

Operating system version

Critical

Migration is not supported for the current operating system version.

Run the

cat /etc/os-release command to check the current operating system version.

Operating system migration (Linux).

Pre-migration check

These checks verify that the source environment meets migration requirements. The rehearsal items differ for same-version and cross-version migrations.

General

Rehearsal item	Level	Description	Recommended action
Unknown error	Critical	An unknown error occurred during the migration rehearsal.	Contact us.
Installation script download	Critical	Failed to download the upgrade tool installation script.	Verify that the wget tool is working correctly. Run the following command to check whether the ECS instance can access the VPC network endpoint. For Alibaba Cloud Linux: `curl http://mirrors.cloud.aliyuncs.com/alinux/migration/` For Anolis: `curl http://mirrors.cloud.aliyuncs.com/anolis/migration/` Check whether a DNS or proxy configuration is preventing access to the YUM repository. If the issue persists, contact us.
Upgrade tool installation	Critical	Failed to install the upgrade tool.	Check if the YUM repository is accessible: `yum repolist` Check whether a DNS or proxy configuration is preventing access to the YUM repository. If the issue persists, contact us.

Cross-version migration

Rehearsal item	Level	Description	Recommended action
Available space in the /boot directory	Critical	Insufficient space in the /boot directory.	Clean up the system disk to ensure the `/boot` partition has more than 100 MiB of available space. Troubleshooting "Not enough space on /boot" errors.
Total system memory	Critical	The total system memory does not meet the minimum requirement.	Change the instance type as needed. For x86_64, total memory must be at least 1.5 GiB. For aarch64, at least 2 GiB. Change an instance type.
System memory or system disk space	Critical	Insufficient available system memory or system disk space.	Ensure that available system memory is greater than 600 MiB and available system disk space is greater than 4 GiB.
YUM/DNF repository configuration	Critical	A repo ID is defined multiple times in the YUM/DNF package repository configuration file.	In a repo configuration file in the `/etc/yum.repos.d/` directory, the `repo id` enclosed in square brackets (`[]`) is used to distinguish different package repositories and must have a unique name. Modify the duplicate package repository identifiers in the repo configuration files in the `/etc/yum.repos.d/` directory to ensure that each identifier is unique. the "A YUM/DNF repository defined multiple times" error.
Btrfs file system	Critical	A Btrfs file system is mounted on the system, or the `btrfs` module is loaded.	The target operating system no longer supports the Btrfs file system. Back up data from the Btrfs partition and reformat it to a mainstream file system, such as EXT4 or XFS. If no Btrfs file system is mounted, unload the `btrfs` module. Troubleshooting "Btrfs has been removed" errors.
XFS file system	Critical	The `/etc/fstab` file contains deprecated XFS mount options.	The system cannot mount an XFS file system after the upgrade if `/etc/fstab` contains deprecated mount options. To fix this, open the `/etc/fstab` file, locate the line that configures the XFS file system, and remove the deprecated mount options from the fourth column or change them to defaults. Troubleshooting "Deprecated XFS mount options present in FSTAB" errors.
NFS file system	Critical	An NFS file system is mounted on the system.	Unmount the NFS file system and temporarily disable NFS before the operating system migration. After the migration is complete, remount the NFS file system. For more information, see Troubleshooting "Use of NFS/CIFS detected. Upgrade can't proceed" errors.
OSSFS file system	Critical	An OSSFS file system is mounted on the system.	Unmount the OSSFS file system and temporarily disable OSSFS before the operating system migration. After the migration is complete, remount the OSSFS file system. Troubleshooting "Use of OSSFS detected" errors.
OpenSSH configuration	Critical	The `PermitRootLogin` configuration is missing.	The OpenSSH configuration file does not explicitly set the `PermitRootLogin` option. Open the `/etc/ssh/sshd_config` file and set `PermitRootLogin` to either `yes` or `no`. Troubleshooting "Possible problems with remote login using root account" errors.
OpenSSH configuration	Critical	The OpenSSH configuration uses insecure or deprecated cryptographic algorithms.	Modify the `Cipher` configuration in the `/etc/ssh/sshd_config` file to remove the following deprecated algorithms: `blowfish-cbc`, `cast128-cbc`, `arcfour`, `arcfour128`, and `arcfour256`. Troubleshooting "OpenSSH configured to use removed ciphers" errors.
OpenSSH configuration	Critical	The OpenSSH configuration uses insecure or deprecated message authentication codes.	Modify the `MACs` configuration in the `/etc/ssh/sshd_config` file to remove the deprecated `hmac-ripemd160` code. Troubleshooting "OpenSSH configured to use removed ciphers" errors.
Kernel version	Critical	The kernel version does not support migration.	The system is not running the latest installed official kernel. Before you migrate, restart the system and boot into the latest installed official kernel. Then, retry the migration. Troubleshooting "Newest installed kernel not in use" errors.
Network interface configuration	Critical	The network interface configuration is not supported for migration.	The system uses an unstable network interface naming scheme, such as `eth0` or `eth1`. This naming method is not reliable after an upgrade and may cause network connectivity issues. Change the naming scheme to proceed with the upgrade. Troubleshooting "Unsupported network configuration" errors.
Python version	Warning	Python 3 is the default version.	On the target system, Python 3 is the primary Python interpreter. This version is not backward-compatible, and Python 2 has limited support with a smaller set of available packages.
glibc version	Warning	Important changes to the glibc version.	The underlying GLIBC library version on the target system is 2.28 (Anolis OS 8) or 2.32 (Alibaba Cloud Linux 3). This version no longer supports nss-related modules and does not provide `libnss_nis.so` or `libnss_nisplus.so`. All nis-related configurations have been removed from `/etc/nsswitch.conf`. The System Security Services Daemon (sssd) provides a fast caching mechanism that improves the performance of resolving user and group information. The `/etc/nsswitch.conf` file is now configured to use sssd preferences for `passwd` and `group` lookups. All code that depends on or uses nis modules must be refactored. You can use tirpc as an alternative.

Same-version migration

Rehearsal item	Level	Description	Recommended action
System disk space	Critical	Insufficient available system disk space.	Ensure the available system disk space is greater than 2 GiB.
System memory	Critical	Insufficient available system memory.	Ensure the available system memory is greater than 300 MiB.
Total system memory	Critical	The total system memory does not meet the minimum requirement.	Change the instance type as needed. The instance must have at least 512 MiB of total memory. Change an instance type.
System memory or system disk space	Critical	Insufficient available system memory or system disk space.	Ensure that available system memory is greater than 300 MiB and available system disk space is greater than 2 GiB.
Package upgrade	Critical	Unsupported i686 packages exist.	The target system does not provide i686 packages. Manually uninstall any i686 RPM packages from your system. Troubleshooting "Anolis OS does not provide i686 packages, please remove them before migration" errors.
Package upgrade	Critical	Unsupported GUI packages exist.	The target system does not support a graphical user interface (GUI). Manually uninstall any GUI-related RPM packages from your system. Troubleshooting "It seems that your system install a GUI module" errors.