Updated on 2025-08-25 GMT+08:00

Backup Is Enabled

Rule Details

Table 1 Rule details

Parameter

Description

Rule Name

gaussdb-mysql-instance-enable-backup

Identifier

gaussdb-mysql-instance-enable-backup

Description

If the backup is disabled for a TaurusDB instance, this instance is non-compliant.

Tag

taurusdb

Trigger Type

Configuration change

Filter Type

gaussdbformysql.instance

Rule Parameters

None

Application Scenarios

You should build restoration and disaster recovery (DR) capabilities in advance to prevent data from being deleted or damaged by mistake in abnormal data processing scenarios.

  1. You should set up a proper automated backup policy. Automated backup is enabled by default when you create a TaurusDB instance and cannot be disabled. However, it can be modified after instance creation is complete. TaurusDB backs up data based on the specified automatic backup policy. TaurusDB backs up data at the instance level. If an instance fails or its data is damaged, you can restore it from backups to ensure data reliability. Backing up data affects the database read and write performance, so you are advised to set the automated backup time window to off-peak hours.
  2. You can use cross-region backup to achieve remote data DR. TaurusDB allows you to store backup files in another region. If instances in a region are faulty, you can use the backup files to restore the instances in the remote region.

For details, see Security Best Practices.

Solution

The automated backup policy is enabled by default and cannot be disabled. The evaluation result of this rule is always compliant, and no action is required. You can modify a same-region backup policy or set a cross-region backup policy as required.

Rule Logic

  • If no backup policy is configured for a TaurusDB instance, this instance is non-compliant.
  • If a backup policy is configured for a TaurusDB instance, this instance is compliant.