Overview

Configuring a Target Server

Before the migration, you need to configure a target server to receive the data migrated from the source server, including the system, application, and service data.

When you configure the target server, you need to specify the network, migration method, target server settings, disk and partition settings, disk encryption, and other migration settings.

You can configure the target server only when the following conditions are met:

• The source server is Connected to SMS.
• The migration is in the Migration Feasibility Check stage.
• The migration is in the Pending target configuration status.

Starting a Full Replication

A full replication copies all data from the source server to the target server with a single click.

• After the full replication starts, do not restart the source server or the SMS-Agent, or the migration will fail.
• During the full replication, the target server stays locked to prevent any operations. After the migration is complete, it will be automatically unlocked.

Synchronizing Incremental Data

After the full replication is complete, you can manually trigger incremental synchronization to transfer newly added or modified data from the source server to the target server.

You can synchronize the incremental data from a source server only when the migration status is Finished.

Setting a Migration Rate

To avoid impacting source server workloads during peak business hours, you can configure time-based bandwidth limits to restrict migration traffic.

A migration rate limit must be an integer from 0 to 1,000. The unit is Mbit/s.

• If you set the rate limit to 0 or leave it empty, the migration speed is unrestricted and will follow the actual network speed between the source and target servers.
• If you set the rate limit to V1, and the actual network speed between the source and target servers is V2, the migration rate will be limited to the lower of V1 and V2.

Uploading Migration Logs

If an exception occurs, uploading run logs to an OBS bucket can provide technical support with the context needed to help you quickly identify and resolve the issue.

• Only the Agent 25.1.0 or later can upload migration logs. To view the version of the Agent you installed on a source server, you can click the source server name in the server list on the SMS console. On the displayed page, click the Task Info tab. In the Source Info area, view the Agent version.
• If a proxy server is used for the migration, you need to select an OBS bucket in the same region as the proxy server, or the logs cannot be uploaded.

Deleting Resources

After the migration is complete, if incremental data synchronization is no longer needed, you can delete the cutover and synchronization snapshots generated during the process to stop further billing.

Once these snapshots are deleted, incremental data synchronization will no longer be possible. Confirm that no additional synchronizations are required before performing this action.

Deleting a Migration Task

After confirming that the migration is complete and the target server can run properly, you can delete the migration task and its configurations to release resources.

Before doing so, you are advised to delete migration-related resources to avoid unnecessary expenses.

• To migrate the source server again after you delete the migration task, you can restart the SMS-Agent on the server to re-register it.
• Deleting a server (or migration task) record will not delete the associated source or target server.