Database

• 1: EPAS(DBaaS)
• 1.1: Overview
• 1.1.1: Server Type
• 1.1.2: Monitoring Metrics
• 1.2: EPAS(DBaaS) Creation Guide
• 1.2.1: Connection
• 1.2.2: Managing
• 1.2.3: Read Replica
• 1.2.4: DB Backup and Recovery
• 1.2.5: Extension use
• 1.3: API Reference
• 1.4: CLI Reference
• 1.5: Release Notes
• 2: PostgreSQL(DBaaS)
• 2.1: Overview
• 2.1.1: Server Type
• 2.1.2: Monitoring Metrics
• 2.2: How-to guides
• 2.2.1: Managing DB Service
• 2.2.2: DB Backup and Restore
• 2.2.3: Configuring Read Replica
• 2.2.4: Connecting to DB Server
• 2.2.5: Using Extensions
• 2.3: API Reference
• 2.4: CLI Reference
• 2.5: Release Note
• 3: MariaDB(DBaaS)
• 3.1: Overview
• 3.1.1: Server Type
• 3.1.2: Monitoring Metrics
• 3.1.3: ServiceWatch Metrics
• 3.2: How-to guides
• 3.2.1: Managing DB Service
• 3.2.2: DB Backup and Restore
• 3.2.3: Configuring Read Replica
• 3.2.4: MariaDB(DBaaS) Server Connection
• 3.3: API Reference
• 3.4: CLI Reference
• 3.5: Release Note
• 4: MySQL(DBaaS)
• 4.1: Overview
• 4.1.1: Server Type
• 4.1.2: Monitoring Metrics
• 4.1.3: ServiceWatch Metrics
• 4.2: How-to guides
• 4.2.1: MySQL(DBaaS) server connection
• 4.2.2: Manage DB Service
• 4.2.3: DB Backup and Recovery
• 4.2.4: Configure Read Replica
• 4.3: API Reference
• 4.4: CLI Reference
• 4.5: Release Note
• 5: Microsoft SQL Server(DBaaS)
• 5.1: Overview
• 5.1.1: Server Type
• 5.1.2: Monitoring Metrics
• 5.2: How-to guides
• 5.2.1: Managing DB Service
• 5.2.2: DB Backup and Recovery
• 5.2.3: Adding Secondary
• 5.2.4: Microsoft SQL Server(DBaaS) server connection
• 5.3: API Reference
• 5.4: CLI Reference
• 5.5: Release Note
• 6: CacheStore(DBaaS)
• 6.1: Overview
• 6.1.1: Server Type
• 6.1.2: Monitoring Metrics
• 6.2: How-to guides
• 6.2.1: Managing CacheStore Service
• 6.2.2: CacheStore Backup and Recovery
• 6.2.3: CacheStore(DBaaS) server connection
• 6.3: API Reference
• 6.4: CLI Reference
• 6.5: Release Note

1 - EPAS(DBaaS)

1.1 - Overview

EPAS (EnterpriseDB Postgres Advanced Server) is Oracle-compatible RDBMS based on PostgreSQL. Samsung Cloud Platform provides EPAS Database as a Service (DBaaS) allowing you to use EPAS without separate installation and management.

EPAS(DBaaS) Service

Service Overview

EPAS(DBaaS) is a fully managed database service that provides an easy-to-use environment for creating, configuring, and managing EPAS databases. You can focus on application development and business logic without worrying about database installation, patching, backup, and recovery.

Service Architecture

EPAS(DBaaS) consists of the following components:

• Database Cluster: A cluster of one or more database servers that provides high availability and load balancing
• Storage: Block storage for storing database data, archives, and backups
• Network: VPC-based network configuration for secure data transmission
• Monitoring: Integrated monitoring and alarming through ServiceWatch

Service Features

EPAS(DBaaS) provides the following features:

• Auto Provisioning: Automatically provision database servers with just a few clicks without manual installation
• Operation Control: Easily start, stop, and restart database servers
• Backup and Recovery: Automated backup and point-in-time recovery for data protection
• Version Management: Support for multiple EPAS versions with easy upgrades
• Replica: Create read replicas for scaling read operations
• Audit: Database audit logging for compliance and security
• Parameter: Database parameter management for performance tuning
• Monitoring: Real-time monitoring and alerting for database health
• User Management: Database user and permission management
• Access Control: IP-based access control for enhanced security
• Archive: Archive management for long-term data retention
• Log Export: Database log export for analysis and troubleshooting
• Migration: Easy migration from on-premises or other cloud databases
• OS Kernel Upgrade: Automated OS kernel upgrades for security and performance

Engine Versions

EPAS(DBaaS) supports the following EPAS versions:

• EPAS 14.17
• EPAS 15.11
• EPAS 16.4
• EPAS 17.6

Server Types

EPAS(DBaaS) provides the following server types:

• Standard: Standard specifications for general workloads
• High Capacity: Large capacity servers with 24+ vCPU for high-performance workloads

Prerequisites

To use EPAS(DBaaS), you must have a VPC configured in your project. For more information on creating a VPC, see VPC Creation Guide.

1.1.1 - Server Type

EPAS(DBaaS) Server Type

EPAS(DBaaS) provides server types with various combinations of CPU, Memory, Network Bandwidth, and more. When creating an EPAS(DBaaS), the Database Engine is installed according to the selected server type based on the intended use.

The server types supported by EPAS(DBaaS) are as follows:

Standard db1v2m4

db1 Server Type

The db1 server type of EPAS(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
• Supports up to 16 vCPUs and 256 GB of memory
• Up to 12.5 Gbps networking speed

dbh2 Server Type

The dbh2 server type of EPAS(DBaaS) is provided with high-capacity server specifications and is suitable for large-scale data processing database workloads.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 128 vCPUs and 1,536 GB of memory
• Up to 25Gbps networking speed

1.1.2 - Monitoring Metrics

EPAS(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics of EPAS (DBaaS) that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

EPAS(DBaaS) server monitoring metrics refer to the Virtual Server Monitoring Metrics guide.

1.2 - EPAS(DBaaS) Creation Guide

EPAS(DBaaS) Creation

You can easily create an EPAS database instance with just a few clicks through the Samsung Cloud Platform Console.

To create an EPAS(DBaaS) service, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the Create button. The Create EPAS(DBaaS) page will appear.
3. On the Create EPAS(DBaaS) page, enter the required information in each section and click the Complete button.

EPAS(DBaaS) Resource Management

Operation Control

You can control the operation status of EPAS(DBaaS) resources.

To control the operation status, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to control. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Start, Stop, or Restart button to control the operation status.

Service Status Synchronization

You can synchronize the service status displayed in the console with the actual service status.

To synchronize the service status, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the Refresh button to synchronize the service status.

Server Type Change

You can change the server type of an EPAS(DBaaS) resource.

To change the server type, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to modify. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Server Type Change button. The Server Type Change popup will appear.
5. Select the new server type and click the Confirm button.

Storage Addition

You can add additional storage to an EPAS(DBaaS) resource.

To add storage, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to modify. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Storage Addition button. The Storage Addition popup will appear.
5. Select the storage purpose, type, and capacity, then click the Confirm button.

Storage Expansion

You can expand the storage capacity of an EPAS(DBaaS) resource.

To expand storage, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to modify. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Storage Expansion button. The Storage Expansion popup will appear.
5. Enter the new storage capacity and click the Confirm button.

EPAS(DBaaS) Termination

You can terminate an EPAS(DBaaS) resource.

To terminate an EPAS(DBaaS) resource, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to terminate. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Terminate button. The Terminate popup will appear.
5. Enter the service name to confirm and click the Confirm button.

1.2.1 - Connection

This section explains how to connect to EPAS(DBaaS) using pgAdmin.

Connection Scenario

The scenario involves connecting to EPAS(DBaaS) through a Bastion host in a VPC environment.

Prerequisites

• VPC created
• Subnet created
• Public IP allocated
• Internet Gateway created and attached
• Security Group configured
• Virtual Server (Bastion host) created
• EPAS(DBaaS) created

Connection Steps

1. Create VPC

   Create a VPC to host the EPAS(DBaaS) and Bastion host.

2. Create Subnet

   Create a subnet within the VPC for the EPAS(DBaaS) and Bastion host.

3. Allocate Public IP

   Allocate a public IP for the Bastion host to allow external access.

4. Create and Attach Internet Gateway

   Create an Internet Gateway and attach it to the VPC to enable internet access.

5. Configure Security Group

   Configure the security group to allow access to the EPAS(DBaaS) from the Bastion host.

6. Create Virtual Server (Bastion Host)

   Create a Virtual Server to serve as the Bastion host.

7. Connect to EPAS(DBaaS) using pgAdmin

   Use pgAdmin to connect to the EPAS(DBaaS) through the Bastion host.

Detailed Connection Steps

1. Create VPC

1. Click All Services > Network > VPC menu.
2. Click the Create button.
3. Enter the VPC name and CIDR block.
4. Click the Confirm button.

2. Create Subnet

1. Click All Services > Network > Subnet menu.
2. Click the Create button.
3. Select the VPC created in step 1.
4. Enter the subnet name and CIDR block.
5. Click the Confirm button.

3. Allocate Public IP

1. Click All Services > Network > Public IP menu.
2. Click the Allocate button.
3. Select the VPC and subnet created in steps 1 and 2.
4. Click the Confirm button.

4. Create and Attach Internet Gateway

1. Click All Services > Network > Internet Gateway menu.
2. Click the Create button.
3. Select the VPC created in step 1.
4. Click the Confirm button.

5. Configure Security Group

1. Click All Services > Network > Security Group menu.
2. Click the Create button.
3. Enter the security group name and description.
4. Add inbound rules to allow access from the Bastion host to the EPAS(DBaaS) port.
5. Click the Confirm button.

6. Create Virtual Server (Bastion Host)

1. Click All Services > Compute > Virtual Server menu.
2. Click the Create button.
3. Select the VPC and subnet created in steps 1 and 2.
4. Select the public IP allocated in step 3.
5. Select the security group configured in step 5.
6. Click the Confirm button.

7. Connect to EPAS(DBaaS) using pgAdmin

1. Install pgAdmin on your local machine.
2. Open pgAdmin and create a new server connection.
3. Enter the connection information:
   • Host: EPAS(DBaaS) private IP address
   • Port: EPAS(DBaaS) port number (default: 5432)
   • Database: Database name
   • Username: Database username
   • Password: Database password
4. Click the Connect button to connect to the EPAS(DBaaS).

1.2.2 - Managing

This section explains how to manage EPAS(DBaaS) resources.

DB User Management

You can manage database users for EPAS(DBaaS).

Creating DB User

To create a database user, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the DB User Management button. The DB User Management popup will appear.
5. Click the Create button. The Create DB User popup will appear.
6. Enter the user name, password, and privileges, then click the Confirm button.

Modifying DB User

To modify a database user, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the DB User Management button. The DB User Management popup will appear.
5. Click the Modify button next to the user you want to modify. The Modify DB User popup will appear.
6. Modify the user information and click the Confirm button.

Deleting DB User

To delete a database user, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the DB User Management button. The DB User Management popup will appear.
5. Click the Delete button next to the user you want to delete. The Delete DB User popup will appear.
6. Click the Confirm button to delete the user.

DB Access Control Management

You can manage access control for EPAS(DBaaS).

Setting IP Access Control

To set IP access control, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the IP Access Control button. The IP Access Control popup will appear.
5. Enter the IP address or CIDR block and click the Add button.
6. Click the Confirm button to save the settings.

Modifying IP Access Control

To modify IP access control, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the IP Access Control button. The IP Access Control popup will appear.
5. Click the x button next to the IP address you want to delete.
6. Click the Confirm button to save the settings.

Archive Management

You can manage archive settings for EPAS(DBaaS).

Setting Archive

To set archive, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Archive button. The Archive popup will appear.
5. Enable or disable archive and configure the settings.
6. Click the Confirm button to save the settings.

DB Log Export

You can export database logs for EPAS(DBaaS).

Exporting DB Log

To export database logs, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to manage. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the DB Log Export button. The DB Log Export popup will appear.
5. Select the log type and date range, then click the Export button.

Minor Version Upgrade

You can upgrade the minor version of EPAS(DBaaS).

Upgrading Minor Version

To upgrade the minor version, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to upgrade. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Minor Version Upgrade button. The Minor Version Upgrade popup will appear.
5. Select the target version and click the Confirm button.

Migration Configuration

You can configure migration for EPAS(DBaaS).

Setting Migration

To set migration, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to migrate. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Migration button. The Migration popup will appear.
5. Enter the source database connection information and migration settings.
6. Click the Confirm button to start the migration.

OS Kernel Upgrade

You can upgrade the OS kernel for EPAS(DBaaS).

Upgrading OS Kernel

To upgrade the OS kernel, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource you want to upgrade. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the OS Kernel Upgrade button. The OS Kernel Upgrade popup will appear.
5. Review the upgrade information and click the Confirm button.

1.2.3 - Read Replica

This section explains how to configure read replicas for EPAS(DBaaS).

Creating Read Replica

You can create read replicas to scale read operations and improve performance.

To create a read replica, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the primary database resource you want to create a replica for. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Create Read Replica button. The Create Read Replica popup will appear.
5. Enter the following information:
   • Replica Name: Name of the read replica
   • Server Type: Server type for the replica
   • Storage: Storage configuration for the replica
6. Click the Confirm button to create the read replica.

Configuring Read Replica

You can configure the settings of a read replica.

Modifying Read Replica

To modify a read replica, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the read replica resource you want to modify. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Modify button. The Modify Read Replica popup will appear.
5. Modify the settings and click the Confirm button.

Promoting Read Replica

You can promote a read replica to a standalone primary database.

To promote a read replica, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the read replica resource you want to promote. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Promote button. The Promote Read Replica popup will appear.
5. Review the promotion information and click the Confirm button to promote the replica.

Deleting Read Replica

You can delete a read replica.

To delete a read replica, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the read replica resource you want to delete. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Delete button. The Delete Read Replica popup will appear.
5. Click the Confirm button to delete the read replica.

1.2.4 - DB Backup and Recovery

Users can configure backups for EPAS(DBaaS) through the Samsung Cloud Platform Console and recover using the backed up files.

EPAS(DBaaS) Backup

To ensure users’ data is safely stored, EPAS(DBaaS) provides data backup functionality based on its own backup commands. Additionally, you can verify whether backups were performed normally through the backup history feature and delete backed up files.

Setting Backup

For information on how to set up backups for EPAS(DBaaS), see EPAS(DBaaS) Creation Guide.

To modify the backup settings of a created resource, follow these steps:

To set up backup, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource for which you want to set up backup. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Modify button in the Backup section. The Backup Settings popup will appear.
5. To set up backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and archive backup cycle, then click the Confirm button.
   • To stop backup settings, uncheck Enable in the Backup Settings popup and click the Confirm button.

Checking Backup History

To view backup history, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource for which you want to check backup history. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Backup History button. The Backup History popup will appear.
5. In the Backup History popup, you can check the backup status, version, backup start date/time, backup completion date/time, and capacity.

Deleting Backup Files

To delete backup history, follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) List page, click the resource for which you want to check backup history. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Backup History button. The Backup History popup will appear.
5. In the Backup History popup, check the file you want to delete and click the Delete button.

EPAS(DBaaS) Recovery

If recovery using backup files is required due to failure or data loss, you can recover based on a specific point in time through the recovery function. When EPAS(DBaaS) recovery is performed, a new server is created with the OS image at the time of initial provisioning, the DB is installed with the version at that backup point, and recovery proceeds with the DB configuration information and data.

To recover EPAS(DBaaS), follow these steps:

1. Click All Services > Database > EPAS(DBaaS) menu. You will be directed to the Service Home page for EPAS(DBaaS).
2. On the Service Home page, click the EPAS(DBaaS) menu. You will be directed to the EPAS(DBaaS) List page.
3. On the EPAS(DBaaS) Resource list page, click the resource you want to recover. You will be directed to the EPAS(DBaaS) Detail page.
4. Click the Database Recovery button. You will be directed to the Database Recovery page.
5. After entering the corresponding information in the Database Recovery Configuration section, click the Complete button.

   Item	Required	Detailed Description
   Recovery Type	Required	Set the point in time the user wants to recover Backup Point (Recommended): Recovery based on backup files. Select from the list of backup file points displayed in the list User-Specified Point: Recover to a point desired by the user within the range of points where backup is possible. The recoverable period can recover from the first backup start time to 1 hour/30 minutes/10 minutes/5 minutes before the current time depending on the Archive backup cycle setting value. Select the date and time you want to backup
   Server Name Prefix	Required	Recovered DB server name Enter 3~16 characters starting with lowercase English letters and using lowercase letters, numbers, and special characters (-) Actual server name is created with a postfix like 001, 002 based on the server name
   Cluster Name	Required	Recovered DB cluster name Enter 3~20 characters using English letters Cluster is a unit that groups multiple servers
   Service Type > Server Type	Required	Recovered DB server type Standard: Standard specifications generally used High Capacity: Large capacity servers with 24vCore or more
   Service Type > Planned Compute	Optional	Status of resources with Planned Compute set In Use: Number of resources in use among resources with Planned Compute set Set: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute for each resource Create Planned Compute Service: Move to Planned Compute service application page For details, see Applying for Planned Compute
   Service Type > Block Storage	Required	Block Storage settings used by recovered DB Basic OS: Area where DB engine is installed DATA: Storage area for table data and archive files Applied identically with the Storage type set in the original cluster Enter capacity in multiples of 8 in the range of 16~5,120 Additional: DATA, Archive, TEMP, Backup data storage area Applied identically with the Storage type set in the original cluster In recovered DB, only DATA, TEMP, Archive purposes can be added Select Use and then enter the storage purpose and capacity Click + button to add storage, x button to delete Capacity can be entered in multiples of 8 in the range of 16~5,120, and up to 9 can be created
   Database Username	Required	Database username Applied identically with the username set in the original cluster
   Database Port Number	Required	Database port number Applied identically with the port number set in the original cluster
   IP Access Control	Optional	Service access policy settings Sets access policy for IPs entered on the page, so separate Security Group policy settings are not required Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button To delete an entered IP, click the x button next to the entered IP
   Maintenance Window	Optional	DB 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 proceed at the set time and service interruption occurs If set to Not Use, Samsung SDS is not responsible for problems caused by not applying patches
   Tags	Optional	Add tags Click the Add Tag button and then enter or select Key, Value values

   Table. EPAS(DBaaS) Recovery Configuration Items

1.2.5 - Extension use

EPAS(DBaaS) Extension usage

The list of Extensions that can be installed in the current database can be checked with the following SQL sentence.

SQL> select * from pg_available_extensions;

In EPAS(DBaaS), the items that are installed additionally, excluding the default Extensions included in each version, are as follows.

In addition to the above items, if additional Extension installation is required, please refer to Support Center > Inquiry for inquiries.

• Once your inquiry is received, we will review and proceed with the installation. Please note that some Extensions may not work properly during Replica configuration and recovery.

1.3 - API Reference

1.4 - CLI Reference

1.5 - Release Notes

2 - PostgreSQL(DBaaS)

2.1 - Overview

Service Overview

PostgreSQL(DBaaS) is an open-source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that automates PostgreSQL installation and performs management functions for operation through a web-based Console.

PostgreSQL(DBaaS) is designed as a high availability architecture considering storage-based data replication and failover time minimization. To prevent data loss, when the content of the Active server changes, it is synchronously replicated to the Standby server. Read-only servers called Replica for read load distribution and disaster recovery (DR) are provided up to 5. Additionally, in preparation for problems with the DB server or data, it provides automatic backup at a time specified by the user, supporting data recovery at a desired point in time.

Provided Features

PostgreSQL(DBaaS) provides the following features.

• Auto Provisioning: Database (DB) installation and configuration via UI, providing Active-Standby redundancy configuration based on storage replication. Automatic failover to Standby when Active server fails.
• Operation Control Management: Provides function to control running server status. Start, stop, and restart possible for DB issues or to reflect configuration values. For HA configuration, users can directly perform Active-Standby node switching through Switch-over.
• Backup and Recovery: Provides data backup function based on own backup commands. Backup time period and retention period can be set by user, and additional charges are incurred depending on backup capacity. Also provides recovery function for backed up data, where user performs recovery and separate DB is created, recovery proceeds to point in time selected by user (backup storage point, user-specified point). When recovering to user-specified point, recovery point can be set up to 5 minutes/10 minutes/30 minutes/1 hour before current time based on stored backup files and archive files.
• Version Management: Provides version upgrade (Minor) function for some feature improvements and security patches. User can select whether to perform backup according to version upgrade, and if performing backup, backs up data before patch execution then performs DB engine update.
• Replica Configuration: Can configure up to 5 Read Replicas in same/different regions for read load distribution and disaster recovery (DR).
• Audit Settings: Supports audit function for major activities in database.
• Parameter Management: Can modify DB configuration parameters for performance improvement and security.
• Service Status Check: Checks final status of current DB service.
• Monitoring: Can check CPU, memory, DB performance monitoring information through Cloud Monitoring service.
• DB User Management: Manages DB account (user) information registered in DB.
• DB Access Control Management: Can register and cancel access-allowed IPs based on DB accounts registered in DB.
• Archive Management: Can set Archive file retention period (1~35 days) and Archive mode (On/Off) in DB server.
• DB Log Export: Can export logs stored through Audit settings to user’s Object Storage.
• Migration: Supports migration using replication method by synchronizing data with operating database in real time without service interruption.
• OS Kernel Upgrade: Can upgrade OS Kernel for some feature improvements and security patch application.

Components

PostgreSQL(DBaaS) provides pre-verified engine versions and various server types according to open source support policy. Users can select and use according to the service scale they want to configure.

Engine Versions

Engine versions supported by PostgreSQL(DBaaS) are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation stops is set to 6 months before the EoTS date.

EOS and EoTS dates may change according to supplier policy, so please refer to the supplier’s license management policy page for details.

• PostgreSQL: https://www.postgresql.org/support/versioning/

Server Type

Server types supported by PostgreSQL(DBaaS) are as follows.

For details on server types provided by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) Server Type.

Standard db1v2m4

Prerequisite Services

List of services that must be configured in advance before creating this service. For details, please prepare in advance by referring to the guide provided for each service.

2.1.1 - Server Type

PostgreSQL(DBaaS) server type

PostgreSQL(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth. When creating PostgreSQL(DBaaS), the Database Engine is installed according to the server type selected for the purpose of use.

The server types supported by PostgreSQL(DBaaS) are as follows.

Standard db1v2m4

db1 server type

The db1 server type of PostgreSQL(DBaaS) is provided with standard specifications(vCPU, Memory) and is suitable for various database workloads.

Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 256 GB of memory Up to 12.5 Gbps of networking speed

dbh2 server type

The dbh2 server type of PostgreSQL(DBaaS) is provided with large-capacity server specifications and is suitable for database workloads for large-scale data processing.

Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor Supports up to 128 vCPUs and 1,536 GB of memory Up to 25Gbps of networking speed

2.1.2 - Monitoring Metrics

PostgreSQL(DBaaS) Monitoring Metrics

The following table shows the performance monitoring metrics of PostgreSQL(DBaaS) that can be checked through Cloud Monitoring. For detailed instructions on using Cloud Monitoring, refer to the Cloud Monitoring guide.

For server monitoring metrics of PostgreSQL(DBaaS), refer to the Virtual Server Monitoring Metrics guide.

2.2 - How-to guides

Users can create PostgreSQL(DBaaS) service by entering required information and selecting detailed options through Samsung Cloud Platform Console.

Creating PostgreSQL(DBaaS)

You can create and use PostgreSQL(DBaaS) service through Samsung Cloud Platform Console.

To create PostgreSQL(DBaaS), follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).

2. On the Service Home page, click the Create PostgreSQL(DBaaS) button. You will be directed to the Create PostgreSQL(DBaaS) page.

3. On the Create PostgreSQL(DBaaS) page, enter information required for service creation and select detailed options.

   • Select required information in Image and Version Selection section.

     Category	Required	Detailed Description
     Image Version	Required	Provides PostgreSQL(DBaaS) version list

     Table. PostgreSQL(DBaaS) Image and Version Selection Items
   • Enter or select required information in Service Information Entry section.

     Category	Required	Detailed Description
     Server Name Prefix	Required	Server name where DB will be installed Enter 3~13 characters starting with lowercase English letters, using lowercase letters, numbers, and special characters (-) Actual server name is created with Postfix like 001, 002 based on server name
     Cluster Name	Required	Cluster name where DB servers are configured Enter 3~20 characters using English letters Cluster is a unit that groups multiple servers
     Service Type > Server Type	Required	Server type where DB will be installed Standard: Standard specifications generally used High Capacity: Large capacity servers with 24vCore or more For details on server types provided by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) Server Type
     Service Type > Planned Compute	Optional	Status of resources with Planned Compute set In Use: Number of resources in use among resources with Planned Compute set Set: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute for each resource Create Planned Compute Service: Move to Planned Compute service application page For details, see Applying for Planned Compute
     Service Type > Block Storage	Required	Block Storage settings used by DB according to purpose Basic OS: Area where DB engine is installed DATA: Storage area for table data and archive files Select storage type then enter capacity (For details on Block Storage types, see Creating Block Storage) SSD: High performance general volume HDD: General volume SSD_KMS, HDD_KMS: Additional encryption volume using Samsung Cloud Platform KMS (Key Management System) encryption key Set Storage type is applied identically to additional storage Enter capacity in multiples of 8 in range of 16~5,120 Must allocate separate TEMP storage for use as large Sort due to SQL execution or monthly batch may cause service interruption Additional: DATA, Archive, TEMP, Backup data storage area Select Use then enter storage purpose and capacity Storage type is applied identically with type set in DATA, capacity can be entered in multiples of 8 in range of 16~5,120 Click + button to add storage, x button to delete. Up to 9 can be added Temporarily saves backup data in BACKUP storage before transmitting backup data If backup data exceeds 100 GB and data changes are frequent, recommend adding separate BACKUP storage for stable backup, recommend setting backup capacity to about 60% of DATA capacity If BACKUP storage is not added, /tmp area is used, and backup fails if capacity is insufficient Only one Block Storage is allocated per service for Archive, TEMP, BACKUP storage
     Redundancy Configuration	Optional	Redundancy configuration If redundancy configuration is used, DB instance is configured divided into Active DB and Standby DB
     Network > Common Settings	Required	Network settings where servers created in service are installed Select if applying same settings to all installed servers Select pre-created VPC and Subnet, IP, Public NAT IP can only be auto-created Public NAT function can be used only if VPC is connected to Internet Gateway, if Use is checked can select from IPs reserved in VPC product’s Public IP. For details, see Creating Public IP
     Network > Per-Server Settings	Required	Network settings where servers created in service are installed Select if applying different settings per installed server Select pre-created VPC and Subnet, IP, Public NAT Enter IP for each server Public NAT function can be used only if VPC is connected to Internet Gateway. If Use is checked can select from IPs reserved in VPC product’s Public IP. For details, see Creating Public IP
     IP Access Control	Optional	Service access policy settings Sets access policy for IPs entered on page, so separate Security Group policy settings are not required Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click Add button To delete entered IP, click x button next to entered IP
     Maintenance Window	Optional	DB maintenance window If Use is selected, set day of week, start time, duration Recommend setting maintenance window for stable DB management. Patch operations proceed at set time and service interruption occurs If set to Not Use, Samsung SDS is not responsible for problems caused by not applying patches

     Table. PostgreSQL(DBaaS) Service Information Entry Items
   • Enter or select required information in Database Configuration Required Information Entry section.

     Category	Required	Detailed Description
     Database Name	Required	Server name applied when installing DB Enter 3~20 characters starting with English letters, using English letters and numbers
     Database Username	Required	DB user name Account is created with this name in OS as well Enter 2~20 characters using lowercase English letters Database usernames with restricted use can be checked in Console
     Database Password	Required	Password to use when accessing DB Enter 8~30 characters including English letters, numbers, and special characters (excluding " ’)
     Database Password Confirm	Required	Re-enter password to use when accessing DB identically
     Database Port Number	Required	Port number required for DB connection Enter DB port in range of 1200~65535
     Backup > Use	Optional	Whether to use backup Select Use to set backup file retention period, backup start time, Archive backup cycle
     Backup > Retention Period	Optional	Backup retention period Select backup retention period, file retention period can be set 7~35 days Additional charges are applied to backup files depending on capacity
     Backup > Backup Start Period	Optional	Backup start time Select backup start time Minutes when backup is performed are set randomly, backup end time cannot be set
     Backup > Archive Backup Cycle	Optional	Archive backup cycle Select Archive backup cycle Archive backup cycle of 1 hour is recommended. When selecting 5 minutes, 10 minutes, 30 minutes, may affect DB performance.
     Audit Log Settings	Optional	Whether to save Audit Log Select Use to set Audit Log function DDL, DML, user connection information records are saved User can specify SQL statement types to Audit through log_statement parameter, can modify through Parameter screen For details on this parameter, refer to PostgreSQL documentation DB performance may degrade when Audit is set
     Parameter	Required	Parameters to use in DB Can check detailed information of parameters by clicking View button Parameters can be modified after DB creation is complete, must restart DB after modification
     Database Encoding	Required	Character encoding method to use in DB Character set used when storing text data DB is created with default setting to selected Encoding
     DB Locale	Required	Locale to use in DB Settings related to string processing, number/currency/date/time display format DB is created with default setting to selected Locale
     Timezone	Required	Standard time zone where Database will be used

     Table. PostgreSQL(DBaaS) Database Configuration Items
   • Enter or select required information in Additional Information Entry section.

     Category	Required	Detailed Description
     Tags	Optional	Add tags Can add up to 50 per resource Click Add Tag button then enter or select Key, Value values

     Table. PostgreSQL(DBaaS) Additional Information Entry Items

4. On Summary panel, check created detailed information and estimated billing amount, then click Create button.

   • When creation is complete, check created resource on Resource List page.

Checking PostgreSQL(DBaaS) Detailed Information

PostgreSQL(DBaaS) service can check and modify overall resource list and detailed information. PostgreSQL(DBaaS) Detail page is composed of Detailed Information, Tags, Operation History tabs, and for DB with Replica configured, Replica Information tab is additionally configured.

To check detailed information of PostgreSQL(DBaaS) service, follow these steps.

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to check detailed information. You will be directed to the PostgreSQL(DBaaS) Detail page.
   • At the top of PostgreSQL(DBaaS) Detail page, status information and additional feature information are displayed.

     Category	Detailed Description
     Cluster Status	Status of cluster where DB is installed Creating: Cluster creation in progress Editing: Cluster changing to state performing Operation Error: Cluster state where error occurred during task execution If occurring continuously, contact administrator Failed: Cluster failed during creation process Restarting: Restarting cluster Running: Cluster operating normally Starting: Starting cluster Stopped: Cluster stopped Stopping: Stopping cluster Synchronizing: Synchronizing cluster Terminating: Deleting cluster Unknown: Cluster status unknown If occurring continuously, contact administrator Upgrading: Cluster changing to state performing upgrade
     Cluster Control	Buttons that can change cluster status Start: Start stopped cluster Stop: Stop running cluster Restart: Restart running cluster Switch-Over: Switch Standby cluster to Active
     Additional Features More	Cluster-related management buttons Service Status Sync: Check real-time DB service status Backup History: If backup is set, check backup normal execution and history Database Recovery: Recover DB based on specific point in time Parameter Management: Can check and modify DB configuration parameters Replica Configuration: Configure Replica which is read-only cluster Replica Configuration (Other Region): Configure disaster recovery Replica in other region, button disabled if no region configured in that Account DB User Management: Check and manage DB account (user) information registered in DB DB Access Control Management: Can register and cancel access-allowed IPs based on DB accounts registered in DB Archive Settings Management: Can set Archive file retention period and Archive mode DB Log Export: Can export logs saved through Audit settings to user’s Object Storage Migration Configuration: Provides Migration function of replication method OS(Kernel) Upgrade: Upgrade OS Kernel version
     Service Termination	Button to terminate service

     Table. PostgreSQL(DBaaS) Status Information and Additional Features

Detailed Information

On PostgreSQL(DBaaS) List page, check detailed information of selected resource, and modify information if necessary.

Replica Information

Replica Information tab is activated only when Replica is configured in cluster. Through Replica Information tab, can check Master cluster name, replica count, Replica’s replication status.

Tags

On PostgreSQL(DBaaS) List page, check tag information of selected resource, and add, change, or delete.

Operation History

On PostgreSQL(DBaaS) List page, can check operation history of selected resource.

Managing PostgreSQL(DBaaS) Resources

If existing configuration options of created PostgreSQL(DBaaS) resource need to be changed, or recovery, Replica configuration is needed, can perform tasks on PostgreSQL(DBaaS) Detail page.

Controlling Operation

If changes occur to running PostgreSQL(DBaaS) resource, can start, stop, restart. Also, if HA is configured, can switch Active-Standby servers through Switch-over.

To control PostgreSQL(DBaaS) operation, follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to control operation. You will be directed to the PostgreSQL(DBaaS) Detail page.
4. Check PostgreSQL(DBaaS) status and complete change through control buttons below.
   • Start: DB service installed server and DB service run (Running).
   • Stop: DB service installed server and DB service stop (Stopped).
   • Restart: Only DB service restarts.
   • Switch Over: Can change Active server and Standby server of DB.

Synchronizing Service Status

Can synchronize real-time service status of PostgreSQL(DBaaS).

To check PostgreSQL(DBaaS) service status, follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to check service status. You will be directed to the PostgreSQL(DBaaS) Detail page.
4. Click Service Status Sync button. Cluster changes to Synchronizing status while checking.
5. When check is complete, status is updated in server information item, and cluster changes to Running status.

Changing Server Type

Can change configured server type.

To change server type, follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to change server type. You will be directed to the PostgreSQL(DBaaS) Detail page.
4. Click Modify icon of server type to change at bottom of detailed information. Server Type Modify popup opens.
5. Select server type in Server Type Modify popup, then click Confirm button.

Adding Storage

If data storage space of 5 TB or more is needed, can add storage. For DB configured in redundancy, added simultaneously to both redundancy servers.

To add storage, follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to add storage. You will be directed to the PostgreSQL(DBaaS) Detail page.
4. Click Add Disk button at bottom of detailed information. Additional Storage Request popup opens.
5. In Additional Storage Request popup, enter purpose and capacity, then click Confirm button.

Expanding Storage

Can expand storage added as data area up to maximum 5 TB based on initially allocated capacity. For DB configured in redundancy, expanded simultaneously to both redundancy servers.

To expand storage capacity, follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to change server type. You will be directed to the PostgreSQL(DBaaS) Detail page.
4. Click Modify icon of additional Disk to expand at bottom of detailed information. Additional Storage Modify popup opens.
5. In Additional Storage Modify popup, enter expansion capacity, then click Confirm button.

Terminating PostgreSQL(DBaaS)

Can reduce operating costs by terminating unused PostgreSQL(DBaaS). However, since terminating service may immediately stop running service, proceed with termination task after fully considering impact of service interruption.

To terminate PostgreSQL(DBaaS), follow these steps:

1. Click All Services > Database > PostgreSQL(DBaaS) menu. You will be directed to the Service Home page for PostgreSQL(DBaaS).
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be directed to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, select resource to terminate and click Service Termination button.
4. When termination is complete, check if resource is terminated on PostgreSQL(DBaaS) list page.

2.2.1 - Managing DB Service

Users can manage PostgreSQL(DBaaS) through the Samsung Cloud Platform Console.

Managing Parameters

Provides functionality to easily view and modify database configuration parameters.

Viewing Parameters

Follow these steps to view configuration parameters.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to view and modify parameters. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Parameter Management button. The Parameter Management popup window will open.
5. In the Parameter Management popup window, click the View button. The View Notification popup window will open.
6. When the View Notification popup window opens, click the Confirm button. Viewing may take some time.

Modifying Parameters

Follow these steps to modify configuration parameters.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to view and modify parameters. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Parameter Management button. The Parameter Management popup window will open.
5. In the Parameter Management popup window, click the View button. The View Notification popup window will open.
6. When the View Notification popup window opens, click the Confirm button. Viewing may take some time.
7. If modification is needed, click the Modify button and enter the modification in the custom value area of the Parameter to be modified.
8. When input is complete, click the Complete button.

Managing DB Users

Provides management functionality to view DB user information and change status information.

Viewing DB Users

Follow these steps to view DB users.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to view DB users. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB User Management button. You will move to the DB User Management page.
5. On the DB User Management page, click the View button. Viewing may take some time.

Changing DB User Status

Follow these steps to change the status of viewed DB users.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to modify DB users. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB User Management button. You will move to the DB User Management page.
5. On the DB User Management page, click the View button. Viewing may take some time.
6. If modification is needed, click the Modify button and change the status area value or enter remarks.
7. When input is complete, click the Complete button.

Managing DB Access Control

Provides IP-based DB user access control management functionality. Users can directly specify IPs that can access the database, allowing access only from permitted IPs.

Viewing DB Access Control

Follow these steps to view DB users with IP access control set.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to manage access control. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB Access Control Management button. You will move to the DB Access Control Management page.
5. On the DB Access Control Management page, click the View button. Viewing may take some time.

Adding DB Access Control

Follow these steps to add IP access control.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to add IP access control. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB Access Control Management button. You will move to the DB Access Control Management page.
5. On the DB Access Control Management page, click the View button. Viewing may take some time.
6. When viewing is complete, click the Add button. The Add DB Access Control popup window will open.
7. In the Add DB Access Control popup window, select the DB user name and enter the IP Address.
8. When input is complete, click the Complete button.

Deleting DB Access Control

Follow these steps to delete IP access control.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to delete IP access control. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB Access Control Management button. You will move to the DB Access Control Management page.
5. On the DB Access Control Management page, click the View button. Viewing may take some time.
6. When viewing is complete, click the Delete button. The Delete popup window will open.
7. In the Delete popup window, click the Confirm button.

Managing Archive

Provides functionality to set Archive mode and Archive Log retention period, allowing users to flexibly configure Archive log management policies according to their operating environment. Additionally, provides functionality to manually delete Archive logs, enabling users to organize unnecessary log data and effectively manage system resources.

Setting Archive Mode

Follow these steps to set Archive mode.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Archive Settings Management button. You will move to the Archive Settings Management page.
5. On the Archive Settings Management page, click the View button. Viewing may take some time.
6. Click the Modify button and select usage and retention period.
7. When modification is complete, click the Complete button.

Deleting Archive Files

Follow these steps to delete Archive files.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Archive Settings Management button. You will move to the Archive Settings Management page.
5. On the Archive Settings Management page, click Delete All Archive if you want to delete all Archive files, or click Delete Backed Up Archive if you want to delete only backed up Archive files.

Modifying Audit Settings

You can change the Audit log storage settings for PostgreSQL(DBaaS).

Follow these steps to change the Audit log storage settings for PostgreSQL(DBaaS).

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to view the service status. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Modify icon in Audit Settings at the bottom of the detailed information. The Modify Audit Settings popup window will open.
5. In the Modify Audit Settings popup window, modify the usage and then click the Confirm button.
   • Selecting Use sets the Audit log function. Setting Audit logs may degrade DB performance.
   • Disabling Use deletes the Audit log storage file. Please back up the Audit log file separately before disabling use.

Exporting DB Log

Supports exporting audit(Audit) log data that requires long-term retention to Object Storage. Users can directly set the log type to be saved, the destination Bucket to export to, and the cycle for exporting logs. Logs are copied and stored to the specified Object Storage according to the set criteria. Additionally, to efficiently manage disk space, provides an option to automatically delete original log files while exporting logs to Object Storage. Using this option allows you to effectively secure storage capacity while safely storing necessary log data for long-term retention.

Setting DB Log Export Mode

Follow these steps to set DB Log export mode.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to export DB Log. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB Log Export button. You will move to the DB Log Export page.
5. On the DB Log Export page, click the Register button. You will move to the Register DB Log Export page.
6. On the Register DB Log Export page, enter the corresponding information and then click the Complete button.

   Category	Required	Detailed Description
   Log Type	Required	Log type to save
   Storage Bucket Name	Required	Object Storage Bucket name to save
   Authentication Key > Access key	Required	Access key to access the Object Storage to save
   Authentication Key > Secret key	Required	Secret key to access the Object Storage to save
   File Creation Cycle	Required	Cycle for creating files in Object Storage
   Delete Original Log	Optional	Whether to delete original logs while exporting to Object Storage

   Table. PostgreSQL(DBaaS) DB Log Export Configuration Items

Managing DB Log Export

Follow these steps to modify, cancel, or immediately export DB Log export settings.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource for which you want to manage DB Log export. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the DB Log Export button. You will move to the DB Log Export page.
5. On the DB Log Export page, click the More button according to the log type you want to manage and click the Immediate Export, Modify, or Cancel button.
   • Immediate Export: The selected log is exported to the Bucket of the previously set Object Storage.
   • Modify: Modifies the DB Log export mode settings.
   • Cancel: Cancels the DB Log export mode settings.

Upgrading Minor Version

Provides version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.

Follow these steps to upgrade Minor Version.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to upgrade the version. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Modify button in the Image version item. The Version Upgrade popup window will open.
5. In the Version Upgrade popup window, select the modified version and backup setting, then click the Confirm button.
6. In the Version Upgrade Notification popup window, click the Confirm button.

Configuring Migration

Provides Migration functionality that replicates in real-time while synchronizing with the operating database, without service interruption, using Replication method.

Follow these steps to configure Migration.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to migrate. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Migration Configuration button. The Migration Configuration popup window will open.
5. In the Migration Configuration popup window, check the instructions and click the Confirm button. You will move to the Migration Configuration page.
6. On the Migration Configuration page, enter the corresponding information and then click the Connection Check button.
7. When connection is complete, click the Complete button.

   Category	Required	Detailed Description
   Source DB Database Name	Required	Database name of the Source DB to be migrated
   Source DB IP	Required	IP of the Source DB to be migrated
   Source DB Port	Required	Port of the Source DB to be migrated
   Source DB Username	Required	Username of the Source DB to be migrated
   Source DB Password	Required	Password of the Source DB to be migrated

   Table. PostgreSQL(DBaaS) Migration Configuration Items

Promoting Migration Cluster to Master Cluster

You can promote a configured Migration Cluster to Master Cluster.

Follow these steps to promote Migration Cluster to Master.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to promote to Master. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Master Promotion button. The Master Promotion Notification popup window will open.
5. In the Master Promotion Notification popup window, click the Confirm button.

Upgrading OS Kernel

You can upgrade the OS Kernel to improve operating database functionality and apply security patches.

Follow these steps to upgrade OS Kernel.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to upgrade OS Kernel. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup window will open.
5. In the OS(Kernel) Upgrade Notification popup window, check the instructions and click the Confirm button.

2.2.2 - DB Backup and Restore

Users can set up PostgreSQL(DBaaS) backup through the Samsung Cloud Platform Console and restore using backed up files.

Backing Up PostgreSQL(DBaaS)

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

Setting Up Backup

For PostgreSQL(DBaaS) backup setup method, please refer to Creating PostgreSQL(DBaaS).

Follow these steps to modify backup settings for created resources.

Follow these steps to set up backup.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to set backup. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Modify button in the backup item. The Backup Settings popup window will open.
5. To set backup, click Use in the Backup Settings popup window, select retention period, backup start time, and Archive backup cycle, then click the Confirm button.
   • To stop backup settings, uncheck Use in the Backup Settings popup window and click the Confirm button.

Viewing Backup History

Follow these steps to view backup history.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to view backup history. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Backup History button. The Backup History popup window will open.
5. In the Backup History popup window, you can check backup status, version, backup start datetime, backup completion datetime, and capacity.

Deleting Backup Files

Follow these steps to delete backup history.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to view backup history. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Backup History button. The Backup History popup window will open.
5. In the Backup History popup window, check the file to delete and then click the Delete button.

Restoring PostgreSQL(DBaaS)

In case of failure or data loss requiring restoration from backup files, you can restore based on a specific point in time through the restore function. When PostgreSQL(DBaaS) restore is performed, a new server is created with the OS image at the initial provisioning time, DB is installed with the version of that backup time, and restoration proceeds with DB configuration information and data.

Follow these steps to restore PostgreSQL(DBaaS).

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) Resource List page, click the resource to restore. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Database Restore button. You will move to the Database Restore page.
5. Enter the corresponding information in the Database Restore Configuration area and then click the Complete button.

   Category	Required	Detailed Description
   Restore Type	Required	Setting the point in time user wants to restore Backup Point(Recommended): Restore based on backup file. Select from the list of backup file time points displayed in the list User-Specified Point: Restore to a point user wants within the backupable time range. The recoverable period can restore from the initial backup start time to 1 hour/30 minutes/10 minutes/5 minutes before current time according to Archive backup cycle setting value. Select the date and time to backup
   Server Name Prefix	Required	Server name of restore DB Enter 3~16 characters starting with lowercase English letters, using lowercase letters, numbers, and special characters(-) Actual server name is created with a postfix like 001, 002 attached based on server name
   Cluster Name	Required	Cluster name of restore DB Enter 3 ~ 20 characters using English letters Cluster is a unit that groups multiple servers
   Service Type > Server Type	Required	Server type where restore DB will be installed Standard: Standard specifications commonly used High Capacity: Large-capacity servers with 24vCore or more
   Service Type > Planned Compute	Optional	Status of resources with Planned Compute set In Use: Number of resources with Planned Compute set that are currently in use Set: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute per resource Create Planned Compute Service: Moves to Planned Compute service application page For details, refer to Applying for Planned Compute
   Service Type > Block Storage	Required	Block Storage settings used by restore DB Basic OS: Area where DB engine is installed DATA: Storage area for table data and archive files, etc. Applied identically with Storage type set in original cluster Enter capacity as a multiple of 8 in the range of 16 ~ 5,120 Additional: Storage area for DATA, Archive, TEMP, Backup data Applied identically with Storage type set in original cluster Only DATA, TEMP, Archive purposes can be added in restore DB. Select Use and then enter storage purpose and capacity To add storage, click the + button, to delete, click the x button Capacity can be entered as a multiple of 8 in the range of 16 ~ 5,120, and can create up to 9
   Database Username	Required	Database username set in original DB
   Database Port Number	Required	Database Port number set in original DB
   IP Access Control	Optional	IP address to access restore DB Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.1/32, 192.168.10.1/32) and click the Add button To delete entered IP, click the x button next to the entered IP
   Maintenance Period	Optional	DB maintenance period When Use is selected, set day of week, start time, and duration It is recommended to set a maintenance period for stable DB management. Patching is performed at the set time and service interruption occurs If set to Not Used, Samsung SDS is not responsible for problems caused by unapplied patches.
   Tags	Optional	Add tags Click the Add Tag button and then enter or select Key, Value values

   Table. PostgreSQL(DBaaS) Restore Configuration Items

2.2.3 - Configuring Read Replica

Users can enter required information for Read Replica through the Samsung Cloud Platform Console and create the service through detailed options.

Configuring Replica

Through Replica configuration, you can create replica servers for read-only or disaster recovery purposes. You can create up to 5 Replicas per Database.

Follow these steps to configure Replica.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to configure Replica. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Configure Replica button. You will move to the Configure Replica page.
5. Enter information in the Configure Replica area and then click the Complete button.

   Category	Required	Detailed Description
   Region	Required	Region to configure Replica Only exposed when Replica Configuration(Other Region) is selected
   Replica Count	Required	Number of Replicas to configure Can configure up to 5 per cluster When selecting a value of 2 or more, additional input is required for Replica name and service type information
   Replica Name	Required	Replica server name Enter 3 ~ 19 characters starting with lowercase English letters, using lowercase letters, numbers, and special characters(-) The entered Replica name is displayed as cluster name in the list
   Service Type > Server Type	Required	Replica server type Standard: Standard specifications commonly used High Capacity: Large-capacity servers with 24vCore or more
   Service Type > Planned Compute	Optional	Status of resources with Planned Compute set In Use: Number of resources with Planned Compute set that are currently in use Set: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute per resource Create Planned Compute Service: Moves to Planned Compute service application page For details, refer to Applying for Planned Compute
   Service Type > Block Storage	Required	Block Storage settings for Replica DB Basic OS: Area used on the server where DB is installed Applied identically according to the Storage type set in the original DB Capacity setting is not possible DATA: Storage area for table data and archive files, etc. Applied identically according to the Storage type set in the original DB Capacity setting is not possible Additional: Storage area for DATA, Archive, TEMP, Backup data Applied identically according to the Storage type set in the original DB Only DATA, TEMP purposes can be added in Replica Select Use and then enter the storage purpose and capacity. Enter capacity in the range of 16 ~ 5,120 as a multiple of 8 To add storage, click the + button, to delete, click the x button. Can add up to 9.
   IP Access Control	Optional	Service access policy setting Sets access policy for IPs entered on the page, so no separate Security Group policy setting is required Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button To delete entered IP, click the x button next to the entered IP
   Maintenance Period	Optional	DB maintenance period When Use is selected, set day of week, start time, and duration It is recommended to set a maintenance period for stable DB management. Patching is performed at the set time and service interruption occurs If set to Not Used, Samsung SDS is not responsible for problems caused by unapplied patches.
   Tags	Optional	Add tags Click the Add Tag button and then enter or select Key, Value values

   Table. PostgreSQL(DBaaS) Replica Configuration Items

Reconfiguring Replica

In case of network failure or Replication delay with Master Cluster, you can replicate Master Cluster data again through the Replica reconfiguration function.

Follow these steps to reconfigure Replica.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to reconfigure Replica. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the Reconfigure Replica button. The Reconfigure Replica Notification popup window will open.
5. In the Reconfigure Replica Notification popup window, click the Confirm button.

Promoting Replica Cluster to Master Cluster

You can promote a configured Replica Cluster to Master Cluster.

Follow these steps to promote Replica Cluster to Master.

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS) List page.
3. On the PostgreSQL(DBaaS) List page, click the resource to promote to Master. You will move to the PostgreSQL(DBaaS) Detail page.
4. Click the More button and click the Master Promotion button. The Master Promotion Notification popup window will open.
5. In the Master Promotion Notification popup window, click the Confirm button.

2.2.4 - Connecting to DB Server

Scenario Overview

The PostgreSQL(DBaaS) Server Connection scenario involves creating a Bastion host(Virtual Server) and Database service, and accessing the DB service through the Bastion host. To stably access PostgreSQL(DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and configure network connections using it. To maintain stable and high security levels, it is recommended to configure the Database service in a Private Subnet environment and the Bastion host in a restricted Public Subnet environment.

This scenario explains the process of creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB connection client.

Scenario Components

You can configure this scenario using the following services.

Scenario Configuration Method

Create the necessary services to configure the scenario through the following procedure.

1. Configuring Network

This explains the process of configuring the network environment for accessing Bastion Host and Database service.

1-1. Creating VPC

1. Click the All Services > Networking > VPC menu. You will move to the VPC’s Service Home page.
2. On the Service Home page, click the Create VPC button. You will move to the Create VPC page.
3. On the Create VPC page, enter the necessary information for service creation.
   • Enter the IP range as 192.168.x.0/16.
4. On the Summary panel, check the detailed creation information and estimated billing amount, then click the Complete button.
   • When creation is complete, check the created resource on the VPC List page.

1-2. Creating Subnet

1. Click the All Services > Networking > VPC menu. You will move to the VPC’s Service Home page.
2. On the Service Home page, click the Subnet menu. You will move to the Subnet List page.
3. Click the Create Subnet button. You will move to the Create Subnet page.
4. On the Create Subnet page, enter the necessary information for service creation.
   • Select General as the Subnet type.
   • Select the previously created VPC.
   • Enter the IP range as 192.168.x.0/24.
5. On the Summary panel, check the detailed creation information and estimated billing amount, then click the Complete button.
   • When creation is complete, check the created resource on the Subnet List page.

1-3. Creating Internet Gateway

1. Click the All Services > Networking > VPC menu. You will move to the VPC’s Service Home page.
2. On the Service Home page, click the Internet Gateway menu. You will move to the Internet Gateway List page.
3. Click the Create Internet Gateway button. You will move to the Create Internet Gateway page.
4. On the Create Internet Gateway page, enter the required information for service creation.
   • Select the previously created VPC.
   • Select Use for the Firewall usage item.
5. On the Summary panel, check the detailed creation information and estimated billing amount, then click the Complete button.
   • When creation is complete, check the created resource on the Internet Gateway List page.

1-4. Creating Public IP

1. Click the All Services > Networking > VPC menu. You will move to the VPC’s Service Home page.
2. On the Service Home page, click the Public IP menu. You will move to the Public IP List page.
3. Click the Reserve Public IP button. You will move to the Reserve Public IP page.
4. On the Reserve Public IP page, enter the required information for service reservation.
5. On the Summary panel, check the detailed creation information and estimated billing amount, then click the Complete button.
   • When creation is complete, check the created resource on the Public IP List page.

1-5. Creating Security Group

1. Click the All Services > Networking > Security Group menu. You will move to the Security Group’s Service Home page.
2. On the Service Home page, click the Create Security Group button. You will move to the Create Security Group page.
3. On the Create Security Group page, enter the required information for service creation.
4. Check the entered information and click the Complete button.
   • When creation is complete, check the created resource on the Security Group List page.

2. Creating Bastion Host

This explains the process of configuring the Bastion Host where the DB connection client should be installed.

2-1. Creating Server Keypair

1. Click the All Services > Compute > Virtual Server menu. You will move to the Virtual Server’s Service Home page.
2. On the Service Home page, click the Keypair menu. You will move to the Keypair List page.
3. Click the Create Keypair button. You will move to the Create Keypair page.
4. On the Create Keypair page, enter the required information for service creation.
5. Check the creation information and click the Complete button.
   • Key download is only possible on the first attempt, and re-issuance is not provided.
   • Please store the downloaded key in a safe place.

2-2. Creating Bastion Host

1. Click the All Services > Compute > Virtual Server menu. You will move to the Virtual Server’s Service Home page.
2. On the Service Home page, click the Create Virtual Server button. You will move to the Create Virtual Server page.
3. On the Create Virtual Server page, enter the required information for service creation.
   • Select Windows for the image.
   • Select the previously created VPC and Subnet.
   • Click Use NAT and select the Public IP reserved in 1-4. Creating Public IP.
   • Connect the Keypair created in 2-1. Creating Server Keypair.
4. On the Summary panel, check the detailed creation information and estimated billing amount, then click the Complete button.
   • When creation is complete, check the created resource on the Virtual Server List page.

2-3. Checking Bastion Host Connection ID and Password

1. Click the All Services > Compute > Virtual Server menu. You will move to the Virtual Server’s Service Home page.
2. On the Service Home page, click the Virtual Server menu. You will move to the Virtual Server List page.
3. On the Virtual Server List page, click the resource created in 2-2. Creating Bastion Host. You will move to the detailed information page of that resource.
4. On the detailed information page, click the RDP password lookup button in the Keypair name item. The RDP password lookup popup window will open.
5. In the RDP password lookup popup window, attach the keypair file downloaded in 2-1. Creating Server Keypair.
6. After attaching, click the Password check button. The ID and Password for accessing that resource will be displayed.
   • The ID and Password will be used as information for accessing the Bastion host later in 5-1. Connecting to Bastion Host.

3. Creating Database

This explains the process of creating the Database service.

3-1. Creating PostgreSQL(DBaaS) Service

1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will move to the PostgreSQL(DBaaS)’s Service Home page.
2. On the Service Home page, click the Create PostgreSQL(DBaaS) button. You will move to the Create PostgreSQL(DBaaS) page.
3. On the Create PostgreSQL(DBaaS) page, enter the required information for service creation.
   • Select and connect the previously created VPC and Subnet.
   • Enter Database-related creation information in the required information input screen.
   • Add the Bastion host IP in the IP access control item.
   • The Database Port defaults to 2866, but users can specify it.
4. On the Summary panel, check the detailed creation information and estimated billing amount, then click the Complete button.
   • When creation is complete, check the created resource on the PostgreSQL(DBaaS) List page.

4. Setting Rules

This explains the process of setting rules for users to access the Bastion host and for the Bastion host to access the Database.

4-1. Adding Security Group Security Rules

1. Click the All Services > Networking > Security Group menu. You will move to the Security Group’s Service Home page.
2. On the Service Home page, click the Security Group menu. You will move to the Security Group List page.
3. Select the Security Group resource created in [1-5. Creating Security Group]. You will move to the detailed information page of that resource.
4. On the detailed information page, click the Rules tab. You will move to the Rules tab.
5. On the Rules tab, click the Add Rule button. You will move to the Add Rule popup window.
6. In the Add Rule popup window, enter the following rules and click the Confirm button.

   Direction	Remote	Destination Address	Protocol	Port	Description
   Inbound	CIDR	User PC IP	TCP	3389 (RDP)	Bastion connection PC → Bastion host
   Outbound	CIDR	DB IP	TCP	Database Port (Direct Input)	Bastion host → Database

   Table. Security Group Security Rules to be Added

4-2. Adding IGW Firewall Rules

1. Click the All Services > Networking > Firewall menu. You will move to the Firewall’s Service Home page.
2. On the Service Home page, click the Firewall menu. You will move to the Firewall List page.
3. On the Firewall List page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway. You will move to the detailed information page of that resource.
4. On the detailed information page, click the Rules tab. You will move to the Rules tab.
5. On the Rules tab, click the Add Rule button. You will move to the Add Rule popup window.
6. In the Add Rule popup window, enter the following rules and click the Confirm button.

   Source Address	Destination Address	Protocol	Port	Action	Direction	Description
   Bastion connection PC IP	Bastion host IP	TCP	3389(RDP)	Allow	Inbound	User PC → Bastion host

   Table. Internet Gateway Firewall Rules to be Added

5. Connecting to Database

This explains the process of connecting to the Database through a DB connection client program.

This guide explains how to connect using pgAdmin. There are various Database client programs and CLI utilities, so users can install and use the appropriate tool.

5-1. Connecting to Bastion Host

1. Run Remote Desktop Connection in the Windows environment of the PC that wants to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
2. When Remote Desktop Connection succeeds, the User credential input window will open. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Connection ID and Password and click the Confirm button.

5-2. Installing DB Connection Client Program (pgAdmin) on Bastion Host

1. Go to the pgAdmin official page and download the pgAdmin program.
   • pgAdmin program download path: https://www.pgadmin.org/download/
2. Connect the user PC’s hard drive to upload the file to the Bastion host.
3. On the Local Resources tab of Remote Desktop Connection, click the More button in the local devices and resources item.
4. Select the local disk of the location where the file was downloaded and click the Confirm button.
5. Copy the downloaded file to upload it to the Bastion Host, then click the pgAdmin installation file to install it.

5-3. Connecting to Database Using DB Connection Client Program (pgAdmin)

1. Run pgAdmin and click the Add New Server button.
2. In the Register - Server popup window, enter the Database server information created in 3-1. Creating PostgreSQL(DBaaS) Service in the General tab and Connection tab, then click the Save button.

   Screen(Tab)	Required Input Item	Input Value
   General	Name	User-defined (ex. service name)
   Connection	Host name/address	Database server IP
   Connection	Port	Database Port
   Connection	Maintenance database	Database name
   Connection	Password	Database password

   Table. DB Connection Client Program Input Items
3. Click the database name created in pgAdmin to perform the connection.
   • After connection, you can perform simple queries, etc.

2.2.5 - Using Extensions

PostgreSQL(DBaaS) Extension usage

The list of extensions that can be installed in the current database can be checked with the following SQL statement.

SQL> select * from pg_available_extensions;

PostgreSQL(DBaaS) has the following additional installation items outside of the default extension by version:

In addition to the above items, if additional Extension installation is required, please refer to Support Center > Inquiry and inquire.

• Once the inquiry is received, we will proceed with the installation after review. Please note that some Extensions may not work normally during Replica configuration and recovery.

2.3 - API Reference

2.4 - CLI Reference

2.5 - Release Note

PostgreSQL(DBaaS)

3 - MariaDB(DBaaS)

3.1 - Overview

Service Overview

MariaDB(DBaaS) is an open source relational database (RDBMS) with high compatibility with MySQL. Samsung Cloud Platform provides an environment where MariaDB installation is automated through a web-based Console and management functions for operation can be performed.

MariaDB(DBaaS) is designed with a high availability architecture considering storage-based data replication and minimizing Failover time. To prevent data loss, when the content of the Active server is changed, it is synchronously replicated to the Standby server, and up to 5 read-only servers called Replicas for read load distribution and disaster recovery (DR) are provided. In addition, to prepare for problems with the DB server or data, it provides a function to automatically backup at a time specified by the user, so that data can be recovered at a desired point in time.

Provided Features

MariaDB(DBaaS) provides the following features.

• Auto Provisioning: Database (DB) installation and settings are possible through UI, and provides Active-standby redundancy configuration based on storage replication. When Active server fails, automatic Failover to Standby occurs.
• Operation Control Management: Provides function to control running server status. In addition to start and stop, restart is possible when there is a problem with the DB or to reflect settings. When high availability (HA) is configured, the user can directly perform node switching of Active-Standby through Switch-over.
• Backup and Recovery: Provides data backup function based on own backup command. Backup time period and retention period can be set by the user, and additional fees are charged depending on backup capacity. Also provides recovery function for backed up data, and when the user performs recovery, a separate DB is created and recovery proceeds to the point selected by the user (backup storage point, user-specified point). When recovering to a user-specified point, the recovery point can be set up to 5 minutes/10 minutes/30 minutes/1 hour ago based on stored backup files and archive files.
• Version Management: Provides version upgrade (Minor) function for some function improvements and security patches. Whether to perform backup according to version upgrade can be selected by the user, and if performing backup, data is backed up before patch execution and then DB engine update is performed.
• Replica Configuration: Up to 5 Read Replicas can be configured in the same/different region for read load distribution and disaster recovery (DR).
• Audit Setting: Provides Audit setting function to monitor user DB access and DDL (Data Definition Language)/DML (Data Manipulation Language) execution results.
• Parameter Management: DB configuration parameter modification for performance improvement and security is possible.
• Service Status Inquiry: Inquires the final status of current DB service.
• Monitoring: CPU, Memory, performance monitoring information can be checked through Cloud Monitoring and Servicewatch.
• DB User Management: Manages by inquiring DB account (user) information registered in DB.
• DB Access Control Management: Allows registration and termination of access allowed IP based on DB accounts registered in DB.
• Archive Management: Archive file retention period (1 day~35 days) setting and Archive mode (On/Off) setting are possible in DB server.
• DB Log Export: Logs stored through Audit settings can be exported to user’s Object Storage.
• Migration: Supports migration using Replication method by synchronizing data in real time with operating database without service interruption.
• OS Kernel Upgrade: OS Kernel can be upgraded for some function improvements and security patch application.

Components

MariaDB(DBaaS) provides engine versions pre-verified according to open source support policy and various server types. Users can select and use them according to the service scale they want to configure.

Engine Version

The engine versions supported by MariaDB(DBaaS) are as follows.

Technical support can be used until the EoTS (End of Technical Service) date of the supplier, and the EOS date when new creation stops is set to 6 months before the EoTS date.

According to supplier policy, EOS and EoTS dates may change, so please check the supplier’s license management policy page for details.

• MariaDB (Community): https://mariadb.org/about/#maintenance-policy

Server Type

The server types supported by MariaDB(DBaaS) are as follows.

For more information on server types provided by MariaDB(DBaaS), see MariaDB(DBaaS) Server Type.

Standard db1v2m4

Prerequisite Services

This is a list of services that must be pre-configured before creating this service. Please prepare in advance by referring to the guide provided for each service.

3.1.1 - Server Type

MariaDB(DBaaS) Server Type

MariaDB(DBaaS) provides server types with various combinations of CPU, Memory, and Network Bandwidth. When creating a MariaDB(DBaaS), the database engine is installed according to the selected server type, which is chosen based on the intended use.

The server types supported by MariaDB(DBaaS) are as follows:

Standard db1v2m4

db1 Server Type

The db1 server type of MariaDB(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
• Supports up to 16 vCPUs and 256 GB of memory
• Up to 12.5 Gbps networking speed

dbh2 Server Type

The dbh2 server type of MariaDB(DBaaS) is provided with high-capacity server specifications and is suitable for large-scale data processing database workloads.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 128 vCPUs and 1,536 GB of memory
• Up to 25Gbps networking speed

3.1.2 - Monitoring Metrics

MariaDB(DBaaS) Monitoring Metrics

The following table shows the performance monitoring metrics of MariaDB(DBaaS) that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

For server monitoring metrics of MariaDB(DBaaS), refer to the Virtual Server monitoring metrics guide.

3.1.3 - ServiceWatch Metrics

MariaDB sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1-minute interval.

Basic Indicators

The following are the basic metrics for the MariaDB namespace.

OS Basic Metrics

MariaDB Basic Metrics

3.2 - How-to guides

Users can create MariaDB(DBaaS) by entering required information and selecting detailed options through the Samsung Cloud Platform Console.

Creating MariaDB(DBaaS)

You can create and use MariaDB(DBaaS) service through the Samsung Cloud Platform Console.

To create MariaDB(DBaaS), follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the Create MariaDB(DBaaS) button. It moves to the Create MariaDB(DBaaS) page.
3. On the Create MariaDB(DBaaS) page, enter the information required for service creation and select detailed options.
   • Select the required information in the Image and Version Selection area.

     Classification	Required	Detailed Description
     Image Version	Required	Provides version list of MariaDB(DBaaS)

     Table. MariaDB(DBaaS) Image and Version Selection Items
   • Enter or select the required information in the Service Information Entry area.

     Classification	Required	Detailed Description
     Server Name Prefix	Required	Server name where DB will be installed Start with lowercase English letters, enter 3 to 13 characters using lowercase letters, numbers, and special characters (-) Actual server name is created with a postfix like 001, 002 based on the server name
     Cluster Name	Required	Cluster name where DB servers are configured Enter 3 to 20 characters using English Cluster is a unit that bundles multiple servers
     Service Type > Server Type	Required	Server type where DB will be installed Standard: Standard specification commonly used High Capacity: Large capacity server with 24 vCore or more For more information on server types provided by MariaDB(DBaaS), see MariaDB(DBaaS) Server Type
     Service Type > Planned Compute	Optional	Resource status with Planned Compute set In Use: Number of resources with Planned Compute set that are in use Settings: Number of resources with Planned Compute set Coverage Preview: Amount applied by resource-based Planned Compute Create Planned Compute Service: Move to Planned Compute service application page For more information, see Apply for Planned Compute
     Service Type > Block Storage	Required	Block Storage setting used by DB according to purpose Basic OS: Area where DB engine is installed DATA: Storage area for table data and archive files, etc. Select storage type then enter capacity. (For more information by Block Storage type, see Creating Block Storage) SSD: High-performance general volume HDD: General volume SSD_KMS, HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key Set Storage type is applied equally to additional storage Enter capacity in multiples of 8 within the range of 16 to 5,120 Since service interruption may occur due to large Sort such as SQL execution or monthly batch, separate TEMP storage must be allocated and used Additional: DATA, Archive, TEMP, Backup data storage area Select Use then enter Purpose and Capacity of storage Storage type is applied equally to the type set in DATA, and capacity can be entered in multiples of 8 within the range of 16 to 5,120 To add storage, click the + button, and to delete, click the x button. Can add up to 9 Before transferring backup data, temporarily store backup data in BACKUP storage If backup data exceeds 100 GB and data changes are frequent, it is recommended to add separate BACKUP storage for stable backup. It is recommended to set backup capacity to about 60% of DATA capacity If BACKUP storage is not added, /tmp area is used, and backup fails if capacity is insufficient Only one Block Storage is allocated per service for Archive, TEMP, BACKUP storage
     Redundancy Configuration	Optional	Redundancy configuration If using redundancy configuration, DB instances are configured as Active DB and Standby DB
     Network > Common Settings	Required	Network settings where servers created in the service are installed Select if you want to apply the same settings to all installed servers Select pre-created VPC and Subnet, IP, Public NAT Only automatic IP generation is possible Public NAT function is only available when VPC is connected to Internet Gateway. If you check Use, you can select from IPs reserved in Public IP of VPC product. For more information, see Creating Public IP
     Network > Per Server Settings	Required	Network settings where servers created in the service are installed Select if you want to apply different settings for each installed server Select pre-created VPC and Subnet, IP, Public NAT Enter IP for each server Public NAT function is only available when VPC is connected to Internet Gateway. If you check Use, you can select from IPs reserved in Public IP of VPC product. For more information, see Creating Public IP
     IP Access Control	Optional	Service access policy setting Since access policy is set for the IP entered on the page, you don’t need to set Security Group policy separately Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button To delete the entered IP, click the x button next to the entered IP
     Maintenance Period	Optional	DB maintenance period If selecting Use, set day of week, start time, and duration It is recommended to set the maintenance period for stable DB management. Patch work is performed at the set time and service interruption occurs If set to not used, Samsung SDS is not responsible for problems caused by not applying patches.

     Table. MariaDB(DBaaS) Service Information Entry Items
   • Enter or select the required information in the Database Configuration Required Information Entry area.

     Classification	Required	Detailed Description
     Database Name	Required	Server name applied when DB is installed Start with English, enter 3 to 20 characters using English and numbers
     Database Username	Required	DB user name Account with that name is also created in OS Enter 2 to 20 characters using lowercase English letters Limited Database usernames can be checked in Console
     Database Password	Required	Password to use when accessing DB Enter 8 to 30 characters including English letters, numbers, and special characters (excluding " ’)
     Database Password Confirmation	Required	Re-enter password to use when accessing DB identically
     Database Port Number	Required	Port number required for DB connection Enter DB port within the range of 1200 to 65535
     Backup > Use	Optional	Backup usage Select Use to set backup file retention period, backup start time, and Archive backup cycle
     Backup > Retention Period	Optional	Backup retention period Select backup retention period. File retention period can be set from 7 days to 35 days Separate fees are charged for backup files depending on capacity
     Backup > Backup Start Period	Optional	Backup start time Select backup start time The minutes when backup is performed are set randomly, and backup end time cannot be set
     Backup > Archive Backup Cycle	Optional	Archive backup cycle Select Archive backup cycle 1 hour is recommended for Archive backup cycle. When selecting 5 minutes, 10 minutes, 30 minutes, it may affect DB performance
     Audit Log Setting	Optional	Audit Log storage Select Use to set Audit Log function User access information recording is stored Users can specify event types to Audit through server_audit_events parameter, and can modify through Parameter screen For details on that parameter, see MariaDB documentation DB performance may deteriorate when Audit is set
     ServiceWatch Log Collection	Optional	ServiceWatch log collection Select Use to set ServiceWatch log collection function For details on collected logs, see ServiceWatch Metrics Provided free up to 5 GB for all services in Account, and fees are charged depending on storage capacity when exceeding 5 GB When collecting, log group and log stream are automatically created, and cannot be deleted until resource is deleted To prevent exceeding 5 GB, directly deleting log data or shortening retention period is recommended
     Parameter	Required	Parameters to use for DB Click the View button to check detailed information of parameters After DB creation is complete, parameter modification is possible, and DB must be restarted after modification
     DB Character Set	Required	Character encoding method to use for DB As a character set used when storing text data, DB is created with default setting to selected Encoding
     Time Zone	Required	Standard time zone where Database will be used

     Table. MariaDB(DBaaS) Database Configuration Items
   • Enter or select the required information in the Additional Information Entry area.

     Classification	Required	Detailed Description
     Tags	Optional	Add tags Can add up to 50 per resource Click the Add Tag button then enter or select Key, Value values

     Table. MariaDB(DBaaS) Additional Information Entry Items
4. In the Summary panel, review the detailed information and estimated charges, and click the Create button.
   • Once creation is complete, check the created resource on the Resource List page.

Checking MariaDB(DBaaS) Detailed Information

MariaDB(DBaaS) service allows you to check and modify the entire resource list and detailed information. The MariaDB(DBaaS) Details page consists of Detailed Information, Tags, Operation History tabs, and for DBs with Replica configured, Replica Information tab is additionally configured.

To check the detailed information of MariaDB(DBaaS) service, follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, click the resource to check detailed information. It moves to the MariaDB(DBaaS) Details page.
   • At the top of the MariaDB(DBaaS) Details page, status information and additional function information are displayed.

     Classification	Detailed Description
     Cluster Status	Cluster status where DB is installed Creating: Cluster is being created Editing: Cluster is changing to Operation execution state Error: State where error occurred while cluster is performing operation If it occurs continuously, contact administrator Failed: State where cluster failed during creation process Restarting: State where cluster is being restarted Running: State where cluster is operating normally Starting: State where cluster is starting Stopped: State where cluster is stopped Stopping: State where cluster is in stop state Synchronizing: State where cluster is synchronizing Terminating: State where cluster is being deleted Unknown: State where cluster status is unknown If it occurs continuously, contact administrator Upgrading: State where cluster is changing to upgrade execution state
     Cluster Control	Buttons to change cluster status Start: Start stopped cluster Stop: Stop running cluster Restart: Restart running cluster Switch-Over: Switch Standby cluster to Active
     More Additional Functions	Cluster-related management buttons Sync Service Status: Check real-time DB service status Backup History: If backup is set, check backup normal execution status and history Database Recovery: Recover DB based on specific point in time Parameter Management: Check and modify DB configuration parameters Replica Configuration: Configure Replica which is read-only cluster Replica Configuration (Other-Region): Configure disaster recovery replica in different region, button is disabled if no region configured in that Account DB User Management: Check and manage DB account (user) information registered in DB DB Access Control Management: Allows registration and termination of access allowed IP based on DB accounts registered in DB Archive Setting Management: Archive file retention period setting and Archive mode setting are possible DB Log Export: Logs stored through Audit settings can be exported to user’s Object Storage Migration Configuration: Provides Migration function of Replication method OS(Kernel) Upgrade: OS Kernel version upgrade
     Service Termination	Button to terminate service

     Table. MariaDB(DBaaS) Status Information and Additional Functions

Detailed Information

On the MariaDB(DBaaS) List page, you can check the detailed information of the selected resource and modify information if necessary.

Replica Information

The Replica Information tab is activated only when Replica is configured in the cluster. Through the Replica Information tab, you can check Master cluster name, replica count, and Replica status.

Tags

On the MariaDB(DBaaS) List page, you can check the tag information of the selected resource and add, change, or delete it.

Operation History

You can check the operation history of the selected resource on the MariaDB(DBaaS) List page.

Managing MariaDB(DBaaS) Resources

If you need to change existing configuration options of created MariaDB(DBaaS) resources or perform recovery, Replica configuration, you can perform operations on the MariaDB(DBaaS) Details page.

Controlling Operation

If changes occur in running MariaDB(DBaaS) resources, you can start, stop, or restart. Also, if configured with HA, you can switch Active-Standby servers through Switch-over.

To control MariaDB(DBaaS) operation, follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, click the resource to control operation. It moves to the MariaDB(DBaaS) Details page.
4. Check MariaDB(DBaaS) status and complete changes through the control buttons below.
   • Start: DB service installed server and DB service will run (Running).
   • Stop: DB service installed server and DB service will stop (Stopped).
   • Restart: Only DB service will restart.
   • Switch Over: Can switch Active server and Standby server of DB.

Syncing Service Status

You can sync the real-time service status of MariaDB(DBaaS).

To check MariaDB(DBaaS) service status, follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, click the resource to check service status. It moves to the MariaDB(DBaaS) Details page.
4. Click the Sync Service Status button. While retrieving, the cluster changes to Synchronizing status.
5. When retrieval is complete, the status is updated in the server information item, and the cluster changes to Running status.

Changing Server Type

You can change the configured server type.

To change the server type, follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, click the resource to change server type. It moves to the MariaDB(DBaaS) Details page.
4. Click the Edit icon of the server type you want to change at the bottom of detailed information. The Edit Server Type popup window opens.
5. In the Edit Server Type popup window, select the server type and click the OK button.

Adding Storage

If data storage space of 5TB or more is needed, you can add storage. For DB configured with redundancy, both redundancy servers are added simultaneously.

To add storage, follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, click the resource to add storage. It moves to the MariaDB(DBaaS) Details page.
4. Click the Disk Add button at the bottom of detailed information. The Additional Storage Request popup window opens.
5. In the Additional Storage Request popup window, after entering purpose and capacity, click the OK button.

Expanding Storage

Storage added as data area can be expanded up to maximum 5 TB based on the initially allocated capacity. For DB configured with redundancy, both redundancy servers are expanded simultaneously.

To expand storage capacity, follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, click the resource to change server type. It moves to the MariaDB(DBaaS) Details page.
4. Click the Edit icon of the additional Disk you want to expand at the bottom of detailed information. The Edit Additional Storage popup window opens.
5. In the Edit Additional Storage popup window, after entering expansion capacity, click the OK button.

Terminating MariaDB(DBaaS)

You can reduce operating costs by terminating unused MariaDB(DBaaS). However, if you terminate the service, the running service may stop immediately, so you should proceed with termination after fully considering the impact caused by service interruption.

To terminate MariaDB(DBaaS), follow these steps:

1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) List page.
3. On the MariaDB(DBaaS) List page, select the resource to terminate and click the Terminate Service button.
4. When termination is complete, check if the resource is terminated on the MariaDB(DBaaS) List page.

3.2.1 - Managing DB Service

Users can manage MariaDB(DBaaS) through Samsung Cloud Platform Console.

Managing Parameter

Provides functionality to easily view and modify database configuration parameters.

Viewing Parameters

Follow these steps to view configuration parameters.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to view or modify parameters on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click Parameter Management button. Parameter Management popup window will open.
5. Click View button in the Parameter Management popup window. View Notification popup window will open.
6. Click Confirm button when the View Notification popup window opens. It will take some time to view.

Modifying Parameters

Follow these steps to modify configuration parameters.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to view or modify parameters on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click Parameter Management button. Parameter Management popup window will open.
5. Click View button in the Parameter Management popup window. View Notification popup window will open.
6. Click Confirm button when the View Notification popup window opens. It will take some time to view.
7. If modification is needed, click Modify button and enter the modification in the custom value area of the Parameter to be modified.
8. When input is complete, click Complete button.

SQL> SHOW COLLATION WHERE Charset = 'character set name';

Managing DB Users

Provides management functionality to view DB user information and change status information.

Viewing DB Users

Follow these steps to view DB users.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to view DB users on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB User Management button. You will be taken to the DB User Management page.
5. Click View button on the DB User Management page. It will take some time to view.

Changing DB User Status

Follow these steps to change the status of viewed DB users.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to modify DB users on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB User Management button. You will be taken to the DB User Management page.
5. Click View button on the DB User Management page. It will take some time to view.
6. If modification is needed, click Modify button and change the status area value or enter note content.
7. When input is complete, click Complete button.

Managing DB Access Control

Provides IP-based DB user access control management functionality. Users can directly specify IPs that can access the database, setting it so that only allowed IPs can access.

Viewing DB Access Control

Follow these steps to view DB users with IP access control set.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to manage access control on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB Access Control Management button. You will be taken to the DB Access Control Management page.
5. Click View button on the DB Access Control Management page. It will take some time to view.

Adding DB Access Control

Follow these steps to add IP access control.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to add IP access control on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB Access Control Management button. You will be taken to the DB Access Control Management page.
5. Click View button on the DB Access Control Management page. It will take some time to view.
6. When viewing is complete, click Add button. DB Access Control Add popup window will open.
7. Enter DB username selection and IP Address in the DB Access Control Add popup window.
8. When input is complete, click Complete button.

Deleting DB Access Control

Follow these steps to delete IP access control.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to delete IP access control on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB Access Control Management button. You will be taken to the DB Access Control Management page.
5. Click View button on the DB Access Control Management page. It will take some time to view.
6. When viewing is complete, click Delete button. Delete popup window will open.
7. Click Confirm button in the Delete popup window.

Managing Archive

Provides Archive mode setting and Archive Log retention period setting functionality, allowing users to flexibly set Archive log management policies according to their operating environment. Additionally, it provides functionality to manually delete Archive logs, enabling effective management of system resources by cleaning up unnecessary log data.

Setting Archive Mode

Follow these steps to set Archive mode.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to set Archive mode on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click Archive Setting Management button. You will be taken to the Archive Setting Management page.
5. Click View button on the Archive Setting Management page. It will take some time to view.
6. Click Modify button and select usage and retention period.
7. When modification is complete, click Complete button.

Deleting Archive Files

Follow these steps to delete Archive files.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to set Archive mode on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click Archive Setting Management button. You will be taken to the Archive Setting Management page.
5. To delete all Archive files on the Archive Setting Management page, click Delete All Archives, and to delete only backed up Archive files, click Delete Backed Up Archives button.

Modifying Audit Settings

You can change MariaDB(DBaaS)’s Audit log storage settings.

Follow these steps to change MariaDB(DBaaS)’s Audit log storage settings.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to view service status on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click Modify icon in Audit Settings at the bottom of the detail information. Audit Settings Modify popup window will open.
5. Modify usage in the Audit Settings Modify popup window and click Confirm button.
   • When Use is selected, Audit log functionality is set. When Audit log is set, DB performance may degrade.
   • When Use is disabled, the Audit log storage file is deleted. Back up the Audit log file separately before disabling use.

Exporting DB Log

Supports exporting audit (Audit) logs that require long-term preservation to Object Storage. Users can directly set the log type to be stored, the target Bucket to export to, and the cycle for exporting logs. Logs are copied and stored to the specified Object Storage according to the set criteria. Additionally, for efficient management of disk space, it also provides an option to automatically delete the original log file while exporting the log to Object Storage. By using this option, you can effectively secure storage capacity while safely storing necessary log data for the long term.

Setting DB Log Export Mode

Follow these steps to set DB Log Export mode.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to export DB Log on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB Log Export button. You will be taken to the DB Log Export page.
5. Click Register button on the DB Log Export page. You will be taken to the DB Log Export Register page.
6. Enter the corresponding information on the DB Log Export Register page and click Complete button.

   Category	Required	Description
   Log Type	Required	Log type to store
   Storage Bucket Name	Required	Object Storage Bucket name to store
   Authentication Key > Access key	Required	Access key to access the Object Storage to store
   Authentication Key > Secret key	Required	Secret key to access the Object Storage to store
   File Creation Cycle	Required	Cycle for creating files in Object Storage
   Original Log Deletion	Optional	Whether to delete the original log while exporting to Object Storage

   Table. MariaDB(DBaaS) DB Log Export Configuration Items

Managing DB Log Export

Follow these steps to modify, cancel, or immediately export DB Log Export settings.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to manage DB Log Export on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click DB Log Export button. You will be taken to the DB Log Export page.
5. On the DB Log Export page, click More button according to the log type you want to manage and click Immediate Export, Modify, or Cancel button.
   • Immediate Export: Selected logs are exported to the previously set Object Storage’s Bucket.
   • Modify: Modifies DB Log Export mode settings.
   • Cancel: Cancels DB Log Export mode settings.

Upgrading Minor Version

Provides version upgrade functionality according to some feature improvements and security patches. Only Minor version upgrade functionality within the same Major version is supported.

Follow these steps to upgrade Minor Version.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to upgrade version on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click Modify icon in the Image Version item. Version Upgrade popup window will open.
5. Select the modification version and backup setting in the Version Upgrade popup window, then click Confirm button.
6. Click Confirm button in the Version Upgrade Notification popup window.

Configuring Migration

Provides Migration functionality that replicates in real-time with a running database using Replication method without service interruption.

Follow these steps to configure Migration.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to migrate on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click Migration Configuration button. Migration Configuration popup window will open.
5. Confirm the guidelines in the Migration Configuration popup window and click Confirm button. You will be taken to the Migration Configuration page.
6. Enter the corresponding information on the Migration Configuration page and click Connection Check button.
7. When connection is complete, click Complete button.

   Category	Required	Description
   Source DB Database Name	Required	Database name of the Source DB to be migrated
   Source DB IP	Required	IP of the Source DB to be migrated
   Source DB Port	Required	Port of the Source DB to be migrated
   Source DB Username	Required	Username of the Source DB to be migrated
   Source DB Password	Required	Password of the Source DB to be migrated

   Table. MariaDB(DBaaS) Migration Configuration Items

Promoting Migration Cluster to Master Cluster

You can promote a configured Migration Cluster to Master Cluster.

Follow these steps to promote Migration Cluster to Master.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to promote to Master on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click Master Promotion button. Master Promotion Notification popup window will open.
5. Click Confirm button in the Master Promotion Notification popup window.

Upgrading OS Kernel

You can upgrade the OS Kernel to improve running database functionality and apply security patches.

Follow these steps to upgrade OS Kernel.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to upgrade OS Kernel on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click More button and click OS(Kernel) Upgrade button. OS(Kernel) Upgrade Notification popup window will open.
5. Confirm the guidelines in the OS(Kernel) Upgrade Notification popup window and click Confirm button.

3.2.2 - DB Backup and Restore

Users can set up MariaDB(DBaaS) backup and restore using backed up files through Samsung Cloud Platform Console.

Backing up MariaDB(DBaaS)

MariaDB(DBaaS) provides data backup functionality based on its own backup command. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion functionality.

Setting up Backup

For MariaDB(DBaaS) backup configuration method, please refer to Creating MariaDB(DBaaS).

Follow these steps to modify the backup settings of the created resource.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to set up backup on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click Modify button in the backup item. Backup Setting popup window will open.
5. To set up backup, click Use in the Backup Setting popup window, select retention period, backup start time, Archive backup cycle, and click Confirm button.
   • To stop backup setting, uncheck Use in the Backup Setting popup window and click Confirm button.

Viewing Backup History

Follow these steps to view backup history.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to view backup history on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click Backup History button. Backup History popup window will open.
5. In the Backup History popup window, you can view backup status, version, backup start date/time, backup completion date/time, and capacity.

Deleting Backup Files

Follow these steps to delete backup files.

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to view backup history on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click Backup History button. Backup History popup window will open.
5. Check the file you want to delete in the Backup History popup window and click Delete button.

Restoring MariaDB(DBaaS)

In case of failure or data loss, you can restore based on a specific point in time using the restore functionality. When MariaDB(DBaaS) restore is performed, a new server is created with the OS image at the time of initial provisioning, DB is installed with the version of that backup point, and restore is performed with the DB’s configuration information and data.

Follow these steps to restore MariaDB(DBaaS).

1. Click All Services > Database > MariaDB(DBaaS) menu. You will be taken to MariaDB(DBaaS)’s Service Home page.
2. Click MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
3. Click the resource for which you want to restore on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Detail page.
4. Click Database Restore button. You will be taken to the Database Restore page.
5. Enter information in the Database restore configuration area and click Complete button.

   Category	Required	Description
   Restore Type	Required	Set the point in time the user wants to restore Backup Point (Recommended): Restore based on backup file. Select from the list of backup file points displayed User-Specified Point: Restore to the point in time the user wants within the range where backup is possible. The restorable period depends on the Archive backup cycle setting value, and can restore from the initial backup start point to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to backup
   Server Name Prefix	Required	Server name of restore DB Enter 3-16 characters starting with English lowercase letters, using lowercase letters, numbers, and special characters (-) Actual server name is created with postfix like 001, 002 based on server name
   Cluster Name	Required	Cluster name of restore DB Enter 3-20 characters using English Cluster is a unit that groups multiple servers
   Service Type > Server Type	Required	Server type where restore DB will be installed Standard: Standard specifications commonly used High Capacity: Large capacity server with 24vCore or more (to be provided later)
   Service Type > Planned Compute	Optional	Resource status with Planned Compute set In Use: Number of resources in use among those with Planned Compute set Set: Number of resources with Planned Compute set Coverage Preview: Amount applied with Planned Compute per resource Planned Compute Service Create: Move to Planned Compute service application page For details, refer to Applying for Planned Compute
   Service Type > Block Storage	Required	Block Storage settings used by restore DB Basic OS: Area where DB engine is installed DATA: Storage area for table data, archive files, etc. Applied identically with the Storage type set in the original cluster Capacity is entered in multiples of 8 within the 16-5,120 range Additional: DATA, Archive, TEMP, Backup data storage area Applied identically with the Storage type set in the original cluster In restore DB, only DATA, TEMP, Archive purposes can be added Select Use and enter storage purpose and capacity To add storage, click + button, to delete, click x button Capacity can be entered in multiples of 8 within the 16-5,120 range, and can create up to 9
   Database Username	Required	Database username set in the original DB
   Database Port Number	Required	Database Port number set in the original DB
   IP Access Control	Optional	IP address to access restore DB Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.1/32, 192.168.10.1/32) and click Add button To delete entered IP, click x button next to the entered IP
   Maintenance Window	Optional	DB maintenance window If Use is selected, set day of week, start time, duration For stable DB management, set maintenance window is recommended. Patching is performed at the set time and service interruption occurs If set to Not Used, problems caused by not applying patching are not the responsibility of Samsung SDS.
   Tag	Optional	Add tag Click Add Tag button and enter or select Key, Value values

   Table. MariaDB(DBaaS) Restore Configuration Items