Before using Server Migration Center (SMC) to migrate a migration source to the platform, you need to first import the migration source information and connect it to your platform account via the migration tool Agent.

This topic describes the procedure for manually installing the migration tool Agent and importing the migration source.

Prerequisites

Make sure that you have completed the preparations as required. For details, see Preparations.

Procedure

You need to install the migration tool Agent on the migration source. The Agent can collect migration source information and import it to the platform.

Step 1: Import the migration source

Linux operating system

Windows operating system

Log in to the source server to be migrated.

Execute the following command to download the migration tool agent over the public network.

sudo wget -O smc-agent_Linux_amd64.tar.gz https://smc.tos-cn-beijing.volces.com/smc-agent_Linux_amd64.tar.gz

tip

You can also use any server connected to the public network to download the migration tool Agent, and then upload the Agent to the source server to be migrated via FTP or other tools. For more information, see Overview of local data upload.

Execute the following command to decompress and start the migration tool Agent, and import the source server information to the platform.

sudo tar -zxvf smc-agent_Linux_amd64.tar.gz && sudo ./smc_manage start -ak <your_access_key> -sk <your_secret_key>

warning

You need to run the migration tool Agent with administrator (root) privileges.

Replace <your_access_key> and <your_secret_key> with the actual API Access Key. For information about how to obtain an Access Key, see Managing an Access Key.

After the Agent starts running, it will generate a temporary key pair id_rsa (temporary private key) and id_rsa.pub (temporary public key) in the smc_tools directory.

The target instance or relay instance will use this temporary key pair during the migration process. This reduces the risk of leakage of your proprietary key and ensures your key security.

Do not delete this key pair. Otherwise, the migration will fail.

To resolve migration failure caused by accidental deletion of the key pair, you can execute the sudo ./smc_manage stop and sudo ./smc_manage start commands in the directory where the migration Agent is located to restart the Agent. This will allow you to re-import the migration source and generate a temporary key pair.

After a successful migration, use the source server login credentials (password or key pair) to log in to the target instance or custom image.

After decompression, you will obtain the following files:

File name	Description
Linux-version	The version information of the current package.
smc_agent	The binary file serving as the main file of the migration tool.
smc_manage	The binary file serving as the migration management tool.
agent_cfg.json	The JSON file used to record migration process information.
excludes.txt	The txt file. The paths of files and directories not to be migrated need to be written into this file.
user_cfg.json	The JSON file serving as the user information configuration file.
smc_tools	The folder containing temporary key pairs, block replication tools, detection scripts, and other content used by SMC during the migration process.

When the migration tool Agent starts as expected, it will upload migration source information to SMC.

tip

Do not close the migration tool Agent before the import process completes. Otherwise, the migration source will disconnect from the SMC console, and the import will fail.

You can execute the following command in the directory where the Agent is running to view the SourceId (migration source ID) and Agent running logs to troubleshoot migration issues.

tail -f smc.log

Sample output

Related operation

You can also perform the following operations on the migration Agent.

Operation	Description
sudo ./smc_manage start	Start the Agent.
sudo ./smc_manage stop	Stop the Agent.
Configure proxy server information	When the source server accesses the public network through a proxy, you need to configure proxy server information for the Agent as well.
Exclude files or directories that do not need to be migrated	You can add information about files that do not need to be migrated to prevent their data from being migrated to the platform.
Modify the Access Key	If the key you entered is incorrect or you need to change the key configuration, you can modify the Access Key.
Specify the project associated with the migration source	You can specify the project to which the imported migration source belongs to facilitate management.

tip

Since the Windows operating system only supports data migration by using block replication, excluding files or directories that do not need to be migrated is not supported.

Log in to the source server to be migrated.

You can download and run the migration tool Agent through PowerShell or graphical user interface.

warning

You can also use any server connected to the public network to download the migration tool Agent, and then upload the Agent to the source server to be migrated via FTP or other tools. For more information, see Overview of local data upload.

You need to run the migration tool as an administrator.

Antivirus software may prohibit the migration tool from running. Check the antivirus software configuration.

Once the Agent starts running, it will automatically generate the smc.txt file to record the Agent running logs, facilitating the troubleshooting of migration issues.

PowerShell

Execute the following command in PowerShell to download the migration tool Agent.

(New-Object -TypeName System.Net.WebClient).DownloadFile('https://smc.tos-cn-beijing.volces.com/smc-agent_Windows_x86_64.zip', 'C:\smc-agent_Windows_x86_64.zip')

tip

By default, it is downloaded to the C:\ directory.

Execute the following command in PowerShell to decompress the migration tool Agent package.

Use Unzip for decompression
PowerShell 5.0 or later
PowerShell 3.0 or later

cd C:\ ; unzip -o .\smc-agent_Windows_x86_64.zip ; C:\smc_agent -autostart=true -ak=<your_access_key> -sk=<your_secret_key>

tip

Replace <your_access_key> and <your_secret_key> with the actual API Access Key. For information about how to obtain an Access Key, see Obtaining Access Key.

After decompression, you will obtain the following files:

File name	Description
Windows-version.txt	The version information of the current Agent.
smc_agent.exe	The application file serving as the main file of the migration tool.
agent_cfg.json	The JSON file used to record migration process information.
user_cfg.json	The JSON file serving as the user information configuration file.
bin	The folder where binary files are stored.
sciter.dll	The library file required by the migration tool.
notice.txt	The compliance specifications for the migration tool.

The system will automatically open the migration Agent graphical user interface, fill in the Access Key provided in the command, and automatically import migration source information.

Graphical user interface

Log in to the source server.

Open the Agent download link in your browser to download the migration tool Agent.

tip

You can also use any server connected to the public network to download the migration tool Agent, and then upload the Agent to the source server to be migrated via FTP or other tools. For more information, see Overview of local data upload.

Decompress the migration tool package. For details about the files obtained after decompression, see Agent file information.

Right-click smc_agent.exe and click "Run as administrator" to run the migration tool Agent.

Enter the Access Key ID and Secret Access Key contained in the platform Access Key, and click the "Run" button to start the migration Agent.

tip

For information about how to obtain an Access Key, see Obtaining Access Key.

When the migration tool Agent starts as expected, it will upload migration source information to SMC.

tip

Do not close the migration tool Agent before the import process completes. Otherwise, the migration source will disconnect from the SMC console, and the import will fail.

You can view the Agent running log file smc.txt in the directory where the Agent is running to obtain the SourceId (migration source ID) and Agent running logs, which helps troubleshoot migration issues.

Related operation

You can also perform the following operations on the migration Agent.

Operation	Description
Configure proxy server information	When the source server accesses the public network through a proxy, you need to configure proxy server information for the Agent as well.
Specify the project associated with the migration source	You can specify the project to which the imported migration source belongs to facilitate management.

Step 2: Perform a precheck on the migration source

SMC will automatically perform a precheck on the migration source when you import the source, helping eliminate configurations that do not meet migration requirements.

View the precheck result. Learn more.

Based on the precheck result of the migration source, you can fix exceptions in each check item and perform the precheck on the migration source again.

After the migration source passes the precheck, you can create a migration task for it to migrate data from the source server to the platform. Learn more.

Related operation

You can also perform the following operations on the migration source.

Operation	Description
View migration source details	You can view basic information, attributes, and disk details of the migration source to confirm whether the target instance specified in the migration task can support the migration source data.
Modify basic information of the migration source	You can modify the migration source name to distinguish between different migration sources.
Delete the migration source	You can delete the migration source that is no longer used.

Subsequent operations

After the migration source is imported, we recommend that you create and start a migration task within 24 hours to prevent the migration tool Agent from going offline due to prolonged idleness of the migration source.