Help Center/ GeminiDB/ GeminiDB Redis API/ Working with GeminiDB Redis API/ Data Backup/ Managing Automated Backups
Updated on 2024-10-11 GMT+08:00
View PDF

Managing Automated Backups

GeminiDB Redis allows you to create automated backups to protect your data. If a database or table is deleted, maliciously or accidentally, backups can help recover your data.

Configuring an Automated Backup Policy

Automated backups are generated based on a backup policy and saved as packages in OBS buckets to secure and protect your data. Regularly backing up your database is recommended. If your database becomes faulty or data is corrupted, you can restore it from backup. 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.

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

Figure 1 Modifying backup policies

  • Retention Period: Automated backup files are saved for seven days by default. Full backups are retained till the retention period expires.
    • 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 daily.
    • The system checks existing automated backups and deletes any backups that exceed the backup retention period you configure.
    • Time Window: A one-hour period the backup will be scheduled for, such as 04:00–05: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. For instance, a backup generated on Monday will be deleted on Wednesday; or a 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:

    • A 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: All options are selected by default.
    • 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.
  • If the automated backup policy is disabled, any automated backups in progress stop immediately.

Modifying an Automated Backup Policy

  1. Log in to the GeminiDB console.
  2. In the service list, choose Databases > GeminiDB.
  3. On the Instances page, click the instance whose backup policy you want to modify.
  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. Then, click OK.

    For details about how to set a backup policy, see Configuring an Automated Backup Policy.

    Figure 2 Modifying a backup policy

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

Disabling Automated Backup

  1. Log in to the GeminiDB console.
  2. In the service list, choose Databases > GeminiDB.
  3. On the Instances page, click the instance whose backup policy you want to modify.
  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 the backup policy and click OK.

    Figure 3 Disabling backup policies

    When disabling the automated backup policy, you can decide whether to delete the automated backups by selecting Delete automated backups.
    • If you select it, all backup files within the retention period will be deleted. No automated backups are displayed in the backup list until you enable the automated backup policy again.
    • If you do not select it, all 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 as 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 GeminiDB console.
    2. In the service list, choose Databases > GeminiDB.
    3. On the Instances page, click the instance whose backup you want to delete.
    4. On the Backups & Restorations page, locate the backup you want to delete and click Delete.
    5. In the Delete Backup dialog box, confirm the backup details and click Yes.
  • Method 2
    1. Log in to the GeminiDB console.
    2. In the service list, choose Databases > GeminiDB.
    3. On the Backups page, locate the backup that you want to delete and click Delete.
    4. In the Delete Backup dialog box, confirm the backup details and click Yes.

Setting the Policy for Restoring Data to a Specified Time Point

  1. Log in to the GeminiDB console.
  2. In the service list, choose Databases > GeminiDB.
  3. On the Instances page, click the target instance.
  4. Choose Backups & Restorations in the navigation pane one the left, and click Point in Time Restoration. After the setting is complete, click OK.

    Figure 4 Setting the policy for restoring data to a specified time point

    • You can toggle on or off Enable to enable or disable the backup function.
    • Backup Interval refers to the time interval, in minutes, for automated backups. The value ranges from 5 to 120. For example, if the initial backup is scheduled for 04:00, the subsequent backup will take place at 04:05.
    • Retention Period determines how long automated backups are kept in days. The value ranges from 1 to 7. Full backups are retained till the retention period expires.

Parent topic: Data Backup