Help Center/
Relational Database Service/
User Guide (Paris Region) /
FAQs/
Backup and Restoration/
Why Has My Automated Backup Failed?
Updated on 2022-12-08 GMT+08:00
Why Has My Automated Backup Failed?
Automated backup failures may be caused by the following reasons:
- The network environment is unstable, due to issues such as network delay or interruption. RDS will detect these problems and trigger an automated backup after half an hour. You can also perform a manual backup before then.
- Multi-task executions are complicated, resulting in problems such as task waiting or interruption. RDS will detect these problems and trigger an automated backup half an hour later. You can also perform a manual backup in time.
- A DB instance status is unavailable, possibly because the DB instance is faulty or being modified. RDS will trigger an automated backup after the DB instance status becomes available. You can also perform a manual backup before then.
- A parameter change is incorrect. For example, a DB instance may be faulty after a parameter template containing incorrectly changed parameters apply to it. You can check whether original and current values are correct, check whether any related parameters also need to be changed, reset the parameter template, or reboot the DB instance.
- An error has occurred during data import.
For example, system table records get lost due to inappropriate data import.
If the problem persists, contact technical support.
Parent topic: Backup and Restoration
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot