ApsaraDB RDS for PostgreSQL provides the high-frequency snapshot backup feature. You can specify a backup frequency that ranges from 15 minutes to 12 hours for your ApsaraDB RDS for PostgreSQL instance to increase the backup frequency.
Prerequisites
An RDS instance that uses enhanced SSDs (ESSDs) is created. Serverless RDS instances is not supported.
If this is the first time you use the backup feature of ApsaraDB RDS, you must attach the AliyunServiceRoleForDBS policy by using your Alibaba Cloud account. For more information, see How do I create a service-linked role for DBS?
Billing rules
If the total size of backup files does not exceed the free quota on backup storage, no backup storage fees are generated. If the total size of the backup files of your RDS instance exceeds the free quota, you are charged for the excess backup storage that you use. For more information, see Backup storage fees.
Feature description
If you do not enable the high-frequency snapshot backup feature, you can set the snapshot backup frequency to once a day.
If you enable the high-frequency snapshot backup feature, you can specify a backup frequency that ranges from 15 minutes to 12 hours based on your business requirements.
The snapshot retention policy changes based on the snapshot backup frequency.
Snapshot backup frequency | Snapshot retention policy |
Minutes | If you set the snapshot backup frequency to a value at the minute granularity, all snapshots that are completed within 1 hour are retained. For snapshots that are generated 1 hour ago, ApsaraDB RDS deletes the snapshots except for the first snapshot after the hour. For snapshots that are generated 24 hours ago, ApsaraDB RDS deletes the snapshots except for the first snapshot after 00:00 every day. For example, if you set the snapshot backup frequency to 15 minutes, four snapshots are generated within 1 hour and all snapshots are retained. For snapshots that are generated within the range of 1 to 24 hours, the first snapshot that is completed in each hour is retained, and a total of 23 snapshots are retained within the range. For snapshots that are generated within the range of 24 hours to 7 days, the first snapshot that is completed on each day is retained, and a total of 6 snapshots are retained within the range. In this example, if you set the snapshot backup frequency to 15 minutes, a total of 33 snapshots are retained within a week. |
Hours | If you set the snapshot backup frequency to a value at the hour granularity, all snapshots that are completed within 24 hours are retained. For snapshots that are retained for more than 24 hours, ApsaraDB RDS keeps only the first snapshot after 00:00 every day. For example, if you set the snapshot backup frequency to 6 hours, four snapshots are generated within 24 hours and all snapshots are retained. For snapshots that are generated within the range of 24 hours to 7 days, the first snapshot that is completed on each day is retained, and a total of 6 snapshots are retained within the range. In this example, if you set the snapshot backup frequency to 6 hours, a total of 10 snapshots are retained within a week. |
For more information about snapshot retention policies, see Manage the snapshots that are generated by the high-frequency snapshot backup feature.
Enable the high-frequency snapshot backup feature
In the left-side navigation pane of the details page of your RDS instance, click Backup and Restoration. On the Backup Strategy tab of the page that appears, click Edit in the Data Backup Settings section to specify a snapshot backup frequency.
Before you can use this feature, you must enable the Single-digit Second Backup feature. If the single-digit second backup feature is disabled, ApsaraDB RDS automatically enables the single-digit second backup feature when you enable the high-frequency snapshot backup feature.
For more information about other parameters, see Back up an ApsaraDB RDS for PostgreSQL instance.
Related operations
Operation | Description |
Modifies the backup settings of an instance. To specify a snapshot backup frequency, you must configure the BackupInterval parameter. |