Configuring the Target Server

• You have prepared the account, required permissions, source and target servers, and network environment. For details, see Preparations.
• You have installed and started the Agent on the source server, and the source server is displayed in the server list on the SMS console. The source server meets the following requirements:
  • It is Connected to SMS.
  • The migration is in the Migration Feasibility Check stage.
  • The migration is in the Pending target configuration status.

1. Log in to the management console.
2. Click Service List. Choose Migration > Server Migration Service.
3. In the navigation pane on the left, choose Servers.
4. In the server list, locate the source server to be migrated, and click Configure Target in the Migration Stage/Status column or choose More > Configure Target in the Operation column.
   Note

   If the source server is not displayed in the list, rectify the fault by referring to Why Wasn't My Source Server Added to the SMS Console After I Configured the Agent?

5. On the Configure Basic Settings page, configure parameters based on Table 1.

   Table 1 Basic parameter settings

   Area	Parameter	Sub-Parameter	Description
   Migration Template	Migration Template	-	Use a default template or create one by referring to Managing a Migration Template. After you choose a migration template, the system will populate Network Type, Migration Rate Limit, Migration Method, Enable Continuous Synchronization, Resize Disks and Partitions, Region, and Project based on the template.
   Network Settings	Network Type	Internet	An EIP must be bound to the target server. Public is the default value of Network Type.
   		Private	A Direct Connect connection, VPN connection, VPC peering connection, VPC subnet, or Cloud Connect connection must be provisioned. The private IP address of the target server will be used for migration.
   	IP Version	IPv4	IPv4 can be used for data migration.
   		IPv6	On a dual-stack network, IPv6 can be used for migration.
   	Migration Rate Limit	-	You can limit the migration rate based on the source bandwidth and service requirements. If you do not want to limit the migration rate, set this parameter to 0. Traffic limiting is unavailable if: The migration uses an IPv6 network. Traffic Control (TC) is missing from the source server.
   	Overrate Threshold (%)	-	You can regulate how much the migration rate can exceed the configured limit. If the migration rate exceeds the threshold multiple consecutive times, the migration task is automatically paused. For example, if the migration rate limit is set to 10 Mbit/s and the overrate threshold is set to 10%, the task is automatically paused when the migration rate exceeds 11 Mbit/s (110% of the limit) multiple times consecutively. CAUTION: This option is only available for Linux migration. It will not be available or applied if: The migration uses an IPv6 network. Traffic Control (TC) is missing from the source server.
   Migration Drill	-	-	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. After this function is enabled, the system automatically launches a migration drill before starting the full replication. The entire migration drill takes 5 to 15 minutes, and pay-per-use resources incur costs during this period. You can review the drill results in the task details. For details, see Checking the Migration Drill Status and Report.
   Migration Settings (Optional)	Migration Method	Linux block-level	Migration and synchronization are performed block by block. This method has high efficiency but poor compatibility.
   		Linux file-level	Migration and synchronization are performed file by file. This method has low efficiency but excellent compatibility.
   		Windows block-level	Migration and synchronization are performed block by block. This method is very efficient and is the only migration method for Windows servers.
   	Enable Continuous Synchronization	No	After the full replication, SMS will automatically launch the target server without synchronizing incremental data. To synchronize incremental data, click Sync in the Operation column.
   		Yes	After the full replication, SMS will periodically synchronize incremental data. To complete the migration, you need to manually launch the target server.
   	Resize Disks and Partitions	Disable	The disk and partition settings from the source server will be retained on the target server.
   		Enable	You can resize disks and partitions for the target server. For details, see Resizing Disks and Partitions on Windows and Resizing Disks and Partitions on Linux.
   	Start Target Upon Launch	No	After the migration is complete, the target server will automatically shut down.
   		Yes	The target server will be started after the migration is complete.
   	Enable Concurrency	Automatic	The SMS-Agent automatically configures the maximum number of migration processes allowed based on source server conditions.
   		Manual	You can specify the maximum number of processes the SMS-Agent can start concurrently for migration and synchronization tasks, respectively. This parameter is available for Linux file-level migrations. To learn how to configure it, see How Do I Set the Number of Concurrent Processes for Linux File-Level Migrations?
   Resource Limits (Optional)	CPU Limit	-	These options are only available for Linux migrations. For details, see How Do I Limit Resource Allocation for the Agent in a Linux Migration?
   	Memory Limit	-
   	Disk Throughput Limit	-
   Verify Data Consistency	If this option is enabled, the system will automatically verify data consistency after the full replication is complete. This is a quick verification, and only the file size and last modification time will be verified. You can modify the verification policy when you launch an incremental synchronization. Note that consistency verification cannot be performed for servers with Btrfs file systems. Enable Hash Verification: If this option is enabled, the system will generate and compare hash values for each file to be verified. Hash verification is recommended when individual files are large and important. Enabling this option will increase CPU and disk I/O overheads for the source server and extend the verification time. CAUTION: Hash values cannot be calculated for files in use, so these files will be skipped during the verification. Enabling this option requires you to specify the verification scope, and only files in the specified scope will be verified. Verification Scope Under Exclude paths, enter the paths you want to exclude from the verification. A maximum of 30 paths can be entered. Use commas (,) to separate the paths. For example, /root/data,/var. Leaving it empty will initiate a full verification. Under Include paths, enter the paths you want to verify. NOTICE: If the entered paths are incorrect or empty, 0 will be displayed for them in the verification results. The more data you need to verify, the longer the verification will take. It is wise to narrow the verification scope to only key paths. The following paths will be excluded from consistency verification by default: Linux: /bin, /boot, /dev, /home, /etc, /lib, /media, /proc, /sbin, /selinux, /sys, /usr, /var, /run, and /tmp Windows: top-level directories of partitions, for example, C:\ and O:\ If you want to verify some of the excluded paths, see Modifying the Default Excluded Paths.

6. Click Next: Configure Target in the lower right corner.
7. In the Basic Settings area, select the region you are migrating to.
8. In the Target Server area, choose whether to use an existing cloud server or create a new one as the target server. For details about the requirements on target servers, see How Do I Create a Target Server that Meets the SMS Requirements?
   • Use existing

     In the list of existing servers, select one that meets the specifications requirements displayed in the Recommended Target row. If no existing server meets the requirements, click Create ECS and purchase an ECS with the required specifications. The purchased ECS must meet the following requirements:

     • A target server running Windows must have at least 2 GB of memory.
     • A target server must have at least as many disks as the source server, and each disk on the target server must be at least the size recommended by the system.
     • The target server must run the same OS as the source server, or there will be a server name conflict.
     • The target server must have been configured with an EIP, VPN, or Direct Connect connection.
     • The security group of the target server must be correctly configured. It must be configured to allow access on the following ports:

       Windows: TCP ports 8899, 8900, and 22

       Linux: port 22 for a file-level migration and ports 8900 and 22 for a block-level migration

       For details, see How Do I Configure Security Group Rules for Target Servers?

   • Create new

     The system automatically presets the name, AZ, specifications, disk specifications, EIP, VPC, subnet, and security group for the target server. You can also click Expand and Modify to manually modify the server settings.

     • If you select Recommended for Server Template, the VPC, subnet, and security group will be automatically created. You can update the configurations as needed.
       Note

       • If Create new is selected for VPC, the system automatically creates a VPC for the target server based on the following rules:

         If the source server's IP address is 192.168.X.X, the system creates a VPC and a subnet that both belong to network range 192.168.0.0/16.

         If the source server's IP address is 172.16.X.X, the system creates a VPC and a subnet that both belong to network range 172.16.0.0/12.

         If the source server's IP address is 10.X.X.X, the system creates a VPC and a subnet that both belong to network range 10.0.0.0/8.

       • If Create new is selected for Security Group, the system automatically creates a security group for the target server and allows traffic to the target server over certain ports:

         Windows: ports 8899, 8900, and 22

         Linux: port 22 for file-level migration

         Linux: ports 8900 and 22 for block-level migration

       The server name, AZ, specifications, system disk, data disk and EIP in advanced settings are automatically configured. You can update the configurations as needed.

     • You can also choose your own server template. Then the VPC, subnet, security group, AZ, and disk settings will be preconfigured based on that template. You have the flexibility to adjust these preset settings as needed. For details about how to create a template, see Managing a Server Template.

9. Click Next: Confirm in the lower right corner.
10. (Optional) Click Save as Server Template. In the displayed Create Server Template dialog box, enter the template name and click OK to save the target configuration as a template.
    Note

    Save as Server Template is available only when you select Create new for Target Server.

11. After you confirm that the configuration is correct, click Save. In the displayed dialog box, read the migration conditions and click Yes.

    If you want to start the migration immediately, click Save and Start. In the displayed dialog box, read the migration conditions and click Yes.

    Note

    If Target Configuration and Ready show up in the Migration Stage/Status column, the target server has been configured.

1. On the Configure Migration page, on Configure Basic Settings tab, expand Migration Settings (Optional), enable Resize Disks and Partitions, and click Resize Disks and Partitions.
2. Click Resize Disk and adjust the size of each disk as required. After the adjustment is complete, you can check the overview of the disks to be migrated at the bottom of the window.
   • If the total partition size after resizing is larger than the disk size, you need to expand the disk capacity to fit the partition size.
   • If the total partition size after resizing is much smaller than the disk size, you can downsize the disk.

3. Click Next: Confirm. Confirm the configurations and click OK.
   Caution

   After you click OK, disk and partition resizing can no longer be disabled for this task. If you want to restore the original disk and partition settings, locate the source server and choose More > Delete in the Operation column. Then restart the Agent on the source server, and configure the target server again.

1. On the Configure Migration page, on Configure Basic Settings tab, expand Migration Settings (Optional), enable Resize Disks and Partitions, and click Resize Disks and Partitions.
2. Configure volume groups.
   • If the source server uses LVM, you can resize logical and physical volumes.
   • If the source server does not use LVM, skip this step.

3. Click Next: Configure Disks.
4. Click Resize Disk and adjust the size of each disk as required. After the adjustment is complete, you can check the overview of the disks to be migrated at the bottom of the window.
   • If the total partition size after resizing is larger than the disk size, you need to expand the disk capacity to fit the partition size.
   • If the total partition size after resizing is much smaller than the disk size, you can downsize the disk.

5. Click Next: Confirm. Confirm the configurations and click OK.
   Caution

   After you click OK, disk and partition resizing can no longer be disabled for this task. If you want to restore the original disk and partition settings, locate the source server and choose More > Delete in the Operation column. Then restart the Agent on the source server, and configure the target server again.

If Migration Drill is enabled when you configure a migration task, you can check the migration drill status and report.

1. In the server list, click the name of the source server to expand the migration task details.
2. On the Task Progress tab, check the status and progress of the migration drill.
3. In the upper part of the task details page, click View Report next to Drill Status. In the report displayed on the right, you can check the drill details, check items, and check results.