What Are the Notes, Constraints, and Precautions for Server Migration?

• You need to check the OS version of the server you are migrating. If it is too early, for instance, Windows Server 2008, the kernel may be incompatible and services on the server may fail to start after the migration is complete. To avoid this issue, you need to evaluate whether a lift-and-shift migration is suitable for the server before the migration.
• You need to disable any software such as antivirus or security software that may prevent the SMS Agent from start on the server. If you are not sure whether there is a software conflict with the Agent, back up your data before the migration.
• Linux block-level migration is in the open beta test (OBT) and is only recommended for testing scenarios.
• The VirtIO drivers must be installed in the source server OS, or the target server may fail to start after the migration is complete. If your source server runs on Huawei Cloud, you can install the drivers by referring to Installing VirtIO Drivers.
• There are differences between the source and target servers after the migration. For details, see What Are the Differences Between the Source and Target Servers After the Migration?

• Before using SMS, you need to set up a secure network. For details about the network requirements, see How Do I Set Up a Secure Migration Network for Using SMS?
• You need to correctly configure security group rules for the target server by referring to How Do I Configure Security Group Rules for Target Servers?
• The migration occupies some source server resources, such as memory, CPU, disk I/O, and bandwidth. You can limit the resource allocation for the migration. If the source server runs Linux, Traffic Control (TC) must be installed and run properly on it. Otherwise, traffic limiting may not be applied.

• The migration speed is affected by factors such as network bandwidth, disk I/O, CPU and memory usage, and file size and quantity, so it is impossible to accurately estimate the migration duration. The remaining migration duration estimated by SMS for a migration task is for reference only. For more information, see Migration Duration.
• It is recommended that data migration and service cutover be completed within 30 days.
• The time required for an incremental synchronization is affected by many factors, such as the number of incremental files, the continuity of valid blocks, and the size of incremental data. It is impossible for SMS to estimate the required time.

• Before a migration is complete, do not perform operations on the OS or disks of the target server, including but not limited to changing or reinstalling the OS.
• Make sure you have backed up any data on the target server that you need to save and ensure that the disks can be formatted. Disks on the target server will be formatted and re-partitioned based on the source disk settings during the migration.
• During the migration of a Windows source server, do not restart the source server. The restart will disconnect the source server from the SMS console. To retry the migration, you need to delete the migration task and create a new one.
• Do not restart the Agent during a Windows migration or a Linux block-level migration.
• You are advised not to start the Agent during a Linux file-level migration unless necessary, even though resumable data transfer is supported.
• During the migration, a temporary pay-per-use disk is created and attached to the target server to ensure that the migration runs normally. After the migration is complete, the disk is automatically detached and deleted. If you manually delete the migration task before it completes, you need to manually delete the temporary disk to avoid extra fees.
• If an error occurs during the migration, you are advised to provide migration logs to technical support engineers so that the fault can be resolved quickly.

  For details about how to get migration logs, see Where Can I Find the Agent Run Logs?

• SMS migrates OS and data. It ensures data consistency before and after the migration, but does not ensure that your applications will run properly on the target server after the migration is complete. You may need to adjust your applications by yourself.
• SMS gives you the capability to verify data consistency before and after the migration. You can enable verification when you configure the target server or initiate an incremental synchronization. Note that consistency verification cannot be performed for servers with Btrfs file systems.

After the full migration of a Linux server, some parameter settings in the directories below on the target server are modified to make the target server compatible with Huawei Cloud and ensure that the target server can start properly. During incremental synchronization, data in these directories is not synchronized by default to prevent parameter settings in these directories on the target server from being overwritten or modified.

/proc/*,
/sys/*,
/lost+found/*,
/tmp/_MEI*,
/var/lib/ntp/proc/*,
/boot/*,
/boot/efi/*,
/etc/fstab,
/etc/*,
/etc/X11/*,
/root/initrd_bak/*,
/lib/modules/*,
/boot/grub2/x86_64-efi/*,
/boot/grub2/i386-pc/*

To limit the migration speed for a Linux source server, the tc command and cbq kernel module must be installed on the source server.

• To check whether the tc command is installed, run the following command on the Linux terminal. If the system returns the tc function list, the tc command has been installed.

  # tc

• To check whether the cbq module is installed, run the following command on the Linux terminal. If the system returns the related information, the cbq module is loaded.

   lsmod | grep sch_cbq

• Resumable transfer is supported following network interruptions.
• Resumable transfer is supported following a Linux restart but is not available after a Windows restart.

• Allow access from the server where the MgC Agent is installed over port 5985.
• Use PowerShell 3.0 or later.
• Have WinRM enabled and be able to access the server where the MgC Agent is installed. For more information, see How Do I Configure WinRM and Troubleshoot WinRM Connection Problems?
• Allow the execution of shell scripts. To review the current execution policy, you can open PowerShell on the source servers as an administrator and run the following command:

  Get-ExecutionPolicy

  If Restricted is returned, no scripts can be executed. Run the following command and enter Y to change the policy to RemoteSigned:

  Set-ExecutionPolicy RemoteSigned

• Allow access from the server where the MgC Agent is installed over port 22.
• Allow direct root access. That means remote connections using root with SSH or other tools must be allowed on these Linux source servers.
• Have SFTP and SSH enabled.
• Support the following key exchange algorithms and MAC algorithms:
  • Key exchange algorithms: ssh-ed25519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, rsa-sha2-512, and rsa-sha2-256
  • MAC algorithms: hmac-sha2-256 and hmac-sha2-512

  If a server does not support the preceding security algorithms, you are advised to upgrade OpenSSH to 8.0 or later. Otherwise, deep collection cannot be performed for that server.

• Have their iptables configured to allow all communications with the server where the MgC Agent is installed. To verify that, you can run the following command on the source servers. If the source field in the command output contains the IP address and port of the server where the MgC Agent is installed, it means that the MgC Agent is not allowed to access these source servers. In this case, you need to allow access from the MgC Agent.

  iptables -L INPUT -v -n

  

  Run the following command to allow the access.

  iptables -D INPUT -s <IP-address-of-the-MgC-Agent-server-indicated-by-the-source-field>

Table 1 lists the Windows OSs that can be collected and migrated by MgC.

MgC supports collection and migration for Linux distributions and versions that use OpenSSH 7.0 or later. If a source server uses OpenSSH earlier than 7.0, perform the following operations:

• Upgrade OpenSSH to 7.0 or later.
• If the OpenSSH version cannot be upgraded, add an environment variable on the server where the MgC Agent is installed. For details, see How Do I Set Environment Variables to Collect and Migrate Linux Servers That Use OpenSSH Earlier Than 7.0?

Table 2 lists the Linux OSs that can be collected and migrated by MgC.