This document describes how to migrate systems and applications on source servers from your IDCs or other cloud platforms to Tencent Cloud through the online migration in the CVM console. The online migration meets the business requirements for enterprise cloudification, cross-cloud migration, cross-account or cross-region migration, and hybrid cloud deployment.
The source server can be a physical server, a virtual machine, or a cloud server on another cloud platform, such as AWS, Google Cloud Platform, VMware, Alibaba Cloud, or Huawei Cloud.
QcloudCSMFullAccesspolicy with the sub-account.
SecretKeyin API Key Management.
Click here to obtain the compressed migration tool package.
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.
2. (Optional) Exclude files and directories on the source server that do not need to be migrated.Note
The files in the
go2tencentclouddirectory will not be migrated. Do not place the files to be migrated in this directory.
If there are files or directories in the Linux source server that do not need to be migrated, you can add them to the rsync_excludes_linux.txt file.
3. 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.
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.Note
You can also configure the account API access key in the
user.jsonfile before migration.
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.
Go to the online migration page in the CVM console to create a migration task.
i. Log in to the CVM console, 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 parameters as instructed in Creating and starting migration task.
For example, to migrate a Linux source server to the Shanghai region of Tencent Cloud and generate the destination CVM image, you can configure the migration task as shown below:
Start the migration task
After creating a migration task, you can click the Migration Task tab to view the task as shown below: You can click Start/Restart 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:Note
You can skip this step if your task is scheduled, which will automatically start running at the scheduled execution time.
Wait for the migration task to end
After the migration task status becomes Successful, the migration is completed successfully as shown below:
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.