Accidental deletions and operational errors can leave your database in an inconsistent or unrecoverable state. AnalyticDB for PostgreSQL Serverless Pro mode protects your data with automatic and manual backups, and lets you restore any backup to a new instance for disaster recovery or troubleshooting.
Billing
Backup data consumes instance storage space. For pricing details, see Serverless Pro.
Back up data
AnalyticDB for PostgreSQL Serverless Pro mode supports two backup types:
| Backup type | Trigger | When to use |
|---|---|---|
| Automatic | Runs on the schedule defined in your backup policy | Ongoing data protection with minimal manual effort |
| Manual | Triggered on demand from the console | Before major schema changes or high-risk operations |
Only instances in the running state can be backed up. Schedule automatic backups during off-peak hours to minimize performance impact.
View and modify the automatic backup policy
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the instance and click its ID.
In the left navigation pane, click Backup and Restoration.
Click the Backup Settings tab to view the current backup policy.
To modify the policy, click Modify Backup Settings.
In the Backup Settings panel, configure the following parameters.
Parameter Description Data Backup Retention Period (Days) Number of days to retain backup data. Valid values: 1 to 7. During the public preview, the maximum is 7 days. Data Backup Cycle Days of the week on which backups run. Select at least one day. Data Backup Time Time range when the backup starts. Example: 05:00–06:00. Set this to off-peak hours. Data Backup Frequency Settings Enables or disables the high-frequency backup and restoration feature, which supports point-in-time recovery (PITR). If disabled, you cannot restore to a specific point in time. Use caution when you disable it. Data Backup Frequency Interval between backups. The next backup starts after the current one completes. Click OK.
Create a manual backup
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the instance and click its ID.
In the left navigation pane, click Backup and Restoration.
On the Backup and Restoration page, click Create Backup.
In the dialog box, click OK.
The backup job starts within one minute. The time required depends on the amount of data. After the job completes, refresh the page to view the results.
View backup jobs
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the instance and click its ID.
In the left navigation pane, click Backup and Restoration.
Click the
icon on the right to view the list of backup jobs.
View backup sets
A backup set is a full copy of all data in the database, stored in Object Storage Service (OSS). The default retention period is 7 days.
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the instance and click its ID.
In the left navigation pane, click Backup and Restoration.
On the Data Backup tab, view information about the base backup set. The Consistency Point in Time column shows the point in time to which you can restore the instance from this backup set while keeping the database in a consistent state.
Restore data
Restoration creates a new instance from a backup set.
Before you begin
Make sure the new instance meets the following requirements before starting the restore:
| Requirement | Detail |
|---|---|
| Region | Same region as the source instance |
| Resource type | Serverless Pro mode |
| Serverless Cache Size | Greater than or equal to that of the source instance |
Restore to a new instance
Log on to the AnalyticDB for PostgreSQL console. In the upper-left corner, select a region. Find the instance and click its ID.
In the left navigation pane, click Backup and Restoration.
On the Data Backup tab, find the target backup set and click Restore To New Instance in the Actions column.
On the Clone Instance page, configure the required parameters.
Click Buy Now.
Data is copied when the new instance is created. The time required depends on the data volume of the source instance. Wait for the process to complete.