The multi-level storage pool feature provided by DBS (DBS) is used to automatically replicate data backups that are stored in DBS to other storage pools. You can configure backup policies that use multi-level storage pools to manage on-premises storage pools and storage pools in the cloud. This way, data backups are stored in multiple storage pools. This enhances data security and reduces the costs of DBS resources.

Prerequisites

The data backups that you want to manage reside in one of the following regions that support the multi-level storage pool feature: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), and China (Shenzhen).

Announcement

The public preview period of the multi-level storage pool feature of DBS ended on June 20, 2022. This feature will be included in the infrastructure of DBS to provide services in scenarios such as cross-region backup and backup file download. For more information, see Notice on the end of the public preview of the multi-level storage pool feature.

Overview

In hybrid cloud scenarios, you must store database backups in multiple types of storage pools such as cloud storage and on-premises Network Attached Storage (NAS) file systems. The multi-level storage pool feature allows you to perform data management, scheduling, validation, and backup retention period configuration by storage pool to meet your business requirements.

Table 1. Terms
TermDescription
data sourceThe data entity that you want to back up. A data source can be an ApsaraDB RDS for MySQL database, a self-managed Oracle database, or specific files. For more information, see Add a data source.
storage poolThe storage medium in which data backups are stored. You can use the built-in storage spaces provided by DBS, Object Storage Service (OSS) buckets, or self-managed NAS file systems as storage pools. For more information, see Add and remove a storage pool.
backup policyA policy that allows you to back up data from multiple data sources at a time based on your business requirements. A backup policy contains configuration items such as the backup cycle, retention period, and replication method of full backups, incremental backups, and log backups.
backup policy that uses multiple levels of storage poolsA backup policy that allows you to back up data from data sources and store data backups to multiple levels of storage pools. You can apply the backup policy to a backup schedule.
  • Level-1 storage pool: Backups of a data source are stored in the specified level-1 storage pool.
  • Level-2 storage pool: Backups that are stored in the level-1 storage pool can be dumped to multiple level-2 storage pools.
dumpThe process during which data backups are replicated from one storage pool to another one.

Typical scenarios

ScenarioDescription
Geo-redundancyData is backed up in cloud storage services across regions.

For example, if a data source is deployed in the China (Beijing) region, you can implement geo-redundancy by specifying the built-in storage space provided by DBS in the China (Beijing) region as the level-1 storage pool and the built-in storage space provided by DBS in the China (Hangzhou) region as a level-2 storage pool.

ArchivingYou 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 configure a backup policy to perform full backup operations on a daily basis. You can specify the built-in storage space provided by DBS in the China (Beijing) region as the level-1 storage pool in which backups are stored for seven days. You can also specify your data center as a level-2 storage pool to which backups are dumped on a weekly basis.

Backup and migration to the cloud
  • You can configure backup tasks to back up data and store data backups in your data center, and then dump data backups to a cloud-based storage pool.
  • You can also configure backup tasks to back up data and directly store data backups in a cloud-based storage pool.
On-demand archiving in the same regionYou can specify the frequency of archiving operations based on your business requirements.

Procedure

  1. Log on to the DBS console. In the left-side navigation pane, click Backup Strategies. In the upper part of the page that appears, select a region.
  2. Click Add backup strategy on the Backup strategy list page.
    Note You can also modify an existing backup policy. After a backup policy is modified, backup schedules that were created based on the backup policy are not affected.
  3. On the Create Policy Template page, specify the backup policy name, backup method, and backup policy that is used to back up data into the level-1 storage pool.
    1. Specify a name for the backup policy.
    2. Select Logical Backup or Physical Backup. You cannot modify this parameter after the backup policy is created.
      Note
      • Logical Backup: You can perform a logical backup on ApsaraDB RDS instances, PolarDB instances, ApsaraDB for Redis instances, ApsaraDB for MongoDB instances, on-premises databases, and self-managed databases hosted on Elastic Compute Service (ECS) instances.
      • Physical Backup: You can perform a physical backup only on self-managed databases.

      You cannot modify this parameter after the backup policy template is created. For more information, see Database engines and features.

    3. Click Modify to the right of backup policy. In the dialog box that appears, set the parameters. Then, click OK.
      ParameterDescription
      Full Backup MethodThe method that is used to perform full backups. Valid values:
      • Periodic Backup: performs full backups on a specific periodic basis.
        Note If you set the Full Backup Method parameter to Periodic Backup, you must set the Full backup frequency parameter.
      • Single Backup
      Full backup frequency

      The interval at which full backups are performed. Default value: Every Week. You can perform one to seven full backups every week.

      Note This parameter is displayed only if you set the Full Backup Method parameter to Periodic Backup.
      Full Backup Cycle

      The days of the week when full backups are performed. You can select one or more days of a week.

      Start At
      The start time of each full backup. You can select an exact hour of the day.
      Note If a previous full data backup is not complete at the start time of the next backup, DBS skips the next backup.
      Incremental Backup Interval

      The interval at which incremental backups are performed. Unit: minutes. Valid values: 10, 20, 30, 40, 50, and 60. Default value: 10. If you set the interval to 10 minutes, DBS performs an incremental backup every 10 minutes.

      Note
      • This parameter is displayed only if you select Physical Backup.
      • If you select Logical Backup and enable the incremental backup feature for databases such as MySQL databases, incremental backups are performed in real time.
    4. Click Modify to the right of Level-1 Storage Pool (Backup). In the dialog box that appears, set the parameters to specify a level-1 storage pool. Then, click OK.
      ParameterDescription
      Storage TypeThe type of the storage that you want to use. Valid values: DBS Storage, NAS, and OSS For User.
      Note
      • You can back up data to Network Attached Storage (NAS) file systems or Object Storage Service (OSS) buckets only if you use the logical backup method and have joined the public preview.OSS For User
      • If the Storage Type parameter is set to NAS for the level-1 storage pool, you cannot configure a level-2 storage pool.
      • If you have joined the public preview and you need to set this parameter to NAS or OSS For User, you must add NAS files systems or OSS buckets as DBS storage pools in advance.
      Storage Pool

      The storage pool in which data backups are stored. You must select a storage pool that resides within the same region as the data source.

      Note You cannot modify this parameter after the backup policy template is created.
      Retention Period

      The duration for which full backups are retained. Valid values: 1 Week, 1 Month, 1 Quarter, 6 Months, 1 Year, 2 Years, 3 Years, 4 Years, 5 Years, 6 Years, 7 Years, 8 Years, 9 Years, and 10 Years. Default value: 2 Years.

      Encryption MethodSpecifies whether and how to encrypt backups. Default value: Built-in encryption. Valid values:
      • Built-in Encryption: Backups are encrypted.

        The server-side encryption feature is used in OSS. When you upload an object to OSS, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. For more information, see Server-side encryption.

      • Non-encrypted: Backups are not encrypted.
  4. Move the pointer over the Add a level-2 storage pool icon and click Dump.
    Note To configure level-2 storage pools, you must obtain the public preview qualification of the multi-level storage pool feature. If you have not obtained the public preview qualification, this feature is unavailable. For more information, see Notice on the end of the public preview of the multi-level storage pool feature.
    1. Click Modify to the right of Dump Policy. In the dialog box that appears, set the parameters. Then, click OK.
      Table 2. Parameters that are used to configure a dump policy
      ParameterDescription
      Full Dump MethodThe method that you want to use to dump backups. Valid values:
      • Periodic Backup: DBS dumps the most recent full backup set that is not dumped to level-2 storage pools on a periodic basis. If no new backup sets exist when the specified point in time is reached, DBS continues to monitor the creation of backup sets and performs a dump immediately after a backup set is created.

        For example, you can configure DBS to perform a full backup operation and store full backups in the level-1 storage pool every day, and dump backups to level-2 storage pools every Sunday. In this case, DBS dumps only the most recent full backup set to level-2 storage pools every Sunday.

      • Event Trigger: When a full or incremental backup is stored in the level-1 storage pool, DBS immediately dumps the backup to level-2 storage pools.
      Note If you set the Full Backup Method parameter to Periodic Backup, you must set the Full Dump Cycle and Full Dump Start At parameters.
      Full Dump FrequencyThe interval at which you want to dump backups.
      • If you set the Full Dump Method parameter to Periodic Backup, you can set this parameter to one of the following values:
        • Every Week: This is the default value. You can specify one or more days of a week.
        • Every Month: You can specify one or more days from the first day to the 28th day of a month.
        • Every Year: You can select a specific day of a year. For example, you can specify January 1. You cannot specify more than one day.
      • If you set the Full Dump Method parameter to Event Trigger, this parameter is set to Event Trigger by default.
      Full Dump CycleThe days of the week when you want to dump full backups.

      This parameter is displayed only if you set the Full Dump Method parameter to Periodic Backup.

      Full Dump Start AtThe start time of each dump operation.

      This parameter is displayed only if you set the Full Dump Method parameter to Periodic Backup.

      Incremental DumpSpecifies whether to dump incremental backups. If you enable this feature, DBS dumps incremental backups from the level-1 storage pool to level-2 storage pools.
    2. Click Modify to the right of Level-2 Storage Pool (Dump). In the dialog box that appears, set the parameters to specify a level-2 storage pool. Then, click OK.
      Table 3. Parameters that are used to specify a level-2 storage pool
      ParameterDescription
      Storage ClassThe type of the storage that you want to use. Valid values: DBS Storage, NAS, and OSS For User.

      Before you set this parameter to NAS or OSS For User, you must add the OSS buckets or NAS file systems that you want to use to the storage pool list. For more information, see Add and remove a storage pool.

      You can dump data backups to NAS file systems or OSS buckets only if you use the logical backup method.

      Storage PoolThe storage pool to which you want to dump backups. You cannot modify this parameter after the backup policy is created.
      • You can dump backups across regions. For example, you can specify the built-in storage space provided by DBS in the China (Hangzhou) region as the level-1 storage pool and the built-in storage space provided by DBS in the China (Beijing) region as a level-2 storage pool.
      • You can also dump backups across storage mediums. For example, you can specify the built-in storage space provided by DBS in the China (Hangzhou) region as the level-1 storage pool and an on-premises NAS file system as a level-2 storage pool.
      Retention PeriodThe duration for which you want to retain backups in the storage pool. The default value is 2 Years, the maximum value is 10 Years, and the minimum value is 1 Week. For more information, see How do I manage the lifecycle rules of backup sets?.
      Encryption MethodThe method that you want to use to encrypt data. Valid values:
      • Built-in Encryption: Backups are encrypted.

        The server-side encryption feature is used in OSS. When you upload an object to OSS, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. For more information, see Server-side encryption.

      • Non-encrypted: Backups are not encrypted.
  5. Optional:Configure other level-2 storage pools. Perform the steps that are described in Step 4 to configure other level-2 storage pools that you want to use.
  6. Click OK.
    A backup policy that uses multiple levels of storage pools is created.

What to do next

  • Back up a database: Select the created backup policy template when you create a backup schedule to back up the database. For more information, see Back up databases.

  • View, modify, clone, or delete the created backup policy template on the Backup strategy list page.
    • After you modify the backup policy template, you can apply it only to the backup schedules that are created after the modification. Backup schedules that are created before the backup policy template is modified are not affected.

      You can modify the backup policy configured for a backup schedule in the Running state. For more information, see Modify the backup policy of a backup schedule.

    • If the backup policy template is associated with a backup schedule, you cannot delete the backup policy template.