Why Has My Automated Backup Failed?

Automated backups may fail for the following reasons:

1. The network environment is unstable due to issues such as network delay or interruption. GaussDB(for MySQL) will detect these problems and trigger another automated backup half an hour later. You can also perform a manual backup before then.
2. Multi-task executions are complicated, resulting in problems such as task waiting or interruptions. GaussDB(for MySQL) will detect these problems and trigger another automated backup half an hour later. You can also perform a manual backup.
3. An instance is unavailable, possibly because the instance is faulty or being modified. GaussDB(for MySQL) will trigger an automated backup when the instance status becomes available. You can also perform a manual backup before then.
4. A parameter is changed incorrectly. For example, an instance may become faulty after a parameter template containing incorrect parameters was applied 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 instance.
5. An error occurred during data import.

   If system catalog records get lost due to improper data import, you can import data again by referring to Migrating Data to GaussDB(for MySQL) Using DRS.

6. If the issue persists, contact technical support.