This topic describes the limits of which you need to take note when you use Server Migration Center (SMC).
Limits on the number of migration sources and migration jobs
Number of migration sources that can be registered within an Alibaba Cloud account
Submit a ticket.
Number of migration jobs that can be created within an Alibaba Cloud account
Submit a ticket.
Number of migration jobs that can be concurrently run within an Alibaba Cloud account
Submit a ticket.
Limits on the data to be migrated
Operating system of the source server
The partitioning scheme of some disks cannot be replicated, such as dynamic disk partitions and extended disk partitions. If the partitioning scheme of a source disk cannot be replicated, the destination disk is built as a standard partitioned disk.
You cannot migrate the volume shadow snapshots of the source server.
The partitioning scheme of some disks cannot be replicated, such as logical volume manager (LVM) partitions and extended disk partitions. If the partitioning scheme of a source disk cannot be replicated, the destination disk is built as a standard partitioned disk.
Swap partitions cannot be replicated. After the source server is migrated, you must reconfigure a swap partition.
Some file system formats are not supported. During the migration process, the file systems in the unsupported formats are converted to the file systems in the mainstream formats, such as ext2, ext3, and ext4.
By default, if block replication is disabled, the virtual memory, cache, system snapshots, software configurations such as cloud-init and network services, and Docker directory data are not migrated. For more information, see the
rsync_excludes_linux.txt filtering configuration file in the installation directory of the SMC client.
The path of the default filtering configuration file varies based on the installation directory of the SMC client.
Limits on operating systems
The following table describes the operating systems that are supported by the SMC client.
Windows Server 2003
Windows Server 2008
Windows Server 2012
Windows Server 2016
Windows Server 2019
Windows Server 2022
CentOS 5, CentOS 6, CentOS 7, and CentOS 8
Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and Red Hat Enterprise Linux 8
Ubuntu 10, Ubuntu 12, Ubuntu 14, Ubuntu 16, Ubuntu 17, Ubuntu 18, Ubuntu 19, and Ubuntu 20
Debian 7, Debian 8, Debian 9, and Debian 10
openSUSE 13, openSUSE 42, and openSUSE 15
SUSE Linux Enterprise 11, SUSE Linux Enterprise 12, and SUSE Linux Enterprise 15
Alibaba Cloud Linux
Oracle Linux 5, Oracle Linux 6, Oracle Linux 7, and Oracle Linux 8
Amazon Linux 2014 and later
Each source server can be associated with only one migration job.
A migration job is unfinished if it is in the Ready, Running, Stopped, InError, or Expired state.
When a server is migrated to an image, a virtual private cloud (VPC) is created by default. Each Alibaba Cloud account can have up to 10 VPCs in a region, including your VPCs and the VPCs created for the intermediate instances. To increase the VPC quota, submit a ticket.
If you need to migrate multiple servers at a time, we recommend that you select an existing VPC. Otherwise, the migration job may fail to be created due to insufficient VPC quota.
You must use Grand Unified Bootloader (GRUB) V2.02 or later for migration sources that run the Linux operating system. For more information, see Install GRUB on a Linux server.
You must use GRUB V2.02 or later for earlier versions of Linux distributions such as CentOS 5, Red Hat Enterprise Linux 5, Debian 7, Amazon Linux, and Oracle Linux.