Before using the CMS, you must evaluate the migration source. This topic describes what to evaluate for the migration source to help you better evaluate the status of your migration source.
Item | Content |
Recommended configurations for migration servers | We recommend that you keep the configurations of the source and target servers consistent. The migration consumes resources. A compromised configuration may cause the migration to be slow or even fail. After the migration is complete, you can increase or reduce the capacity based on customers' business needs. |
Limitation on the number and capacity of disks on the migration source | The capacity for a single disk is not limited but the number of disks must be less than 24. If the number of disks is exceeded, reduce the number of disks on the source server or submit a ticket for technical consulting. |
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. |
Confirming application verifiers | To maintain data consistency, users must stop services when using the product for incremental migration. After businesses are migrated to the cloud, relevant personnel familiar with the businesses should test and verify the migration so as to reduce downtime. |
What factors will affect application pullup | Unauthorized application software, pirated software, clustered databases, U-Key hardware verification, and some hardware binding verification. |
Precautions regarding network environments | If the migration speed reaches the upper threshold during migration, test the egress bandwidth on the source server, the ingress bandwidth on the target server, and the bandwidth limit configuration on the CMS console. Identify the existence of special networks, dedicated access, and public network environment. |
Identifying specific requirements | Identify specific requirements such as confidential files and IP addresses that need to remain unchanged, |
Precautions when using this product for complex businesses | Users must record business information, and migrate, switch, and test business systems for associated businesses of the same type as needed. Users must stop services when using the product for incremental migration to keep data 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. |
Four steps for Windows OS | Check the system version, close the anti-virus software, quit QEMU, and check the disk space (adjust the disk space of the volume shadow service if necessary). |
Precautions regarding Linux OS | Whether the root permission is required on the migration source; The mount point to migrate on the migration source; whether the fstab file is correctly written. |
Using resource collection on the 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. |
Limit of migration source and target servers | BMS migration is currently not supported in the CMS. Please ensure that no BMS is involved in the migration source and target servers in your migration task. |
Network limit of migration source | Only exclusive IP addresses are supported. Please confirm the network status of your migration source server. |
Limit of migration drive letter | The boot location must be on the first partition of the first drive. |
Storage service limit of migration source | Shared storage cannot be migrated. Check whether your migration source server must migrate shared storage. |