This document describes how to migrate the system and applications from a source server in your IDC or a cloud platform to CVM through the online migration in private network mode in the CVM console.
Compared with the public network mode, migration over the private network has a higher migration transfer speed, which can significantly improve the migration efficiency. Plus, it doesn't restrict the public network access capability of the source server, making the migration configuration more flexible.
QcloudCSMFullAccesspolicy with the sub-account.
SecretKeyin API Key Management.
Click here to obtain the compressed migration tool package.
Choose the appropriate migration mode according to the network environments of your source servers and destination CVMs.
Currently, the CVM console supports the online migration in the public and private network modes. The private network mode applies to three scenarios. Each migration mode or scenario has different network requirements for source servers and destination CVMs. If both source servers and destination CVMs can access the public network, you can use the default mode for migration. If source servers or destination CVMs cannot directly access the public network, you need to establish a connection between them through VPC Peering Connection, VPN Connections, Cloud Connect Network, or Direct Connect before using the private network mode for migration.
Before migration, you need to check the following configuration based on the actual conditions:
|Linux source server||
|Destination CVM (optional)||
- You can use tool commands such as
sudo ./go2tencentcloud_x64 --checkto automatically check the source server.
- By default, the go2tencentcloud migration tool automatically performs checks upon launch. To skip checks and perform forced migration, configure
truein the client.json file.
- For more information on the go2tencentcloud migration tool, see Compatibility and Tool Configuration Description.
go2tencentcloud.zipto the source server and run the following command to enter the corresponding directory.
go2tencentcloud.zipand enter the directory.
ii. Run the following commands in sequence to decompress `go2tencentcloud-linux.zip` and enter the directory.
3. (Optional) Exclude files and directories on the source server that do not need to be migrated. If there are files or directories on the Linux source server that do not need to be migrated, you can add them to the [rsync_excludes_linux.txt](https://intl.cloud.tencent.com/document/product/213/44340) file. 4. (Optiona) Set the network proxy. - If the migration is in [Private network migration mode: scenario 2](https://intl.cloud.tencent.com/document/product/213/44340), skip this step. - If the migration is in [private network migration mode: scenario 3](https://intl.cloud.tencent.com/document/product/213/44340), configure the IP address and port of the proxy network. - 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 you need to verify the network proxy, enter the username and password of the network proxy in `Client.Net.Proxy.User` and `Client.Net.Proxy.Password`. 5. Import the migration source. i. For example, on a 64-bit Linux source server, execute the following commands in sequence as the root user to run the tool.Note
The files in the
go2tencentclouddirectory will not be migrated. Do not place the files to be migrated in this directory.
chmod +x go2tencentcloud_x64
ii. Enter the
SecretKey of the account API access key obtained in Prerequisites and press Enter as shown below:
If the information in the following figure is displayed in the window of the migration tool, the migration source has been imported to the console successfully, and you can go to the console to view it:
You can log in to the CVM console and enter the online migration page to view the imported migration source, whose status is Online as shown below:
If "Import source server successfully" isn't displayed, the migration source failed to be imported, and you can view the log (which is the
logs/log file in the migration tool directory by default) for troubleshooting. Then, run the migration tool to import the migration source again.
6. Go to the online migration page in the CVM console to create a migration task. i. Log in to the [CVM console](https://console.cloud.tencent.com/cvm/csm/online?rid=1), go to the online migration page, and click **Create Migration Task** on the right of the desired migration source. ii. In the **Create Migration Task** pop-up window, configure the task as instructed in [Migration Task Configuration Description](https://intl.cloud.tencent.com/document/product/213/44338). For example, to migrate a Linux source server to the Shanghai region of Tencent Cloud in private network mode and generate the destination CVM image, you can configure the migration task as shown below: !(https://qcloudimg.tencent-cloud.cn/raw/63c9481797c861890a2ea9ca37c4f272.png) 7. Start the migration taskNote
After the migration source is imported successfully, don't close the migration tool in the instance until the migration task is completed; otherwise, the migration task can't be completed after the migration source becomes offline.
After creating a migration task, you can click the Migration Task tab to view the task as shown below: You can click Start/Retry on the right of the task to start it, click OK in the pop-up window, and the task status will become **Migrating** as shown below: 8. Wait for the migration task to end After the migration task status becomes **Successful**, the migration is completed successfully as shown below: !(https://qcloudimg.tencent-cloud.cn/raw/7beb11db18bd9913b44941dd05f8a4a4.png)Note
You can skip this step if your task is scheduled, which will automatically start running at the scheduled execution time.
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 end. The migration tool supports checkpoint restart for data transfer.