SMS Functions

Migration drills help you fully assess the feasibility and identify potential risks of a migration task beforehand. The system verifies if security group ports are set correctly, domains connect normally, and necessary permissions are available. If issues are identified, the system offers fixes to minimize risks and disruptions during migration. For more information, see Configuring the Target Server.

SMS allows you to resize disks and partitions based on the actual disk usage. For more information, see Resizing Disks and Partitions on Windows and Resizing Disks and Partitions on Linux.

SMS allows you to upload migration logs to a specified OBS bucket. This way, you can view migration logs at any time or quickly locate and analyze faults if any using these logs. For more information, see Uploading Migration Logs.

A migration template defines the migration settings for servers, such as the network type, network traffic control, continuous synchronization, and region and project settings. You can modify your migration templates at any time. For more information, see Managing a Migration Template.

A server template defines the environment settings for servers, such as VPC, subnet, and security group settings. You can modify your server templates at any time. For more information, see Managing a Server Template.

SMS supports continuous synchronization of incremental data after the initial full replication is complete. You can enable continuous synchronization when configuring a target server.

• If you do not enable continuous synchronization, after the initial full replication is complete, SMS will automatically launch the target server. To synchronize incremental data, you can click Sync in the Operation column.
• If you enable continuous synchronization, after the initial full replication is complete, SMS will periodically synchronize incremental data from the source server to the target server. To complete the entire migration, you need to manually launch the target server.

For more information, see Configuring the Target Server.

After the target servers are launched, if there are data changes on your source servers, you can manually initiate incremental synchronization. For more information, see Synchronizing Incremental Data.

A migration consumes a lot of traffic and bandwidth. To minimize the impact of migration on services, you can limit the migration traffic during specific periods. For more information, see Setting the Migration Rate.

Before launching a target server, you can clone the server for service testing, and then only launch the server after tests confirm there are no issues. For more information, see (Optional) Cloning a Target Server.