Help Center/ Server Migration Service/ User Guide(ME-Abu Dhabi Region)/ FAQs/ OS Compatibility and Migration Restrictions/ Why Can't I Save the Migration Configuration as a Template?

Updated on 2024-03-15 GMT+08:00

View PDF

Why Can't I Save the Migration Configuration as a Template?

Symptom

After you completed the migration configuration, you clicked Save as Template to save the configuration as a template for future use, but the message "Failed to save the configuration" was displayed.

Possible Causes

The image used to create the target server is a private image and has been deleted. SMS cannot identify the information about this private image. As a result, the migration configuration fails to be saved as a template.

Solution

Go to the ECS console and reinstall or change the OS of the target server.

If you want to change the firmware type of the target server from BIOS to UEFI, create a private image by following the instructions provided in How Do I Resolve Error "Inconsistent firmware type. Source: UEFI, Target: BIOS" When I Create a Migration Task?

Parent topic: OS Compatibility and Migration Restrictions

Previous topic: How Do I Check the Firmware Type of a Source Server?

Next topic: How Do I Set Resource Limits for SMS-Agent During a Linux Server Migration?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.