The Cloud Migration tool provides resumable breakpoints and file uploads. If the migration tool is interrupted or migration failure occurs, you can fix the issues and then resume the migration from where it was suspended.

For more information about how to troubleshoot issues that may occur while using the Cloud Migration tool, see this topic and Cloud Migration tool FAQ. If the problem persists, see Feedback and support.

Note
  • If you use V1.3.0 or later of the Cloud Migration tool to migrate and start the instance for the first time after migration, you must wait for the file system access permissions to be automatically recovered. For more information, see How can I check my system after migrating a Linux server? in Cloud Migration tool FAQ .
  • If you use V1.3.0 or earlier of the Cloud Migration tool to migrate a server of Windows Server 2008 or later, use the Reset File Permission tool to fix the default file system access permissions to ensure the availability of the instance and its components.

Error messages prompted on Windows servers

  • Why have I received an "IllegalTimestamp" error message on my Windows server?

    Check whether the system time is configured correctly.

  • Why have I received an "UnKnownError" error message on my Windows server?

    Check whether the platform parameter value is valid in the user_config.json configuration file.

  • Why have I received an "OperationDenied" error message on my Windows server?

    When an error message such as rsync: send_files failed to open "...": Permission denied (13) is prompted, the Cloud Migration tool is not permitted to access the specified directory or folder, and the rsync command fails. You can configure rsync_excludes_linux.txt or Rsync/etc/rsync_excludes_win.txt to filter the specified directory or folder and try again.

  • Why have I received an "InvalidAccountStatus.NotEnoughBalance" error message on my Windows server?

    The default billing method of intermediate instances is pay-as-you-go. If your account balance is insufficient, the migration cannot be completed. You must top up your account and try again.

  • Why have I received a "Forbidden.RAM" error message on my Windows server?

    The RAM user does not have sufficient permissions to call the operation.

    You must grant the AliyunECSFullAccess and AliyunVPCFullAccess permissions to the RAM user. For more information, see Implement access control by using RAM.

  • Why have I received an "InvalidImageName.Duplicated" error message on my Windows server?

    The specified value of image_name cannot be the same as that of an existing image.

  • Why have I received an "InvalidAccountStatus.SnapshotServiceUnavailable" error message on my Windows server?

    The snapshot service may not have been activated in your account. You can enable the snapshot service in the ECS console.

  • Why have I received a "Connect to Server Failed" error message on my Windows server?
    The Windows server is unable to connect to the intermediate instance. Perform the following steps to troubleshoot the error:
    1. View the migration log for details.
    2. Before you proceed, perform the following checks:
      • Check whether the status of the intermediate instance is normal.
      • Check whether the network service of the on-premises server is normal. Check whether TCP ports 80, 443, 8703, and 8080 have been enabled on your server. The Cloud Migration tool must have access permissions on these ports.
    3. After the error has been fixed, run the main program and try again.
  • Why have I received a "Do Rsync Disk x Failed" error message on my Windows server?
    The data transfer has been interrupted. Perform the following steps to troubleshoot the error:
    1. View the migration log for details. If return: 3072 or return: 7680 is displayed multiple times in the error log file, check whether database or container services such as Oracle, MySQL, Microsoft SQL Server, MongoDB, and Docker have been enabled on the source server. If the services are enabled, disable these services or exclude the related directories before you continue the migration.
    2. Before you proceed, perform the following checks:
      • Check whether the status of the intermediate instance is normal.
      • Check whether the network service of the on-premises server is normal. Check whether TCP ports 80, 443, 8703, and 8080 have been enabled on your server. The Cloud Migration tool must have access permissions on these ports.
    3. After the error has been fixed, run the main program and try again.

What do I do if Windows server migration stops at the "Prepare For Rsync Disk 0" stage?

Windows server migration stops at the "Prepare For Rsync Disk 0" stage, and lVssSnapshotul::VssSnapshotul GetSnapshotul Failed: 0x80042308 is displayed in the log file. In this scenario, perform the following steps:

  1. Enable the Volume Shadow Copy service.
    1. Log on to your on-premises server. Click Start, enter services.msc in the dialog box, and then press the Enter key.
    2. Find the Volume Shadow Copy service, right-click the service, and then choose Start from the shortcut menu.
  2. Uninstall the QEMU Guest Agent software.
    1. Log on to your on-premises server. Click Start, enter services.msc in the dialog box, and then press the Enter key.
    2. Check whether the QEMU Guest Agent VSS Provider service is running. If this service is not available, you can re-run the Cloud Migration tool.
    3. Find the uninstall script, possibly in the C:\Program Files (x86)\virtio\monitor\uninstall.bat directory, and run the script to uninstall the QEMU Guest Agent software.
  3. Re-run the Cloud Migration tool.

What do I do if the system prompts me to activate Windows after a Windows server migration?

Use Key Management Service (KMS) to activate Windows after you reinstall Windows KMS Client Key.
  1. Connect to the Windows instance.
  2. On the Microsoft Appendix A: KMS Client Setup Keys page, find the corresponding KMS client key. This section uses xxxx-xxxx-xxxx-xxxx-xxxx as an example.
  3. Open the Command Prompt as an administrator, and run the following commands:
    slmgr /upk
    slmgr /ipk xxxx-xxxx-xxxx-xxxx-xxxx
  4. Use KMS to activate Windows.

What do I do if the drive letters of data disks are missing or incorrect after a Windows server migration?

If the drive letters are missing, you can manually add the drive letters in the Disk Management utility.
  1. Open the Control Panel, click System and Security, click Administrative Tools, and then double-click Computer Management.
  2. In the Disk Management utility, find and right-click a data disk that has a missing drive letter, and then choose Change Drive Letters and Path... from the shortcut menu.
  3. Click Add and specify a drive letter.
If the drive letters are incorrect, you can change them in the Disk Management utility.
  1. Open the Control Panel, click System and Security, click Administrative Tools, and then double-click Computer Management.
  2. In the Disk Management utility, find and right-click a data disk that has an incorrect drive letter, and then choose Change Drive Letters and Path... from the shortcut menu.
  3. Click Change and select a drive letter from the drop-down list.

After a Windows server has been migrated, the file system access permissions are abnormal or some system menus are displayed in different languages during instance startup. What do I do?

You must wait for the file system access permissions to be automatically recovered. For more information, see How do I check my system after I migrate a Windows server? in Cloud Migration tool FAQ.

Error messages prompted on Linux servers

  • Why have I received a check rsync failed or rsync not found error message on my Linux server?

    Check whether the rsync component has been installed on the source server. For more information, see Migrate your server to Alibaba Cloud by using the Cloud Migration tool.

  • Why have I received a check virtio failed error message on my Linux server?

    Check whether the VirtIO driver has been installed on the source server.

  • Why have I received a check selinux failed error message on my Linux server?

    Check whether SELinux has been disabled for the source server.

    If not, you can run the setenforce 0 command to disable SELinux temporarily.

  • Why have I received a Do Grub Failed error message on my Linux server?

    If error messages such as Do Grub Failed is prompted, check whether the boot loader GRUB is installed on the source server.

    You can install GRUB v1.9 or later and try again. For more information, see Install GRUB v1.99 in a Linux server.

    Note You must use GRUB v2.02 or later for some operating systems such as Amazon Linux.

Why is there no data in the original data disk directory at instance startup after a Linux server migration?

Data disks are not automatically attached on startup after a Linux server with data disks is migrated. You can run the ls /dev/vd* command to view the data disk devices. You can attach the data disks manually as needed, and edit the configuration file in the /etc/fstab directory to enable the data disks to be attached upon instance startup.

Why am I unable to start an ECS instance that was created based on the custom image generated from a Linux server migration?

Use the following methods to troubleshoot the error:
  • Check the driver. Before you create an I/O optimized instance, ensure that the VirtIO driver has been installed on the source server. For more information, see Install virtio driver.
  • Check whether the configurations of GRUB installed on the source server are correct.
  • If your source server system is CentOS 5 or Debian 7, the GRUB version is earlier than v1.9, and the following output appears when you connect to the ECS instance by using the Management Terminal in the ECS console, install GRUB v1.9 or later and try again. For more information, see Install GRUB in a Linux server.

What do I do if the network service is abnormal when Others Linux instances are started?

Alibaba Cloud does not perform any configurations such as network or SSH configurations on ECS instances that were created from imported images of the Others Linux type. You can manually modify the network service configurations.

From March 31, 2018, the network configurations of images generated by the Cloud Migration tool have been changed. By default, IP addresses are allocated with the Dynamic Host Configuration Protocol (DHCP).