Overview

Cloning a Target Server

To verify whether your target server can run properly before launching it, you can clone it as a new ECS in the continuous synchronization stage for service pre-verification.

The cloned server must be in the same AZ as the target server but can be in a different VPC.

Launching a Target Server

To stop continuous synchronization of incremental data from the source server to the target server, you can manually launch the target server to complete the migration. Once the target server is launched, the system terminates continuous synchronization of incremental data.

To synchronize newly generated incremental data, you can click Sync in the Operation column.

Viewing Server Details

To review key metrics such as the migration rate, amount of migrated data, and migration progress, you can visit the server details page. This page also displays the source and target server information, migration status, and details of any errors that occurred.

The source and target server information is collected by SMS only for data migration. To learn what source server information is collected by SMS, see What Information Does SMS Collect About Source Servers?

Deleting the Target Server Configuration

To update the target server or migration settings, you can delete the target server configuration from the task. Then you can re-configure the target server.

After the target server configuration is deleted from a migration task, incremental data synchronization will no longer be possible. If you reset the target server and migrate data again, all data on the source server will be migrated again, overwriting the existing data on the target server.

Deleting a Server Clone

If the ECS cloned from the target server has been tested, you can delete the ECS to release resources.

After you delete the ECS on the SMS console, you can check whether the deletion is successful on the ECS console.