SecretId
and SecretKey
.QcloudCSMFullAccess
and QcloudCVMFullAccess
permissions in the CAM console.Linux source server | 1. Check and install Virtio. For more information, see Checking Virtio Drivers in Linux. 2. Run which rsync to check whether Rsync is installed. If not, install it as instructed in How do I install Rsync?.3. Check whether SELinux is enabled, If yes, disable it as instructed in How do I disable SELinux?. 4. After a migration request is made to the Tencent Cloud API, the API will use the current UNIX time to check the generated token. Make sure that the system time of your server is correct. |
Windows source server | 1. Check and install Virtio. For more information, see Checking or installing the Virtio driver. 2. (Optional) Check and install Cloudbase-Init (See Installing Cloudbase-Init on Windows). It’s recommended to install it on the source server before the migration. In this case, the network configuration and OS license activation are performed automatically after the migration. Otherwise you need to log in to the instance via VNC, and modify the network configuration manually on the destination server after migration. |
Destination CVM | Storage space: The cloud disks (including the system disk and data disks) of the destination CVM must offer sufficient storage space for saving data from the source server. Security group: Port 80, port 443 and port 3389 are opened. Bandwidth: Set the bandwidth cap on both the two ends to the highest possible value. During the process, the traffic consumed is approximately the amount of data migrated. Adjust the billing mode beforehand if necessary. Network: If the source or destination server only supports IPv6 but not IPv4, see Parameters in the client.json file. |
sudo ./go2tencentcloud_x64 --check
.client.json
file, set Client.Extra.IgnoreCheck
to true
.go2tencentcloud.zip
, and go to the corresponding directory.wget https://go2tencentcloud-1251783334.cos.ap-guangzhou.myqcloud.com/latest/go2tencentcloud.zip
unzip go2tencentcloud.zip
cd go2tencentcloud/go2tencentcloud-linux
go2tencentcloud
directory will not be migrated. Do not place the files to be migrated in this directory.chmod +x go2tencentcloud_x64
sudo ./go2tencentcloud_x64
SecretId
and SecretKey
of the account API access key obtained in Prerequisites and press Enter as shown below:
go2tencentcloud.zip
to the source server. Decompress the file to the go2tencentcloud
folder. Open go2tencentcloud-windows
, and the directory is shown as below.
go2tencentcloud_x64.exe
.go2tencentcloud_x64.exe
and run it as admin. Enter SecretId
and SecretKey
in the pop-up window.go2tencentcloud_x64.exe
.SecretId
and SecretKey
) in the pop-up window.
logs/log
file under the migration tool directory for troubleshooting.Item | Required | Description |
Destination region | Yes | Tencent Cloud region to which the source server is to be migrated. For more information on regions, see Regions and AZs. |
Task name | Yes | The migration task name. |
Task description | No | Migration task description. |
Destination type | Yes | Set the destination type for the source server to be migrated to Tencent Cloud. CVM image: Create a CVM image for the source server.
Image name: Name of the destination CVM image that will be generated for the migration source. If the name already exists, the migration task ID is appended to the name. CVM instance: Select a CVM instance in the destination region as the migration destination.
Destination instance: We recommend you use the same operating system for the source server and destination CVM. For example, to migrate a CentOS 7 source server, select a CentOS 7 CVM as the destination. |
Network mode | Yes | The network used for transferring data. Public network: Transfer over the public network. Private network: Transfer over the private network. For details, see Migrating via Private Network.
VPC: Create the relay instance in a VPC when migrating to a CVM image.
Subnet: Create the relay instance in a subnet when migrating to a CVM image. |
Migration method | Yes | For Linux instances: File-level migration: Higher compatibility and relatively slower transfer speed. Block-level migration: Faster transfer speed and relatively lower compatibility. |
| | Windows block-level migration: Block-level migration, with faster transfer speed and relatively lower compatibility. |
Configure incremental sync | No | You can customize the incremental sync duration to continuously sync the data. Not enable: The migration tool scans for and migrate the increments. Generally, it is implemented for once. Enable: You can select the incremental sync duration. The migration tool will continuously sync the data to Tencent Cloud. You can also manually stop the incremental sync in the task list. |
Scheduled execution time | No | Set the time when the migration task will be automatically started after creation. It can be as early as 10 minutes after the current time. |
Item | Required | Description |
Data rate (KB/s) | No | The upper limit of data rate during the migration (0 to 25600 KB/s). It’s set to 0 by default. This item is not available for migration to Windows. |
Checksum verification | No | When it is enabled, data consistency check is enhanced, but the transfer speed may be reduced. This item is not available for migration on Windows. |
do_not_delete_csm_instance
will be created under your account after the migration starts. Don't reinstall, shut down, or terminate the relay instance or reset its password. It will be automatically terminated by the system after the migration ends.
Was this page helpful?