Why Does Automated Backup for a GaussDB Instance Fail?

The possible causes and solutions for automatic backup failures are as follows:

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

  If the system 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 the system 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 the system detects any of these problems, it triggers another automated backup half an hour later. Alternatively, you can perform a manual backup immediately.

• A parameter change was incorrect.

  If your 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 instance.

• An error occurred during data import.

  For example, system catalog records are lost due to inappropriate data import. You can import data again by referring to the migration plan.

• If the problem persists, contact customer service.