Currently, source server operating systems supported by the online migration tool include but are not limited to the following ones. (It is recommended that you pay attention to the earliest supported system versions.)
Linux
Windows
CentOS 5/6/7/8
Windows Server 2008R2
Windows Server 2012
Windows Server 2016
Windows Server 2019
Windows Server 2022
Windows Server 2025
Ubuntu 10/12/14/16/18/20/24
Debian 7/8/9/10/12
SUSE 11/12/15
openSUSE 42
Amazon Linux AMI
Red Hat 5/6/7/8/9
Oracle Linux 5/6/7/8/9
Supported Migration Modes
Public network migration mode
Private network migration mode
If both your source server and destination CVM can access the public network, you can use the public network migration mode.
In the current public network migration mode, the source server calls Tencent Cloud APIs through the Internet to initiate a migration request, and transfers data to the destination CVM to complete the migration. The public network migration scenario is shown below:
If your source server or destination CVM is located in a private network or Virtual Private Cloud (VPC), the source server cannot directly establish a connection with the destination CVM through the Internet. In this case, you can use the private network migration mode of the tool. You need to establish a connection between the source server and the destination CVM through VPC peering connection, VPN connections, Cloud Connect Network, or Direct Connect.
Scenario 1
: This scenario is applicable to the migration via Online Migration Tool. If your source server or the destination CVM cannot access the public network, you can first access the Tencent Cloud API via the internet through a server with public network access (such as a gateway) to initiate a migration request, and then transfer data and migrate to the destination CVM through the connection. This scenario does not require the source server and destination CVM can access the public network.
Scenario 2
: If your source server can access the public network, use the source server to call Tencent Cloud APIs through the Internet to initiate a migration request, and then transfer data to the destination CVM through the connection to complete the migration. This scenario requires the source server, but not the destination CVM, to be able to access the public network.
Scenario 3
: If your source server can access the public network through a proxy, use the source server to call Tencent Cloud APIs through the network proxy to initiate a migration request, and then transfer data to the destination CVM through the connection to complete the migration. This scenario requires neither the source server nor the destination CVM to be able to access the public network.
Files in the Compressed Package
After go2tencentcloud.zip is decompressed, it contains the following files:
File Name
Description
go2tencentcloud-linux
Migration tool directory for Linux systems.
go2tencentcloud-windows
Migration tool directory for Windows systems.
readme.txt
Directory overview file.
release_notes.txt
Migration tool change log.
Descriptions of files in the migration tool directory go2tencentcloud-linux are as follows:
File Name
Description
go2tencentcloud_x64
Executable program of the migration tool for x86 64-bit Linux systems.
go2tencentcloud_x32
Executable program of the migration tool for x86 32-bit Linux systems.
go2tencentcloud_arm64
Executable program of the migration tool for ARM 64-bit Linux systems.
tools
Directory for dependency files of the migration tool.
logs
Directory of migration tool logs.
user.json
User information during migration.
client.json
Configuration file of the migration tool during migration.
rsync_excludes_linux.txt
Configuration file, which excludes the files or directories of Linux source servers that do not need to be migrated.
Descriptions of files in the migration tool directory go2tencentcloud-windows:
File Name
Description
go2tencentcloud_x64.exe
Executable program of the migration tool for the 64-bit Windows operating system.
logs
Directory of migration tool logs.
user.json
User information in the migration.
client.json
Configuration file of the migration tool.
client.exe
Executable program of the migration tool for the Windows operating system.
Note:
The configuration files cannot be deleted. You must store them under the same folder as the go2tencentcloud executable program.
rsync_excludes_linux.txt file description
This file excludes files of Linux source servers that do not need to be migrated or configuration files under specified directories. The following directories and files have been excluded by default in this file. Do not delete or modify them.
To exclude other directories or files, append them to the rsync_excludes_linux.txt file. For example, to exclude all content on the data disk attached to /mnt/disk1, configure the rsync_excludes_linux.txt file as follows:
Check whether the source server meets the migration requirements. Only checks are performed, not involving migration.
-ignore-check
Skip the automatic check by the tool, and perform migration directly.
-log-file
Set the log file name. The default name is log.
-log-level
Set the log output level. Valid values: 1: ERROR level; 2: INFO level; 3: DEBUG level. Default value: 2.
-version
Print the tool version number.
-secret-id
Set SecretId of the key for accessing Tencent Cloud APIs with the target account.
-secret-key
Set SecretKey of the key for accessing Tencent Cloud APIs with the target account.
-region
Set the destination region for migration.
-mode
Set the network mode for data transfer. Valid values: 0: public network mode (data transfer over the public network); 2: private network mode for scenario 2 (data transfer over a private network); 3: private network mode for scenario 3 (data transfer over a private network). Default value: 0.
-console
Create a task automatically and perform migration by the tool. Manual task creation in the console is not needed. This option applies to batch migration scenarios.
-dest-type
Migration destination type, value range: Image (migrate to CVM image) and Instance (migrate to CVM instance), default value: Instance.
-instance-id
Set the destination CVM instance ID when migrating to a CVM instance.
-out-image-name
Set the image name when migrating to a CVM image.
-dest-vpc-id
Set the VPC ID that has connectivity with the source server's private network when migrating to a CVM image in private network mode.
-dest-subnet-id
Set the subnet ID that has connectivity with the source server's private network when migrating to a CVM image in private network mode.
-proxy-ip
Set the HTTP proxy IP address for the tool when the source server accesses the public network via an HTTP proxy.
-proxy-port
Set the HTTP proxy port for the tool when the source server accesses the public network via an HTTP proxy.
-proxy-user
Set the HTTP proxy username for the tool when the source server accesses the public network via an HTTP proxy.
-proxy-password
Set the HTTP proxy user password for the tool when the source server accesses the public network via an HTTP proxy.
-bandwidth-limit
Set the bandwidth limit in KB/s. The tool has no bandwidth limit by default. This option is only valid for migration from Linux source servers.
Migration Failure Handling Guide
After a server migration task is initiated in the console, the task may fail due to certain reasons. In case of a task failure, you can view the error code in the console and troubleshoot the issues as described below.
Error Code
Error Description
Guide
ERROR_REMOTE_INSTANCE_STATUS_NOT_VALID
The status of the current destination CVM instance does not allow migration.
Only instances in the Running and Shut Down statuses can be used as a destination CVM instance.
ERROR_SAME_INSTANCE
Migration is not allowed because the source server and the destination CVM instance are the same.
Change the destination CVM instance and initiate the migration task again.
ERROR_NO_IPV6
The IPv6 address of the destination CVM instance is missing.
The destination CVM instance has no IPv6 address. You can use an IPv4 address for migration.
ERROR_NO_PUBLIC_IP
The public network mode cannot be used for migration because the destination CVM instance has no public IP address.
The public network mode cannot be used for migration because the destination CVM instance has no public IP address. You can assign an elastic IP address (EIP) to the destination CVM instance or use the private network mode for migration.
ERROR_SAME_IP
Connection cannot be established in private network mode because the private IP address of the source server is the same as that of the destination CVM instance.
You can use the public network mode for migration or modify the private IP address of the destination CVM instance.
ERROR_OS_NOT_MATCH
Migration is not allowed between a Windows instance and a Linux instance.
Windows instances only support migration to other Windows instances, and Linux instances only support migration to other Linux instances. You can replace the destination CVM instance and perform migration again.
ERROR_INSTANCE_TYPE_NOT_SUPPORTED
The instance type of the destination CVM instance does not support using this instance as the migration destination.
Method 1: You can set the migration destination to an image. After obtaining a custom image, you can select the instance type you need and create an instance based on this custom image.
Method 2: You can first migrate the data to another instance of a supported type (such as Standard SA5), create a custom image after migration, and select the instance type you need to create an instance based on this custom image.
ERROR_SEC_GROUP_PORT_NOT_OPEN3
Security group port 80, 443, or 3389 of the destination CVM instance is not open.
You can open the corresponding security group port in the console.
ERROR_ADD_MORE_DISK
The number of data disks for the destination CVM instance is insufficient.
You can increase the number of data disks for the destination CVM instance to meet the migration requirements.
ERROR_SYSTEM_DISK_SIZE_NOT_ENOUGH
The system disk capacity for the destination CVM instance is insufficient.
