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 interruptions. RDS will detect these problems and trigger an automated backup half an hour later. You can also perform a manual backup.
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 become faulty after a parameter template containing incorrect parameters was applied to 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.
For MySQL, you can import data again by referring to section Migrating Data to RDS for MySQL Using mysqldump.
For PostgreSQL, you can import data again by referring to section Migrating Data to RDS for PostgreSQL Using psql.
For Microsoft SQL Server, you can import data again by referring to section Migrating Data to RDS for SQL Server Using SQL Server Management Studio.
If the problem persists, contact technical support.