Operating systems supported by the online migration tool include but not limited to the following:
Linux
Windows
CentOS 5/6/7/8
Windows Server 2008
Windows Server 2012
Windows Server 2016
Windows Server 2019
Windows Server 2022
Ubuntu 10/12/14/16/18/20
Debian 7/8/9/10
SUSE 11/12/15
openSUSE 42
Amazon Linux AMI
Red Hat 5/6/7/8
Oracle Linux 5/6/7/8
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.zip
The migration zip for Linux system.
go2tencentcloud-windows.zip
The migration zip for Windows system.
readme.txt
Directory overview file.
release_notes.txt
Migration tool change log.
After go2tencentcloud-linux.zip is decompressed, it contains the following files:
File Name
Description
go2tencentcloud_x64
Executable program of the migration tool for the 64-bit Linux operating system.
go2tencentcloud_x32
Executable program of the migration tool for the 32-bit Linux operating system.
user.json
User information in the migration.
client.json
Configuration file of the migration tool.
rsync_excludes_linux.txt
rsync configuration file, which excludes files and directories that do not need to be migrated in the Linux system.
After go2tencentcloud-windows.zip is decompressed, it contains the following files:
File Name
Description
go2tencentcloud_x64.exe
Executable program of the migration tool for the 64-bit Windows operating system.
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.
Parameters in the user.json file
The user.json configuration file is described as below:
Parameter
Type
Required
Description
SecretId
String
Yes
Secret ID for your account to access APIs. For more information, see Access Key.
SecretKey
String
Yes
Secret key for your account to access APIs. For more information, see Access Key.
Parameters in the client.json file
The client.json configuration file is described as below:
Parameter
API Type
Required
Description
Client.Extra.IgnoreCheck
Bool
No
The default value is false. The default value is false. The migration tool automatically checks the source server environment upon startup by default. To skip the check, set this parameter to true.
Client.Extra.Daemon
Bool
No
The default value is false. If you need the migration tool to run in the background, set this parameter to true.
Client.Net.Proxy.Ip
String
No
The default value is empty. In the private network migration Scenario 3, the IP address of the network proxy needs to be configured.
Client.Net.Proxy.IPv6
Bool
No
It defaults to false. Set it to true if you want to transfer data via IPv6. Otherwise, the migration data will be transferred via IPv4.
Client.Net.Proxy.Port
String
No
The default value is empty. In the private network migration Scenario 3, the port of the network proxy needs to be configured.
Client.Net.Proxy.User
String
No
The default value is empty. In the private network migration Scenario 3, if your network proxy needs to be verified, configure the username of the network proxy.
Client.Net.Proxy.Password
String
No
The default value is empty. In the private network migration Scenario 3, if your network proxy needs to be verified, configure the password of the network proxy.
Note:
Except for the above parameters, other configuration items in the client.json file usually don't need to be entered.
rsync_excludes_linux.txt file description
This file is used to exclude files on the Linux source server or configuration files under specified directories that do not need to be migrated. By default, the rsync_excludes_linux.txt file already excludes the following directories and files. Do not delete or modify the existing configurations.
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:
Yes
No
Was this page helpful?