tencent cloud

This document introduces how to use the migration tool go2tencentcloud to migrate the Linux-based CVM online.

Preparations

• You already have a Tencent Cloud account and a destination CVM.
• Stop applications on the source server to prevent existing applications from being affected by the migration.
• Click here to download the compressed migration tool package.
• You can create a key and obtain the SecretId and SecretKey in API Key Management.
• Check that both source servers and destination CVM meet the migration requirements. For example, the cloud disks of the destination CVM should have sufficient capacity to save data migrated from source servers.
• We recommend you back up your data in the following ways before migrating:
• Source server: You can use the source server snapshot feature or other methods to back up data.
• Destination CVM: You can create a snapshot as instructed in Creating Snapshots or use other methods to back up data.

Migration Toolkit

Files in the compressed package

After go2tencentcloud.zip is decompressed, it contains the following files:

After go2tencentcloud-linux.zip is decompressed, it contains the following files:

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:

You can refer to the following examples to modify the configuration file based on the actual business scenarios.

• Example 1: To migrate a Linux source server to a CVM located in Guangzhou, configure the user.json file as follows:

  {  
  "SecretId": "your secretId",
  "SecretKey": "your secretKey",  
  "Region": "ap-guangzhou",  
  "InstanceId": "your instance id"
  } 
  

• Example 2: A Linux source server has one data disk, of which the mount point is /mnt/disk1, and the size is 10 GB. To migrate this server to a CVM (with at least one data disk attached) located in the Guangzhou region, configure the user.json file as follows:

  {  
  "SecretId": "your secretId",
  "SecretKey": "your secretKey",  
  "Region": "ap-guangzhou",  
  "InstanceId": "your instance id",
  "DataDisks": [
   {
       "Index": 1,
       "Size": 10,
       "MountPoint": "/mnt/disk1"
   }
  ]
  }
  

• Example 3: A Linux source server has two data disks. The mount point for disk 1 is /mnt/disk1, and the size is 10 GB. The mount point for disk 2 is /mnt/disk2, and the size is 20GB. To migrate this server to a CVM (with at least two data disks attached) located in Guangzhou, with disk 1 and disk 2 of the source server to be migrated to the first and second data disks of the destination CVM respectively, configure the user.json file as follows:

  {  
  "SecretId": "your secretId",
  "SecretKey": "your secretKey",  
  "Region": "ap-guangzhou",  
  "InstanceId": "your instance id",
  "DataDisks": [
   {
       "Index": 1,
       "Size": 10,
       "MountPoint": "/mnt/disk1"
   },
   {
       "Index": 2,
       "Size": 20,
       "MountPoint": "/mnt/disk2"
   }
  ]
  }  
  

Parameters in the client.json file

The client.json configuration file is described as below:

If neither the source server or destination CVM can access the public network directly, you can establish a connection between them through VPC Peering Connection, VPN Connections, Cloud Connect Network, or Direct Connect and then migrate via the private network mode. Determine the appropriate migration mode according to the network environment of your source server and destination CVM.

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.

/dev/*
/sys/*
/proc/*
/var/cache/yum/*
/lost+found/*
/var/lib/lxcfs/*
/var/lib/docker-storage.btrfs/root/.local/share/gvfs-metadata/*

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:

/dev/*
/sys/*
/proc/*
/var/cache/yum/*
/lost+found/*
/var/lib/lxcfs/*
/var/lib/docker-storage.btrfs/root/.local/share/gvfs-metadata/*
/mnt/disk1/*

Parameters of the migration tool

Migration Directions

Data Backup

• Source server: You can use the source server snapshot feature or other methods to back up data.
• Destination CVM: You can create a snapshot as instructed in Creating Snapshots or use other methods to back up data.

Checking Before the Migration

Before migration, you need to check the source server and destination CVM separately as detailed below:

Note

• You can use tool commands such as ./go2tencentcloud_x64 --no-console --check to automatically check the source server.
• By default, the go2tencentcloud migration tool automatically performs checks upon launch. To skip checks and perform forced migration, configure Client.Extra.IgnoreCheck to true in the client.json file.

Starting migration

If you use go2tencentcloud supporting checkpoint restart provided by Tencent Cloud for migration, the migration process includes the following three stages. You can intuitively view the migration progress when the tool is running.

• Stage 1: The destination CVM enters the migration mode, and is ready for migration.
• Stage 2: The destination CVM is in the migration mode, and receives data migrated.
• Stage 3: The destination CVM exits the migration mode, and the migration completes.

Each stage will generate some subtasks to perform related operations, and some time-consuming subtasks may have maximum timeout periods by default. The time required for data transfer depends on the size of the data on the source server, network bandwidth, etc. Please wait for the migration process to complete.

Note

The destination CVM enters migration mode after the migration starts. Do not reinstall the system, shut down, terminate, or reset passwords of the destination CVM until the migration is completed and the destination CVM exits the migration mode.

Checking after the Migration

• If the migration fails, check the error information in log files (under the migration tool directory by default), operation guides, or FAQs about Service Migration for troubleshooting methods.
• If the migration is successful, check whether the target CVM starts up normally, whether data on the target CVM is consistent with that on the source server, and whether the network and other system services are normal.

If you have any questions or the migration has an exception, see FAQs about Service Migration or Contact Us.