The page has been translated by Gen AI.

Backing up and restoring the DB

Users can configure backups of PostgreSQL (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.

Backing up PostgreSQL(DBaaS)

PostgreSQL (DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.

Configure backup

For backup configuration of PostgreSQL(DBaaS), refer to PostgreSQL(DBaaS) 생성하기.

To modify the backup settings of the created resource, follow the steps below.

Caution
  • For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity.

  • Especially when the backup data exceeds 100 GB and undergoes frequent changes, please provision additional storage amounting to about 60 % of the data size.

  • For instructions on adding and expanding storage, refer to the PostgreSQL(DBaaS) Add Storage and PostgreSQL(DBaaS) Expand Storage guides.

  • If a backup is configured, it will run at the designated time after the set schedule, and additional fees will be incurred based on the backup size.

  • If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.

To set up a backup, follow these steps.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. PostgreSQL(DBaaS) List page, click the resource you want to configure backup for. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Edit button of the backup item. 4. Backup Settings popup window opens.
  5. When setting up a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, and then click the Confirm button.
    • If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
      Once user authentication is complete, the backup configuration is disabled and backup execution stops.

Check Backup History

guide
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on setting up notification policies, refer to 알림 정책 생성하기.

To view the backup history, follow these steps.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup file

Caution
Backup files cannot be restored after deletion. Please be sure to verify whether the data is unnecessary before deleting it.

To delete the backup history, follow these steps.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. Navigate to the PostgreSQL (DBaaS) List page.
  3. PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
    • When user authentication is completed, the backup file is deleted.

PostgreSQL(DBaaS) Recover

If a failure or data loss requires restoration from a backup file, you can recover using the recovery feature based on a specific point in time. When performing a PostgreSQL (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds with the database’s configuration information and data.

Caution
Performing recovery requires at least the same amount of space as the Disk capacity of the data type. If there is insufficient disk space, recovery may fail.

To recover PostgreSQL (DBaaS), follow these steps.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. PostgreSQL(DBaaS) resource Click the resource you want to restore on the list page. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TypeRequiredSet the point in time the user wants to recover
    • Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
    • Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
    server name prefixEssentialRecovery DB server name
    • must start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to input 3 to 16 characters
    • A postfix such as 001, 002 is appended to the base server name, generating the actual server name
    Cluster nameRequiredCluster name of the recovery DB
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeRequiredServer type for the recovery DB installation
    • Standard: standard specifications commonly used
    • High Capacity: large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
    • Basic OS: Area where the DB engine is installed
    • DATA: Storage area for table data, archive files, etc.
      • Same as the storage type set in the original cluster
      • Enter capacity as a multiple of 8 within the range 16 to 5,120
    • Additional: Storage area for DATA, Archive, TEMP, Backup data
      • Same as the storage type set in the original cluster
      • In the recovery DB, only DATA, TEMP, and Archive purposes can be added.
      • After selecting Use, enter the storage purpose and capacity
      • To add storage, click the Add button; to delete, click the x button
      • Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
    Database usernameRequiredDatabase username configured in the source DB
    Database Port numberRequiredDatabase port number configured in the source DB
    IP access controlSelectIP address for accessing the recovery DB
    • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.1/32, 192.168.10.1/32), then click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • If you select Use, set the day of week, start time, and duration
    • It is recommended to set a maintenance window for stable DB management. Patch operations will be performed at the scheduled time, causing service interruption
    • If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
    TagSelectAdd Tag
    • Add Tag after clicking the button Enter or select Key, Value values
    Table. PostgreSQL (DBaaS) recovery configuration items
DB Service Manage
Configure Read Replica