Server Migration Module

Item

Prerequisites

Migration Source and Upper Limit of Migration Tasks

Each user can activate a maximum of 1000 migration sources. Each user can create a maximum of 1000 migration tasks. Each user can perform a maximum of 50 migration tasks concurrently.

Binding Limit of Migration Source

Each migration source can only be bound to one migration target at a time, generating the only migration task in an "unfinished" state. A completed or abnormal migration task cannot be bound to the target as the migration source.

Software & Hardware and Authorization Limit of Migration Source

Unauthorized application software, pirated software, cluster database, and U-Key that may affect the use of the product, should be avoided.

Configuration Limit of Migration Source and Target

The memory of the target server must be greater than 4 GB. You are advised to use the same configuration for the target server as the migration source. If the memory of the migration source VM is less than 4 GB, increase the memory as needed after migration.

Limit of Migration Source and Target

BMS migration is not supported.

Network Limit of Migration Source

Only exclusive IP addresses are supported.

Limit of Migration Drive Letter

The boot location must be on the first partition of the first drive.

Storage Service Limit of Migration Source

Clients cannot share storage.

Disk Number and Capacity Limit of Migration Source

The capacity for a single disk is not limited but the number of disks must be less than 24. If this limit is exceeded, reduce the number of disks on the source server or submit a ticket for technical consultation.

Limit of Database and Cluster Services

Use shared storage for Oracle RAC and ASM disks for some Oracle RAC. The CMS cannot be used to migrate ASM disks or Oracle RAC. CMS is not recommended for large databases. Please use a professional migration tool for migrating databases instead. If you use a CMS for migration, you should stop the application process before the "Stop Incremental Synchronization" step.

Limit of Network Environment Factors

Network problems may affect the migration speed. You must test the egress bandwidth on the source server, the ingress bandwidth on the target server, and the bandwidth limit configuration. Identify the existence of special networks, dedicated access, and Internet environments.

Pullup and Support Limit of Complex Applications

When migrating complex businesses, record business information, and migrate, switch, and test business systems as needed. During incremental migration, you must stop related service processes to ensure consistency. After businesses are migrated to the cloud, relevant personnel familiar with the businesses should test and verify the migration so as to reduce downtime.

Specific Requirements

If there are specific requirements such as confidential files and IP addresses that need to remain unchanged, you must submit a ticket for technical consultation to meet the corresponding requirements.

Resource and Performance Limit of Migration Source

The CMS agent is deployed on the source server and uses the CPU and memory of the source server. If the CPU or memory usage of the source server is too high, the CMS agent may affect business operations and even break down the migration source. Servers with 4 cores and 4 GPUs can meet resource migration requirements. After the agent starts on the source server, the CMS continuously monitors the source server and displays data such as CPU usage, memory usage, and disk data increase in a certain period. Users evaluate the system based on the given data. If an accurate evaluation is not possible, consult the relevant professionals.

Specification Limit of Target Equipment

Target server specifications include A10/V100s GPU servers and T4/V100 GPU servers.

OS

For Windows operating systems that can be migrated, see the Windows Compatibility List. For Linux operating systems that can be migrated, see the Linux Compatibility List. You cannot migrate multiple operating systems.