Available in VPC
In Backup, you can check the backup information configured per server for safe storage of cache data for users using Cloud DB for PostgreSQL. Also, when the cache data is damaged due to a failure, you can perform restoration using the backup file that was in storage. To use the backup and restoration, it is recommended to first understand the basic execution rules for the backup provided by Cloud DB for PostgreSQL. The basic backup execution rules are as follows:
- Backup execution methods
- Performed daily, once a day
- Select between automatic settings and user-defined settings
- Automatic settings: Settings: Backups are performed within 15 minutes from 00:00
- User-defined settings: Backups are performed within 15 minutes from the time selected by the user
- Exceptional situations
- Backup is performed within 30 minutes from the DB creation.
- When DB settings change, the backup is performed up to 5 minutes after the backup time
- Backup file
- Retention period: You can store for up to 30 days according to the user settings.
- For example, if the retention limit is set, keep backups at the maximum condition between the duration and quantity
- Under the retention settings with 10 days and 7 items, performing a daily backup should result in storing 10 backups
- Under the retention settings with 10 days and 7 items, performing a backup once every two days should result in storing 7 backups
- For example, if the retention limit is set, keep backups at the maximum condition between the duration and quantity
- Storage location: Separate data storage (storage contracts are made according to the backup file size)
- Retention period: You can store for up to 30 days according to the user settings.
- If you have made configuration changes at the DB Server level, the backup scheduler intentionally delays the backup for a certain period to ensure backup stability.
- Although the default policy is to perform backups daily, the actual timing may vary depending on data size and whether compression is enabled.
- During service improvement operations, an ongoing backup may be restarted if necessary.
Backup page
The basics of using the backup are as follows:

| Component | Description |
|---|---|
| ① Menu name | Shows the current menu name. |
| ② Basic features | Check details for Cloud DB for PostgreSQL and refresh the Backup page. |
| ③ Backup list | Configured backup settings per server and settings information |
Check backup settings list
You can check the backup settings list per PostgreSQL Server in operation. To check the backup settings list:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB for PostgreSQL. - Click the Backup menu.
- When the backup settings list appears, check the required information.
- DB Service name: Service name specified by the user
- Backup retention date: Maximum number of days for the backup file to be stored in data storage
- Number of backups: The quantity of backup files to be retained (keep backups at the maximum condition between the duration and quantity)
- Backup start time: The time that the daily backup is performed ("AUTO" if set to automatic)
- Backup data size: Size of the completed backup file
- Latest backup date: Date for the latest backup that was performed
- View details: Details and restoration of the backup file list created per server, saved to Object Storage.
Check backup file list per server
To check the backup file list created for each server after completing the backup:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB for PostgreSQL. - Click the Backup menu.
- Click [Details] from View details of the backup settings row you want to check the details for.
- Check the details for the backup file.
- Backup date: Date that the backup was performed
- Backup start time: Time when the backup was started
- Backup completion time: Time when the backup was completed
- Run time: Time it took for the backup to be completed.
- Backup file size: Size of the created backup file upon completion of backup (MB)
- Archived Wal File size: Size of the archived Wal file created upon completion of backup (MB)
- Capacity expected to be required for restoration: size of the expected disk size if the server is to be recovered with the backup file
Backup method
Cloud DB for PostgreSQL has changed its default backup method from pg_basebackup to pgBackRest to ensure stable data protection. By changing the backup method, backup efficiency and recovery stability are improved, and backups are performed on either the primary or secondary depending on the operating environment.
- Before the 2025.09.18 release: pg_basebackup
- Backup tools provided by PostgreSQL by default
- In large-scale databases, limitations such as performance degradation and insufficient management features occur.
- After the 2025.09.18 release: pgBackRest
- High-performance backup and recovery tools with third-party open source
- Improved backup efficiency and recovery stability
Changes according to the backup method
After the 2025.09.18 release, pgBackRest-based backups are performed according to the following conditions:
- Case 1) If port 20021 is not open on any server within the cluster, the backup is performed on the Primary server.
- Case 2) If all servers within the cluster can communicate through port 20021, backup can be performed on the Secondary server.
- Case 1) The load on the Primary server may increase.
- Case 2) Without adding load to the Primary server, backup can be performed on the Secondary server.
How to configure the ACG for the Secondary server
To configure the ACG (Access Control Group) to perform backups on the Secondary server:
- Clusters created after the 2025.09.18 release automatically have the ACG applied.
- Clusters created before the 2025.09.18 release must configure the ACG as follows:
1. Check the ACG rules of all servers in the cluster.
2. Add the following rules to both Inbound and Outbound:- Protocol: TCP
- Access source: ACG name of the DB cluster
- Port: 20021

Restoration
Cloud DB for PostgreSQL provides a service that enables you to restore lost data using backup files, and create PostgreSQL Servers easily and quickly. It allows the user to restore the data up to the desired time within the range available for recovery. To restore:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB for PostgreSQL. - Click the Backup menu.
- Click [Details] in the backup settings row you want to restore.
- Click [Point-in-time recovery].

- When the Point-in-time recovery popup window appears, check or enter the required information for restoration.
- Available DB restoration time: range of time available for restoration (maximum backup retention setting value)
- DB restoration time: Point in time to restore to
- Subnet: subnet to be used by the server to be restored
- DB Server Type: PostgreSQL Server type to restore
- DB Server name: PostgreSQL Server name to restore
- DB Service name: PostgreSQL Services name to restore
- Data storage type: the type of data storage to restore
- Click [Restore].
- Click [OK].
- Click PostgreSQL Server.
- Check the status of the server restoration.
- Creating: status in which the PostgreSQL is being created (restored) with the information entered by the user
- Configuring: status in which the PostgreSQL server is being created (restored) for configuration with the information entered by the user
- Running: status in which the creation (restoration) and configuration of the PostgreSQL server has been completed with the information entered by user, and access to PostgreSQL from the application servers is available
The completion of the server restoration may take a certain amount of time (minutes).
Store in Object Storage
In Cloud DB for PostgreSQL, you can store the created backup files in Object Storage and use them when performing backup. To save a stored backup file to Object Storage:
Additional fees apply when you subscribe to Object Storage. For more information on Object Storage and its pricing plans, see Service > Storage> Object Storage in NAVER Cloud Platform portal.
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB for PostgreSQL. - Click the Backup menu.
- Click [See details] of the backup settings row for the backup file you want to save to Object Storage.
- Click [Send to Object Storage].

- When the Send to Object Storage popup window appears, click and select the bucket you want to save into.

- Click [Send to Object Storage].
- Click [OK].
- When sending to Object Storage, unlocking bucket, appropriate access control, and ACL settings are required.
- For the Japan Region, disable access control settings for the Object Storage bucket.
- Sending to Object Storage may take a certain amount of time (minutes) to be completed.
- The feature to restore in Cloud DB for PostgreSQL with the backup file from the Object Storage is currently not supported, but will be provided in the future.
- You can restore easily by using the automatic backup feature of the Cloud DB for PostgreSQL.