Managing Automated Backups

Precautions

• Backup files are saved as packages in OBS buckets. Upload of backup files and service reads both consume bandwidth, so the upload bandwidth of OBS is limited. The bandwidth of a single node ranges from 20 MB/s to 70 MB/s.

  For better performance, you need to specify appropriate nodes for an instance and take into account the bandwidth for uploading backups.

• The CPU usage may increase 5% to 15% because uploading backups consumes CPU resources.
• The memory usage may increase by about 300 MB during the upload of backups. The increase depends on the instance's data volume. The increased memory mainly caches data during backup upload and service read. After the backup upload is complete, the memory recovers.

Automated Backup Policy

Automated backups are generated according to a backup policy and saved as packages in OBS buckets to ensure data confidentiality and durability. You are advised to regularly back up your database, in case it becomes faulty or damaged. However, backing up data might affect the database read and write performance so it is recommended that you enable automated backups during off-peak hours.

When you create an instance, an automated backup policy is enabled by default.

Figure 1 Enabling automated backup

• Incremental Backup: Incremental backup is enabled by default. You can manually enable or disable incremental backup. After you enable this function, it will take effect at the next full backup. Selecting Create a backup immediately after the incremental backup policy is modified is suggested. If you select this option, the system starts a full backup and the incremental backup policy takes effect. If you do not select this option, the policy takes effect at the next full backup. After incremental backup is enabled, the system stores backup data in OBS.
• Incremental Backup Interval: Incremental backups are generated every 15 minutes. To enable automated backup, contact technical support.
• Retention Period: Automated backup files are saved for seven days by default. The backup retention period can range from 1 to 35 days. Full backups are retained till the retention period expires. However, even if the retention period has expired, the most recent backup will be retained.
  • Extending the retention period improves data reliability. You can extend the retention period as needed.
  • If you shorten the retention period, the new backup policy takes effect for existing backups. Any automated backups (including full and incremental backups) that have expired will be automatically deleted. Manual backups will not be automatically deleted but you can delete them manually.
  

  • If the retention period is less than seven days, the system automatically backs up data every day.
  • The system checks existing automated backup files and deletes the files that exceed the backup retention period you set.
  • Time Window: A one-hour period the backup will be scheduled within 24 hours, such as 00:00–01:00. The backup time is in GMT format. If the DST or standard time is switched, the backup time segment changes with the time zone.

  If Retention Period is set to 2, full and incremental backups that have been stored for more than two days will be automatically deleted. That is, the backup generated on Monday will be deleted on Wednesday. Similarly, the backup generated on Tuesday will be deleted on Thursday.

  Policy for automatically deleting full backups:

  To ensure data integrity, even after the retention period expires, the most recent backup will be retained, for example,

  If Backup Cycle was set to Monday and Tuesday and the Retention Period was set to 2:

  • The full backup generated on Monday will be automatically deleted on Thursday. The reasons are as follows:

    The full backup generated on Monday expires on Wednesday, but it is the last backup, so it will be retained until a new backup expires. The next backup will be generated on Tuesday and will expire on Thursday. So the full backup generated on Monday will not be automatically deleted until Thursday.

  • The full backup generated on Tuesday will be automatically deleted on the following Wednesday. The reasons are as follows:

    The backup generated on Tuesday will expire on Thursday, but as it is the last backup, so it will be retained until a new backup expires. The next backup will be generated on the following Monday and will expire on the following Wednesday. So the full backup generated on Tuesday will not be automatically deleted until the following Wednesday.

• Backup Cycle: By default, each day of the week is selected.
  • All: Each day of the week is selected. The system automatically backs up data every day.
  • Select a cycle: You can select one or more days in a week. The system automatically backs up data at the specified time.
  

  A full backup starts within one hour of the time you specify. The amount of time required for the backup depends on the amount of data to be backed up. The more data has to be backed up, the longer it will take.

• After the DB instance is created, you can modify the automated backup policy as needed. You can change the time window after the DB instance is created. The system backs up data based on the automated backup policy you have set.
• After the automated backup policy is disabled, any automated backups in progress stop immediately.

Modifying an Automated Backup Policy

1. Log in to the management console.
2. In the service list, choose Databases > GeminiDB Cassandra API.
3. On the Instances page, click the instance whose backup policy you want to modify and click its name.
4. Choose Backups & Restorations in the navigation pane one the left, and click Modify Backup Policy. In the displayed dialog box, set the backup policy and click OK.
   For details, see Automated Backup Policy.

   Figure 2 Modifying the backup policy
   

5. Check or manage the generated backups on the Backups or Backups & Restorations page.

Disabling an Automated Backup Policy

1. Log in to the management console.
2. In the service list, choose Databases > GeminiDB Cassandra API.
3. On the Instances page, locate the instance that you want to disable automated backup for and click its name.
4. Choose Backups & Restorations in the navigation pane one the left, and click Modify Backup Policy.
5. In the displayed dialog box, click to disable automated backup and click OK.
   Figure 3 Disabling automated backup
   
   When your disable automated backup, specify whether to delete the automated backups:

   • If you select Delete automated backups, all backup files within the retention period will be deleted. There are no automated backups displayed until you enable automated backup again.
   • If you do not select Delete automated backups, backup files within the retention period will be retained, but you can still manually delete them later if needed. For details, see Deleting an Automated Backup.

   If automated backup is disabled, any automated backups in progress stop immediately.

Deleting an Automated Backup

If automated backup is disabled, you can delete stored automated backups to free up storage space.

If automated backup is enabled, the system will delete automated backups when they expire. You cannot delete them manually.

Deleted backups cannot be recovered. Exercise caution when performing this operation.

• Method 1
  1. Log in to the management console.
  2. In the service list, choose Databases > GeminiDB Cassandra API.
  3. On the Instances page, click the instance whose automated backups you want to delete and click its name.
  4. Choose Backups & Restorations in the navigation pane on the left, locate the backup you want to delete and click Delete in the Operation column.
  5. In the displayed dialog box, confirm the backup details and click Yes.
• Method 2
  1. Log in to the management console.
  2. In the service list, choose Databases > GeminiDB Cassandra API.
  3. On the Backups page, locate the backup that you want to delete and click Delete in the Operation column.
  4. In the displayed dialog box, confirm the backup details and click Yes.