What Information Does SMS Collect About Source Servers?
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 Windows server. Table 2 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 Table 2 can be migrated. |
Firmware type |
Used for migration feasibility checks. The source server can be booted from BIOS or UEFI. |
|
CPU |
Used for recommending the target server flavor. |
|
Memory |
Used for recommending the target server flavor. |
|
System directory |
Used for configuring the target server. After the migration is complete, it will be used to restore the registry. |
|
Disk partition style |
Used for configuring the target server. Before the migration starts, the disks of the target server must be formatted based on the disk settings of the source server. |
|
File system |
Used for migration feasibility checks. Only the NTFS partitions can be migrated. |
|
Available space |
Used for migration feasibility checks. If there is not enough space on a source server partition, the migration may fail. |
|
OEM system check |
Used for migration feasibility checks. If the system is an OEM system, the OS needs to be reactivated after the migration is complete. |
|
Driver files |
Used for migration feasibility checks. The source server must have basic disk drivers. |
|
System services |
Used for migration feasibility checks. Volume Shadow Copy Service (VSS) must be available on the source server. |
|
User permissions |
Used for migration feasibility checks. You must have the administrator permissions to run the Agent. |
|
Disk information |
|
Used for checking whether the disk specifications of the target server meet the migration requirements. |
Item |
Sub-Item |
Usage |
---|---|---|
Environment information |
OS version |
Used for migration feasibility checks. Only servers with OSs included in Table 3 or Table 4 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 cannot migrate paravirtualized source servers. |
|
Firmware type |
Used for migration feasibility checks. The source server can be booted from BIOS or UEFI. |
|
Boot mode |
Used for migration feasibility checks. 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. Source servers using raw devices cannot be migrated. |
|
Disk partition |
Used for migration feasibility checks. 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 starts, the disks of the target server must be formatted based on the disk settings of the source server. |
|
File system |
Used for migration feasibility checks. Supported file systems include Ext2, Ext3, Ext4, VFAT, XFS, and Btrfs. |
|
Disk information |
|
Used for checking whether the disk specifications of the target server meet the requirements. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.