Why Has Automated Backup of My RDS Instance Failed?

The following figure shows the possible reasons for automated backup failures.

Figure 1 Reasons why automated backup fails

• The network environment may be unstable due to problems such as network delay or interruptions.

  If RDS detects any of these problems, it triggers another automated backup half an hour later. Alternatively, you can perform a manual backup immediately.

• If multiple tasks are being executed simultaneously, there can be problems such as excessive task wait times or interruptions.

  If RDS detects any of these problems, it triggers another automated backup half an hour later. Alternatively, you can perform a manual backup immediately.

• The DB instance is abnormal probably because it is faulty or being modified.

  If RDS detects any of these problems, it triggers another automated backup half an hour later. Alternatively, you can perform a manual backup immediately.

• The backup speed depends on how many tables there are in the databases.

  If the number of tables exceeds 500,000, the backup will fail.

• A parameter change was incorrect.

  If your DB instance becomes faulty after you modify parameters of a parameter template and apply the template to the instance, check whether the modified parameters are set to correct values and whether there are any associated parameters that need to be changed, or reset the parameters to their defaults and reboot the DB instance.

• An error occurred during data import.

  For example, system table records get lost due to inappropriate data import.

  • For RDS for MySQL, you can import data again by referring to Migration Solution Overview.
  • For RDS for PostgreSQL, you can import data again by referring to Migration Solution Overview.
  • For RDS for SQL Server, you can import data again by referring to Migration Solution Overview.
• If the problem persists, contact customer service.