What Are the Important Statements of SMS?
- Source server data collection
After the Agent is started on a source server, it will report source server details to SMS. This information will only be used to check the feasibility of a migration. For details about what information will be collected from the source server, see What Information Does SMS Collect About Source Servers?
- License invalidity
After OSs, applications, and files on source servers are migrated to target servers, the SIDs and MAC addresses of the servers will change. This means that some OS or application licenses may become invalid. SMS is not responsible for this type of issue. You can use the license server on Huawei Cloud to obtain new Windows OS licenses and update or obtain application licenses at your own expense.
- Do not perform operations on the OS or disks of target servers before the migration is complete. This includes, but is not limited to, changing or reinstalling the OS. SMS is not responsible for any fees or data damage resulting from such actions.
- Target server disk formatting
During the migration, disks on the target server are formatted and re-partitioned based on the source disk settings. Any existing data on the target server will be lost. Before the migration, make sure you have backed up any data on the target server that you need to save and ensure that the disks can be formatted. SMS is not responsible for any data losses incurred.
- Source disk data security
SMS does not monitor data in source disks during the migration. You need to ensure the security of your source disk data yourself. If the target servers or servers in the same VPC as the target servers are infected by any Trojans or viruses migrated from the source servers, SMS is not responsible for such problems.
- Migration errors caused by source servers
SMS is not responsible for migration errors caused by source server problems, including but is not limited to damaged hardware (such as damaged disks or NICs), improper configurations, or software compatibility issues (such as incompatible OSs and applications), damaged data files, heavy service traffic, or slow network speeds. You can fix these problems by yourself, but if any such problems persist, you can contact Huawei Cloud for assistance. Huawei Cloud will make every effort to assist in resolving the problems but does not guarantee all possible problems can be resolved. The following problems with a source server may lead to migration errors:
- A faulty source server OS. For example, a Windows startup file is damaged or missing.
- An incorrectly configured source server OS. For example, GRUB or fstab is incorrectly configured on the source server.
- Source server network problems. For example, the source server cannot access the Internet, the network is too slow, or the SSH connection or firewall is faulty.
- Slow I/O on source server disks, too much incremental data, scattered effective clusters (on Windows), or too many small files (on Linux). These problems can slow down the migration or synchronization progress.
- An incompatible source platform service or software
- The Agent may be disabled by a source platform service or software, or the I/O monitoring could be disabled by antivirus software on the source server.
- If your target servers on Huawei Cloud cannot be started after the migration is complete, Huawei Cloud can provide technical support to help you solve problems, but does not promise that the all possible problems can be resolved. There are many possible reasons that a target server may be unable to start, for example:
- The source server cannot be restarted.
- The source server has a non-standard OS configuration.
- The source server has drivers or software that is incompatible with Huawei Cloud.
- To ensure compatibility with Huawei Cloud, SMS modifies the system configurations of target servers. For details, see What Are the Differences Between Target and Source Servers After the Migration? SMS can ensure data consistency before and after the migration but cannot ensure that your services run properly after the migration. You need to modify related service configurations thereafter.
- You are advised not to add data to target servers before the service cutover or to source servers after the service cutover. If new data is generated on both your source and target servers after the service cutover, SMS cannot combine data on the source and target servers. If you want to combine the new data on the source and target servers, you must design a solution by yourself.
- GPU server driver problems
If driver problems, such as lacking drivers for computing or graphics acceleration, occur on target GPU servers after the migration is complete, you need to install related drivers. If the problem persists, Huawei Cloud can provide technical support for you, but does not guarantee all problems can be resolved.
- Change to Huawei Cloud EulerOS (HCE)
HCE is an openEuler-based cloud operating system. When migrating servers running CentOS 7 or CentOS 8, SMS allows you to change the OS to HCE. But you need to use x2hce-ca to evaluate the compatibility of applications with HCE and perform the OS change only after the applications are adapted to HCE. If services on the target servers cannot run properly, Huawei Cloud can provide technical support for you, but does not guarantee all problems can be resolved.
- When migrating Windows servers, SMS calls some Windows APIs to obtain data. SMS is not responsible for any call failures caused by the OS configuration and hardware problems of these Windows servers. You need to solve the problems by yourself.
- Service isolation and conflicts
SMS does not check your services on source servers or target servers, let alone conflicts between them. You need to identify service conflicts and make isolation if necessary. If there are such conflicts, SMS is not responsible.
- Temporary disks
SMS is free, but you pay for the temporary disks used during the migration. For each migration, a temporary disk is created and attached to the target server to ensure that the migration proceeds smoothly. Once the migration is complete, the disk is automatically detached and deleted.
- If you delete a migration task before it is complete, you need to manually delete the temporary disk. Otherwise, the disk will continue to be billed, resulting in additional costs.
- If you reinstall or change the OS for the target server before the migration is complete, the migration task will fail. You need to manually delete the temporary disk used for the migration. Otherwise, the disk will continue to be billed, resulting in additional costs.
SMS is not liable for any additional fees incurred due to the temporary disk.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot