Configuring a Target Server

Scenarios

Prerequisites

• 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.

Procedure

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.
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	-	You can use the default migration template provided by the system. You can also manually create a migration template in advance. 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 for 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 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 disk partitions.
   	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 option is only available for Linux file-level migrations.
   Resource Limits (Optional)	CPU Limit	-	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	-
   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.

   • Resizing Disks and Partitions

   1. Click Resize Partition on the right of option Yes. In the displayed Resize Partition dialog box, resize the disk partitions on the target server as needed.

   Note

   • You can choose whether to migrate a source partition and resize the corresponding target partition.
     Caution

     • For the system and swap partitions on a Linux source server, Migration is fixed to Yes by default.
     • For Linux Btrfs file systems, Migration is fixed to Yes by default.
     • If you set Migration to No for all the logical volumes in the LVM, Migration will be set to No for the corresponding physical volumes automatically.
     • If you set Migration to Yes for at least one of the logical volumes in the LVM, Migration will also be set to Yes for the corresponding physical volumes automatically.
     • In Linux block-level migration, you can only increase a partition size.
     • In Linux file-level migration, you can increase or decrease a partition size. Ensure that the new partition size is at lease 1 GB larger than the used partition space. If the current partition size is smaller than the sum of the used partition space plus 1 GB, the disk partition size cannot be decreased.
   • If the new partition size is larger than the disk size, click Resize Disk to expand the disk.
   • If the new partition size is smaller than the disk size, click Resize Disk to shrink the disk.

   2. Click OK.

   Caution

   After you click OK, the setting of Partition Resizing cannot be changed to No. If you want to restore the original disk partition settings, locate the row that contains the server to be migrated, click More in the Operation column, and select Delete from the drop-down list. Then, restart the Agent installed on the source server, configure the target server again, and set Partition Resizing to No.

6. Click Next: Configure Target in the lower right corner.
7. On the Configure Target page, set parameters as prompted.

   Table 2 Parameters for configuring a target server

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

   • Use existing

     A target server must meet requirements listed below. If no existing server meets the requirements, click Buy Now to create one that meets the requirements based on the recommended target server specifications.

     • 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:

       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 during migration
     • If you select Recommended for Server Template, the VPC, subnet, and security group will be automatically created. You can update the configurations as needed.

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

       Note

       • Supported device types for data disks are Virtual Block Device (VBD) and Small Computer System Interface (SCSI). VBD is the default data disk device type.
       • Data disks can be created as shared disks.

     • If you select an existing template, the VPC, subnet, security group, AZ, and disk will be configured based on the template. You can update the configurations as needed. For details about how to create a template, see Creating a Server Template.
       Note

       If you set Server Template to Recommended, 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 network segment 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 network segment 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 network segment 10.0.0.0/8.

       • Create a security group and enable ports based on the service requirements: ports 8900 and 22 for Linux block-level migration, or port 22 for Linux file-level migration.

8. Click Next: Confirm in the lower right corner.
9. (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.

10. 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.