Why Has My Automated Backup Failed?

The possible reasons for automated backup failures are as follows:

1. The network environment may be unstable due to problems such as network delay or interruptions. If GaussDB(for MySQL) detects any of these problems, it triggers another automated backup half an hour later. Alternatively, you can perform a manual backup immediately.
2. If multiple tasks are being executed simultaneously, there can be problems such as excessive task wait times or interruptions. If GaussDB(for MySQL) detects any of these problems, it triggers another automated backup half an hour later. Alternatively, you can perform a manual backup immediately.
3. The DB instance is abnormal probably because it is faulty or being modified. If GaussDB(for MySQL) detects any of these problems, it triggers an automated backup when the instance status becomes available. Alternatively, you can perform a manual backup immediately.
4. 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.
5. An error occurred during data import. For example, system catalog records get lost due to inappropriate data import. You can import data again by referring to Migrating Data to GaussDB(for MySQL) Using DRS. The system will automatically identify and back up the data again.
6. If the problem persists, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.