Overview

Online migration refers to migrating or synchronizing systems and applications on the source server or virtual machine from your IDCs or other cloud platforms to Tencent Cloud with no system downtime.
Tencent Cloud provides the migration tool go2tencentcloud. After you run the migration tool on the source server, the entire source server can be migrated to the destination Tencent Cloud CVM. With this migration tool, you do not need to prepare, upload, or import images. The source server is directly migrated onto the cloud, meeting business requirements for enterprise cloudification, cross-cloud migration, cross-account or cross-region migration, and hybrid cloud deployment.

Migration Tool

Supported migration modes

Default mode

If both your source server and destination CVM can access the public network, you can use the default migration mode.
In the current default 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.

Private network migration mode

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 Connection, Cloud Connect Network , or Direct Connect.

• Scenario 1: if your source server or destination CVM cannot access the public network, use a server (such as the gateway) that can access the public network 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 neither the source server nor the destination CVM to be able to 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.
  

Supported operating systems

Operating systems supported by the online migration tool include but are not limited to the following (32-bit or 64-bit):

Files in the compressed package

Note：

The configuration files cannot be deleted. You must store them under the same folder as the go2tencentcloud executable program.

• Description of parameters in the user.json file:

  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.
  Region	String	Yes	Region of the destination CVM. You only need to specify the region, not the availability zone. For more information on values, see the region list.
  InstanceId	String	Yes	Instance ID of the destination CVM. The ID format is ins-xxxxxxxx.
  DataDisks	Array	No	List of data disks to be migrated from the source server. Each entry represents one data disk, and up to 20 data disks are supported.
  DataDisks.Index	Integer	No	Serial number of the data disk. Value range: [1,20]. The value 1 indicates that this data disk will be migrated to the first data disk mounted on the destination CVM. Likewise, the value 2 indicates that this data disk will be migrated to the second data disk mounted on the destination CVM.
  DataDisks.Size	Integer	No	Size of the data disk on the source server. Unit: GB. Value range: [10,16000].
  DataDisks.MountPoint	String	No	Mount point of the data disk on the source server, for example, "/mnt/disk1".

  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"
  }  

  Note：

  You need to replace the parameter values with the actual values.

  For example, a Linux source server has one data disk, the mount point is /mnt/disk1, and the size of the data disk is 10 GB. To migrate this server to a CVM (with at least one data disk mounted) 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"
        }
    ]
  }  

  For example, 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 mounted) 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"
        }
    ]
  }  

  Note：

  You need to replace the parameter values with the actual values.

• Description of parameters in the client.json file:

  Parameter	Type	Required	Description
  Client.Net.Mode	Integer	Yes	Default value: 0. Valid values:0 (default mode)), 1 (private network migration mode: scenario 1), 2 (private network migration mode: scenario 2), 3 (private network migration mode: scenario 3). Enter a value based on your actual migration mode or scenario.
  Client.Net.Proxy.Ip	String	No	IP address of the network proxy. If you select private network migration mode: scenario 3, this parameter must be specified.
  Client.Net.Proxy.Port	Integer	No	Port of the network proxy. If you select private network migration mode: scenario 3, this parameter must be specified.
  Client.Net.Proxy.User	String	No	Username of the network proxy. If you select private network migration mode: scenario 3, and the network proxy needs to be authenticated, this parameter must be specified.
  Client.Net.Proxy.Password	String	No	Password of the network proxy. If you select private network migration mode: scenario 3, and the network proxy needs to be authenticated, this parameter must be specified.
  Client.Extra.IgnoreCheck	Bool	No	Default value: false. Upon launch, the migration tool automatically checks the environment of the source server. To skip this check, configure this parameter to true.
  Client.Rsync.BandwidthLimit	String	No	Bandwidth limit in KBytes/sec. The default value is empty, meaning there is no bandwidth limit during transfer.
  Client.Rsync.Checksum	Bool	No	Transfer checksum. If this parameter is configured to true, it can strengthen the transfer consistency check, but will increase the CPU load of the source server and slow down the transfer speed. The default value is false, meaning no check will be performed by default.

  Note:

  Except for the above parameters, other configuration items in the client.json file usually do not need to be specified.

• Description of the rsync_excludes_linux.txt file:
  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 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 of the data disk mounted on /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

Checking before the migration

Before migration, check the following items of the source server and destination CVM:

Note：

• You can use tool commands such as sudo ./go2tencentcloud_x64 --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.

Migration Directions

If you use go2tencentcloud 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. The migration tool supports checkpoint restart.

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.

Migration directions in default mode

1. In the user.json file, configure the destination CVM for the migration.
   Configure the required parameters based on description of parameters in the user.json file.
2. In the client.json file, configure the migration mode and other parameters.
   Configure Client.Net.Mode in the client.json file to 0, that is, select the default mode. If necessary, configure other parameters based on the description of parameters in the client.json file.
3. (Optional) Exclude files and directories on the source server that do not need to be migrated.
   If you need to exclude some files and directories that do not need to be migrated when migrating the Linux source server, append them to the rsync_excludes_linux.txt file.
4. Run the tool.
   For example, on a 64-bit Linux source server, execute the following command as the root user to run the tool.

   sudo ./go2tencentcloud_x64

   To configure the log file name and logging level when running the tool, execute the following command:

   sudo ./go2tencentcloud --log-file=my.log --log-level=3

   Please wait for the migration process to complete.
   If the migration in default mode succeeds, the console output is as follows:
   

Migration directions in private network migration mode

Scenario 1

1. Establish a connection between the source server and the destination CVM.
   Establish a connection between the source server and the destination CVM by using VPC peering connection, VPN connection, or CCN.
2. In the user.json file, configure the destination CVM for the migration.
   Configure the required parameters based on description of parameters in the user.json file.
3. In the client.json file, configure the migration mode and other parameters.
   Configure Client.Net.Mode in the client.json file to 1, that is, select the private network migration mode: scenario 1. If necessary, configure other parameters based on the description of parameters in the client.json file.
4. (Optional) Exclude files and directories on the source server that do not need to be migrated.
   If you need to exclude some files and directories that do not need to be migrated when migrating the Linux source server, append them to the rsync_excludes_linux.txt file.
5. Run the tool on a server (such as the gateway) that can access the public network.
   For example, on a server that can access the public network, execute the following command to run the tool for migration stage 1.

   sudo ./go2tencentcloud_x64

   If Stage 1 is finished and please run next stage at source machine is prompted, stage 1 is completed.
   
6. Run the tool on the source server.
   After step 5 (stage 1) is completed, copy the entire tool directory in stage 1 to the source server, and then run the tool for migration stage 2.
   Execute the following command to run the tool for migration stage 2.

   sudo ./go2tencentcloud_x64

   If Stage 2 is finished and please run next stage at gateway machine is prompted, stage 2 is completed.
   
7. Run the tool on a server (such as the gateway) that can access the public network.
   After step 6 (stage 2) is completed, copy the entire tool directory in stage 2 to the server in stage 1, and then run the tool for migration stage 3.
   Execute the following command to run the tool for migration stage 3.

   sudo ./go2tencentcloud_x64

   If Migrate successfully is prompted, the entire migration task has been completed.
   

Scenario 2

1. Establish a connection between the source server and the destination CVM.
   Establish a connection between the source server and the destination CVM by using VPC peering connection, VPN connection, or CCN.
2. In the user.json file, configure the destination CVM for the migration.
   Configure the required parameters based on description of parameters in the user.json file.
3. In the client.json file, configure the migration mode and other parameters.
   Configure Client.Net.Mode in the client.json file to 2, that is, select the private network migration mode: scenario 2. If necessary, configure other parameters based on the description of parameters in the client.json file.
4. (Optional) Exclude files and directories on the source server that do not need to be migrated.
   If you need to exclude some files and directories that do not need to be migrated when migrating the Linux source server, append them to the rsync_excludes_linux.txt file.
5. Run the tool.
   For example, on a 64-bit Linux source server, execute the following command as root to run the tool.

   sudo ./go2tencentcloud_x64

   Please wait for the migration process to complete.
   If the following appears on the console, the migration has been completed successfully.
   

Scenario 3

1. Establish a connection between the source server and the destination CVM.
   Establish a connection between the source server and the destination CVM by using VPC peering connection, VPN connection, or CCN.
2. In the user.json file, configure the destination CVM for the migration.
   Configure the required parameters based on description of parameters in the user.json file.
3. In the client.json file, configure the migration mode and other parameters.
   1. Configure Client.Net.Mode in the client.json file to 3, that is, select the private network migration mode: scenario 3.
   2. Configure Client.Net.Proxy.Ip and Client.Net.Proxy.Port in the client.json file to the IP address and port of the network proxy.
      If your network proxy needs to be authenticated, configure Client.Net.Proxy.User and Client.Net.Proxy.Password to the username and password of the network proxy. You may leave them in blank if authentication is not required. If necessary, you can configure other parameters based on the description of parameters in the client.json file.
4. (Optional) Exclude files and directories on the source server that do not need to be migrated.
   If you need to exclude some files and directories that do not need to be migrated when migrating the Linux source server, append them to the rsync_excludes_linux.txt file.
5. Run the tool.
   For example, on a 64-bit Linux source server, execute the following command as root to run the tool.

   sudo ./go2tencentcloud_x64

   Please wait for the migration process to complete.
   If the following appears on the console, the migration has been completed successfully.
   

Checking after the migration

1. If the migration fails, check the error information in log files (under the migration tool directory by default), operation guides, or About Service Migration for troubleshooting methods.
2. If the migration succeeds, check whether the destination CVM can be started normally, whether data on the destination CVM is consistent with that on the source server, whether the network is normal, and whether other system services run normally.
3. If you have any questions or the migration has an exception, see About Service Migration or contact us.