Configuring the Target Server

Scenarios

Before starting the migration, you need to configure the target server. The target server is used to receive data from the source server. You can clone the target server for service testing, and launch the target server after you verify that your services can run properly on the target server.

Prerequisites

The migration task is in the Ready status.

Procedure

1. Log in to the SMS console.
2. In the navigation pane on the left, choose Servers.
   Figure 1 Server list
   

3. In the server list, locate the source server to be migrated and click Configure Target in the Migration Stage/Status column.
   You can also choose More > Configure Target in the Operation column.

   

   If you do not find your source server, check whether you have logged in to the account you are migrating to.

   

4. On the Configure Basic Settings page, configure parameters by referring to Table 1.

   Table 1 Basic parameter settings

   Parameter	Option	Description
   Migration Template	N/A	After you select a migration template, the system populates Network, Migration Rate Limit, Migration Method, Continuous Synchronization, Partition Resizing, Region, and Project based on the template. You can choose the default template created by the system or any one you created. To learn how to create a migration template, see Creating a Migration Template.
   Network Type	Public	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.
   Migration Rate Limit	-	You can configure the rate limiting based on the source bandwidth and service requirements. If you do not want to limit the migration rate, set this parameter to 0. NOTE: For a Linux migration, traffic limiting is done with Traffic Control (TC). If TC is not installed on the source server, the migration rate limit you configured here will not be applied during the migration. Some Linux distributions do not support traffic limiting. For example, CentOS 8 and other CentOS 8-based distributions do not come with the TC module preinstalled.
   CPU Limit	N/A	These options are only available for Linux migrations. For details, see How Do I Set Resource Limits for SMS-Agent During a Linux Server Migration?
   Memory Limit	-
   Disk Throughput Limit	-
   Migration Method	Linux block-level	Migration and synchronization are performed by block. This method is efficient but the compatibility is poor.
   	Linux file-level	Migration and synchronization are performed by file. This method is inefficient, but the compatibility is excellent.
   	Windows block-level	Migration and synchronization are performed by block. This method is very efficient and is the only migration method available for Windows servers.
   IP Address Version	IPv4	IPv4 can be used for data migration.
   	IPv6	On a dual-stack network, IPv6 can be used for migration. For details about the preparations and precautions for migration over IPv6, see Migrating Servers over an IPv6 Network.
   Continuous Synchronization	No	After the full replication is complete, SMS will automatically launch the target server without synchronizing incremental data. To synchronize incremental data, you will need to click Sync in the Operation column.
   	Yes	After the full replication is complete, the migration will enter the continuous synchronization stage. During this stage, incremental data will be periodically synchronized from the source server to the target server, and you will be unable to use the target server since it has not been launched yet. To finish this stage, you will need to click Launch Target in the Operation column.
   Partition Resizing	No	The disk and partition settings from the source server will be retained on the target server.
   	Yes	You can resize the disks and partitions on the target server. For details, see Resizing disks and partitions.
   Start Target Upon Launch	No	The target server will be stopped after the migration is complete.
   	Yes	The target server will be started after the migration is complete.
   Measure Network Performance	No	Network performance will not be measured.
   	Yes	Before the full migration starts, the packet loss rate, network jitter, network latency, bandwidth, memory usage, and CPU usage will be measured. For details, see How Do I Measure the Network Performance Before the Migration?
   Enable Concurrency	No	By default, one process is used for migration and synchronization.
   	Yes	You need to set Max. Concurrent Migrations and Max. Concurrent Syncs, which determine the maximum number of processes the Agent can start concurrently to execute migration and synchronization. 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?

   • Resizing disks and partitions
   1. Select Yes for Partition Resizing and click Resize Partition. In the displayed dialog box, resize the disks and partitions on the target server as needed.

   Figure 2 Resizing disks and partitions (Windows)
   

   Figure 3 Resizing disks and partitions (Linux)
   
   

   • You can choose whether to migrate source partitions and resize the paired target partitions.
   • For a Linux server using LVM, you can choose whether to migrate physical or logical volumes and resize the paired target volumes.
   

   • In a Windows migration, the system and boot partitions are migrated by default.
   • In a Windows migration, you can increase the sizes of partitions, but you cannot decrease them.
   • Partition resizing is not available for Btrfs partitions on Linux.
   • In a Linux migration, the system and swap partitions are migrated by default.
   • You can choose to migrate all or none volume groups by configuring Migrate All Volume Groups.
   • If you choose to migrate none of the logical volumes in a volume group, their physical volumes will not be migrated by default.
   • In a Linux block-level migration, you can increase the sizes of partitions, but you cannot decrease them.
   • In a Linux file-level migration, you can increase or decrease size of each partition. The new partition size must be at least 1 GB larger than the used partition space. If the current partition size is not 1 GB larger than the used partition space, the partition size cannot be decreased. For details, see What Are the Rules for Resizing Volume Groups, Disks, and Partitions?
   • 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 decrease the disk size as needed.

   2. Click Next: Configure Disks. Resize the disks as needed. Then confirm the configurations and click OK.

   

   After you click OK, the value of Partition Resizing cannot be changed from Yes to No. If you want to restore the disk partition settings as they were, locate the source server to be migrated and choose More > Delete in the Operation column. Then restart the Agent on the source server, configure the target server again, and set Partition Resizing to No.

5. Click Next: Configure Target in the lower right corner.
   Figure 4 Configure Target
   

6. On the Configure Target page, set parameters as prompted.

   Table 2 Parameters for configuring a target server

   Parameter	Option	Operation
   Region	-	Select a region where you want to provision the target server. Consider your service requirements when selecting a region.
   Project	-	Select a project in the region from the drop-down list. You can select a project only after a region is selected.
   Server	Use existing	Select an existing server based on the recommended specifications above the server list. For details, see Use existing.
   	Create new	Configure VPC, Subnet, Security Group, and the parameters in Advanced Settings. For details, see Create new.

   • Use existing
     The target server must meet requirements listed below. If no existing server meets the requirements, click Create Now to create one based on the recommended specifications. For details, see Purchasing an ECS.

     

     Source servers can be migrated to pay-per-use or yearly/monthly ECSs. You can select ECSs of whichever billing mode is appropriate.

     • 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.
     • A target server must run the same OS as the source server, or there will be a server name conflict or other problems.
     • A target server must be reachable by the source server. An EIP must be bound to the target server, or a VPN or Direct Connect connection must be established between the source and target.
     • The security group of the target server must be correctly configured. It must be configured to allow access on TCP ports 8899, 8900, and 22 for a Windows migration, on ports 8900 and 22 for a Linux block-level migration, or on port 22 for a Linux file-level migration.
       

       • For security purposes, you are advised to open these ports only to the source server.
       • The firewall of the target server must allow traffic to these ports.

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

   • Create new
     • If you select Recommended for Server Template, a VPC, subnet, and security group will be automatically created based on source settings. You can change the recommended settings as needed.
       Advanced options such as the server name, AZ, specifications, system disk, data disk and EIP are automatically configured. You can change the settings as needed.

       Figure 5 Recommended
       

       Figure 6 Advanced Settings
       

       

       • Data disks must be either VBD or SCSI. VBD is the default device type for data disks. For details about disk device types, see Device Types and Usage Instructions.
       • Data disks can be created as shared disks. For details about shared disks, see Shared EVS Disks and Usage Instructions.
     • If you select a custom template, the VPC, subnet, security group, AZ, and disk will be populated based on the template. You can change the settings as needed. To learn how to create a server template, see Creating a Server Template.
       

       If you select Recommended for Server Template, SMS will automatically:

       • Create a VPC and subnet.

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

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

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

       • Create a security group and allow traffic to the target server over the ports required by SMS: ports 8899, 8900, and 22 for a Windows migration, ports 8900 and 22 for a Linux block-level migration, or port 22 for a Linux file-level migration.

7. Click Next: Confirm in the lower right corner.
   Figure 7 The configuration confirmation page
   

8. (Optional) Click Save as Server Template. In the displayed Create Server Template dialog box, enter a template name and click OK to save the target server settings as a template.
   

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

   Figure 8 Create Server Template
   

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

   Figure 9 Saving the configuration
   
   Figure 10 Saving the configuration and starting the migration
   
   

   If is displayed in the Migration Stage column, the target server has been configured.