The multi-level storage pool feature of Database Backup allows data backups to be automatically replicated across storage pools. You can manage on-premises and cloud databases with ease and share data backups among storage pools by configuring backup policies that use multi-level storage pools. This enhances security and reduces backup costs.

Background information

In hybrid cloud scenarios, you must store database backups in multiple storage pools such as cloud databases and on-premises network attached storage (NAS) systems. The multi-level storage pool feature enables storage pool-specific management, scheduling, validation, and backup retention period configuration to meet your business requirements.

Terms

Term Description
data source The data entity to be backed up, such as an ApsaraDB RDS for MySQL instance, a self-managed Oracle database, or specific files. For more information, see Add a data source.
backup policy A policy that allows you to specify parameters such as backup cycle, retention period, and replication method when full backup, incremental backup, or log backup is performed on a data source. Backup policies allow you to batch back up specific data sources based on business scenarios. For more information, see Configure a multi-level backup policy.
dump The process during which data backups are replicated from one storage pool to another.
storage pool The storage medium of data backups.
  • Level-1 storage pool: Backups of the data source are first stored in level-1 storage pools.
    Note To ensure backup performance, Database Backup allows you to specify level-1 storage pools only in the same region as the data source.
  • Level-2 storage pool: Backups stored in level-1 storage pools are dumped to level-2 storage pools.
dump method The method based on which backups are dumped. The following dump methods are supported:
  • Periodic dump: dumps the latest and undumped backup sets based on a specific cycle. If no qualified backup sets exist when the specific point of time is reached, the system continues to monitor the creation of backup sets and perform a dump immediately when a backup set is created.
  • Event trigger: When full or incremental backups are complete in the level-1 storage pool, the system immediately dumps the backups to level-2 storage pools.

Supported data sources

Physical and logical backups of all types of data sources are supported. However, you can use backup schedules created only by using batch backup. For more information, see Back up one or more databases.

Typical scenarios

Scenario Description
Geo-redundancy You can use the multi-level storage pool feature to store backups across regions. For more information, see Geo-redundancy.

For example, geo-redundancy is implemented if you specify DBS built-in storage in the China (Beijing) region as the level-1 storage pool and DBS built-in storage in the China (Hangzhou) region as a level-2 storage pool.

Archiving You can use the multi-level storage pool feature to archive backups to your data center or a cloud-based storage pool.

For example, if you want to archive backups, you can set the data source to backups and configure a backup policy to perform full backups on a daily basis. You can specify DBS built-in storage in the China (Beijing) region as the level-1 storage pool in which generated backup sets are stored for seven days. You also need to specify your data center as a level-2 storage pool to which backup sets are dumped on a weekly basis.

Backup and migration to the cloud
  • Backups can be first stored in your data center and then be dumped to a cloud-based storage pool.
  • Backups can also be directly stored in a cloud-based storage pool.
Archiving at a specific frequency You can choose the frequency of archiving operations based on your needs.

Note

This feature is in public preview. To use this feature, join the DingTalk group whose ID is 32596162.

Billing

During the public preview, you are charged only for storage during dumps. The billing method is the same as that for ordinary backups. For more information, see Billing overview.

During the public preview, you are not charged for the use of level-two storage pools.

Procedure

  • If a backup schedule is not created, perform the following operations:
    1. Configure a multi-level backup policy. For more information, see Configure a backup policy.
    2. Create a backup schedule and select the backup policy configured in the preceding step. For more information, see Back up one or more databases.
  • If a backup schedule is created, perform the following operation:
    Configure a multi-level backup policy in the backup schedule. For more information, see Modify the backup policy of a backup schedule.
    Note You can use backup schedules created only by using batch backup.