This topic describes the migration test items that are supported by the migration test feature of Server Migration Center (SMC) and provides suggestions on how to fix the abnormal migration test items.
Overview
After a migration test is performed, you can refer to this topic to check the test items of server migration or operating system migration and fix the detected issues based on the recommended solutions that are provided.
Test items of server migration
Test items of the source environment
The test items of the source environment include CPU Utilization, Memory Usage, and Firewall Status.
Linux
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
CPU Utilization | Warning | The CPU utilization exceeds 90%. This may affect the operation of the SMC client. | Disable the services or processes that are no longer used. |
Memory Usage | Warning | The memory usage exceeds 95%. This may affect the operation of the SMC client. | Disable the services or processes that are no longer used. |
File System Type | Warning | A file system type that is not supported is used. | The system automatically changes the file system type to the second, third, or fourth extended file system when the relevant partition is migrated. |
File System Inode Usage | Warning | The inode usage of the file system exceeds 99%. This may cause migration failures. | Delete the files that are no longer used to free up inodes. |
File System Space Usage | Warning | The storage usage of the file system exceeds 99%. This may cause migration failures. | Delete the files that are no longer used to release storage. |
Firewall Status | Warning | The firewall is enabled. In this case, networks may be disconnected. | Check the network status of the migration source. For more information, see the What public endpoints and ports does my source server need to access? section of the "FAQ" topic. |
Network Proxy Status | Warning | The proxy is enabled. In this case, networks may be disconnected. | Check the network status of the migration source. For more information, see the What public endpoints and ports does my source server need to access? section of the "FAQ" topic. |
initramfs File | Warning | The initramfs file does not exist in the | Recreate the initramfs file. |
vmlinuz File | Warning | The vmlinuz file does not exist in the | Recreate the vmlinuz file. |
Windows
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
PowerShell Version | Warning | The PowerShell version is earlier than PowerShell 3.0, and the source environment cannot be checked. | Install PowerShell 3.0 or later. Then, create another migration job to start a migration test and check the source environment again. |
CPU Utilization | Warning | The CPU utilization exceeds 90%. This may affect the operation of the SMC client. | Disable the services or processes that are no longer used. |
Memory Usage | Warning | The memory usage exceeds 95%. This may affect the operation of the SMC client. | Disable the services or processes that are no longer used. |
VSS Status | Warning | Volume Shadow Copy Service (VSS) is disabled, and VSS snapshots cannot be created. | Check and modify the VSS service status. |
VSS Minimum Storage Space | Warning | The available storage space of the volume is less than 300 MB, and VSS snapshots cannot be created. | Release the volume space based on your business requirements or save VSS snapshots to a volume with sufficient available storage space. |
VSS Storage Space Limit | Warning | An upper limit is set for the VSS storage space. If a large amount of data is written to a disk during the migration, the available storage space for VSS snapshots may be insufficient. | Cancel or increase the upper limit of the VSS storage space. |
VSS Available Storage Space | Warning | The storage usage of the volume is greater than 95%. If a large amount of data is written to a disk during the migration, the available storage space for VSS snapshots may be insufficient. | Release the volume space based on your business requirements or save VSS snapshots to a volume with sufficient available storage space. |
Antivirus Software | Warning | The antivirus software is running. In this case, exceptions may occur during the migration. | Disable or uninstall the antivirus software based on your business requirements. |
Network Proxy Status | Warning | The proxy is enabled. In this case, networks may be disconnected. | Check the status of the network proxy. For more information, see the What public endpoints and ports does my source server need to access? section of the "FAQ" topic. |
Firewall Status | Warning | The firewall is enabled. In this case, networks may be disconnected. | Check the status of the firewall. For more information, see the What public endpoints and ports does my source server need to access? section of the "FAQ" topic. |
Driver Registry Status | Warning | The driver registry is configured to disable drivers from being installed. In this case, the migrated instance may fail to be started. | |
Virtio Driver | Warning | The virtio driver is not installed. In this case, the migrated instance may fail to be started. | |
Xen Driver | Warning | The Xen driver remains in specific images. In this case, the migrated instance may fail to be started. | |
System File | Warning | The core system files are missing. In this case, the system may fail to run as expected. | Restore the system files based on your business requirements. |
Test items of the destination environment
The test items of the destination environment help you check whether the current Alibaba Cloud account meets the basic requirements for the migration, such as the account balance, permissions, and the environment for creating Elastic Compute Service (ECS) instances.
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
Prepare VPC | Critical | The virtual private cloud (VPC) failed to be created. | If the QuotaExceeded.Vpc:VPC quota exceeded error occurs, check whether the number of VPCs in the current region exceeds the quota. |
Prepare vSwitch | Critical | The vSwitch failed to be created. | |
Prepare Security Group | Critical | The security group failed to be created. | Troubleshoot the error by viewing the error details and referring to the CreateSecurityGroup topic. |
Create Intermediate Instance | Critical | The intermediate instance failed to be created. | Troubleshoot the error by viewing the error details and referring to the CreateInstance topic. |
Release Intermediate Instance | Critical | The intermediate instance failed to be released. | Check the status of the intermediate instance. |
Release Network Resource | Critical | The network resources failed to be released. | Check the status of network resources, such as VPCs, vSwitches, and security groups. |
Check Client Status | Critical | The SMC client does not report the status of the migration source for an extended period of time. The migration test report may be incomplete. | Check the status of the SMC client in the migration source. If the SMC client is stopped, delete the current migration job and start the SMC client again. Then, create another migration job with the migration test feature enabled and perform a migration test. |
Test items of data synchronization
The test items of data synchronization help assess the basic steps in data synchronization, such as network connectivity, snapshot creation, and data transmission.
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
Connectivity Check for Intermediate Instance | Critical | The connection to port 8080 of the intermediate instance failed. | Check the network status of the migration source and make sure that the migration source can access the public IP address and port 8080 of the intermediate instance. If you migrate the migration source over a VPC, the migration source must access the private IP address of the intermediate instance. |
Connectivity Check for Data Synchronization | Critical | The connection to port 8703 of the intermediate instance failed. | Check the network status of the migration source and make sure that the migration source can access the public IP address and port 8703 of the intermediate instance. If you migrate the migration source over a VPC, the migration source must access the private IP address of the intermediate instance. |
Disk Partition Initialization | Critical | The disk partition failed to be initialized. | Check whether the capacity of the destination disk is smaller than that of the source disk. |
Block Replication Key Obtaining | Warning | The key for block replication failed to be obtained. | |
Partition Snapshot Creation | Critical | Snapshots failed to be created for the partition. |
|
Block Replication Test | Critical | Partitions failed to be synchronized based on block replication. | |
File Replication Test | Critical | Partitions failed to be synchronized based on file replication. | |
Network Performance Test | Warning | The iperf test tool failed to be run. | Manually estimate the amount of time required for the migration and test the data transfer speed. For more information, see Estimate the time required for migration and test the data transfer speed. |
Test items of operating system migration
Backup of the source environment
During the backup process, the following operations are performed on an ECS instance: creating, rolling back, and deleting snapshots for basic disks.
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
Instance Status | Critical | The instance failed to be started. | Check the status of the instance. After you make sure that the instance can be started as expected, retry the migration test. |
Create Cloud Disk Snapshot | Critical | Disk snapshots failed to be created. | Check whether a snapshot is being created for the cloud disk. If yes, wait until the snapshot is created and then retry the migration test. |
Check Client Status | Critical | The SMC client does not report the status of the migration source for an extended period of time. The migration test report may be incomplete. | Check the status of the SMC client in the migration source. If the SMC client is stopped, restart the SMC client and retry the migration test. |
Roll Back Cloud Disk Snapshot | Critical | Disk snapshots failed to be rolled back. | Check whether the snapshot that is used to roll back the data of the cloud disk is manually deleted. If yes, retry the migration test and do not delete the backup snapshot during the migration test. |
Delete Snapshot | Critical | Disk snapshots failed to be deleted. |
Test items of the source environment
The test items of the source environment help you check whether the operating system of the migration source meets the basic requirements of migration tools, such as the system architecture and system version.
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
System Architecture | Critical | The current system architecture does not support migration. | Only operating systems that use the x86_64 or AArch64 architecture can be migrated. Run the For more information about the supported migration scenarios, see Migrate a Linux operating system. |
System Version | Critical | The current system version does not support migration. | Run the
For more information about the supported migration scenarios, see Migrate a Linux operating system. |
Test items before migration
The test items before migration help you check whether the operating system of the migration source meets the basic requirements for the migration. The test items vary based on whether the operating system migration is performed across system versions.
General test items
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
Unknown Error | Critical | An unknown error occurred during the migration test. | |
Installation Script Download | Critical | The installation script of the upgrade tool failed to be downloaded. |
|
Upgrade Tool Installation | Critical | The upgrade tool failed to be installed. |
|
Test items for the migration between operating systems of different versions
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
Available Space of /boot Directory | Critical | The available storage space of the /boot directory is insufficient. | Free up the storage space of the system disk to ensure that the available storage space of the |
Total System Memory | Critical | The total system memory does not reach the lower limit. | Change the instance type. The total memory size of an instance that uses the x86_64 architecture must be no less than 1.5 GiB, and the total memory size of an instance that uses the AArch64 architecture must be no less than 2 GiB. For more information, see Change instance types. |
System Memory or System Disk Space | Critical | The available system memory is insufficient or the available storage space of the system disk is insufficient. | Free up the system memory or storage space to ensure that the available system memory size is larger than 600 MiB and the available storage space of the system disk is larger than 4 GiB. |
YUM/DNF Repository Configurations | Critical | Duplicate repository IDs are defined in the configuration file of the YUM or DNF software repository. | The repository IDs in the repository configuration file of the |
Btrfs File System | Critical | The Btrfs file system is mounted or the Btrfs module is loaded in the system. | The destination system does not support the Btrfs file system. We recommend that you back up the data of the Btrfs partition and format the Btrfs file system to another mainstream file system format such as ext4 or XFS. If no Btrfs file system is mounted, uninstall the Btrfs module. For more information, see What do I do if the "Btrfs has been removed from Anolis8" error message appears? |
XFS File System | Critical | A discarded mount option for the XFS file system exists in the /etc/fstab file. | If the discarded mount options for the XFS file system exist in the /etc/fstab file and you do not manually modify the /etc/fstab file after the upgrade, the XFS file system cannot be mounted. Open the /etc/fstab file, find the rows in which the XFS file system is configured, and then delete the discarded mount options for the XFS file system or change the mount options to defaults in the fourth column. For more information, see What do I do if the "Deprecated XFS mount options present in FSTAB" error message appears? |
NFS File System | Critical | The Network File System (NFS) file system is mounted in the system. | Unmount the NFS file system and disable the NFS file system until the operating system migration is complete. After the operating system migration is complete, mount the NFS file system again. For more information, see What do I do if a "Use of NFS detected. Upgrade can't proceed" error occurs? |
OSSFS File System | Critical | The OSSFS file system is mounted in the system. | Unmount the OSSFS file system and disable the OSSFS file system until the operating system migration is complete. After the operating system migration is complete, mount the OSSFS file system again. For more information, see What do I do if a "Use of NFS detected. Upgrade can't proceed" error occurs? |
OpenSSH Configurations | Critical | The PermitRootLogin parameter is not specified. | You have not specified whether to allow SSH-based logons from root users in the OpenSSH configuration file. Open the |
OpenSSH Configurations | Critical | Encryption algorithms that are not secure or not recommended are used in the OpenSSH configurations. | Modify the Cipher configurations in the /etc/ssh/sshd_config file to remove the following encryption algorithms that are discarded: blowfish-cbc, cast128-cbc, arcfour, arcfour128, and arcfour256. For more information, see What do I do if I receive the "OpenSSH configured to use removed ciphers" error message? |
OpenSSH Configurations | Critical | A message authentication code that is not secure or not recommended is used in the OpenSSH configurations. | Modify the MAC configurations in the /etc/ssh/sshd_config file to remove the following message authentication code that is discarded: hmac-ripemd160. For more information, see What do I do if I receive the "OpenSSH configured to use removed ciphers" error message? |
Kernel Version | Critical | The kernel version of the migration source is not supported. | The current default startup kernel in the system is not of the latest version provided by Alibaba Cloud. Set the kernel of the latest version provided by Alibaba Cloud as the default startup kernel, restart the instance, and then perform the migration. For more information, see What do I do if the "Newest installed kernel not in use" error message appears? |
ENI Configurations | Critical | The elastic network interface (ENI) configurations of the migration source are not supported. | The ENIs in the current system are named eth0 and eth1. This ENI naming method is unstable and cannot ensure the reliability of ENI names after the upgrade. This may cause network connection issues after the upgrade. To continue with the upgrade, you must use another ENI naming method. For more information, see What do I do if the "Unsupported network configuration" error message appears? |
Python Version | Warning | Python 3 is the default version. | The destination system uses Python 3 as the main Python version, which is not compatible with earlier versions. Python 2 provides only limited support and software packages. |
glibc Version | Warning | The glibc version is significantly changed. | The destination system uses glibc 2.28 that applies to Anolis OS 8 or glibc 2.32 that applies to Alibaba Cloud Linux 3. These glibc versions do not support NSS-related modules or provide the libnss_nis.so or libnss_nisplus.so library. All NIS configurations are deleted from the |
Test items for the migration between operating systems of the same version
Migration test item | Anomaly severity | Anomaly description | Recommended solution |
System Disk Space | Critical | The available storage space of the system disk is insufficient. | Free up the storage space to ensure that the available storage space of the system disk is larger than 2 GiB. |
System Memory | Critical | The available system memory is insufficient. | Free up the system memory to ensure that the available system memory size is larger than 300 MiB. |
Total System Memory | Critical | The total system memory does not reach the lower limit. | Change the instance type to ensure that the total memory size of the instance is no less than 512 MiB. For more information, see Change instance types. |
System Memory or System Disk Space | Critical | The available system memory is insufficient or the available storage space of the system disk is insufficient. | Free up the system memory or storage space to ensure that the available system memory size is larger than 300 MiB and the available storage space of the system disk is larger than 2 GiB. For more information, see What do I do if the "To ensure the migration, this machine must have 2G free space on disk and 300MB RAM available" error message appears? |
Software Package Upgrade | Critical | An i686 software package that does not support migration exists. | The destination system does not provide i686 software packages, whereas i686 software packages are installed on the current instance. Check and uninstall the i686 RPM packages. For more information, see What do I do if the "Anolis OS does not provide i686 packages, please remove them before migration" error message appears? |
Software Package Upgrade | Critical | A GUI software package that does not support migration exists. | The destination system does not support GUI, whereas GUI-related software packages are installed on the current instance. Check and uninstall the GUI-related RPM packages. |