Notes and Constraints
This section describes the constraints and limitations on using SMS.
Server Requirements
| Item | Description |
|---|---|
| Server specifications |
|
| OSs |
|
| Available disk space | |
| File systems |
|
| Shared file systems | SMS cannot migrate data from shared file systems such as NFS or CIFS, or from NAS devices. |
Migration Constraints
| Item | Description |
|---|---|
| Source server quantity | A maximum of 1,000 source servers are allowed per account. Delete the records of migrated servers in a timely manner so that other servers can continue to be migrated. |
| External storage of servers | SMS cannot migrate data from the external storage attached to a source server. |
| Encrypted files | SMS cannot migrate OSs that contain protected folders or encrypted volumes. |
| Servers that run multi-node databases and Active Directory Domain Services (AD DS) | SMS cannot migrate servers that host active directories or multi-node databases. |
| Data of database applications and domain controller applications | SMS cannot migrate data of database applications and domain controller applications. |
| Applications bound to hardware | SMS cannot migrate OSs that contain applications bound to hardware. |
| Dynamic disks | Dynamic disks in Windows systems are migrated as basic disks. After the migration is complete, the target server will not have dynamic disks. |
| Unused or empty disks | SMS only migrates disks that are attached and used on a source server. Unused disks will not be migrated. |
| Servers with system volumes located on disks other than the first disk | SMS cannot migrate servers whose system volumes are not on the first disk. |
| Thinly-provisioned logical volumes | SMS cannot migrate thinly-provisioned volumes. |
| Servers with RAID arrays | SMS cannot migrate servers with RAID arrays. |
| Big data clusters and container clusters | SMS cannot migrate clusters including but not limited to container clusters and big data clusters. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.