SMS uses the Agent to collect source server details to evaluate the migration feasibility and provide data required for selecting or configuring target servers. Table 1 lists the data collected from a Linux server. All collected data is used for migration only.
Item | Sub-Item | Usage |
|---|---|---|
Environment information | OS version | Used for migration feasibility checks. Only source servers with OSs included in Supported Linux OSs can be migrated. |
CPU | Used for recommending the target server flavor. | |
Memory | Used for recommending the target server flavor. | |
Paravirtualization | Used for migration feasibility check. SMS does not support migration of paravirtualized source servers. | |
Firmware type | Used for migration feasibility check. The source server can be booted from BIOS or UEFI. | |
Boot mode | Used for migration feasibility check. The source server must be booted from BIOS. | |
rsync | Used for evaluating synchronization feasibility. SMS synchronization depends on rsync on the source server. | |
Raw device | Used for migration feasibility check. The source servers to be migrated cannot contain raw devices. | |
Disk partition | Used for migration feasibility check. The source disk partition style must be Main Boot Record (MBR) or GUID Partition Table (GPT). | |
Disk partition style | Used for configuring the target server. Before the migration, the disks of the target server must be formatted to be the same as those of the source server. | |
File system | Used for migration feasibility check. The file systems on the source server must be Ext2, Ext3, Ext4, VFAT, XFS, or Btrfs. | |
Disk information |
| Used for checking whether the disk specifications of the target server meet the migration requirements. |