Updated on 2023-11-21 GMT+08:00

Overview

GeminiDB Cassandra API supports instance backups and restorations to ensure data reliability. After an instance is deleted, the manual backup data is retained. Automated backup data is released together with instances. Backup data cannot be downloaded or exported.

Backup Methods

Both automatic backup and manual backup are supported.

  • Automated backup

    You can click Modify Backup Policy on the GeminiDB console, and the system will automatically back up your instance data based on the time window and backup cycle you set in the backup policy and will store the data for the retention period you specified.

    Automated backups cannot be manually deleted. You can adjust their retention period by referring to Modifying an Automated Backup Policy, and backups that expire will be automatically deleted.

  • Manual backup

    A manual backup is a full backup of a DB instance and can be retained until you manually delete it. Manual backup can be triggered at any time to meet your service requirements.

    Regularly backing up your database is recommended. If your database becomes faulty or data is corrupted, you can restore it from backups.

    Table 1 Backup methods

    Method

    Scenario

    Automated backup

    After you set a backup policy, the system automatically backs up your database based on the policy. You can also modify the policy based on service requirements.

    Manual backup

    You can enable full backup for your instance based on service requirements.

    Cross-region backup

    GeminiDB Cassandra API allows you to store backups in the destination region. Then for disaster recovery, you can restore the backups to a new instance in another region.

    Creating a Table-level Backup

    If a database or table is deleted maliciously or accidentally, you can use backups to restore data.

How Backup Works

GeminiDB Cassandra provides a dedicated node (seed) responsible for managing backups. As shown in the following figure, a GeminiDB Cassandra cluster chooses the seed node for backing up data. The node takes snapshots of data in seconds and then stores them as compressed backups in OBS buckets, without using any store space of your instance. The CPU usage may increase 5% to 15% because uploading backups consumes CPU resources.

Figure 1 Backup process

Backup Storage

Backups are stored in OBS buckets, providing disaster recovery and saving space.

After you purchase an instance, GeminiDB Cassandra API will provide additional backup storage of the same size as you purchased. For example, if you purchase an instance of 100 GB, you will obtain additional backup storage of 100 GB free of charge. If the size of backup data does not exceed 100 GB, the backup data is stored on OBS free of charge. If the size of the backup data exceeds 100 GB, you will be charged based on the OBS billing rules.