Help Center > > FAQs> Common> What Kind of Information About Source Servers Are Collected by SMS?

What Kind of Information About Source Servers Are Collected by SMS?

Updated at: Jul 19, 2019 GMT+08:00

SMS uses the migration Agent to collect information about source servers to evaluate the migration feasibility and provide required data for selecting and configuring target ECSs. Table 1 lists the information to be collected for a Windows OS. Table 2 lists the information to be collected for a Linux OS. All collected data is used for data migration only.

Table 1 Information about the source server that runs a Windows OS

Item

Parameter

Objective

Environment check information

OS Version

Used for migration feasibility evaluation: Only source servers with OSs included in Table 1 can be migrated.

Firmware Type

Used for migration feasibility evaluation: The source server can be booted from BIOS or UEFI.

CPU

Used for selecting the target ECS: The number of vCPUs of the target ECS cannot be less than that of the source server.

Memory

Used for selecting the target ECS: The memory of the target ECSs cannot be less than that of the source servers.

System Directory

Used for configuring target ECSs: After the migration is complete, restore the registry.

Disk Partition Format

Used for configuring target ECSs: Before the migration, the disk of the target ECS must be formatted to be the same as that of the source server.

File System

Used for migration feasibility evaluation: Only the source servers with New Technology File System (NTFS) file system can be migrated.

Available Space

Used for migration feasibility evaluation: If the available space on the source server partition is insufficient, the migration may fail.

OEM System Check

Used for migration feasibility evaluation: If the system is an OEM system, the OS needs to be reactivated after the migration.

Driver files

Used for migration feasibility evaluation: The source server must have a basic disk drive.

System services

Used for migration feasibility evaluation: The Volume Shadow Copy Service (VSS) must be available on the source server.

User permissions

Used for migration feasibility evaluation: You must have the administrator permissions to run the migration Agent.

NIC Information

  • NIC Name
  • MTU

Used for distinguishing different source servers

Disk Information

  • Disk Name
  • Disk Partition Format
  • Disk Size
  • Used Space

Used for checking whether the disk specifications of target ECSs meet the migration requirements

Table 2 Information about the source server that runs a Linux OS

Item

Parameter

Objective

Environment check information

OS Version

Used for migration feasibility evaluation: Only source servers with OSs included in Table 1 can be migrated.

CPU

Used for selecting the target ECS: The number of vCPUs of the target ECS cannot be less than that of the source server.

Memory

Used for selecting the target ECS: The memory of the target ECSs cannot be less than that of the source servers.

Paravirtualization Check

Used for evaluating migration feasibility: The SMS service does not support migration of paravirtualized source servers.

Firmware Type

Used for migration feasibility evaluation: The source server can be booted from BIOS or UEFI.

Boot Mode

Used for migration feasibility evaluation: The source server must be booted from BIOS.

Rsync Component Check

Used for evaluating synchronization feasibility: The SMS synchronization function depends on the Rsync component on the source server.

Raw Equipment Check

Used for migration feasibility evaluation: The source servers to be migrated cannot contain raw devices.

Disk Partition Information

Used for migration feasibility evaluation. The disk type of the source server must be Main Boot Record (MBR) or GUID Partition Table (GPT).

Disk Partition Format

Used for configuring target ECSs: Before the migration, the disk of the target ECS must be formatted to be the same as that of the source server.

File System

Used for migration feasibility evaluation: The file system type of the source server must be ext2, ext3, ext4, VFAT, XFS, Reiserfs, swap, or lvm2_member.

NIC Information

  • NIC Name
  • MTU

Used for distinguishing different source servers

Disk Information

  • Disk Name
  • Disk Partition Format
  • Disk Size
  • Used Space

Used for checking whether the disk specifications of target ECSs meet the migration requirements

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel