We provide a service that easily creates and manages relational, unstructured, and analytical databases in a web environment.
1 - EPAS(DBaaS)
1.1 - Overview
Service Overview
EPAS(DBaaS) is a relational database management system (RDBMS) with high compatibility with Oracle databases. Samsung Cloud Platform provides an environment that can automate EPAS installation and perform management functions for operation through a web-based Console.
EPAS (DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for potential issues with the DB server or data, we provide an automatic backup feature at user-specified times, enabling data recovery at the desired point in time.
Figure. EPAS(DBaaS) Architecture
Provided features
EPAS(DBaaS) provides the following features.
Auto Provisioning: It allows installation and configuration of Database (DB) through the UI, and provides an Active‑standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, a node transition between Active-Standby can be performed directly by the user through a switch-over.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be configured by the user, and additional fees may apply based on the backup size. * It also provides a recovery feature for backed‑up data; when the user initiates a recovery, a separate database is created, and the recovery proceeds to the point in time selected by the user (the backup creation time or a user‑specified time). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour prior to the stored backup and archive files.
Version Management: Provides Minor version upgrade functionality based on some feature improvements and security patches. * Whether to perform a backup for a version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, after which the DB engine is updated.
Replica configuration: Up to five Read Replicas can be configured in the same or different regions for read load balancing and disaster recovery (DR).
Audit configuration: Provides an Audit configuration feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
Parameter Management: Performance improvement and security-related DB configuration parameters can be modified.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
Archive Management: You can set the Archive file retention period (1~35 days) on the DB server and configure the Archive mode (On/Off).
DB Log Export: You can export stored logs to the user’s Object Storage via Audit settings.
Migration: Synchronizes data in real time with the operational database and supports migration using replication without service interruption.
OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.
Components
EPAS (DBaaS) provides pre‑validated engine versions and various server types. Users can select and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by EPAS (DBaaS) are as follows.
Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
EOS Date (Samsung Cloud Platform new creation stop date)
EoTS Date(Community Technical Support End Date)
14.17
2026-05-20
2026-12-01
14.18
2026-05-20
2026-12-01
14.19
2026-05-20
2026-12-01
15.12
2027-09 (planned)
2028-02-13
15.13
2027-09 (planned)
2028-02-13
15.14
2027-09 (planned)
2028-02-13
15.15
2027-09 (planned)
2028-02-13
16.8
2028-06 (planned)
2028-11-09
16.9
2028-06 (planned)
2028-11-09
16.10
2028-06 (planned)
2028-11-09
16.11
2028-06 (planned)
2028-11-09
17.6
2029-06 (planned)
2029-11-08
17.7
2029-06 (planned)
2029-11-21
Table. EPAS (DBaaS) provided engine versions
Information
The next version of EPAS is scheduled to be provided after September 2026. The actual service delivery schedule is subject to change.
EPAS 15.17
EPAS 16.13
EPAS 17.9
Server type
The server types supported by EPAS (DBaaS) are as follows.
For detailed information about the server types provided by EPAS (DBaaS), see EPAS(DBaaS) 서버 타입.
Standard db1v2m4
Category
example
Detailed description
Server type
Standard
Provided server types
Standard: Standard specifications (vCPU, Memory) commonly used
High Capacity: Large server specifications of 24 vCores or more
Server specifications
db1
Provided server specifications
db1: Standard specifications (vCPU, Memory) commonly used
dbh2: Large-capacity server specifications
Provide servers with 24 vCores or more
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. EPAS (DBaaS) server type components
Preceding Service
This is a list of services that must be pre‑configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
A service that provides an isolated virtual network in a cloud environment.
Table. EPAS (DBaaS) Preliminary Service
1.1.1 - Server type
EPAS(DBaaS) server type
EPAS (DBaaS) offers server types composed of various combinations such as CPU, Memory, and Network Bandwidth.
When creating EPAS (DBaaS), the Database Engine is installed according to the server type selected for the intended use.
Reference
The server types offered may vary depending on the region and AZ.
The server types supported by EPAS (DBaaS) are as follows.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server type categories
Standard: Configured with standard specifications (vCPU, Memory) commonly used
High Capacity: Specifications for large‑capacity servers beyond Standard
Server specifications
db1
Provided server type classification and generation
db1: means a standard specification, and 1 indicates the generation
dbh2: h indicates a large-capacity server specification, and 2 indicates the generation
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. EPAS (DBaaS) server type format
db1 server type
The db1 server type of EPAS (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db1v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db1v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db1v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db1v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db1v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db1v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db1v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db1v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db1v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db1v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db1v10m80
10 vCore
80 GB
Maximum 10 Gbps
Standard
db1v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db1v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db1v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db1v12m96
12 vCore
96 GB
Maximum 12.5 Gbps
Standard
db1v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db1v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db1v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db1v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db1v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db1v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db1v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db1v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. EPAS(DBaaS) server type specifications - db1 server type
db2 server type
The db2 server type of EPAS (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db2v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db2v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db2v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db2v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db2v32m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db2v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db2v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db2v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db2v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db2v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db2v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db2v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db2v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db2v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db2v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db2v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db2v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db2v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db2v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db2v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db2v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db2v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db2v10m80
10 vCore
80 GB
Up to 10 Gbps
Standard
db2v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db2v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db2v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db2v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db2v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db2v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db2v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db2v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db2v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db2v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db2v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db2v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db2v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db2v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db2v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db2v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db2v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. EPAS(DBaaS) server type specifications - db2 server type
dbh2 server type
The dbh2 server type of EPAS (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
High Capacity
dbh2v24m48
24 vCore
48 GB
Maximum 25 Gbps
High Capacity
dbh2v96
(Note: Actually original is dbh2v24m96; I must output exactly as-is. Apologies.)
TEXT: dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
Table. EPAS (DBaaS) server type specifications - dbh2 server type
db3 server type
The db3 server type of EPAS (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db3v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db3v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db3v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db3v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db3v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db3v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db3v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db3v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db3v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db3v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db3v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db3v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db3v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db3v6m72
6 vCore
72 GB
Maximum 10 Gbps
Standard
db3v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db3v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db3v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db3v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db3v8m96
8 vCore
96 GB
Maximum 10 Gbps
Standard
db3v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db3v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db3v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db3v10m80
10 vCore
80 GB
Up to 10 Gbps
Standard
db3v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db3v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db3v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db3v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db3v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db3v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db3v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db3v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db3v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db3v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db3v14m168
14 vCore
168 GB
Maximum 12.5 Gbps
Standard
db3v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db3v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db3v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db3v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db3v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db3v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. EPAS(DBaaS) server type specifications - db3 server type
dbh3 server type
The dbh3 server type of EPAS(DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz Intel 6th‑generation (Granite Rapids) Xeon 6
CPU
Maximum 4.1 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
High Capacity
dbh3v24m48
24 vCore
48 GB
Maximum 25 Gbps
High Capacity
dbh3v24m96
24 vCore
96 GB
Maximum 25 Gbps
High Capacity
dbh3v24m192
24 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh3v24m288
24 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh3v32m64
32 vCore
64 GB
Maximum 25 Gbps
High Capacity
dbh3v32m128
32 vCore
128 GB
Maximum 25 Gbps
High Capacity
dbh3v32m256
32 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh3v32m384
32 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh3v48m192
48 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh3v48m576
48 vCore
576 GB
Maximum 25 Gbps
High Capacity
dbh3v64m256
64 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh3v64m768
64 vCore
768 GB
Maximum 25 Gbps
High Capacity
dbh3v72m288
72 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh3v72m864
72 vCore
864 GB
Maximum 25 Gbps
High Capacity
dbh3v96m384
96 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh3v96m1152
96 vCore
1152 GB
Maximum 25 Gbps
High Capacity
dbh3v128m512
128 vCore
512 GB
Maximum 25 Gbps
High Capacity
dbh3v128m1536
128 vCore
1536 GB
Maximum 25 Gbps
Table. EPAS(DBaaS) server type specifications - dbh3 server type
Database password
Required
Password to use when accessing the DB
Enter 8 to 30 characters, including letters, numbers, and special characters (“‘ excluded)
Check database password
Required
Re-enter the same password to use for DB access
Database Port number
Required
Port number required for DB connection
Enter the DB port within the range 1200 ~ 65535
Backup > Use
Selection
Backup usage
Select Use to set backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period
Selection
Backup retention period
Select the backup retention period. Set the file retention period from 7 days to 35 days
Backup files incur additional charges based on size
Backup > Backup Start Period
Selection
Backup start time
Select backup start time
The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be configured
Backup > Archive backup schedule
Selection
Archive backup frequency
Select the archive backup frequency
The archive backup frequency is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log Settings
Selection
Whether to store Audit Log
Select Use to enable the Audit Log feature
DDL, DML, SELECT, and user connection information records are stored
The user can specify the types of SQL statements to audit via the edb_audit_statement parameter, and can modify it through the Parameter screen
For detailed information about this parameter, refer to the EDB documentation
Enabling Audit may degrade database performance
ServiceWatch log collection
Selection
ServiceWatch log collection status
Select Use to configure the ServiceWatch log collection feature
Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB
When collecting, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed
To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Parameter
required
DB configuration parameters
View button can be clicked to view detailed information of the parameters
Parameters can be modified after the service creation is completed, and the DB must be restarted after any modification
Database Encoding
Required
Character encoding method to be used for the DB
Character set used when storing text data
The DB is created with the selected encoding as the default setting
DB Locale
Required
Locale
settings related to string handling, number/currency/date/time display formats, etc.
The DB is created with the selected Locale as the default setting.
Time zone
Required
Standard time zone used by the database
License
Required
EPAS License verification status
This is a verification item for license usage; you cannot proceed to the next step unless you click Confirm
Table. EPAS (DBaaS) Database configuration items
Additional Information Input area, please enter or select the required information.
Category
Required status
Detailed description
tag
Selection
Add Tag
Up to 50 per resource can be added
Add Tag button after clicking, enter or select Key, Value values
Table. EPAS (DBaaS) additional information input fields
Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
When creation is complete, check the created resource on the Resource List page.
EPAS(DBaaS) Check detailed information
The EPAS (DBaaS) service allows you to view and edit the full list of resources and detailed information. On the EPAS(DBaaS) Details page, it is composed of the Details, Tags, Activity Log tabs, and for databases with a Replica configured, a Replica Information tab is added.
Follow the steps below to view detailed information about the EPAS (DBaaS) service.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS (DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to view detailed information. 3. EPAS(DBaaS) Details Go to the page.
EPAS(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Category
Detailed description
Cluster status
Cluster status with DB installed
Creating: Cluster is being created
Editing: Cluster is transitioning to an operational state
Error: Cluster is in an error state during task execution
If this persists, contact the administrator
Failed: Cluster is in a failed state during creation
Restarting: Cluster is being restarted
Running: Cluster is operating normally
Starting: Cluster is being started
Stopped: Cluster is in a stopped state
Stopping: Cluster is in the process of stopping
Synchronizing: Cluster is being synchronized
Terminating: Cluster is being terminated
Unknown: Cluster status is unknown
If this persists, contact the administrator
Upgrading: Cluster is transitioning to an upgrading state
Cluster control
Button to change the cluster state
Start: Start a stopped cluster
Stop: Stop a running cluster
Restart: Restart a running cluster
Switch-Over: Switch a standby cluster to Active
More features
Cluster-related management buttons
Service status synchronization: Real-time DB service status lookup
Backup history: When backup is configured, check whether it runs correctly and view its history
Database recovery: Recover the DB based on a specific point in time
Parameter management: View and modify DB configuration parameters
Replica configuration: Configure a read-only cluster as a Replica
Replica configuration (Other-Region): Configure a disaster-recovery Replica in another region; if the account has no region to configure, the button is disabled
DB user management: View and manage DB account (user) information registered in the DB
DB access control management: Based on DB accounts registered in the DB, you can register and revoke allowed IP addresses
Archive settings management: Set archive file retention period and configure archive mode
DB Log export: Logs stored via audit settings can be exported to the user’s Object Storage
Migration configuration: Provides migration functionality using replication
Block Storage usage management: Provides usage query functionality per Block Storage type
OS (Kernel) upgrade: Upgrade OS Kernel version
Service cancellation
Button to cancel the service
Table. EPAS (DBaaS) status information and additional features
Detailed Information
You can view detailed information of the selected resource on the EPAS (DBaaS) List page and, if necessary, edit the information.
Category
Detailed description
Server Information
Server information configured in this cluster
Category: Server type (Active, Standby, Replica)
Server name: Server name
IP port: Server IP and port
Availability Zone: Server creation location
Status: Server status
Service
Service name
Resource Type
Resource Type
SRR
Unique resource ID in Samsung Cloud Platform
In the DB service, it refers to the cluster SRN
Resource Name
Resource name
In the DB service, it refers to the cluster name
Resource ID
Unique resource ID in the service
Constructor
User who created the service
Creation Date/Time
Service creation date and time
Modifier
User who edited the service information
Modification date and time
Date and time the service information was modified
Image version
Installed DB image and version information
If a version upgrade is required, click the Edit icon to configure
If log collection configuration is required, click the Edit icon next to Log Collection to configure
Time zone
Standard time zone used by the database
DB Locale
Locale to use in the DB
Database Encoding
Character encoding to use for the DB
VIP
Virtual IP information
can be checked only when high availability is configured
Network
Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP access control
Service access policy configuration
If you need to add or delete IPs, click the Edit icon to configure
Active & Standby
Active/Standby server type, default OS, additional Disk information
If you need to modify the server type, click the Edit icon next to the server type to configure. Refer to the server type modification procedure in 서버 타입 변경하기
Modifying the server type requires a server reboot
If you need to expand storage, click the Edit icon next to the storage capacity to expand. Refer to the storage expansion procedure in 스토리지 증설하기
If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure in 스토리지 추가하기
Table. EPAS(DBaaS) Database detailed information items
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab lets you check the Master cluster name, replica count, and Replica status.
Category
Detailed description
Master information
Name of the Master cluster
Replica count
Number of Replicas created in the Master cluster
Replica status
Replica server status in the Master cluster
Server name, status query, status details, and status verification time can be viewed
To view the Replica status, click the Status Query button
While the query is in progress, the cluster remains in Synchronizing state, and once the query completes, the cluster changes to Running state.
Table. Replica information tab detailed information items
tag
EPAS(DBaaS) List page allows you to view the tag information of the selected resource, and add, modify, or delete it.
Category
Detailed description
Tag list
Tag list
You can view the Key and Value information of the tag
Up to 50 tags can be added per resource
When entering a tag, you can search and select from the list of previously created Keys and Values
Table. EPAS (DBaaS) Tag Tab Items
Job History
EPAS (DBaaS) List page lets you view the operation history of the selected resource.
Category
Detailed description
Task History List
Resource Change History
Operation Time, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Operator Information Check
Table. Work History tab detailed information items
EPAS(DBaaS) Resource Management
If you need to change or restore the existing configuration options of a created EPAS (DBaaS) resource, or require a Replica configuration, you can perform the operation on the EPAS(DBaaS) Details page.
Operation Control
If changes occur to a running EPAS (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of EPAS (DBaaS), follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS (DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource you want to control. 3. Navigate to the EPAS(DBaaS) Details page.
Check the EPAS (DBaaS) status and complete the change using the control button below.
Start: DB service is installed on the server and the DB service is running (Running).
Stop: The server where the DB service is installed and the DB service will be stopped (Stopped).
Restart: Only the DB service will be restarted.
Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize service status
You can synchronize the real-time service status of EPAS (DBaaS).
To check the service status of EPAS (DBaaS), follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List Navigate to the page.
On the EPAS(DBaaS) List page, click the resource to view its service status. 3. Go to the EPAS(DBaaS) Details page.
Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
When the query completes, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
To change the server type, follow these steps.
Caution
If you modify the server type, a server restart is required. Please verify separately any software license modifications or software settings and their implementation due to server specification changes.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
EPAS(DBaaS) List page, click the resource whose server type you want to change. 3. EPAS(DBaaS) Details page is accessed.
Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
Edit Server Type In the popup window, after selecting the server type, click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. In a redundant DB setup, all redundant servers are added simultaneously.
To add storage, follow these steps.
Caution
It is applied in the same way as the Storage type selected when creating the service.
For a DB configured with redundancy, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
A Replica’s storage cannot be larger than the primary’s storage. * Expand the Replica storage first, then expand the Master storage.
When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List Navigate to the page.
EPAS(DBaaS) List Click the resource to add storage on the page. 3. EPAS(DBaaS) Details Go to the page.
Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding Storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB setup, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List Navigate to the page.
EPAS(DBaaS) List Click the resource on the page for which you want to change the server type. 3. EPAS(DBaaS) Details Go to the page.
Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. 4. Edit Additional Storage popup opens.
Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
EPAS(DBaaS) Terminate
You can cancel unused EPAS (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
Caution
Replica is not deleted together. * If you also delete the Replica, delete it separately from the resource list.
If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel EPAS (DBaaS), follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS(DBaaS) List page is accessed.
Select the resource to terminate on the EPAS (DBaaS) List page, and click the Terminate Service button.
Once the termination is complete, check the EPAS(DBaaS) list page to confirm that the resource has been terminated.
1.2.1 - Managing DB Services
Users can manage EPAS (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows you to easily view and modify database configuration parameters.
View Parameter
Follow these steps to retrieve configuration parameters.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
EPAS (DBaaS) List page, click the resource for which you want to view or modify parameters. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. View Notification A popup window opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
Edit Parameter
Follow the instructions.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
EPAS (DBaaS) List page, click the resource for which you want to view or modify parameters. 3. EPAS(DBaaS) Details Navigate to the page.
More button, click it, then click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. View Notification A popup window opens.
View notification when the popup window opens, click the Confirm button. 6. Retrieving may take a short amount of time.
If editing is required, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
When the input is complete, click the Done button.
Manage DB Users
Provides administrative features to view DB user information and modify status information.
Query DB Users
To look up DB users, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
EPAS(DBaaS) List page, click the resource you wish to query the DB user for. 3. Go to the EPAS(DBaaS) Details page.
Click the More button and then click the DB User Management button. 4. Go to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
Change DB User Status
To change the status of the retrieved DB user, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
EPAS(DBaaS) List page: click the resource for which you want to edit the DB user. 3. EPAS(DBaaS) Details Go to the page.
Click the More button and then click the DB User Management button. 4. DB User Management go to the page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
If modification is required, click the Edit button, and change the status area value or enter remarks.
When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IP addresses that can access the database, configuring it so that only authorized IPs are allowed access.
안내
Perform a DB user lookup before setting DB access control. For DB user lookup, please refer to DB 사용자 관리하기.
View DB Access Control
To view DB users with IP access control enabled, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
Click the EPAS(DBaaS) menu on the Service Home page. 2. EPAS (DBaaS) List Navigate to the page.
EPAS (DBaaS) List page, click the resource you want to manage access control for. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button and then click the DB Access Control Management button. 4. DB Access Control Management Navigate to the page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
Add DB access control
Follow these steps to add IP access control.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List Navigate to the page.
On the EPAS (DBaaS) List page, click the resource for which you want to add IP access control. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button, then click the DB Access Control Management button. 4. Go to the DB Access Control Management page.
Click the Search button on the DB Access Control Management page. 5. Retrieving may take a short amount of time.
When the query is complete, click the Add button. 6. Add DB Access Control A popup window opens.
Add DB Access Control In the popup window, select the DB username and enter the IP address.
Once the input is complete, click the Save button.
Delete DB access control
To delete IP access control, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
EPAS (DBaaS) List page, click the resource for which you want to delete IP access control. 3. Navigate to the EPAS(DBaaS) Details page.
Click the More button, then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving takes a short amount of time.
When the query is complete, click the Delete button. 6. Delete popup window opens.
Delete in the popup window Confirm click the button.
Managing Archives
Provides Archive mode configuration and Archive Log retention period settings, allowing users to flexibly configure Archive log management policies to suit their operating environment.
Additionally, it provides a feature to manually delete archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
안내
When creating a service, the default setting uses Archive mode, and the retention period is 3 days.
Configure Archive mode
To set the Archive mode, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List page is accessed.
On the EPAS (DBaaS) List page, click the resource for which you want to set Archive mode. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button, then click the Archive Settings Management button. 4. Go to the Archive Settings Management page.
On the Archive Settings Management page, click the Search button. 5. Retrieving may take a short amount of time.
Click the Edit button and select the usage status and retention period.
When the edit is complete, click the Done button.
Delete archive file
To delete the Archive file, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
Service Home 페이지에서 EPAS(DBaaS) 메뉴를 클릭하세요. 2. Navigate to the EPAS (DBaaS) List page.
EPAS(DBaaS) List Click the resource on the page for which you want to set Archive mode. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button and then click the Archive Settings Management button. 4. Go to the Archive Settings Management page.
Archive Settings Management page, if you want to delete all Archive files, click the Delete All Archives button; if you want to delete only backed‑up Archive files, click the Delete Backed‑up Archives button.
Modify Audit Settings
You can modify the Audit log storage settings of EPAS (DBaaS).
To change the Audit log storage settings of EPAS (DBaaS), follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
on the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List Navigate to the page.
On the EPAS (DBaaS) List page, click the resource to view the service status. 3. EPAS(DBaaS) Details Navigate to the page.
Click the Edit icon of Audit Settings at the bottom of the detailed information. 4. Edit Audit Settings A popup window opens.
Modify Audit Settings After changing the usage in the popup window, click the Confirm button.
When Use is selected, the Audit log feature is enabled. * Enabling audit logging may degrade database performance.
If you disable use, the Audit log storage file will be deleted. * Back up the Audit log file separately before disabling.
Export DB Log
Supports exporting log data that requires long-term retention among audit (Audit) logs to Object Storage. Users can directly configure the log types that need to be stored, the destination Bucket for export, and the log export interval. Copies logs to the specified Object Storage for retention according to the configured criteria.
Additionally, to efficiently manage disk space, we provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for the long term.
안내
To use the DB Log export feature, you need to create an Object Storage. * For Object Storage creation, please refer to the Object Storage 사용자 가이드.
Please be sure to verify the expiration date and time of the authentication key. * If the authentication key expires, logs will not be stored in the bucket.
Please ensure that authentication key information is not exposed to external parties.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
Click the All Services > Database > EPAS(DBaaS) menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
Click the EPAS(DBaaS) menu on the Service Home page. 2. Go to the EPAS (DBaaS) List page.
On the EPAS (DBaaS) List page, click the resource for which you want to export the DB Log. 3. Go to the EPAS(DBaaS) Details page.
Click the More button and then click the DB Log Export button. 4. Navigate to the DB Log Export page.
On the DB Log Export page, click the Register button. 5. Go to the Register DB Log Export page.
On the DB Log Export Registration page, after entering the required information, click the Complete button.
Category
Required
Detailed description
Log type
Required
Log type to be saved
Save bucket name
Required
Object Storage bucket name to be saved
Authentication key > Access key
Required
Access key for accessing the Object Storage you want to store
Authentication key > Secret key
Required
Secret key for accessing the Object Storage you want to store
File creation cycle
Required
File creation frequency in Object Storage
Whether to delete the original log
Selection
Whether to delete the original logs when exporting to Object Storage
Table. EPAS (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
EPAS (DBaaS) List page, click the resource you want to manage DB Log export for. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button and then click the DB Log Export button. 4. Go to the Export DB Log page.
On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, or Terminate buttons.
Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
Edit: Modify the DB Log export mode setting.
Cancel: Cancels the DB Log export mode setting.
Minor version upgrade
If a latest patch that includes security enhancements and feature improvements is available, it can be applied through the version upgrade feature. Only minor version upgrades are supported within the same major version.
Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.
It is recommended to perform an immediate backup in advance to prepare for any issues that may arise during the upgrade process. * If not, a failure may occur and some data may not be recoverable.
In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. * First check the version of Replica, and if necessary, perform a version upgrade.
The backed-up data is automatically deleted after the version upgrade is completed.
To perform a minor version upgrade, follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS (DBaaS) List Navigate to the page.
On the EPAS(DBaaS) List page, click the resource to upgrade the Minor version. 3. EPAS(DBaaS) Details Navigate to the page.
Version Upgrade The popup window opens.
Version Upgrade In the popup window, select the updated version, then click the Confirm button.
Version Upgrade Notification Click the OK button in the popup window.
Configure Migration
Provides a Migration feature that synchronizes in real time with the operational database and replicates using a Replication method without any service interruption.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS (DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to migrate. 3. Go to the EPAS(DBaaS) Details page.
Click the More button and click the Migration Configuration button. 4. Migration Configuration The popup window opens.
Migration configuration In the popup window, review the instructions and click the Confirm button. 5. Go to the Migration configuration page.
After entering the required information on the Migration configuration page, click the Check Connection button.
When the 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 that is the migration target
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 that is the migration target
Table. EPAS (DBaaS) Migration Configuration Items
Promote Migration Cluster to Master Cluster
You can promote a fully configured Migration Cluster to a Master Cluster.
Caution
When the master is promoted, synchronization with the source DB that is the migration target is stopped.
To promote the Migration Cluster to Master, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to promote to Master. 3. Navigate to the EPAS(DBaaS) Details page.
Click the More button and then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
Master Promotion Notification Click the Confirm button in the popup window.
Managing Block Storage Usage
You can view the usage of Block Storage by type allocated to the DB instance.
To view Block Storage usage, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to view Block Storage usage. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button and then click the Block Storage Usage Management button. 4. Go to the Block Storage Usage Management page.
On the Block Storage Usage Management page, click the View button. 5. Block Storage Usage Management The page displays usage by Block Storage type.
Retrieving usage by Block Storage type takes a short amount of time.
Upgrade OS Kernel
You can upgrade the OS kernel to improve the functionality of the running database and apply security patches.
Caution
The service will be unavailable while the OS upgrade is in progress.
The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS Kernel, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to upgrade the OS Kernel. 3. EPAS(DBaaS) Details Navigate to the page.
Click the More button, then click the OS(Kernel) Upgrade button. 4. OS(Kernel) Upgrade Notification A popup window opens.
OS(Kernel) Upgrade Notification Check the instructions in the popup window and click the Confirm button.
1.2.2 - Backing up and restoring the DB
Users can configure backups for EPAS (DBaaS) through the Samsung Cloud Platform Console and restore using the backed‑up files.
EPAS(DBaaS) Backing up
To ensure that user data is stored securely, EPAS (DBaaS) provides a data backup feature based on its own backup commands. Additionally, you can verify whether the backup was successful using the backup history feature, and you can also delete backed-up files.
Configure Backup
Refer to EPAS(DBaaS) 생성하기 for how to configure backup settings for EPAS (DBaaS).
To modify the backup settings of a created resource, follow the steps below.
Caution
For reliable backups, we recommend adding separate BACKUP storage or sufficiently expanding storage capacity. * Especially when the backup data exceeds 100 GB and experiences frequent changes, please secure additional storage equal to about 60 % of the data size. * For storage addition and expansion methods, please refer to the guides EPAS(DBaaS) 스토리지 추가하기, EPAS(DBaaS) 스토리지 증설하기.
If a backup is configured, it runs at the specified time after the set time, and additional fees apply based on the backup size.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
On the EPAS (DBaaS) List page, click the resource you want to configure backup for. 3. Go to the EPAS(DBaaS) Details page.
Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
When configuring a backup, click Use in the Backup Settings popup, select retention period, backup start time, and Archive backup interval, then click the Confirm button.
If you want to stop the backup setting, deselect Use in the Backup Settings popup window and authenticate via the logged-in user’s mobile phone. Once user authentication is completed, the backup setting is disabled and backup execution stops.
Perform immediate backup
If additional data protection is required, you can quickly create a backup using the instant backup feature.
To perform an immediate backup, follow these steps.
Click the All Services > Database > EPAS(DBaaS) menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS (DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to perform an immediate backup. 3. Go to the EPAS(DBaaS) Details page.
Click the Immediate Backup button of the backup item. 4. Immediate Backup Settings popup window opens.
In the Immediate backup setup popup, click the Confirm button.
Check backup history
안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, refer to 알림 정책 생성하기.
To view the backup history, follow these steps.
Click the All Services > Database > EPAS(DBaaS) menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
Click the EPAS(DBaaS) menu on the Service Home page. 2. Go to the EPAS (DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to view the backup history. 3. Navigate to the EPAS(DBaaS) Details page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
EPAS(DBaaS) List page, click the resource to view the backup history. 3. Navigate to the EPAS(DBaaS) Details page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
When user authentication is completed, the backup file will be deleted.
Recover EPAS(DBaaS)
If a failure or data loss occurs and restoration from a backup file is required, recovery can be performed based on a specific point in time using the recovery feature. When you perform EPAS (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and recovery proceeds with the database’s configuration information and data.
Caution
To perform recovery, you need at least an amount of space equal to the Disk data type’s capacity. If disk space is insufficient, recovery may fail.
To restore EPAS(DBaaS), follow the steps below.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
Click the EPAS(DBaaS) menu on the Service Home page. 2. EPAS (DBaaS) List Navigate to the page.
EPAS(DBaaS) resource On the list page, click the resource you want to recover. 3. EPAS(DBaaS) Details page is accessed.
Click the Database Recovery button. 4. Go to the Database Recovery page.
Database Recovery Configuration After entering the relevant information in the area, click the Complete button.
Required status
Detailed description
Recovery type
Required
Set the point in time the user wants to recover
Backup point (recommended): Recover based on the backup file. Select from the list of backup file timestamps displayed in the list
Custom point: Recover to a user‑desired point within the range where backups are possible. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the initial backup start time up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix
Required
Recovery DB server name
Start with a lowercase English letter, then use lowercase letters, numbers, and special characters (-) to input 3 to 16 characters
Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name
Required
Recovery DB cluster name
Enter using English letters, 3 ~ 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Recovery DB server type
Standard: standard specifications commonly used
High Capacity: large-capacity server with 24vCore or more
Service Type > Planned Compute
Selection
Planned Compute가 설정된 자원 현황
In Use: Number of resources with Planned Compute configured that are currently in use
Configured: Number of resources with Planned Compute configured
Coverage Preview: Amount applied by Planned Compute per resource
Create Planned Compute Service: Go to the Planned Compute service application page
DATA: Storage area for table data, archive files, etc.
Applied identically with the storage type set in the original cluster
Enter capacity as a multiple of 8 within the range 16 to 5,120
Additional: Storage area for DATA, Archive, TEMP, Backup data
Applied identically with the storage type set in the original cluster
In the recovery DB, only DATA, TEMP, and Archive purposes can be added
After selecting Use, enter the storage purpose and capacity
To add storage, click the Add button; to delete, click the x button
Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username
Required
Database username
Apply the same username set in the original cluster
Database Port number
Required
Database Port number
Apply the same Port number as set in the original cluster
IP access control
Selection
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
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 an entered IP, click the x button next to the entered IP
Maintenance period
Selection
DB maintenance window
Use if selected, you can set the day of the week, start time, and duration
The maintenance window is a feature that lets the user define the time slot for patch operations, and any patch work during that period must be performed directly by the user.
We ask you to set a maintenance window for the stable operation of the system; we are not responsible for any problems arising from not setting it or from failure to perform tasks within the designated period.
tag
Selection
Add Tag
After clicking the Add Tag button, enter or select Key, Value values
Table. EPAS (DBaaS) recovery configuration items
1.2.3 - Configure Read Replica
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using the detailed options.
Configure Replica
You can create replica servers for read‑only or disaster‑recovery purposes through replica configuration. You can create up to 5 replicas per database.
information
To configure a disaster recovery Replica, please create it via Replica configuration(Other Region).
To configure a Replica, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to configure the Replica. 3. Navigate to the EPAS(DBaaS) Details page.
Click the Replica configuration button. 4. Go to the Replica configuration page.
After entering information in the Replica configuration area, click the Complete button.
Category
required status
Detailed description
Region
Required
Region to configure the Replica
Replica configuration (Other Region)exposed only when selected
Replica count
Required
Number of Replicas to configure
Up to 5 can be configured per cluster
If you select more than one value, additionally enter the Replica name and service type information
Replica name
Required
Replica server name
Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) to enter 3 to 19 characters
The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type
Required
Replica server type
Standard: standard specification commonly used
High Capacity: large-capacity server with 24 vCore or more
Service Type > Planned Compute
Selection
Status of resources with Planned Compute configured
In Use: Number of resources with Planned Compute that are currently in use
Configured: Number of resources with Planned Compute configured
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Navigate to the Planned Compute service application page
Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
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 an entered IP, click the x button next to the entered IP
maintenance period
Selection
Database maintenance window
If you select Use, set the day, start time, and duration
It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
If set to unused, we are not responsible for any issues arising from patches not being applied.
Tag
Select
Add Tag
Add Tag after clicking the button Enter or select Key, Value values
Table. EPAS (DBaaS) Replica configuration items
Reconfigure Replica
If a network outage or replication delay with the Master Cluster occurs, you can use the Replica reconstruction function to replicate the Master Cluster’s data again.
To reconfigure the Replica, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
On the EPAS(DBaaS) List page, click the resource to reconfigure the Replica. 3. EPAS(DBaaS) Details Navigate to the page.
Click the Reconstruct Replica button. 4. Replica Reconfiguration Notification A popup window opens.
Replica Reconfiguration Notification popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a configured Replica Cluster to a Master Cluster.
Caution
When the Master is promoted, synchronization with the existing Master Cluster is stopped.
To promote a Replica Cluster to Master, follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS(DBaaS) List go to the page.
On the EPAS(DBaaS) List page, click the resource to promote to Master. 3. Go to the EPAS(DBaaS) Details page.
Click the More button, then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
In the Master Promotion Notification popup, click the Confirm button.
1.2.4 - EPAS (DBaaS) server connection
Scenario Overview
EPAS(DBaaS) Server Connection scenario creates a Bastion host (Virtual Server) and a Database service, and accesses the DB service through the Bastion host. To reliably connect to EPAS (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Figure. EPAS (DBaaS) Connection Architecture
Scenario components
You can build the scenario using the following services.
Service group
service
Detailed description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Networking
VPC > Subnet
A service that lets users segment the network within a VPC to match their purpose and scale
Networking
VPC > Public IP
A service that reserves a public IP and allocates and releases it to Compute resources.
Networking
VPC > Internet Gateway
A service that connects VPC resources to the Internet
Networking
Security Group
Virtual firewall that controls server traffic
Database
EPAS(DBaaS)
A service that easily creates and manages EPAS in a web environment.
Compute
Virtual Server
Virtual server optimized for cloud computing
Compute
Virtual Server > Keypair
Encryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
All Services > Networking > FirewallClick the menu. 1. Navigate to the Firewall’s Service Home page.
On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
On the detail information page, click the Rules tab. 4. Go to the Rules tab.
Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address
Destination address
Protocol
Port
Operation
Direction
Explanation
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. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide explains how to connect using pgAdmin. Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB client program (pgAdmin) on the Bastion host
Go to the official pgAdmin page and download the pgAdmin program.
Connect the user’s PC hard drive to upload the file to the Bastion host.
Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install it.
5-3. ### Connect to the Database using the DB client program (pgAdmin)
Run pgAdmin and click the Add New Server button.
In the Register - Server popup, enter the Database server information created in 3-1. EPAS(DBaaS) 서비스 생성하기 into the General and Connection tabs, and click the Save button.
Screen (tab)
Required input element item
input value
General
Name
Custom (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 fields
Click the name of the database created in pgAdmin to connect.
After connecting, you can perform simple queries, etc.
1.2.5 - Extension Usage
Using EPAS(DBaaS) Extension
Reference
You can view the list of extensions included in each EPAS version on the PostgreSQL official page.
You can view the list of extensions that can be installed in the current database with the SQL statement below.
SQL> select * from pg_available_extensions;
In EPAS(DBaaS), the items installed in addition to the default extensions included per version are as follows.
Extension name
Explanation
pg_cron
A scheduler that can schedule jobs using cron syntax within the database.
pgvector
Provides AI vector operation features such as vector data types and similarity search.
postgis
Provides GIS (Geographic Information System) spatial object storage and spatial query functionality
If you need to install additional extensions beyond the items above, refer to Support Center > Inquiry and contact us.
After a request is received, we will review it and proceed with installation. Please note that some extensions may not function properly during replica configuration and recovery.
1.3 - API Reference
API Reference
1.4 - CLI Reference
CLI Reference
1.5 - Release Note
EPAS(DBaaS)
2026.07.16
FEATUREAdd immediate backup, Disk usage query feature, and ServiceWatch service integration
Add immediate backup and disk usage query feature
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
Through the Disk usage query feature, you can view the usage of each Block Storage type assigned to an instance.
ServiceWatch service integration
You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.
Add third-generation server type
The third-generation server type has been newly added. * For more details, please refer to the EPAS(DBaaS) 서버 타입.
Provides notification functionality for backup success and failure. * For detailed information, refer to 알림 정책 생성하기.
Migration feature added
Provides replication-based zero-downtime data migration functionality. * For more details, see Migration 구성하기.
Add HDD, HDD_KMS type to the Block Storage type
2025.02.27
NEWEPAS(DBaaS) service official version release
A web-based EPAS (DBaaS) service that enables easy creation and management of EPAS has been launched.
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 through a web-based console and performs management functions for operation.
PostgreSQL(DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for potential issues with the DB server or data, we provide an automatic backup feature at user-specified times, enabling data recovery at the desired point in time.
Figure. PostgreSQL(DBaaS) Architecture
Provided features
PostgreSQL(DBaaS) provides the following features.
Auto Provisioning: UI allows installation and configuration of Database (DB), and provides an Active-standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the node transition of Active‑Standby can be performed directly by the user through a switch‑over.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be configured by the user, and additional fees may be incurred based on the backup size. * It also provides a recovery function for backed‑up data, and when the user initiates a recovery, a separate database is created, and the recovery proceeds to the point in time selected by the user (backup creation time, user‑specified time). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
Version Management: We provide Minor version upgrade functionality due to some feature improvements and security patches.
Replica configuration: For load balancing of read traffic and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
Audit Settings: Supports audit (Audit) functionality for key activities within the database.
Parameter management: It is possible to modify DB configuration parameters related to performance improvement and security.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
Archive Management: You can set the retention period for Archive files (1~35 days) on the DB server and configure the Archive mode (On/Off).
DB Log Export: You can export stored logs to the user’s Object Storage through Audit settings.
Migration: Synchronizes data in real time with the operational database and supports migration using replication without service interruption.
OS kernel upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.
Components
PostgreSQL(DBaaS) provides pre‑validated engine versions and various server types according to its open‑source support policy. Users can select and use it according to the scale of the service they wish to configure.
Engine version
The engine versions supported by PostgreSQL (DBaaS) are as follows.
Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
The next version of PostgreSQL is scheduled to be available after September 2026. The actual service delivery schedule is subject to change.
PostgreSQL 15.17
PostgreSQL 16.13
PostgreSQL 17.9
Server type
The server types supported by PostgreSQL (DBaaS) are as follows.
For detailed information about the server types offered by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) 서버 타입.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server types
Standard: Standard specifications (vCPU, Memory) commonly used
High Capacity: Large server specifications of 24 vCores or more
Server specifications
db1
Provided server specifications
db1: Standard configuration (vCPU, Memory) commonly used
dbh2: Large-scale server specifications
Provides servers with 24 vCore or more
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. PostgreSQL (DBaaS) server type components
Preceding Service
This is a list of services that must be pre‑configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
A service that provides an isolated virtual network in a cloud environment
Table. PostgreSQL (DBaaS) Preliminary Service
2.1.1 - Server type
PostgreSQL(DBaaS) server type
PostgreSQL (DBaaS) offers server types composed of various combinations such as CPU, Memory, and Network Bandwidth.
When creating PostgreSQL(DBaaS), the Database Engine is installed according to the server type selected for the intended use.
Reference
The server types offered may vary depending on the region and AZ.
The server types supported by PostgreSQL (DBaaS) are as follows.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server type categories
Standard: Configured with standard specifications (vCPU, Memory) commonly used
High Capacity: Large-capacity server specifications exceeding Standard
Server specifications
db1
Provided server type classification and generation
db: means standard specifications, and 1 indicates the generation
dbh: h indicates large‑capacity server specifications, and 2 indicates the generation
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. PostgreSQL (DBaaS) server type format
db1 server type
The db1 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db1v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db1v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m8
4 vCore
8 GB
Maximum 10 Gbps
Standard
db1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m48
4 vCore
48 GB
Maximum 10 Gbps
Standard
db1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db1v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db1v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db1v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db1v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db1v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db1v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db1v10m20
10 vCore
20 GB
Maximum 10 Gbps
Standard
db1v10m40
10 vCore
40 GB
Maximum 10 Gbps
Standard
db1v10m80
10 vCore
80 GB
Up to 10 Gbps
Standard
db1v10m120
10 vCore
120 GB
Maximum 10 Gbps
Standard
db1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db1v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db1v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db1v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db1v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db1v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db1v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db1v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db1v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db1v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db1v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db1v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. PostgreSQL(DBaaS) server type specifications - db1 server type
db2 server type
The db2 server type of PostgreSQL (DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
server server type
vCPU
Memory
Network Bandwidth
Standard
db2v2m4
2 vCore
4 GB
Maximum 10 Gbps
Standard
db2v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db2v16
(Note: The original text “db2v2m16” seems like a code; I kept it unchanged as per rule.) | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v32m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Maximum 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Maximum 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
Table. PostgreSQL (DBaaS) server type specifications - db2 server type
dbh2 server type
The dbh2 server type of PostgreSQL (DBaaS) is provided with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
High Capacity
dbh2v24m48
24 vCore
48 GB
Maximum 25 Gbps
High Capacity
dbh2v24m96
24 vCore
96 GB
Maximum 25 Gbps
High Capacity
dbh2v24m192
24 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh2v24m288
24 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh2v32m64
32 vCore
64 GB
Maximum 25 Gbps
High Capacity
dbh2v32m128
32 vCore
128 GB
Maximum 25 Gbps
High Capacity
dbh2v32m256
32 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh2v32m384
32 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh2v48m192
48 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh2v48m576
48 vCore
576 GB
Maximum 25 Gbps
High Capacity
dbh2v64m256
64 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh2v64m768
64 vCore
768 GB
Maximum 25 Gbps
High Capacity
dbh2v72m288
72 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh2v72m864
72 vCore
864 GB
Maximum 25 Gbps
High Capacity
dbh2v96m384
96 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh2v96m1152
96 vCore
1152 GB
Maximum 25 Gbps
High Capacity
dbh2v128m512
128 vCore
512 GB
Maximum 25 Gbps
High Capacity
dbh2v128m1536
128 vCore
1536 GB
Maximum 25 Gbps
Table. PostgreSQL(DBaaS) server type specifications - dbh2 server type
db3 server type
The db3 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db3v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db3v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db3v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db3v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db3v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db3v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db3v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db3v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db3v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db3v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db3v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db3v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db3v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db3v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db3v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db3v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db3v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db3v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db3v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db3v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db3v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db3v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db3v10m80
10 vCore
80 GB
Maximum 10 Gbps
Standard
db3v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db3v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db3v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db3v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db3v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db3v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db3v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db3v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db3v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db3v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db3v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db3v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db3v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db3v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db3v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db3v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db3v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. PostgreSQL(DBaaS) server type specifications - db3 server type
dbh3 server type
The dbh3 server type of PostgreSQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
Intel 6th‑generation (Granite Rapids) Xeon 6738P Processor up to 4.1 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
High Capacity
dbh3v24m48
24 vCore
48 GB
Maximum 25 Gbps
High Capacity
dbh3v24m96
24 vCore
96 GB
Maximum 25 Gbps
High Capacity
dbh3v24m192
24 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh3v24m288
24 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh3v32m64
32 vCore
64 GB
Maximum 25 Gbps
High Capacity
dbh3v32m128
32 vCore
128 GB
Maximum 25 Gbps
High Capacity
dbh3v32m256
32 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh3v32m384
32 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh3v48m192
48 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh3v48m576
48 vCore
576 GB
Maximum 25 Gbps
High Capacity
dbh3v64m256
64 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh3v64m768
64 vCore
768 GB
Maximum 25 Gbps
High Capacity
dbh3v72m288
72 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh3v72m864
72 vCore
864 GB
Maximum 25 Gbps
High Capacity
dbh3v96m384
96 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh3v96m1152
96 vCore
1152 GB
Maximum 25 Gbps
High Capacity
dbh3v128m512
128 vCore
512 GB
Maximum 25 Gbps
High Capacity
dbh3v128m1536
128 vCore
1536 GB
Maximum 25 Gbps
Table. PostgreSQL (DBaaS) server type specifications - dbh3 server type
Database password
Required
Password to use when accessing the DB
Enter 8 to 30 characters, including letters, numbers, and special characters (“‘ excluded)
Check database password
Required
Re-enter the same password to use for DB access
Database Port number
Required
Port number required for DB connection
Enter the DB port within the range 1200 ~ 65535
Backup > Use
Selection
Backup usage
Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period
Selection
Backup retention period
Select the backup retention period, and set the file retention period from 7 days to 35 days
Backup files incur additional charges based on their size
Backup > Backup Start Period
Selection
Backup start time
Select backup start time
The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be set
Backup > Archive backup schedule
Selection
Archive backup frequency
Select the archive backup frequency
The archive backup frequency is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log configuration
Selection
Whether to store Audit Log
Select Use to configure the Audit Log feature
DDL, DML, and user connection information records are stored
The user can specify the type of SQL statements to audit via the log_statement parameter, and can modify it through the Parameter screen
In the Additional Information Input area, enter or select the required information.
Category
Required status
Detailed description
tag
Selection
Add Tag
Up to 50 per resource can be added
After clicking the Add Tag button, enter or select Key, Value values
Table. PostgreSQL(DBaaS) additional information input fields
Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
Once creation is complete, verify the created resource on the Resource List page.
PostgreSQL(DBaaS) View detailed information
The PostgreSQL (DBaaS) service allows you to view and edit the full resource list and detailed information. On the PostgreSQL(DBaaS) Details page, it consists of the Details, Tags, Activity History tabs, and for databases with a Replica configured, a Replica Information tab is added.
Follow the steps below to view detailed information about the PostgreSQL (DBaaS) service.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List Click the resource to view detailed information on the page. 3. PostgreSQL(DBaaS) Details Go to the page.
PostgreSQL(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Category
Detailed description
Cluster status
Cluster status with DB installed
Creating: Cluster is being created
Editing: Cluster is transitioning to an operational state
Error: Cluster encountered an error during operation
If it occurs continuously, contact the administrator
Failed: Cluster failed during creation
Restarting: Restarting the cluster
Running: Cluster is operating normally
Starting: Starting the cluster
Stopped: Cluster is stopped
Stopping: Cluster is being stopped
Synchronizing: Synchronizing the cluster
Terminating: Deleting the cluster
Unknown: Cluster status is unknown
If it occurs continuously, contact the administrator
Upgrading: Cluster is transitioning to an upgrading state
Cluster control
Buttons to change the cluster state
Start: Start a stopped cluster
Stop: Stop a running cluster
Restart: Restart a running cluster
Switch-Over: Switch a standby cluster to Active
View more features
Cluster-related management buttons
Service Status Synchronization: Retrieve real-time DB service status
Backup History: Check backup execution status and view history when backups are configured
Database Recovery: Recover the database to a specific point in time
Parameter Management: View and modify DB configuration parameters
Replica Configuration: Configure a read‑only Replica cluster
Replica Configuration (Other Region): Configure a disaster‑recovery Replica in another region; the button is disabled if the account has no region available for configuration
DB User Management: View and manage DB account (user) information registered in the database
DB Access Control Management: Register and revoke allowed IP addresses based on DB accounts registered in the database
Archive Settings Management: Configure archive file retention period and archive mode
DB Log Export: Export stored logs to the user’s Object Storage via Audit settings
Migration Configuration: Provides migration functionality using a replication method
Block Storage Usage Management: Provides usage query functionality for each Block Storage type
OS (Kernel) Upgrade: Upgrade the OS Kernel version
Service cancellation
Cancel Service button
Table. PostgreSQL (DBaaS) status information and additional features
Detailed Information
PostgreSQL(DBaaS) List page lets you view detailed information of the selected resource and, if necessary, edit the information.
Category
Detailed description
Server Information
Server information configured in this cluster
Category: Server type (Active, Standby, Replica)
Server name: Server name
IP port: Server IP and port
Availability Zone: Server location
Status: Server status
service
Service name
Resource Type
Resource Type
SRN
Unique resource ID in Samsung Cloud Platform
In the DB service, it refers to the cluster SRN
Resource Name
Resource name
In the DB service, it refers to the cluster name
Resource ID
Unique resource ID in the service
Constructor
User who created the service
Creation Date/Time
Service creation date and time
Modifier
User who edited the service information
Modification date and time
Date and time the service information was modified
Image version
Installed DB image and version information
If a version upgrade is required, click the Edit icon to configure
If log collection configuration is required, click the Edit icon next to Log Collection to configure
Time zone
Standard time zone used by the database
DB Locale
Locale to use in the DB
Database Encoding
Character encoding to use for the DB
VIP
Virtual IP information
can be verified only when redundancy is configured
Network
Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP access control
Service access policy configuration
If you need to add or remove an IP, click the Edit icon to configure
Active & Standby
Active/Standby server type, default OS, additional Disk information
If you need to modify the server type, click the Edit icon next to the server type to configure it. Refer to the server type modification procedure in 서버 타입 변경하기
Modifying the server type requires a server reboot
If you need to expand storage, click the Edit icon next to the storage capacity to expand it. Refer to the storage expansion procedure in 스토리지 증설하기
If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure in 스토리지 추가하기
Table. PostgreSQL(DBaaS) Database detailed information items
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, the number of replicas, and the replication status of the Replica.
Category
Detailed description
Master information
Name of the Master cluster
Replica count
Number of Replicas created in the Master cluster
Replica status
Replica server status in the Master cluster
You can view the server name, status query, status details, and status check time
To view the Replica status, click the Status Query button
While the query is in progress, the cluster remains in Synchronizing state, and once the query completes, the cluster changes to Running state
Table. Replica information tab detailed information items
tag
PostgreSQL(DBaaS) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.
Category
Detailed description
Tag list
Tag list
You can view the Key and Value information of the tag
Up to 50 tags can be added per resource
When entering a tag, you can search and select from the list of previously created Keys and Values
Table. PostgreSQL(DBaaS) tag tab item
Job History
On the PostgreSQL(DBaaS) List page, you can view the operation history of the selected resource.
Category
Detailed description
Task History List
Resource Change History
Operation Time, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Operator Information Check
Table. Work History tab detailed information items
PostgreSQL(DBaaS) Managing Resources
If you need to change or restore the existing configuration options of a created PostgreSQL(DBaaS) resource, or require a Replica configuration, you can perform the task on the PostgreSQL(DBaaS) Details page.
Operation Control
If changes occur to a running PostgreSQL (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of PostgreSQL(DBaaS), follow the steps below.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource you want to control. 3. Go to the PostgreSQL(DBaaS) Details page.
Check the PostgreSQL(DBaaS) status and complete the change using the control button below.
Start: DB service is installed on the server and the DB service is running (Running).
Stop: The server where the DB service is installed and the DB service will be stopped (Stopped).
Restart: Only the DB service will be restarted.
Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize service status
You can synchronize the real-time service status of PostgreSQL (DBaaS).
To check the service status of PostgreSQL (DBaaS), follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource to view the service status. 3. Navigate to the PostgreSQL(DBaaS) Details page.
Click the Service status synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
When the query is completed, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
Caution
If you modify the server type, a server restart is required. Please verify separately any software license modifications or software settings and their implementation due to server specification changes.
To change the server type, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource to change the server type. 3. Navigate to the PostgreSQL(DBaaS) Details page.
Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
Edit Server Type In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. In a redundant DB setup, all redundant servers are added simultaneously.
Caution
It is applied in the same way as the Storage type selected when creating the service.
For a DB configured with redundancy, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
A Replica’s storage cannot be larger than the primary’s storage. * Expand the Replica storage first, then expand the Master storage.
When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List Click the resource to add storage on the page. 3. PostgreSQL(DBaaS) Details Go to the page.
Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB setup, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) list page, click the resource to change the server type. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the Edit icon for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage A popup window opens.
Edit Additional Storage After entering the expanded capacity in the popup window, click the Confirm button.
PostgreSQL(DBaaS) Terminate
You can cancel unused PostgreSQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
Caution
Replica is not deleted together. * If you also delete the Replica, handle it separately in the resource list.
If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel PostgreSQL(DBaaS), follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
After termination is complete, check whether the resource has been terminated on the PostgreSQL(DBaaS) list page.
2.2.1 - Managing DB Services
Users can manage PostgreSQL (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
Provides a feature that allows you to easily view and modify database configuration parameters.
Query Parameter
To view configuration parameters, follow these steps.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL(DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. View Notification popup opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List Click the resource on the page for which you want to view or modify parameters. 3. PostgreSQL(DBaaS) Details Go to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. Lookup Notification A popup window opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
If editing is required, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
When the input is complete, click the Done button.
Manage DB Users
Provides administrative features to view DB user information and modify status information.
Query DB Users
To look up DB users, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource you want to use to view DB users. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the DB User Management button. 4. Go to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
Changing DB User Status
To change the status of the retrieved DB user, follow these steps.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List On the page, click the resource for which you want to edit the DB user. 3. PostgreSQL(DBaaS) Details Go to the page.
Click the More button, then click the DB User Management button. 4. Navigate to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
If modification is required, click the Edit button, and change the status area value or enter remarks.
When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IP addresses that can access the database, configuring it so that only authorized IPs are allowed access.
안내
Perform a DB user lookup before setting DB access control. For DB user lookup, please refer to DB 사용자 관리하기.
View DB Access Control
To view DB users with IP access control enabled, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource you want to manage access control for. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the DB Access Control Management button. 4. Go to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
Add DB access control
Follow these steps to add IP access control.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Go to the page.
On the PostgreSQL(DBaaS) List page, click the resource for which you want to add IP access control. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the DB Access Control Management button. 4. Go to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
When the query is complete, click the Add button. 6. Add DB Access Control The popup window opens.
Add DB Access Control In the popup window, select the DB username and enter the IP address.
When the input is complete, click the Complete button.
Delete DB access control
To delete IP access control, follow these steps.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List Click the resource you want to delete IP access control for. 3. PostgreSQL(DBaaS) Details Go to the page.
Click the More button, then click the DB Access Control Management button. 4. Go to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
When the query is complete, click the Delete button. 6. Delete popup window opens.
Delete popup window: click the Confirm button.
Manage Archive
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment.
Additionally, it provides a feature to manually delete archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
안내
When creating a service, the default setting uses Archive mode, and the retention period is 3 days.
Configure Archive mode
To set the Archive mode, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL (DBaaS) List page, click the resource you want to set Archive mode for. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Archive Settings Management Navigate to the page.
On the Archive Settings Management page, click the Search button. 5. Retrieving may take a short amount of time.
Click the Edit button and select usage status and retention period.
When the edit is complete, click the Done button.
Delete archive file
To delete the Archive file, follow these steps.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource for which you want to set Archive mode. 3. Go to the PostgreSQL(DBaaS) Details page.
Click the More button, then click the Archive Settings Management button. 4. Go to the Archive Settings Management page.
On the Archive Settings Management page, if you want to delete all Archive files, click the Delete All Archives button; if you want to delete only backed-up Archive files, click the Delete Backed-up Archives button.
Modify Audit Settings
You can change the Audit log storage settings of PostgreSQL (DBaaS).
To change the Audit log storage settings of PostgreSQL (DBaaS), follow the steps below.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Go to the page.
PostgreSQL(DBaaS) List Click the resource on the page to view the service status. 3. PostgreSQL(DBaaS) Details Go to the page.
Click the Edit icon of Audit Settings at the bottom of the detailed information. 4. Modify Audit Settings A popup window opens.
Audit 설정 수정 팝업창에서 사용 여부를 수정한 후, 확인 버튼을 클릭하세요.
When Use is selected, the Audit log feature is enabled. * Enabling audit logging may degrade database performance.
If you disable use, the Audit log storage file will be deleted. * Back up the Audit log file separately before disabling.
Export DB Log
Supports exporting log data that requires long-term retention among audit (Audit) logs to Object Storage. Users can directly configure the log types that need to be stored, the destination Bucket for export, and the log export interval. Copies logs to the designated Object Storage for retention according to the configured criteria.
Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files.
안내
To use the DB Log export feature, you need to create an Object Storage. * For Object Storage creation, please refer to the Object Storage 사용자 가이드.
Please be sure to verify the expiration date and time of the authentication key. * If the authentication key expires, logs will not be stored in the bucket.
Please ensure that authentication key information is not exposed to external parties.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List On the page, click the resource whose DB Log you want to export. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button and then click the DB Log Export button. 4. Export DB Log Go to the page.
On the DB Log Export page, click the Register button. 5. Go to the Register DB Log Export page.
DB Log Export Registration page, after entering the required information, click the Complete button.
Category
Required
Detailed description
Log type
Required
Log type to be saved
Save bucket name
Required
Name of the Object Storage bucket to be saved
Authentication key > Access key
Required
Access key for accessing the Object Storage you want to store
Authentication key > Secret key
Required
Secret key for accessing the Object Storage you want to store
File creation cycle
Required
File creation frequency in Object Storage
Whether to delete the original log
Selection
Whether to delete the original logs when exporting to Object Storage
Table. PostgreSQL(DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource you want to manage DB Log export for. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the DB Log Export button. 4. Go to the Export DB Log page.
On the DB Log Export page, click the More button according to the log type you want to manage, then click the Export Now, Edit, or Cancel button.
Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
Edit: Modify the DB Log export mode settings.
Cancel: Cancel the DB Log export mode setting.
Minor version upgrade
If a latest patch that includes security enhancements and feature improvements is available, it can be applied via the version upgrade feature. Only minor version upgrades are supported within the same major version.
Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.
It is recommended to perform an immediate backup in advance to prepare for any issues that may arise during the upgrade process. * If not, a failure may occur, and some data may not be recoverable.
In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. *
The backed-up data is automatically deleted after the version upgrade is completed.
To perform a minor version upgrade, follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource to upgrade the Minor version. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
In the Version Upgrade popup, after selecting the updated version, click the Confirm button.
Version Upgrade Notification In the popup window, click the OK button.
Configure Migration
Provides a Migration feature that synchronizes in real time with the operational database and replicates using a Replication method without any service interruption.
You can promote a fully configured Migration Cluster to a Master Cluster.
Caution
When the master is promoted, synchronization with the source DB that is the migration target is stopped.
To promote the Migration Cluster to Master, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource to promote to Master. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the Master promotion button. 4. Master Promotion Notification The popup window opens.
Master Promotion Notification in the popup window, click the Confirm button.
Managing Block Storage Usage
You can view the usage of Block Storage by type allocated to the DB instance.
To view Block Storage usage, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource to view Block Storage usage. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the Block Storage Usage Management button. 4. Go to the Block Storage Usage Management page.
On the Block Storage Usage Management page, click the View button. 5. Block Storage Usage Management The page displays usage by Block Storage type.
Retrieving usage by Block Storage type takes a little time.
OS Kernel Upgrade
You can upgrade the OS kernel to improve the functionality of the running database and apply security patches.
Caution
The service will be unavailable while the OS upgrade is in progress.
The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
After the upgrade is complete, you cannot restore to the previous OS.
To upgrade the OS Kernel, follow these steps.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource to upgrade the OS Kernel. 3. Go to the PostgreSQL(DBaaS) Details page.
Click the More button, then click the OS(Kernel) Upgrade button. 4. OS(Kernel) Upgrade Notification A popup window opens.
OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
2.2.2 - Backing up and restoring the DB
Users can configure backups for PostgreSQL (DBaaS) via the Samsung Cloud Platform Console and restore using the backed‑up files.
PostgreSQL(DBaaS) Backing Up
PostgreSQL (DBaaS) provides data backup based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
Refer to PostgreSQL(DBaaS) 생성하기 for how to configure backup settings for PostgreSQL(DBaaS).
To modify the backup settings of a created resource, follow the steps below.
Caution
For reliable backups, we recommend adding separate BACKUP storage or sufficiently expanding storage capacity. * Especially when the backup data exceeds 100 GB and experiences frequent changes, please provision additional storage equal to approximately 60 % of the data size. * For instructions on adding and expanding storage, refer to the PostgreSQL(DBaaS) 스토리지 추가하기 and PostgreSQL(DBaaS) 스토리지 증설하기 guides.
If a backup is configured, it runs at the specified time after the set time, and additional fees are incurred based on the backup size.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource to set up a backup. 3. PostgreSQL(DBaaS) Details Go to the page.
Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
If you want to stop the backup setting, uncheck Use in the Backup Settings popup window and authenticate via the logged-in user’s mobile phone. Once user authentication is completed, the backup setting is disabled and backup execution stops.
Perform immediate backup
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
To perform an immediate backup, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List On the PostgreSQL(DBaaS) List page, click the resource to perform an immediate backup. 3. Go to the PostgreSQL(DBaaS) Details page.
Click the Immediate Backup button for the backup item. 4. Immediate backup settings popup window opens.
Immediate backup setting popup window, click the Confirm button.
Check backup history
안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, please refer to 알림 정책 생성하기.
To view the backup history, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List Click the resource to view the backup history on the page. 3. PostgreSQL(DBaaS) Details Go to the page.
Backup History Click the button. 4. Backup History The popup window opens.
Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
To delete the backup history, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
On the PostgreSQL (DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
When user authentication is completed, the backup file will be deleted.
PostgreSQL(DBaaS) Recover
If a failure or data loss requires restoration from a backup file, you can recover using the recovery feature based on a specific point in time. When you perform a PostgreSQL(DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds with the database’s configuration information and data.
Caution
To perform recovery, at least an amount of space equal to the Disk data type capacity is required. If disk space is insufficient, recovery may fail.
To restore PostgreSQL(DBaaS), follow the steps below.
All Services > Database > PostgreSQL (DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL(DBaaS) List Go to the page.
PostgreSQL(DBaaS) Resource On the list page, click the resource you want to recover. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the Database Recovery button. 4. Database Recovery Navigate to the page.
Database Recovery Configuration After entering the relevant information in this area, click the Complete button.
Category
Required
Detailed description
Recovery type
Required
Set the point in time the user wants to recover
Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
Custom point: Recover to a user‑desired point within the range of recoverable backup times. The recoverable period depends on the Archive backup interval setting, allowing recovery from the initial backup start time up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix
Required
Recovery DB server name
Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name
Required
Cluster name of the recovery DB
Enter using English letters, 3 ~ 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Server type for the recovery DB installation
Standard: standard specifications commonly used
High Capacity: large-capacity server with 24vCore or more
Service Type > Planned Compute
Selection
Status of resources with Planned Compute set
In Use: Number of resources with Planned Compute set that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Go to the Planned Compute service application page
DATA: Storage area for table data, archive files, etc.
Applied identically with the storage type set in the original cluster
Enter capacity as a multiple of 8 within the range 16 to 5,120
Additional: Storage area for DATA, Archive, TEMP, Backup data
Applied identically with the storage type set in the original cluster
In the recovery DB, only DATA, TEMP, and Archive purposes can be added
After selecting Use, enter the storage purpose and capacity
To add storage, click the Add button; to delete, click the x button
Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username
Required
Database username set in the source DB
Database Port number
Required
Database Port number configured in the source DB
IP access control
Selection
IP address for accessing the recovery DB
Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.1/32, 192.168.10.1/32), then click the Add button
To delete an entered IP, click the x button next to the entered IP
Maintenance period
Selection
DB maintenance window
If you select Use, set the day, start time, and duration
The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch work within that period must be performed directly by the user.
We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from not performing tasks within the window.
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Configure 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.
information
To configure a disaster recovery Replica, please create it via Replica configuration(Other Region).
To configure a Replica, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource to configure a Replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the Replica configuration button. 4. Go to the Replica configuration page.
After entering the information in the Replica configuration area, click the Complete button.
Category
required status
Detailed description
Region
Required
Region to configure the Replica
Replica configuration (Other Region)is displayed only when selected
Replica count
Required
Number of Replicas to configure
Up to 5 can be configured per cluster
If you select more than one value, additionally enter the Replica name and service type information
Replica name
Required
Replica server name
must start with a lowercase English letter, and using lowercase letters, numbers, and special characters(-) enter 3 to 19 characters
The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type
Essential
Replica server type
Standard: standard specification commonly used
High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute
Select
Status of resources with Planned Compute configured
In Use: Number of resources with Planned Compute configured that are currently in use
Configured: Number of resources with Planned Compute configured
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Navigate to the Planned Compute service application page
Block Storage configuration for using a replica DB
Basic OS: Area used on the server where the DB is installed
Applied identically according to the storage type set in the source DB
Capacity cannot be set
DATA: Storage area for table data, archive files, etc.
Applied identically according to the storage type set in the source DB
Capacity cannot be set
Additional: Storage area for DATA, Archive, TEMP, Backup data
Applied identically according to the storage type set in the source DB
In a replica, only DATA and TEMP purposes can be added
After selecting Use, enter the storage purpose and capacity. Capacity must be a multiple of 8 within the range 16 to 5,120
To add storage, click the Add button; to delete, click the x button. Up to 9 can be added.
IP access control
Select
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not 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 an entered IP, click the x button next to the entered IP
maintenance period
Select
Database maintenance window
Select Use to set the day, start time, and duration
It is recommended to configure a maintenance window for stable database management. Patch operations will be performed at the scheduled time, causing service interruption
If set to unused, we are not responsible for issues arising from patches not being applied.
tag
Selection
Add Tag
Add Tag After clicking the Add Tag button, enter or select Key and Value
If a network failure or replication delay with the Master Cluster occurs, you can re-replicate the Master Cluster’s data using the Replica reconstruction feature.
To reconfigure the Replica, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
On the PostgreSQL(DBaaS) List page, click the resource to reconfigure the replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Replica Reconstruction Click the button. 4. Replica Reconfiguration Notification A popup window opens.
Replica Reconfiguration Notification popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a fully configured Replica Cluster to a Master Cluster.
Caution
When the Master is promoted, synchronization with the existing Master Cluster is halted.
To promote a Replica Cluster to Master, follow these steps.
All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
PostgreSQL(DBaaS) List page, click the resource to promote to Master. 3. PostgreSQL(DBaaS) Details Navigate to the page.
Click the More button, then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
Master Promotion Notification In the popup window, click the Confirm button.
2.2.4 - Connect to DB server
Scenario Overview
PostgreSQL(DBaaS) server connection scenario involves creating a Bastion host(Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to PostgreSQL (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Figure. PostgreSQL(DBaaS) server connection architecture
Scenario components
You can build the scenario using the following services.
Service group
service
Detailed description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Networking
VPC > Subnet
A service that lets users segment the network within a VPC to match their purpose and scale
Networking
VPC > Public IP
A service that reserves a public IP and allocates and releases it to Compute resources.
Networking
VPC > Internet Gateway
A service that connects VPC resources to the Internet
Networking
Security Group
Virtual firewall that controls server traffic
Database
PostgreSQL(DBaaS)
A service that easily creates and manages EPAS in a web environment.
Compute
Virtual Server
Virtual server optimized for cloud computing
Compute
Virtual Server > Keypair
Encryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
The All Open(Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
All Services > Networking > FirewallClick the menu. 1. Navigate to the Firewall’s Service Home page.
On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
On the detail information page, click the Rules tab. 4. Go to the Rules tab.
Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address
Destination address
Protocol
Port
Operation
Direction
Explanation
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. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide explains how to connect using pgAdmin. Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB client program (pgAdmin) on the Bastion host
Go to the official pgAdmin page and download the pgAdmin program.
Connect the user’s PC hard drive to upload the file to the Bastion host.
Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install it.
5-3. ### Connect to the Database using the DB client program (pgAdmin)
Run pgAdmin and click the Add New Server button.
In the Register - Server popup window, enter the Database server information created in 3-1. PostgreSQL(DBaaS) 서비스 생성하기 on the General and Connection tabs, and click the Save button.
Screen (tab)
Required input element item
input value
General
Name
Custom (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 fields
Click the name of the database created in pgAdmin to connect.
After connecting, you can perform simple queries, etc.
2.2.5 - Extension Use
PostgreSQL(DBaaS) Extension usage
Note
You can view the list of extensions included in each PostgreSQL version on the PostgreSQL official page.
You can view the list of extensions that can be installed in the current database with the SQL statement below.
SQL> select * from pg_available_extensions;
PostgreSQL (DBaaS) includes the following items in addition to the default extensions for each version.
Extension name
Explanation
pgaudit
Provides detailed audit logging at the session and object level
pg_cron
A scheduler that can schedule jobs using cron syntax within the database.
pg_hint_plan
Provides a feature to apply hint clauses to SQL execution plans.
pgvector
Provides vector data types and AI vector operation features such as similarity search.
postgis
GIS (Geographic Information System) provides spatial object storage and spatial query functionality
If you need to install additional extensions beyond the items above, refer to Support Center > Inquiry and contact us.
After a request is received, we will review it and proceed with installation. Please note that some extensions may not function properly during replica configuration and recovery.
2.3 - API Reference
API Reference
2.4 - CLI Reference
CLI Reference
2.5 - Release Note
PostgreSQL(DBaaS)
2026.07.16
FEATUREAdd immediate backup, disk usage monitoring, and integration with ServiceWatch service
Add immediate backup and disk usage monitoring features
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
Through the Disk usage query feature, you can view the usage of each Block Storage type allocated to an instance.
ServiceWatch service integration
You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.
Add third-generation server type
The third-generation server type has been newly added. * For detailed information, refer to PostgreSQL(DBaaS) 서버 타입.
2026.03.19
FEATUREAdd OS (Kernel) upgrade feature
Strengthen the latest security patches and stability via the OS (Kernel) upgrade feature.
2025.12.16
FEATUREAdd Replica configuration feature for disaster recovery
You can set up a disaster recovery Replica using the Replica configuration (Other Region) feature.
2025.07.01
FEATUREUser (access control) management, Archive configuration feature, Add DB Audit Log export feature, Provide backup notification feature, Add migration feature
Add PostgreSQL (DBaaS) feature
Add 2nd-generation server type
Add a 2nd-generation (db2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For more details, see PostgreSQL(DBaaS) 서버 타입.
DB user and access control management and Archive configuration feature added
Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
Migration feature addition
Provides replication-based zero-downtime data migration functionality. * For more details, refer to Migration 구성하기
Add HDD, HDD_KMS type to Block Storage type
2025.02.27
FEATURENew version, addition of server types and per-server IP configuration, addition of Block Storage capacity expansion feature
PostgreSQL (DBaaS) feature change
Add new PostgreSQL versions: 13.16, 14.13, 15.8
Add second-generation server type
Add a 2nd-generation (dbh2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, refer to PostgreSQL(DBaaS) 서버 타입.
After creating the service, Block Storage capacity expansion is possible.
Server-specific network IP configuration feature added allows either common or server-specific configuration depending on the usage purpose.
Samsung Cloud Platform Common Feature Change
Account, IAM, Service Home, tags, etc., have been updated to reflect common CX changes.
2024.10.01
NEWPostgreSQL(DBaaS) service official version release
A volume-encrypted storage selection option has been added to the Block Storage type.
The Role Switch (Active ↔ Standby) feature for the Active DB and Standby DB configured with redundancy has been added.
Integrated with the cloud monitoring service, performance and log monitoring of the DB instance is possible.
Customers can set Planned Compute policy based on the server type they select.
2024.07.02
NEWBeta version release
A PostgreSQL (DBaaS) service that enables easy creation and management of PostgreSQL in a web environment has been launched.
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 that can automate MariaDB installation and perform management functions for operation through a web-based console.
MariaDB(DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and the read‑only server called Replica, used for read load balancing and disaster recovery (DR), is provided up to five instances. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling data recovery at the desired point in time.
Figure. MariaDB(DBaaS) Architecture
Provided features
MariaDB (DBaaS) provides the following features.
Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and provides an Active-standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, a switch-over allows the user to directly perform the Active-Standby node transition.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup time window and storage provider can be configured by the user, and additional charges may be incurred based on the backup size. * It also provides a recovery function for backed‑up data, so when a user initiates a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup creation time or a user‑specified time). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
Version Management: Provides Major and Minor version upgrade features based on certain functionality improvements and security patches.
Replica configuration: For load balancing reads and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
Audit setting: Provides an Audit setting feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
Parameter management: It is possible to modify DB configuration parameters related to performance improvement and security.
Service Status Lookup: Retrieve the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
Archive Management: Within the DB server, you can set the Archive file retention period (1 day~35 days) and configure the Archive mode (On/Off).
Export DB Log: You can export stored logs to the user’s Object Storage via Audit settings.
Migration: Synchronizes data in real time with the operational database and supports migration using replication without service interruption.
OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.
Components
MariaDB (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by MariaDB (DBaaS) are as follows.
Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
EOS Date (Samsung Cloud Platform new creation stop date)
EoTS Date(Community Technical Support End Date)
MariaDB (Community)
10.6.5
2026-03-19
2026-07-06
10.6.9
2026-03-19
2026-07-06
10.6.10
2026-03-19
2026-07-06
10.6.12
2026-03-19
2026-07-06
10.6.14
2026-03-19
2026-07-06
10.6.15
2026-03-19
2026-07-06
10.6.16
2026-03-19
2026-07-06
10.6.17
2026-03-19
2026-07-06
10.6.19
2026-03-19
2026-07-06
10.6.22
2026-03-19
2026-07-06
10.11.8
2027-09 (scheduled)
2028-02-16
10.11.9
2027-09 (scheduled)
2028-02-16
10.11.13
2027-09 (scheduled)
2028-02-16
10.11.15
2027-09 (scheduled)
2028-02-16
11.4.7
2028-12 (scheduled)
2029-05-29
11.4.10
2028-12 (scheduled)
2029-05-29
Table. Engine versions provided for MariaDB (DBaaS)
notice
The next version of MariaDB is scheduled to be available after September 2026. The actual service delivery schedule is subject to change.
MariaDB 10.11.16
Server type
The server types supported by MariaDB (DBaaS) are as follows.
For detailed information about the server types provided by MariaDB (DBaaS), see MariaDB(DBaaS) 서버 타입.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server types
Standard: Standard configuration commonly used (vCPU, Memory)
High Capacity: Large server specifications of 24 vCores or more
Server specifications
db1
Provided server specifications
db1: Standard specifications (vCPU, Memory) commonly used
dbh2: Large-scale server specifications
Provides servers with 24 vCores or more
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. MariaDB (DBaaS) server type components
Preceding Service
This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.
A service that provides an isolated virtual network in a cloud environment
Table. MariaDB (DBaaS) pre-service
3.1.1 - Server type
MariaDB(DBaaS) server type
MariaDB (DBaaS) provides server types composed of various combinations such as CPU, Memory, and Network Bandwidth.
When creating a MariaDB(DBaaS), the Database Engine is installed according to the server type selected for the intended use.
Reference
The server types provided may differ depending on the region and AZ.
The server types supported by MariaDB (DBaaS) are as follows.
Standard db1v2m4
Category
example
Detailed description
Server type
Standard
Provided server type categories
Standard: Configured with the commonly used standard specifications (vCPU, Memory)
High Capacity: Large-capacity server specifications exceeding Standard
Server specifications
db1
Provided server type classification and generation
db1: means a standard specification, and 1 indicates the generation
dbh2: h indicates a large-capacity server specification, and 2 indicates the generation
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. MariaDB (DBaaS) server type format
db1 server type
The db1 server type of MariaDB (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db1v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
db1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db1v2m24
2 vCore
24 GB
Maximum 10 Gbps
Standard
db1v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db1v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db1v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db1v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db1v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db1v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db1v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db1v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db1v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db1v10m80
10 vCore
80 GB
Maximum 10 Gbps
Standard
db1v10m120
10 vCore
120 GB
Maximum 10 Gbps
Standard
db1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db1v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db1v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db1v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db1v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db1v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db1v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db1v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db1v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db1v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db1v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db1v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. MariaDB(DBaaS) server type specifications - db1 server type
Database password
Required
Password to use when accessing the DB
Include English letters, numbers, and special characters (“‘ excluded) and enter 8~30 characters
Check database password
Required
Re-enter the same password to use for DB access
Database Port number
Required
Port number required for DB connection
Enter the DB port within the range 1200 ~ 65535
Backup > Use
Selection
Backup usage
Select Use to set backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period
Selection
Backup retention period
Select the backup retention period. Set the file retention period from 7 days to 35 days
Backup files incur additional charges based on size
Backup > Backup Start Period
Selection
Backup start time
Select backup start time
The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be configured
Backup > Archive backup schedule
Selection
Archive backup interval
Select the archive backup interval
The archive backup interval is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log configuration
Selection
Whether to store Audit Log
Select Use to enable the Audit Log feature
User connection information records are stored
Users can specify the types of events to audit via the server_audit_events parameter, and it can be modified through the Parameter screen
In the Additional Information Input area, enter or select the required information.
Category
Required
Detailed description
tag
Selection
Add Tag
Up to 50 can be added per resource
After clicking the Add Tag button, enter or select Key, Value values
Table. MariaDB(DBaaS) additional information input items
Summary Review the detailed information and estimated charges generated in the panel, and click the Create button.
Once creation is complete, check the created resource on the Resource List page.
MariaDB(DBaaS) Check detailed information
The MariaDB (DBaaS) service lets you view and modify the complete resource list and detailed information. The MariaDB(DBaaS) Details page consists of Details, Tags, Activity History tabs, and for databases with a configured Replica, a Replica Information tab is added.
To view detailed information about the MariaDB (DBaaS) service, follow the steps below.
All Services > Database > MariaDB (DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB (DBaaS) List page, click the resource to view detailed information. 3. MariaDB(DBaaS) Details Go to the page.
MariaDB(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Category
Detailed description
Cluster status
Cluster status with DB installed
Creating: Cluster creation in progress
Editing: Cluster is transitioning to an operational state
Error: Cluster encountered a failure while performing a task
If this persists, contact the administrator
Failed: Cluster failed during creation
Restarting: Restarting the cluster
Running: Cluster is operating normally
Starting: Starting the cluster
Stopped: Cluster is stopped
Stopping: Cluster is being stopped
Synchronizing: Synchronizing the cluster
Terminating: Deleting the cluster
Unknown: Cluster status is unknown
If this persists, contact the administrator
Upgrading: Cluster is transitioning to an upgrading state
Cluster control
Buttons to change the cluster state
Start: Start a stopped cluster
Stop: Stop a running cluster
Restart: Restart a running cluster
Switch-Over: Switch a standby cluster to Active
View more features
Cluster management buttons
Service status synchronization: Real-time DB service status lookup
Backup history: Verify successful backup execution and view history when backup is configured
Database recovery: Recover the DB based on a specific point in time
Parameter management: View and modify DB configuration parameters
Replica configuration: Configure a read-only cluster as a Replica
Replica configuration (Other-Region): Configure a disaster recovery Replica in another region; the button is disabled if the account has no region to configure
DB user management: View and manage DB account (user) information registered in the DB
DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
Archive settings management: Set archive file retention period and configure archive mode
DB Log export: Export stored logs to the user’s Object Storage via Audit settings
Migration configuration: Provides Migration functionality using a Replication method
Block Storage usage management: Provides usage query functionality per Block Storage type
OS (Kernel) upgrade: Upgrade OS Kernel version
Service cancellation
Cancel Service button
Table. MariaDB(DBaaS) status information and additional features
Detailed Information
MariaDB (DBaaS) List page allows you to view detailed information of the selected resource and, if needed, modify the information.
Category
Detailed description
Server Information
Server information configured in this cluster
Category: Server type (Active, Standby, Replica)
Server name: Server name
IP Port: Server IP and port
Availability Zone: Server creation location
Status: Server status
service
Service name
Resource Type
Resource Type
SRN
Unique resource ID in Samsung Cloud Platform
In the DB service, it means the cluster SRN
Resource name
Resource name
In the DB service, it refers to the cluster name
Resource ID
Unique resource ID in the service
Constructor
User who created the service
Creation Date/Time
Service creation date and time
Modifier
User who edited the service information
Modification date and time
Date and time the service information was modified
Image version
Installed DB image and version information
If a version upgrade is required, click the Edit icon to configure
If log collection configuration is required, click the Edit icon next to Log Collection to configure
DB character set
Character encoding to use for the DB
Time zone
Standard time zone used by the database
VIP
Virtual IP information
can be checked only when high availability is enabled
Network
Network information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP))
IP access control
Service access policy configuration
If you need to add or remove an IP, click the Edit icon to configure
Active & Standby
Active/Standby server type, default OS, additional Disk information
If you need to modify the server type, click the Edit icon next to the server type to configure it. See the server type modification procedure at 서버 타입 변경하기
Modifying the server type requires a server reboot
If you need to expand storage, click the Edit icon next to the storage capacity to expand it. See the storage expansion procedure at 스토리지 증설하기
If you need to add storage, click the Add Disk button next to the additional Disk to add it. See the storage addition procedure at 스토리지 추가하기
Table. MariaDB (DBaaS) Database detailed information items
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab lets you view the Master cluster name, the number of replicas, and the Replica status.
Category
Detailed description
Master information
Name of the Master cluster
Replica count
Number of Replicas created in the Master cluster
Replica status
Replica server status in the Master cluster
You can view the server name, status query, status details, and status check time
To view the Replica status, click the Status Query button
While the query is in progress, the cluster remains in the Synchronizing state, and once the query completes, the cluster changes to the Running state
Table. Replica information tab detailed information items
tag
MariaDB (DBaaS) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.
Category
Detailed description
Tag List
Tag list
You can view the tag’s Key, Value information
Up to 50 tags can be added per resource
When entering tags, you can search and select from the list of previously created Keys and Values
Table. MariaDB (DBaaS) Tag Tab Items
Job History
MariaDB (DBaaS) List page allows you to view the operation history of the selected resource.
Category
Detailed description
Task History List
Resource change history
Operation date and time, resource ID, resource name, operation details, event topic, operation result, operator information verification
Table. Work History tab detailed information items
MariaDB(DBaaS) Managing Resources
If you need to change or restore the existing configuration options of a provisioned MariaDB (DBaaS) resource, or set up a replica, you can perform the task on the MariaDB (DBaaS) Details page.
Operation Control
If changes occur to a running MariaDB (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of MariaDB (DBaaS), follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. Go to the MariaDB(DBaaS) List page.
On the MariaDB(DBaaS) List page, click the resource to control its operation. 3. MariaDB(DBaaS) Details Go to the page.
Check the MariaDB (DBaaS) status and complete the change using the control button below.
Start: DB service is installed on the server and the DB service is running (Running).
Stop: The server where the DB service is installed and the DB service will be stopped (Stopped).
Restart: Only the DB service will be restarted.
Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize service status
You can synchronize the real-time service status of MariaDB (DBaaS).
To view the service status of MariaDB (DBaaS), follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB (DBaaS) List page, click the resource to view the service status. 3. MariaDB(DBaaS) Details Go to the page.
Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
When the query completes, the status in the server information item is updated, and the cluster changes to the Running state.
Change Server Type
You can change the configured server type.
Caution
If you modify the server type, a server restart is required. Please verify separately any software license modifications or software settings and their implementation due to server specification changes.
To change the server type, follow these steps.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List page, click the resource to change the server type. 3. MariaDB(DBaaS) Details Navigate to the page.
Click the Edit icon for the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
Server Type Edit After selecting the server type in the popup, click the Confirm button.
Add storage
If you need more than 5 TB of data storage space, you can add additional storage. In a redundant DB setup, all redundant servers are added simultaneously.
Caution
It is applied in the same way as the Storage type selected when creating the service.
For a DB configured with redundancy, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
The storage of a Replica cannot be larger than the storage of the primary. * Expand the Replica storage first, then expand the Master storage.
When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to add storage. 3. MariaDB(DBaaS) Details Go to the page.
Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding Storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB setup, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to change the server type. 3. MariaDB(DBaaS) Details Go to the page.
Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage popup opens.
Edit Additional Storage After entering the expanded capacity in the popup window, click the Confirm button.
Terminate MariaDB(DBaaS)
You can cancel unused MariaDB (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact that may arise from the service interruption.
Caution
Replica is not deleted together. * If you delete the replica as well, please cancel it separately from the resource list.
If you terminate the DB, all stored data and any backup data that was configured will be deleted.
To cancel MariaDB (DBaaS), follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, select the resource to cancel and click the Terminate Service button.
After termination is complete, check on the MariaDB(DBaaS) list page whether the resource has been terminated.
3.2.1 - Managing DB Services
Users can manage MariaDB (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows you to easily view and modify database configuration parameters.
Parameter View
To view configuration parameters, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Go to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management in the popup window, click the Search button. 5. View Notification popup window opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
Edit Parameter
To modify the configuration parameters, follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button and click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. View Notification The popup window opens.
View Notification when the popup window opens, click the Confirm button. 6. Retrieving may take a short amount of time.
If editing is required, click the Edit button and enter the changes in the custom value area of the Parameter to be edited.
When the input is complete, click the Complete button.
참고
If you change the character_set_server value, first verify the collation that matches the character set using the command below.
SQL> SHOW COLLATION WHERE Charset = 'character set name';
Set the parameter values for character-set-server, collation-server, and init_connect using the verified collation.
Item
Detailed description
Whether to restart
character-set-server
Specify default character set
Restart required
collation-server
Specify default collation (Collation)
Restart required
init_connect
SQL statement executed when the client connects to the database
No restart required
Table. Parameter configuration items
Managing DB Users
Provides administrative features for viewing DB user information and modifying status information.
Query DB Users
Follow these steps to query DB users.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB (DBaaS) List Navigate to the page.
MariaDB(DBaaS) List page, click the resource whose DB users you want to view. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the DB User Management button. 4. Navigate to the DB User Management page.
DB User Management on the page, click the Search button. 5. Retrieving may take a short amount of time.
Change DB user status
To change the status of the retrieved DB user, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List On the page, click the resource you want to edit the DB user for. 3. MariaDB(DBaaS) Details Navigate to the page.
Click the More button, then click the DB User Management button. 4. Navigate to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
If modification is required, click the Edit button, and change the status area value or enter remarks.
When the input is complete, click the Done button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IP addresses that can access the database, configuring it so that only authorized IPs are allowed access.
안내
Perform a DB user lookup before setting DB access control. For DB user lookup, please refer to DB 사용자 관리하기.
View DB Access Control
To view DB users with IP access control enabled, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List On the page, click the resource you want to manage access control for. 3. MariaDB(DBaaS) Details Navigate to the page.
Click the More button, then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
Add DB access control
To add IP access control, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource for which you want to add IP access control. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button and then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
Click the Search button on the DB Access Control Management page. 5. Retrieving may take a short amount of time.
When the query is complete, click the Add button. 6. Add DB Access Control The popup window opens.
Add DB Access Control In the popup window, select the DB username and enter the IP address.
When the input is complete, click the Done button.
Delete DB Access Control
To delete IP access control, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List page, click the resource for which you want to delete the IP access control. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
Click the Search button on the DB Access Control Management page. 5. Retrieving may take a short amount of time.
When the query is complete, click the Delete button. 6. Delete popup window opens.
Click the Confirm button on the Delete popup.
Configure Archive mode
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operating environment.
안내
When creating a service, the default setting is Archive mode enabled, and the retention period is 3 days.
To set the Archive mode, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List Click the resource on the page for which you want to set Archive mode. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button and then click the Archive Settings Management button. 4. Navigate to the Archive Settings Management page.
On the Archive Settings Management page, click the Search button. 5. Retrieving may take a short amount of time.
Click the Edit button and select the usage status and retention period.
When the edit is complete, click the Complete button.
Modify Audit Settings
You can change the Audit log storage settings of MariaDB (DBaaS).
Follow these steps to change the Audit log storage settings for MariaDB (DBaaS).
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List On the MariaDB(DBaaS) List page, click the resource to view the service status. 3. MariaDB(DBaaS) Details Go to the page.
Click the Edit icon of the Audit settings at the bottom of the detailed information. 4. Edit Audit Settings The popup window opens.
Modify Audit Settings After changing the usage status in the popup window, click the Confirm button.
Select Use to enable the Audit log feature. * Enabling audit logging may degrade database performance.
If you disable use, the Audit log storage file will be deleted. * Back up the Audit log file separately before disabling.
DB Log Export
Supports exporting log data that requires long-term retention among audit (Audit) logs to Object Storage. Users can directly configure the log types that need to be stored, the destination Bucket for export, and the log export interval. Copies logs to the designated Object Storage for retention according to the configured criteria.
Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for the long term.
안내
To use the DB Log export feature, you need to create an Object Storage. * Please refer to the Object Storage 사용자 가이드 for creating Object Storage.
Please be sure to verify the authentication key’s expiration date and time. * If the authentication key expires, logs will not be stored in the Bucket.
Please ensure that the authentication key information is not exposed to external parties.
Setting DB Log Export Mode
Follow these steps to set the DB Log export mode.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List On the page, click the resource for which you want to export the DB Log. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the DB Log Export button. 4. Navigate to the DB Log Export page.
On the DB Log Export page, click the Register button. 5. Navigate to the Register DB Log Export page.
After entering the required information on the DB Log Export Registration page, click the Complete button.
Category
Required
Detailed description
Log type
Required
Log type to be saved
Save bucket name
Required
Object Storage bucket name to be saved
Authentication key > Access key
Required
Access key for accessing the Object Storage you want to store
Authentication key > Secret key
Required
Secret key for accessing the Object Storage you want to store
File creation cycle
Required
File creation frequency in Object Storage
Whether to delete the original log
Selection
Whether to delete the original logs when exporting to Object Storage
Table. MariaDB (DBaaS) DB Log Export Configuration Items
Manage DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List On this page, click the resource for which you want to manage DB Log export. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the Export DB Log button. 4. Navigate to the DB Log Export page.
On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Terminate buttons.
Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
Edit: Modify the DB Log export mode setting.
Cancel: Cancel the DB Log export mode setting.
Upgrade version
If a latest patch that includes security enhancements and feature improvements is available, you can apply it using the version upgrade feature.
Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.
It is recommended to perform an immediate backup in advance to prepare for any issues that may arise during the upgrade process. * If this is not the case, a failure may occur and some data may not be recoverable.
In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. * Please check the version of Replica first, and if necessary, perform a version upgrade.
The backed-up data is automatically deleted after the version upgrade is completed.
Major version upgrade
Caution
Major version upgrades require a pre‑upgrade simulation test.
Please set up a separate Replica DB, promote it to Master, and pre‑validate the Major upgrade. * Afterward, we recommend proceeding only after thoroughly reviewing the service impact with the Application manager.
To perform a Major version upgrade, follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to upgrade the Major version. 3. MariaDB(DBaaS) Details Go to the page.
Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
Version Upgrade In the popup window, select the upgrade type and patch version, then click the Confirm button.
Version Upgrade Notification: Click the Confirm button in the popup window.
Minor version upgrade
Supports minor version upgrades within the same major version.
To perform a minor version upgrade, follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to upgrade the Minor version. 3. MariaDB(DBaaS) Details Go to the page.
Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
Version Upgrade In the popup window, select the upgrade type and the patch version, then click the Confirm button.
Version Upgrade Notification In the popup window, click the Confirm button.
Configure Migration
Provides a Migration feature that synchronizes in real time with the operational database and replicates using a Replication method without service interruption.
You can promote a fully configured Migration Cluster to a Master Cluster.
Caution
When the master is promoted, synchronization with the source DB that is the migration target is stopped.
To promote the Migration Cluster to Master, follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to promote to Master. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
Master Promotion Notification Click the Confirm button in the popup window.
Managing Block Storage Usage
You can view the usage of Block Storage by type allocated to the DB instance.
To view Block Storage usage, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to view Block Storage usage. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button, then click the Block Storage Usage Management button. 4. Block Storage Usage Management Navigate to the page.
On the Block Storage Usage Management page, click the Search button. 5. Block Storage Usage Management The page displays usage by Block Storage type.
Retrieving usage by Block Storage type takes a short amount of time.
OS Kernel Upgrade
You can upgrade the OS Kernel to enhance the functionality of the operational database and apply security patches.
Caution
The service will be unavailable while the OS upgrade is in progress.
The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
After the upgrade is complete, you cannot revert to the original OS.
Follow these steps to upgrade the OS Kernel.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to upgrade the OS Kernel. 3. MariaDB(DBaaS) Details Navigate to the page.
Click the More button, then click the OS(Kernel) Upgrade button. 4. OS (Kernel) Upgrade Notification A popup window opens.
OS(Kernel) Upgrade Notification Check the instructions in the popup window and click the Confirm button.
3.2.2 - Backing up and restoring the DB
Users can set up backups for MariaDB (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up MariaDB(DBaaS)
PostgreSQL (DBaaS) provides data backup functionality based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
For backup configuration of MariaDB (DBaaS), please refer to MariaDB(DBaaS) 생성하기.
To modify the backup settings of the created resource, follow the steps below.
Caution
For reliable backups, we recommend adding separate BACKUP storage or sufficiently expanding storage capacity. * Especially when the backup data exceeds 100 GB and experiences frequent changes, please provision additional storage equal to approximately 60 % of the data size. * For instructions on adding and expanding storage, refer to the MariaDB(DBaaS) 스토리지 추가하기, MariaDB(DBaaS) 스토리지 증설하기 guides.
If a backup is configured, it runs at the specified time after the set time, and additional fees are incurred based on the backup size.
If you change the backup setting to Unconfigured, backup execution will stop immediately, and stored backup data will be deleted and can no longer be used.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Go to the page.
MariaDB(DBaaS) List Click the resource for which you want to set up a backup. 3. MariaDB(DBaaS) Details Go to the page.
Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
When configuring a backup, click Use in the Backup Settings popup, select retention period, backup start time, and Archive backup interval, then click the Confirm button.
If you wish to stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone. Once user authentication is complete, the backup configuration is disabled and backup execution stops.
Perform backup immediately
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
To perform an immediate backup, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
On the MariaDB(DBaaS) List page, click the resource to perform an immediate backup. 3. MariaDB(DBaaS) Details Go to the page.
Click the Immediate Backup button of the backup item. 4. Immediate backup settings The popup window opens.
In the Immediate backup setup popup, click the Confirm button.
Check backup history
안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, refer to 알림 정책 생성하기.
To check the backup history, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Go to the page.
MariaDB(DBaaS) List On the page, click the resource to view the backup history. 3. MariaDB(DBaaS) Details Go to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, you can view the backup status, version, backup start date and time, backup completion date and time, and size.
Delete backup file
To delete the backup file, follow these steps.
Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Navigate to the page.
MariaDB(DBaaS) List page, click the resource to view the backup history. 3. MariaDB(DBaaS) Details Go to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, select the files you wish to delete, then authenticate via the logged-in user’s mobile phone.
When user authentication is completed, the backup file will be deleted.
Recover MariaDB(DBaaS)
If a failure or data loss requires restoration from a backup file, recovery can be performed based on a specific point in time using the recovery feature. When you perform a MariaDB(DBaaS) recovery, a new server is created using the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds with the database’s configuration information and data.
Caution
To perform recovery, at least twice the capacity of the Disk data type is required. If disk space is insufficient, recovery may fail.
To recover MariaDB (DBaaS), follow the steps below.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List Go to the page.
On the MariaDB(DBaaS) List page, click the resource you want to recover. 3. MariaDB(DBaaS) Details Go to the page.
Click the Database Recovery button. 4. Database Recovery Navigate to the page.
After entering information in the Database recovery configuration area, click the Complete button.
Category
Required
Detailed description
Recovery type
Required
Set the point in time the user wants to recover
Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
Custom point: Recover to a user‑desired point within the recoverable backup time range. The recoverable period depends on the Archive backup interval setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix
Required
Recovery DB server name
Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name
Required
Cluster name of the recovery DB
Enter using English letters, 3 ~ 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Server type for the recovery DB installation
Standard: Standard specifications commonly used
High Capacity: Large-capacity server of 24vCore or more (to be provided later)
Service Type > Planned Compute
Selection
Status of resources with Planned Compute set
In Use: Number of resources with Planned Compute that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Go to the Planned Compute service application page
DATA: Storage area for table data, archive files, etc.
Apply the same storage type as set in the original cluster
Enter capacity as a multiple of 8 within the range 16 to 5,120
Add: Storage area for DATA, Archive, TEMP, Backup data
Apply the same storage type as set in the original cluster
In the recovery DB, only DATA, TEMP, and Archive purposes can be added
After selecting Use, enter the storage purpose and capacity
To add storage, click the Add button; to delete, click the x button
Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username
Required
Database username set in the source DB
Database Port number
Required
Database Port number set in the source DB
IP access control
Selection
IP address for accessing the recovery DB
Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.1/32, 192.168.10.1/32), then click the Add button
To delete an entered IP, click the x button next to the entered IP
maintenance period
Selection
DB maintenance window
If you select Use, you can set the day, start time, and duration
The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and patch tasks within that time are the user’s responsibility.
We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or failing to perform tasks within the window.
tag
Selection
Add Tag
Add Tag after clicking the button, enter or select Key, Value values
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Configure 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.
information
To configure a disaster recovery Replica, please create it via Replica Configuration (Other Region).
To configure a Replica, follow these steps.
All Services > Database > MariaDB (DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB (DBaaS) List page is accessed.
On the MariaDB (DBaaS) List page, click the resource to configure a Replica. 3. MariaDB(DBaaS) Details Go to the page.
Click the Replica configuration button. 4. Replica configuration Navigate to the page.
After entering information in the Replica configuration area, click the Complete button.
Category
required status
Detailed description
Region
Required
Region to configure the Replica
Replica configuration (Other Region) is displayed only when selected
Replica count
Required
Number of Replicas to configure
Up to 5 can be configured per cluster
If you select more than one value, additionally enter the Replica name and service type information
Replica name
Required
Replica server name
must start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) to enter 3 to 19 characters
The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type
Essential
Replica server type
Standard: standard specification commonly used
High Capacity: large-capacity server with 24vCore or more (to be provided later)
Service Type > Planned Compute
Select
Status of resources with Planned Compute configured
In Use: Number of resources with Planned Compute configured that are currently in use
Configured: Number of resources with Planned Compute configured
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Navigate to the Planned Compute service application page
DATA: Storage area for table data, archive files, etc.
Applied identically with the storage type set in the source cluster
Capacity cannot be set
Additional: DATA, Archive, TEMP, Backup data storage area
Applied identically with the storage type set in the source cluster
In a Replica, only DATA and TEMP can be added
After selecting Use, input the storage purpose and capacity
To add storage, click the Add button, and to delete, click the x button
Capacity can be entered in multiples of 8 within the range 16–5,120, and up to a maximum of 9 can be created, including the number set in the source cluster
IP access control
Selection
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not 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 an entered IP, click the x button next to the entered IP
maintenance period
Select
Database 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 management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
If set to unused, we are not responsible for issues arising from patches not being applied.
tag
Select
Add Tag
after clicking the Add Tag button, Key, Value enter or select
If a network outage or replication delay with the Master Cluster occurs, you can use the Replica reconstruction function to replicate the Master Cluster’s data again.
To reconfigure the Replica, follow these steps.
Click the All Services > Database > MariaDB(DBaaS) menu. 1. Go to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
On the MariaDB(DBaaS) List page, click the resource to reconfigure the Replica. 3. MariaDB(DBaaS) Details Go to the page.
Click the Replica Reconstruction button. 4. Replica Reconfiguration Notice A popup window opens.
Replica Reconfiguration Notification In the popup window, click the OK button.
Promote Replica Cluster to Master Cluster
You can promote a fully configured Replica Cluster to a Master Cluster.
Caution
When the Master is promoted, synchronization with the existing Master Cluster is stopped.
To promote a Replica Cluster to Master, follow these steps.
All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
On the MariaDB(DBaaS) List page, click the resource to promote to Master. 3. MariaDB(DBaaS) Details Go to the page.
Click the More button and then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
Master Promotion Notification in the popup window, click the Confirm button.
3.2.4 - MariaDB(DBaaS) server connection
Scenario Overview
MariaDB(DBaaS) Server Connection scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to MariaDB (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Figure. MariaDB(DBaaS) server connection architecture
Scenario components
You can build the scenario using the following services.
Service group
service
Detailed description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Networking
VPC > Subnet
A service that lets users segment the network within a VPC to match their purpose and scale
Networking
VPC > Public IP
A service that reserves a public IP and allocates and releases it to Compute resources.
Networking
VPC > Internet Gateway
A service that connects VPC resources to the Internet
Networking
Security Group
Virtual firewall that controls server traffic
Database
MariaDB(DBaaS)
A service that easily creates and manages MariaDB in a web environment
Compute
Virtual Server
Virtual server optimized for cloud computing
Compute
Virtual Server > Keypair
Encryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
The All Open(Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
Click the All Services > Networking > Firewall menu. 1. Navigate to the Firewall’s Service Home page.
On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
On the detail information page, click the Rules tab. 4. Go to the Rules tab.
Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address
Destination address
Protocol
Port
Operation
Direction
Explanation
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. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide provides instructions on how to connect using MySQL Workbench. Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB client program (MySQL Workbench) on the Bastion host
Go to the official MySQL page and download the MySQL Workbench program.
Connect the user’s PC hard drive to upload the file to the Bastion host.
Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install it.
5-3. ### Connect to the database using a DB client program (MySQL Workbench)
Run MySQL Workbench and click Database > Manage connections. 1. Manage Server Connection A popup window appears.
Manage Server Connection In the popup window, click the New button at the lower left, enter the Database server information created in 3-1. MariaDB(DBaaS) 서비스 생성하기, and click the Test Connection button. 2. Password a popup window appears.
Required input element item
input value
Connection Name
Custom (ex. service name)
Host name
Database server IP
Port
Database Port
Username
Database username
Table DB connection client program input fields
Password In the popup window, enter the password set in 3-1. MariaDB(DBaaS) 서비스 생성하기 and click the OK button. 3. When the operation succeeds, click the OK button in the Manage Server Connection popup window.
Click Database > Connect to Database. 4. Connect to Database A popup window appears.
Select the Connection Name registered in Stored Connection to perform a Database connection. 5. After connecting, you can perform simple queries, etc.
3.3 - API Reference
API Reference
3.4 - CLI Reference
CLI Reference
3.5 - Release Note
MariaDB(DBaaS)
2026.07.16
FEATUREImmediate backup, Disk usage monitoring, addition of Major version upgrade feature, and addition of third-generation server type
Immediate backup, Disk usage monitoring, Add major version upgrade feature
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
Through the Disk usage query feature, you can view the usage of each Block Storage type assigned to an instance.
Through the Major version upgrade feature, users can perform a Major version upgrade.
Add third-generation server type
The third-generation server type has been newly added. * Please refer to the MariaDB(DBaaS) 서버 타입 for more details.
2026.03.19
FEATUREConfigure Replica for disaster recovery, add OS (Kernel) upgrade feature, provide Servicewatch integration feature
You can configure a disaster recovery Replica using the Replica configuration (Other Region) feature.
Strengthen the latest security patches and stability via the OS (Kernel) upgrade feature.
You can monitor metrics and logs by integrating with Servicewatch.
2025.07.01
FEATUREUser (access control) management, Archive configuration feature, Add DB Audit Log export feature, Provide backup notification feature, Add migration feature
Add MariaDB (DBaaS) feature
Add 2nd-generation server type
Add a second‑generation (db2) server type based on Intel 4th‑generation (Sapphire Rapids) processors. * For more details, refer to the MariaDB(DBaaS) server type.
DB user and access control management and Archive configuration feature Add
Provides notification functionality for backup success and failure. * For more details, see 알림 정책 생성하기.
Migration feature addition
Provides replication-based zero-downtime data migration functionality. * For more details, refer to Migration 구성하기.
Add HDD, HDD_KMS type to Block Storage type
2025.02.27
FEATUREAdd server type and configure IP per server, add Block Storage capacity expansion feature
MariaDB (DBaaS) feature change
Add second-generation server type
Add 2nd-generation (dbh2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For more details, refer to MariaDB(DBaaS) 서버 타입.
After creating the service, you can increase the configured Block Storage capacity.
Server-specific network IP configuration feature added allows either common or server-specific settings depending on the usage purpose.
Samsung Cloud Platform Common Feature Change
Account, IAM, Service Home, tags, etc., have been updated to reflect common CX changes.
2024.10.01
NEWMariaDB(DBaaS) service official version release
Block Storage type the volume-encrypted storage selection option has been added.
A feature that can switch the Role (Active ↔ Standby) has been added to the redundant Active DB and Standby DB.
Integrated with the cloud monitoring service, performance and log monitoring of the DB instance is possible.
Based on the server type selected by the customer, Planned Compute policy can be configured.
2024.07.02
NEWBeta version release
A MariaDB (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been launched.
4 - MySQL(DBaaS)
4.1 - Overview
Service Overview
MySQL(DBaaS) is an open-source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that can automate MySQL installation and perform management functions for operation through a web-based Console.
MySQL (DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, it offers an automatic backup feature at user-specified times to prepare for issues with the DB server or data, allowing recovery of data at the desired point in time.
Figure. MySQL(DBaaS) Architecture
Provided features
MySQL (DBaaS) provides the following features.
Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and provides an Active‑standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, a switch-over allows the user to directly perform the Active-Standby node transition.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be set by the user, and additional fees may apply based on backup size. * It also provides a recovery function for backed-up data, and when the user performs a recovery, a separate database is created, and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
Version Management: Provides Major and Minor version upgrade functionality based on certain feature improvements and security patches.
Replica configuration: For read load balancing and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
Parameter Management: You can modify DB configuration parameters related to performance improvement and security.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IP addresses for access.
Archive Management: You can set the retention period (1~35 days) for Archive files on the DB server and configure the Archive mode (On/Off).
Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.
Migration: Synchronizes data in real time with the operational database and supports migration using replication without service interruption.
OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.
Components
MySQL(DBaaS) provides pre‑validated engine versions and various server types according to the open‑source support policy. Users can choose and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by MySQL (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 is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
EOS Date (Samsung Cloud Platform new creation stop date)
EoTS Date(Community Technical Support End Date)
MySQL (Community)
8.0.28
2026-03-19
2026-04-30
8.0.30
2026-03-19
2026-04-30
8.0.32
2026-03-19
2026-04-30
8.0.33
2026-03-19
2026-04-30
8.0.34
2026-03-19
2026-04-30
8.0.35
2026-03-19
2026-04-30
8.0.36
2026-03-19
2026-04-30
8.0.37
2026-03-19
2026-04-30
8.0.41
2026-03-19
2026-04-30
8.0.42
2026-03-19
2026-04-30
8.4.5
2031-12 (planned)
2032-04-30
8.4.7
2031-12 (planned)
2032-04-30
Table. MySQL (DBaaS) provided engine versions
Information
The next version of MySQL is expected to be released after September 2026. The actual service delivery schedule is subject to change.
MySQL 8.4.8
Server type
The server types supported by MySQL (DBaaS) are as follows.
For detailed information about the server types provided by MySQL(DBaaS), see MySQL(DBaaS) 서버 타입.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server types
Standard: Standard configuration (vCPU, Memory) commonly used
High Capacity: Large server specifications of 24 vCores or more
Server specifications
db1
Provided server specifications
db1: Standard configuration (vCPU, Memory) commonly used
dbH2: Large-capacity server specifications
Provides servers with 24 vCores or more
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. MySQL(DBaaS) server type components
Preceding Service
This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.
A service that provides an isolated virtual network in a cloud environment
Table. MySQL (DBaaS) pre-service
4.1.1 - Server type
MySQL(DBaaS) server type
MySQL(DBaaS) provides server types composed of various combinations such as CPU, Memory, and Network Bandwidth.
When creating MySQL(DBaaS), the Database Engine is installed based on the server type chosen for the intended use.
Reference
The server types offered may vary depending on the region and AZ.
The server types supported by MySQL (DBaaS) are as follows.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server type categories
Standard: Configured with the commonly used standard specifications (vCPU, Memory)
High Capacity: Large-capacity server specifications exceeding Standard
Server specifications
db1
Provided server type classification and generation
db1: means a standard specification, and 1 indicates the generation
dbh2: h indicates a large-capacity server specification, and 2 indicates the generation
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. MySQL (DBaaS) server type format
db1 server type
The db1 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db1v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db1v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db1v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db1v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db1v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db1v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db1v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db1v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db1v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db1v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db1v10m80
10 vCore
80 GB
Maximum 10 Gbps
Standard
db1v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db1v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db1v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db1v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db1v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db1v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db1v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db1v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db1v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db1v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db1v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db1v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. MySQL(DBaaS) server type specifications - db1 server type
db2 server type
The db2 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db2v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db2v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db2v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db2v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db2v32m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db2v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db2v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db2v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db2v4m48
4 vCore
48 GB
Maximum 10 Gbps
Standard
db2v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db2v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db2v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db2v6m48
6 vCore
48 GB
Maximum 10 Gbps
Standard
db2v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db2v96m6
6 vCore
96 GB
Up to 10 Gbps
Standard
db2v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db2v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db2v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db2v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db2v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db2v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db2v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db2v10m80
10 vCore
80 GB
Up to 10 Gbps
Standard
db2v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db2v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db2v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db2v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db2v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db2v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db2v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db2v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db2v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db2v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db2v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db2v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db2v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db2v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db2v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db2v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db2v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. MySQL (DBaaS) server type specifications - db2 server type
dbh2 server type
The dbh2 server type of MySQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
High Capacity
dbh2v24m48
24 vCore
48 GB
Maximum 25 Gbps
High Capacity
dbh2v24m96
24 vCore
96 GB
Maximum 25 Gbps
High Capacity
dbh2v24m192
24 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh2v24m288
24 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh2v32m64
32 vCore
64 GB
Maximum 25 Gbps
High Capacity
dbh2v32m128
32 vCore
128 GB
Maximum 25 Gbps
High Capacity
dbh2v32m256
32 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh2v32m384
32 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh2v48m192
48 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh2v48m576
48 vCore
576 GB
Maximum 25 Gbps
High Capacity
dbh2v64m256
64 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh2v64m768
64 vCore
768 GB
Maximum 25 Gbps
High Capacity
dbh2v72m288
72 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh2v72m864
72 vCore
864 GB
Maximum 25 Gbps
High Capacity
dbh2v96m384
96 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh2v96m1152
96 vCore
1152 GB
Maximum 25 Gbps
High Capacity
dbh2v128m512
128 vCore
512 GB
Maximum 25 Gbps
High Capacity
dbh2v128m1536
128 vCore
1536 GB
Maximum 25 Gbps
Table. MySQL(DBaaS) server type specifications - dbh2 server type
db3 server type
The db3 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db3v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db3v8m2
2 vCore
8 GB
Up to 10 Gbps
Standard
db3v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db3v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
db3v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db3v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db3v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db3v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db3v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db3v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db3v6m12
6 vCore
12 GB
Up to 10 Gbps
Standard
db3v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db3v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db3v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db3v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db3v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db3v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db3v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db3v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db3v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db3v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db3v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db3v10m80
10 vCore
80 GB
Up to 10 Gbps
Standard
db3v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db3v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db3v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db3v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db3v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db3v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db3v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db3v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db3v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db3v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db3v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db3v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db3v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db3v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db3v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db3v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db3v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. MySQL(DBaaS) server type specifications - db3 server type
dbh3 server type
The dbh3 server type of MySQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
Intel 6th‑generation (Granite Rapids) Xeon 6738P Processor up to 4.1 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
High Capacity
dbh3v24m48
24 vCore
48 GB
Maximum 25 Gbps
High Capacity
dbh3v24m96
24 vCore
96 GB
Maximum 25 Gbps
High Capacity
dbh3v24m192
24 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh3v24m288
24 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh3v32m64
32 vCore
64 GB
Maximum 25 Gbps
High Capacity
dbh3v32m128
32 vCore
128 GB
Maximum 25 Gbps
High Capacity
dbh3v32m256
32 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh3v32m384
32 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh3v48m192
48 vCore
192 GB
Maximum 25 Gbps
High Capacity
dbh3v48m576
48 vCore
576 GB
Maximum 25 Gbps
High Capacity
dbh3v64m256
64 vCore
256 GB
Maximum 25 Gbps
High Capacity
dbh3v64m768
64 vCore
768 GB
Maximum 25 Gbps
High Capacity
dbh3v72m288
72 vCore
288 GB
Maximum 25 Gbps
High Capacity
dbh3v72m864
72 vCore
864 GB
Maximum 25 Gbps
High Capacity
dbh3v96m384
96 vCore
384 GB
Maximum 25 Gbps
High Capacity
dbh3v96m1152
96 vCore
1152 GB
Maximum 25 Gbps
High Capacity
dbh3v128m512
128 vCore
512 GB
Maximum 25 Gbps
High Capacity
dbh3v128m1536
128 vCore
1536 GB
Maximum 25 Gbps
Table. MySQL(DBaaS) server type specifications - dbh3 server type
Database password
Required
Password to use when accessing the DB
Include English letters, numbers, and special characters (“‘ excluded) and enter 8~30 characters
Check database password
Required
Re-enter the same password to use for DB access
Database Port number
Required
Port number required for DB connection
Enter DB port within the range 1200 ~ 65535
Backup > Use
Selection:
Backup usage
Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period
Selection
Backup retention period
Select the backup retention period. Set the file retention period from 7 days to 35 days
Backup files incur additional charges based on size
Backup > Backup Start Period
Selection
Backup start time
Select backup start time
The minute(s) (minutes) at which the backup runs is set randomly, and the backup end time cannot be set
Backup > Archive backup schedule
Selection
Archive backup interval
Select the Archive backup interval
The Archive backup interval is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Parameter
Required
Parameters for the DB
View button can be clicked to view the parameter’s detailed information
Parameters can be modified after the DB creation is complete, and the DB must be restarted after modification
DB character set
Required
Character encoding to use for the DB
Table case sensitivity
Selection
Case sensitivity of DB table
Time zone
Required
Standard time zone used by the database
ServiceWatch log collection
Selection
ServiceWatch log collection status
Select Use to configure the ServiceWatch log collection feature
It is provided free of charge up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB.
When collected, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed.
To prevent exceeding 5 GB, direct deletion of log data or shortening the retention period is recommended.
Table. MySQL(DBaaS) Database configuration items
In the Additional Information Input area, enter or select the required information.
Category
Required status
Detailed description
tag
Selection
Add Tag
Up to 50 can be added per resource
Add Tag button, then enter or select Key, Value values
Table. MySQL (DBaaS) additional information input fields
Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.
Once creation is complete, verify the created resource on the Resource List page.
Check MySQL(DBaaS) detailed information
The MySQL (DBaaS) service allows you to view and edit the entire resource list and detailed information. MySQL(DBaaS) Details page consists of the Details, Tags, Activity History tabs, and for databases with a Replica configured, the Replica Information tab is added.
To view detailed information about the MySQL (DBaaS) service, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to view detailed information. 3. MySQL(DBaaS) Details Go to the page.
MySQL(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Category
Detailed description
Cluster status
Cluster status with DB installed
Creating: Cluster is being created
Editing: Cluster is being changed to an operational state
Error: Cluster encountered a failure while performing a task
If it occurs continuously, contact the administrator
Failed: Cluster failed during creation
Restarting: Cluster is restarting
Running: Cluster is operating normally
Starting: Cluster is starting
Stopped: Cluster is stopped
Stopping: Cluster is being stopped
Synchronizing: Cluster is synchronizing
Terminating: Cluster is being terminated
Unknown: Cluster status is unknown
If it occurs continuously, contact the administrator
Upgrading: Cluster is being upgraded
Cluster control
Buttons to change the cluster state
Start: Start a stopped cluster
Stop: Stop a running cluster
Restart: Restart a running cluster
Switch-Over: Switch a standby cluster to Active
View more features
Cluster-related management buttons
Service status synchronization: Real-time DB service status lookup
Backup history: If backup is configured, check whether it runs correctly and view its history
Database recovery: Recover the DB based on a specific point in time
Parameter management: Ability to view and modify DB configuration parameters
Replica configuration: Set up a read‑only cluster as a Replica
Replica configuration (Other-Region): Configure a disaster‑recovery Replica in another region; the button is disabled if the account has no region to configure
DB user management: View and manage DB account (user) information registered in the DB
DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
Archive management: Set archive file retention periods and configure archive mode
DB Log export: Export stored logs to the user’s Object Storage via Audit settings
Migration configuration: Provides migration functionality using replication
Block Storage usage management: Provides usage query functionality per Block Storage type
OS (Kernel) upgrade: Upgrade the OS kernel version
Service cancellation
Cancel service button
Table. MySQL (DBaaS) status information and additional features
Detailed Information
MySQL(DBaaS) List page allows you to view detailed information of the selected resource and edit the information if needed.
Category
Detailed description
Server Information
Server information configured in this cluster
Category: Server type (Active, Standby, Replica)
Server Name: Server name
IP Port: Server IP and port
Status: Server status
service
Service name
Resource Type
Resource Type
SRN
Unique resource ID in Samsung Cloud Platform
In the DB service, it refers to the cluster SRN
Resource Name
Resource name
In the DB service, it refers to the cluster name
Resource ID
Unique resource ID in the service
Constructor
User who created the service
Creation Date/Time
Service creation date and time
Modifier
User who edited the service information
Modification date and time
Date and time the service information was modified
Image version
Installed DB image and version information
If a version upgrade is required, click the Edit icon to configure
If log collection configuration is required, click the Edit icon next to Log Collection to configure
DB character set
Encoding method to be used for the DB
Table case sensitivity
Case sensitivity of DB table
Time zone
Standard time zone used by the database
VIP
Virtual IP information
can be checked only when high availability is configured
Network
Network information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP))
| Service access policy configuration
If you need to add or remove an IP, click the Edit icon to configure
|
| Active & Standby | Active/Standby server type, default OS, additional Disk information
If you need to modify the server type, click the Edit icon next to the server type to configure it. Refer to the server type modification procedure in 서버 타입 변경하기
Modifying the server type requires a server reboot
If you need to expand storage, click the Edit icon next to the storage capacity to expand it. Refer to the storage expansion procedure in 스토리지 증설하기
If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure in 스토리지 추가하기
|
Table. MySQL (DBaaS) Database detailed information items
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.
Category
Detailed description
Master information
Name of the Master cluster
Replica count
Number of Replicas created in the Master cluster
Replica status
Replica server status in the Master cluster
You can view the server name, status query, status details, and status check time
To view the Replica status, click the Status Query button
While the query is in progress, the cluster remains in the Synchronizing state, and once the query completes, the cluster changes to the Running state
Table. Replica information tab detailed information items
tag
MySQL(DBaaS) List page lets you view the tag information of the selected resource, and you can add, change, or delete it.
Category
Detailed description
Tag list
Tag list
You can view the tag’s Key, Value information
Up to 50 tags can be added per resource
When entering tags, you can search and select from the list of previously created Keys and Values
Table. MySQL (DBaaS) tag tab item
Job History
On the MySQL(DBaaS) List page, you can view the operation history of the selected resource.
Category
Detailed description
Task History List
Resource change history
Operation date and time, resource ID, resource name, operation details, event topic, operation result, operator information check
Table. Work History tab detailed information items
MySQL(DBaaS) Managing Resources
If you need to change or restore the existing configuration options of a created MySQL(DBaaS) resource, or require a Replica configuration, you can perform the task on the MySQL(DBaaS) Detailed Information page.
Operation Control
If changes occur to a running MySQL (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of MySQL (DBaaS), follow the steps below.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List On the page, click the resource to control its operation. 3. MySQL(DBaaS) Details Go to the page.
Check the MySQL (DBaaS) status and complete the change using the control button below.
Start: DB service is installed on the server and the DB service is running (Running).
Stop: The server where the DB service is installed and the DB service will be stopped (Stopped).
Restart: Only the DB service will be restarted.
Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize service status
You can synchronize the real-time service status of MySQL (DBaaS).
To view the service status of MySQL(DBaaS), follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List On the page, click the resource to view the service status. 3. MySQL(DBaaS) Details Go to the page.
Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
When the query completes, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
To change the server type, follow these steps.
Caution
If you modify the server type, a server restart is required. * Please separately verify any SW license modifications or SW settings and their implementation due to spec changes.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page, click the resource whose server type you want to change. 3. Navigate to the MySQL(DBaaS) Details page.
Click the Edit icon for the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
Edit Server Type In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. For a redundant DB setup, all redundant servers are added simultaneously.
Caution
It is applied in the same way as the Storage type selected when creating the service.
For a high‑availability configured database, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
A Replica’s storage cannot be larger than the primary’s storage. * Please expand the Master storage after expanding the Replica storage.
When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to add storage. 3. MySQL(DBaaS) Details Go to the page.
Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to change the server type. 3. MySQL(DBaaS) Details Go to the page.
Click the Edit icon for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage popup opens.
Terminate MySQL(DBaaS)
You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
Caution
Replica is not deleted together. * If you delete the replica as well, please cancel it separately from the resource list.
If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel MySQL (DBaaS), follow the steps below.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
After termination is complete, verify on the MySQL(DBaaS) list page that the resource has been terminated.
4.2.1 - Managing DB Services
Users can manage MySQL (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows you to easily view and modify database configuration parameters.
Parameter lookup
To view configuration parameters, follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List On the page, click the resource whose parameters you want to view or modify. 3. Navigate to the MySQL(DBaaS) Details page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
In the Parameter Management popup, click the Search button. 5. View Notification The popup window opens.
View Notification when the popup window opens, click the Confirm button. 6. Retrieving may take a short amount of time.
Edit Parameter
To modify the configuration parameters, follow the steps below.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
In the Parameter Management popup, click the Search button. 5. View Notification The popup window opens.
When the View Notification popup opens, click the Confirm button. 6. Retrieving may take a short amount of time.
If modification is required, click the Edit button and enter the changes in the custom value area of the Parameter to be edited.
When the input is complete, click the Complete button.
참고
If you change the character_set_server value, first check the collation that matches the character set using the command below.
SQL> SHOW COLLATION WHERE Charset = 'character set name';
Set the parameter values for character-set-server, collation-server, and init_connect using the verified collation.
Item
Detailed description
Whether to restart
character-set-server
Specify default character set
Restart required
collation-server
Specify default collation (Collation)
Restart required
init_connect
SQL statement executed when the client connects to the database
No restart required
Table. Parameter setting items
Managing DB Users
Provides administrative features to view DB user information and modify status information.
Query DB users
To view DB users, follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource for which you want to view the DB user. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the DB User Management button. 4. Go to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
Change DB user status
To change the status of the retrieved DB user, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List Click the resource on the page for which you want to modify the DB user. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the DB User Management button. 4. Navigate to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
If modification is required, click the Edit button and change the status area value or enter remarks.
When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IP addresses that can access the database, configuring it so that only authorized IPs are allowed.
안내
Perform a DB user lookup before setting DB access control. For DB user lookup, please refer to DB 사용자 관리하기.
View DB access control
To view DB users with IP access control enabled, follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List Click the resource you want to manage access control for on this page. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
Click the Search button on the DB Access Control Management page. 5. Retrieving may take a short amount of time.
Add DB Access Control
Follow these steps to add IP access control.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL (DBaaS) List Click the resource on the page where you want to add IP access control. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
When the query is complete, click the Add button. 6. Add DB Access Control The popup window opens.
Add DB Access Control In the popup window, select the DB username and enter the IP address.
When the input is complete, click the Done button.
Delete DB access control
To delete IP access control, follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page, click the resource for which you want to delete IP access control. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the DB Access Control Management button. 4. Navigate to the DB Access Control Management page.
On the DB Access Control Management page, click the Search button. 5. Retrieving may take a short amount of time.
When the query is complete, click the Delete button. 6. Delete The popup window opens.
Delete popup, click the Confirm button.
Configure Archive mode
Provides Archive mode configuration and Archive Log retention period settings, allowing users to flexibly configure Archive log management policies to suit their operational environment.
안내
When creating a service, the default setting is Archive mode enabled, and the retention period is 3 days.
To set the Archive mode, follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource you want to set Archive mode for. 3. MySQL(DBaaS) Details Go to the page.
Click the More button and then click the Archive Settings Management button. 4. Navigate to the Archive Settings Management page.
On the Archive Settings Management page, click the Search button. 5. Retrieving may take a short amount of time.
Click the Edit button and select usage status and retention period.
When the edit is complete, click the Complete button.
DB Log Export
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types that need to be stored, the destination Bucket for export, and the log export interval. Copies logs to the specified Object Storage for storage according to the configured criteria.
Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for the long term.
안내
To use the DB Log export feature, you need to create an Object Storage. * Please refer to the Object Storage 사용자 가이드 for creating Object Storage.
Please be sure to verify the expiration date and time of the authentication key. * If the authentication key expires, logs will not be stored in the bucket.
Please ensure that the authentication key information is not exposed to external parties.
Setting DB Log Export Mode
Follow these steps to set the DB Log export mode.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page: click the resource whose DB Log you want to export. 3. Navigate to the MySQL(DBaaS) Details page.
Click the More button and then click the DB Log Export button. 4. DB Log Export Go to the page.
On the DB Log Export page, click the Register button. 5. Navigate to the Register DB Log Export page.
DB Log Export Registration page, after entering the required information, click the Complete button.
Category
Required
Detailed description
Log type
Required
Log type to be saved
Save bucket name
Essential
Object Storage bucket name to be saved
Authentication key > Access key
Required
Access key for accessing the Object Storage you want to store.
Authentication key > Secret key
Required
Secret key for accessing the Object Storage you want to store
File creation cycle
Required
File creation frequency in Object Storage
Whether to delete the original log
Selection
Whether to delete the original logs when exporting to Object Storage
Table. MySQL(DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource you want to manage DB Log export for. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the DB Log Export button. 4. Go to the DB Log Export page.
On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Terminate buttons.
Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
Edit: Modify the DB Log export mode setting.
Cancel: Disables the DB Log export mode setting.
Upgrade version
If a latest patch that includes security enhancements and feature improvements is available, you can apply it using the version upgrade feature.
Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.
It is recommended to perform an immediate backup in advance to prepare for any issues that may arise during the upgrade process. * If not, a failure may occur, and some data may not be recoverable.
In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. * Please check the version of Replica first, and if necessary, perform a version upgrade.
The backed-up data is automatically deleted after the version upgrade is completed.
Major version upgrade
Caution
A major version upgrade requires a pre‑simulation test.
Please set up a separate replica DB, promote it to master, and pre-validate the major upgrade. * Afterward, we recommend proceeding only after thoroughly reviewing the service impact with the Application manager.
To perform a Major version upgrade, follow the steps below.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List navigate to the page.
MySQL(DBaaS) List page, click the resource to upgrade the Major version. 3. Navigate to the MySQL(DBaaS) Details page.
Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
Version Upgrade In the popup window, select the upgrade type and patch version, then click the Confirm button.
Version Upgrade Notification Click the Confirm button in the popup window.
Minor version upgrade
Supports minor version upgrades within the same major version.
To perform a minor version upgrade, follow the steps below.
All Services > Database > MySQL(DBaaS) menu, click it. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to upgrade the Minor version. 3. MySQL(DBaaS) Details Go to the page.
Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
Version Upgrade In the popup window, select the upgrade type and patch version, then click the Confirm button.
Version Upgrade Notification Click the Confirm button in the popup window.
Configure Migration
Provides a Migration feature that synchronizes in real time with the operational database and replicates using a Replication method without service interruption.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page, click the resource you want to migrate. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the Migration Setup button. 4. Migration configuration popup window opens.
Migration configuration In the popup window, review the instructions and click the Confirm button. 5. Go to the Migration configuration page.
Migration configuration After entering the required information on the page, click the Verify Connection button.
When the connection is complete, click the Done 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 that is the migration target
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 that is the migration target
Table. MySQL (DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a configured Migration Cluster to a Master Cluster.
Caution
When the master is promoted, synchronization with the source DB that is the migration target is stopped.
To promote the Migration Cluster to Master, follow the steps below.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to promote to Master. 3. MySQL(DBaaS) Details Go to the page.
Click the More button, then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
Master Promotion Notification popup, click the Confirm button.
Managing Block Storage Usage
You can view the usage of Block Storage by type allocated to the DB instance.
To view Block Storage usage, follow these steps.
All Services > Database > MySQL(DBaaS) menu, click it. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
MySQL (DBaaS) List page, click the resource to view Block Storage usage. 3. MySQL(DBaaS) Details Navigate to the page.
Click the More button, then click the Block Storage Usage Management button. 4. Go to the Block Storage Usage Management page.
On the Block Storage Usage Management page, click the Search button. 5. Block Storage Usage Management page shows usage by Block Storage type.
Retrieving usage by Block Storage type may take a short while.
OS Kernel Upgrade
You can upgrade the OS kernel to improve the functionality of the running database and apply security patches.
Caution
The service will be unavailable while the OS upgrade is in progress.
The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
After the upgrade is complete, you cannot revert to the original OS.
To upgrade the OS Kernel, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
Please click the resource to upgrade the OS Kernel on the MySQL(DBaaS) List page. 3. Navigate to the MySQL(DBaaS) Details page.
Click the More button, then click the OS(Kernel) Upgrade button. 4. OS(Kernel) Upgrade Notification A popup window opens.
OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
4.2.2 - Backing up and restoring the DB
Users can configure backups of MySQL (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up MySQL (DBaaS)
PostgreSQL(DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
For instructions on configuring backup settings for MySQL(DBaaS), see MySQL(DBaaS) 생성하기.
To modify the backup settings of the created resource, follow the steps below.
Caution
For reliable backups, we recommend adding separate BACKUP storage or sufficiently expanding storage capacity. * Especially when the backup data exceeds 100 GB and experiences frequent changes, please provision additional storage equal to approximately 60 % of the data size. * Please refer to the guides for adding and expanding storage, MySQL(DBaaS) 스토리지 추가하기, MySQL(DBaaS) 스토리지 증설하기.
If a backup is configured, it runs at the specified time after the set time, and additional fees are incurred based on the backup size.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List On the page, click the resource to configure a backup. 3. MySQL(DBaaS) Details Go to the page.
Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
If you stop the backup setting, uncheck Use in the Backup Settings popup window and authenticate via the logged-in user’s mobile phone. Once user authentication is completed, the backup setting is disabled and backup execution stops.
Perform immediate backup
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
To perform an immediate backup, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page, click the resource to perform an immediate backup. 3. MySQL(DBaaS) Details Go to the page.
Click the Immediate Backup button of the backup item. 4. Immediate backup settings The popup window opens.
In the Immediate backup setting popup, click the Confirm button.
Check backup history
안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, see 알림 정책 생성하기.
To view the backup history, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to view the backup history. 3. MySQL(DBaaS) Details Go to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, you can view the backup status, version, start time, completion time, and size.
Delete backup file
Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
To delete the backup history, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) List page, click the resource to view the backup history. 3. MySQL(DBaaS) Details Go to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
When user authentication is completed, the backup file will be deleted.
MySQL(DBaaS) Recover
If a failure or data loss necessitates restoration from a backup file, the recovery function can restore based on a specific point in time. When performing a MySQL(DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds using the database’s configuration information and data.
Caution
To perform recovery, at least double the Disk data type’s capacity is required. If disk space is insufficient, recovery may fail.
To recover MySQL (DBaaS), follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
MySQL(DBaaS) Resource Click the resource you want to restore on the list page. 3. MySQL(DBaaS) Details Go to the page.
Click the Database Recovery button. 4. Go to the Database Recovery page.
After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category
Required status
Detailed description
Recovery type
Required
Set the point in time the user wants to restore
Backup point (recommended): Restore based on the backup file. Select from the list of backup points displayed in the list.
Custom point: Restore to a user‑desired point within the range of recoverable backup times. The recoverable period depends on the Archive backup interval setting, allowing restoration from the initial backup start time up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix
Required
Recovery DB server name
Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name
Required
Cluster name of the recovery DB
Enter using English letters, 3 ~ 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Server type for the recovery DB installation
Standard: standard specification commonly used
High Capacity: large-capacity server with 24vCore or more (to be provided later)
Service Type > Planned Compute
Selection
Planned Compute가 설정된 자원 현황
In Use: Number of resources with Planned Compute that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Go to the Planned Compute service request page
DATA: Storage area for table data, archive files, etc.
Applied identically with the storage type set in the original cluster
Enter capacity as a multiple of 8 within the range 16 to 5,120
Additional: Storage area for DATA, Archive, TEMP, Backup data
Applied identically with the storage type set in the original cluster
In the recovery DB, only DATA, TEMP, and Archive purposes can be added
After selecting Use, enter the storage purpose and capacity
Click the Add button to add storage, or click the x button to delete
Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username
Required
Database username set in the source DB
Database Port number
Required
Database Port number set in the source DB
IP access control
Selection
IP address for accessing the recovery DB
Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.1/32, 192.168.10.1/32), and click the Add button
To delete an entered IP, click the x button next to the entered IP
Maintenance period
Selection
DB maintenance window
If you select Use, set the day of the week, start time, and duration
The maintenance window is a feature that lets the user define the time slot for performing patch operations, and any patch work within that period must be carried out by the user.
We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
tag
Selection
Add tag
After clicking the Add tag button, enter or select Key, Value values
Table. MySQL(DBaaS) recovery configuration items
4.2.3 - Configure Read Replica
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Configure Replica
You can create replica servers for read‑only or disaster‑recovery purposes through replica configuration. You can create up to 5 replicas per database.
Information
To configure a disaster recovery Replica, please create it via Replica Setup (Other Region).
To configure a Replica, follow these steps.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to configure a Replica. 3. MySQL(DBaaS) Details Navigate to the page.
Click the Replica configuration button. 4. Go to the Replica configuration page.
After entering information in the Replica configuration area, click the Done button.
Category
required status
Detailed description
Region
required
Region to configure the Replica
Replica configuration (Other Region) is displayed only when selected
Replica count
Required
Number of Replicas to configure
Up to 5 can be configured per cluster
If you select more than one value, additionally enter the Replica name and service type information
Replica name
Required
Replica server name
Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) to enter 3 to 19 characters
The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type
Required
Replica server type
Standard: standard specification commonly used
High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute
Selection
Status of resources with Planned Compute configured
In Use: Number of resources with Planned Compute configured that are currently in use
Configured: Number of resources with Planned Compute configured
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Navigate to the Planned Compute service application page
Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not 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 an entered IP, click the x button next to the entered IP
maintenance period
Select
Database 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 management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
If set to unused, we are not responsible for issues arising from patches not being applied.
Tag
Select
Add Tag
Add Tag after clicking the button, enter or select Key, Value values
Table. MySQL (DBaaS) Replica configuration items
Reconfigure Replica
If a network outage or replication delay with the Master Cluster occurs, you can use the Replica reconstruction function to replicate the Master Cluster’s data again.
To reconfigure the Replica, follow the steps below.
All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
On the MySQL(DBaaS) List page, click the resource to reconfigure the Replica. 3. MySQL(DBaaS) Details Navigate to the page.
Click the Replica reconstruction button. 4. Replica Reconfiguration Notification A popup window opens.
Replica Reconfiguration Notification In the popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a configured Replica Cluster to a Master Cluster.
Caution
When the Master is promoted, synchronization with the existing Master Cluster is stopped.
To promote a Replica Cluster to Master, follow these steps.
Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
MySQL(DBaaS) List On the page, click the resource to promote to Master. 3. MySQL(DBaaS) Details Go to the page.
Click the More button and then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
In the Master Promotion Notification popup, click the Confirm button.
4.2.4 - MySQL (DBaaS) server connection
Scenario Overview
MySQL(DBaaS) server connection scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to MySQL (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Figure. MySQL(DBaaS) server connection architecture
Scenario components
You can build the scenario using the following services.
Service group
service
Detailed description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Networking
VPC > Subnet
A service that lets users segment the network within a VPC to match their purpose and scale
Networking
VPC > Public IP
A service that reserves a public IP and allocates and releases it to Compute resources.
Networking
VPC > Internet Gateway
A service that connects VPC resources to the Internet
Networking
Security Group
Virtual firewall that controls server traffic
Database
MySQL(DBaaS)
A service that easily creates and manages MySQL in a web environment
Compute
Virtual Server
Virtual server optimized for cloud computing
Compute
Virtual Server > Keypair
Encryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Explains the process of configuring the network environment for accessing the Bastion Host and Database services.
All Services > Networking > FirewallClick the menu. 1. Navigate to the Firewall’s Service Home page.
On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
On the detail information page, click the Rules tab. 4. Go to the Rules tab.
Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address
Destination address
Protocol
Port
Operation
Direction
Explanation
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. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide provides instructions on how to connect using MySQL Workbench. Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB client program (MySQL Workbench) on the Bastion host
Go to the official MySQL page and download the MySQL Workbench program.
Connect the user’s PC hard drive to upload the file to the Bastion host.
Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install it.
5-3. ### Connect to the database using a DB client program (MySQL Workbench)
Run MySQL Workbench and click Database > Manage connections. 1. Manage Server Connection A popup window appears.
Manage Server Connection In the popup window, click the New button at the bottom left, enter the Database server information created in 3-1. MySQL(DBaaS) 서비스 생성하기, and click the Test Connection button. 2. Password a popup window appears.
Required input element item
input value
Connection Name
Custom (ex. service name)
Host name
Database server IP
Port
Database Port
Username
Database username
Table DB connection client program input fields
Password in the popup window, enter the password you set in 3-1. MySQL(DBaaS) 서비스 생성하기 and click the OK button. 3. When the operation succeeds, click the OK button in the Manage Server Connection popup window.
Click Database > Connect to Database. 4. Connect to Database A popup window appears.
Select the Connection Name registered in Stored Connection to perform a Database connection. 5. After connecting, you can perform simple queries, etc.
4.3 - API Reference
API Reference
4.4 - CLI Reference
CLI Reference
4.5 - Release Note
MySQL(DBaaS)
2026.07.16
FEATUREImmediate backup, Disk usage query, addition of Major version upgrade feature, and addition of 3rd‑generation server type
Immediate backup, Disk usage monitoring, Add major version upgrade feature
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
Through the Disk usage query feature, you can view the usage of each Block Storage type allocated to an instance.
Through the Major version upgrade feature, users can perform a Major version upgrade.
Add third-generation server type
The third-generation server type has been newly added. * For more details, please refer to MySQL(DBaaS) 서버 타입.
2026.03.19
FEATUREConfigure Replica for disaster recovery, add OS (Kernel) upgrade feature, provide Servicewatch integration feature
You can configure a disaster recovery Replica using the Replica configuration (Other Region) feature.
Strengthen the latest security patches and stability via the OS (Kernel) upgrade feature.
You can monitor metrics and logs by integrating with Servicewatch.
2025.07.01
FEATUREUser (access control) management, Archive configuration feature, Add DB Audit Log export feature, Provide backup notification feature, Add migration feature
Add MySQL (DBaaS) feature
Add 2nd-generation server type
Add a 2nd-generation (db2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, refer to MySQL(DBaaS) 서버 타입.
Add DB user and access control management and Archive configuration feature
Provides notification functionality for backup success and failure. * For detailed information, refer to 알림 정책 생성하기.
Migration feature addition
Provides replication-based zero-downtime data migration functionality. * For more details, refer to Migration 구성하기
Add HDD, HDD_KMS types to Block Storage
2025.02.27
FEATUREAdd server type and per-server IP configuration, add Block Storage capacity expansion feature
MySQL(DBaaS) Feature Change
Add second-generation server type
Add a 2nd-generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. * For detailed information, refer to mysql(DBaaS) 서버 타입
After creating the service, you can expand the configured Block Storage capacity.
Server-specific network IP configuration feature added allows either common or server-specific settings depending on the usage purpose.
Samsung Cloud Platform Common Feature Change
Common CX changes for Account, IAM, Service Home, tags, and other items have been applied.
2024.10.01
NEWMySQL(DBaaS) service official version launch
A MySQL (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been launched.
5 - Microsoft SQL Server(DBaaS)
5.1 - Overview
Service Overview
Microsoft SQL Server(DBaaS) is a representative relational database management system (RDBMS) used in various applications. Samsung Cloud Platform provides an environment that can automate Microsoft SQL Server installation and perform management functions for operation through a web-based console.
Microsoft SQL Server (DBaaS) is designed with an Always On‑based availability architecture, so when the Primary server’s content changes, it is synchronously replicated to the Secondary server. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling recovery of data at the desired point in time.
Provided features
Microsoft SQL Server (DBaaS) provides the following features.
Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and provides a Primary-Secondary redundancy configuration built on Always On. * When the Primary server fails, it automatically fails over to the Secondary.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the node transition between Primary and Secondary can be performed directly by the user through a switch-over.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time slots and storage locations, as well as the day of full backups, can be set by the user, and additional fees may apply based on backup size. * It also provides a recovery feature for backed‑up data, so when a user initiates a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup creation time or a user‑specified time). * When restoring to a user-specified point in time, you can set the restore point up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
Version Management: Provides a Minor version upgrade feature based on some functionality improvements and security patches.
Secondary configuration: It is possible to add a Read Replica (Secondary Replica) for read load balancing and disaster recovery (DR).
Audit setting: Provides an Audit setting feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
Parameter management: You can modify DB configuration parameters related to performance improvement and security.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Log Export: You can export stored logs to the user’s Object Storage through Audit settings.
Components
Microsoft SQL Server(DBaaS) provides pre-validated engine versions and a variety of server types. Users can choose and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by Microsoft SQL Server(DBaaS) are as follows.
Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
EoS Date (Samsung Cloud Plaform New Creation Stop Date)
EoTS date (Community technical support end date)
MS SQL Server
2019 (Standard, Enterprise)
KB5033688 / 15.0.4355.3
2029-06 (planned)
Extended support: 2030-01-08
Mainstream support: 2025-02-28
2019 (Standard, Enterprise)
KB5046365 / 15.0.4405.4
2029-06 (planned)
Extended support: 2030-01-08
Mainstream support: 2025-02-28
2019 (Standard, Enterprise)
KB5054833 / 15.0.4430.1
2029-06 (scheduled)
Extended support: 2030-01-08
Mainstream support: 2025-02-28
2019 (Standard, Enterprise)
KB5058722 / 15.0.4435.7
2029-06 (planned)
Extended support: 2030-01-08
Mainstream support: 2025-02-28
2022 (Standard, Enterprise)
KB5048033 / 16.0.4165.4
2032-06 (planned)
Extended support: 2033-01-11
Mainstream support: 2028-01-11
2022 (Standard, Enterprise)
KB5050771 / 16.0.4185.3
2032-06 (planned)
Extended support: 2033-01-11
Mainstream support: 2028-01-11
2022 (Standard, Enterprise)
KB5058721 / 16.0.4200.1
2032-06 (planned)
Extended support: 2033-01-11
Mainstream support: 2028-01-11
2022 (Standard, Enterprise)
KB5059390 / 16.0.4205.1
2032-06 (planned)
Extended support: 2033-01-11
Mainstream support: 2028-01-11
2022 (Standard, Enterprise)
KB5065865 / 16.0.4215.2
2032-06 (planned)
Extended support: 2033-01-11
Mainstream support: 2028-01-11
Table. Microsoft SQL Server (DBaaS) engine version provided
Information
The next version of MS SQL Server is scheduled to be available after September 2026. The actual service delivery schedule is subject to change.
MS SQL Server 2022 (Standard, Enterprise) KB5078297 / 16.0.4236.2
Server type
The server types supported by Microsoft SQL Server (DBaaS) are as follows.
Please refer to Microsoft SQL Server(DBaaS) 서버 타입 for detailed information about the server types provided by Microsoft SQL Server (DBaaS).
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server types
Standard: Standard specifications (vCPU, Memory) commonly used
High Capacity: Large server specifications of 24 vCores or more
Server specifications
db1
Provided server specifications
db1: Standard specifications (vCPU, Memory) configuration
dbh2: Large-capacity server specifications
Provides servers with 24 vCore or more
Server specifications
v2
vCore count
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. Microsoft SQL Server (DBaaS) server type components
Preceding Service
This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.
A service that provides an isolated virtual network in a cloud environment
Table. Microsoft SQL Server (DBaaS) pre-service
5.1.1 - Server type
Microsoft SQL Server(DBaaS) server type
Microsoft SQL Server (DBaaS) provides server types composed of various combinations of CPU, memory, and network bandwidth.
When creating a Microsoft SQL Server (DBaaS), the Database Engine is installed according to the server type selected for the intended use.
Reference
The server types offered may vary depending on the region and AZ.
The server types supported by Microsoft SQL Server(DBaaS) are as follows.
Standard db1v2m4
Category
Example
Detailed description
Server type
Standard
Provided server type categories
Standard: Configured with standard specifications (vCPU, Memory) commonly used
High Capacity: Large-capacity server specifications exceeding Standard
Server specifications
db1
Provided server type classification and generation
db1: indicates a standard specification, and 1 denotes the generation
dbh2: h indicates a high-capacity server specification, and 2 denotes the generation
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. Microsoft SQL Server (DBaaS) server type format
db1 server type
The db1 server type of Microsoft SQL Server (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
db1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
db1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
db1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
db1v2m24
2 vCore
24 GB
Maximum 10 Gbps
Standard
db1v2m32
2 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
db1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
db1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
db1v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
db1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
db1v6m12
6 vCore
12 GB
Maximum 10 Gbps
Standard
db1v6m24
6 vCore
24 GB
Up to 10 Gbps
Standard
db1v6m48
6 vCore
48 GB
Up to 10 Gbps
Standard
db1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
db1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m16
8 vCore
16 GB
Up to 10 Gbps
Standard
db1v8m32
8 vCore
32 GB
Up to 10 Gbps
Standard
db1v8m64
8 vCore
64 GB
Up to 10 Gbps
Standard
db1v8m96
8 vCore
96 GB
Up to 10 Gbps
Standard
db1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
db1v10m20
10 vCore
20 GB
Up to 10 Gbps
Standard
db1v10m40
10 vCore
40 GB
Up to 10 Gbps
Standard
db1v10m80
10 vCore
80 GB
Up to 10 Gbps
Standard
db1v10m120
10 vCore
120 GB
Up to 10 Gbps
Standard
db1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
db1v12m24
12 vCore
24 GB
Up to 12.5 Gbps
Standard
db1v12m48
12 vCore
48 GB
Up to 12.5 Gbps
Standard
db1v12m96
12 vCore
96 GB
Up to 12.5 Gbps
Standard
db1v12m144
12 vCore
144 GB
Up to 12.5 Gbps
Standard
db1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v14m28
14 vCore
28 GB
Up to 12.5 Gbps
Standard
db1v14m56
14 vCore
56 GB
Up to 12.5 Gbps
Standard
db1v14m112
14 vCore
112 GB
Up to 12.5 Gbps
Standard
db1v14m168
14 vCore
168 GB
Up to 12.5 Gbps
Standard
db1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
db1v16m32
16 vCore
32 GB
Up to 12.5 Gbps
Standard
db1v16m64
16 vCore
64 GB
Up to 12.5 Gbps
Standard
db1v16m128
16 vCore
128 GB
Up to 12.5 Gbps
Standard
db1v16m192
16 vCore
192 GB
Up to 12.5 Gbps
Standard
db1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. Microsoft SQL Server(DBaaS) server type specifications - db1 server type
5.1.2 - Monitoring metrics
Cloud Monitoring Service Termination Notice
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026. After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
During the parallel operation period, we must prepare for the Servicewatch transition. * Performance and log data backup, the settings configured by users linked with existing Cloud Monitoring (e. You must verify items such as event policies and perform tasks such as resetting the ServiceWatch service, then complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
Console menu termination (September 2026 service improvement work)
You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
Service termination (service improvement work in November 2026)
All services of Cloud Monitoring, including the API, will be permanently discontinued.
After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
The table below shows the performance monitoring metrics for Microsoft SQL Server (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
Run a query to verify that all data files are ONLINE.
cnt
Instance State [Cluster]
Status during MSSQL cluster configuration
state
Instance State [PID]
sqlservr.exe process pid
PID
Lock Processes [Blocked]
Number of SQL processes blocked by other processes
cnt
Lock Waits [Per Second]
Lock wait count per second
cnt
Page IO Latch Wait Time
Page IO latch waits average wait time
ms
Slowqueries
Number of SQL queries running for a long time (over 5 minutes)
cnt
Slowquery CPU Time
CPU time spent executing SQL that runs for a long time (over 5 minutes)
ms
Slowquery Execute Context ID
Context ID linked to the execution task of a SQL that has been running for a long time (over 5 minutes)
ID
Slowquery Memory Usage
Memory usage incurred by the execution of SQL that runs for a long time (over 5 minutes)
bytes
Slowquery Session ID
Session ID of SQL queries running for a long time (over 5 minutes)
ID
Slowquery Wait Duration Time
Total wait time for wait type
ms
Tablespace Used
Data volume size
bytes
Transaction Time [MAX]
Long-running transaction
cnt
Table. Microsoft SQL Server (DBaaS) Monitoring Metrics
5.1.3 - ServiceWatch metric
Microsoft SQL Server(DBaaS) sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at 1‑minute intervals.
Reference
For how to view metrics in ServiceWatch, refer to the ServiceWatch guide.
basic metrics
The following are basic metrics for the Microsoft SQL Server(DBaaS) namespace.
In the table below, the metrics whose names are shown in bold are the key metrics selected from those provided by Microsoft SQL Server (DBaaS).
The main metrics are used to configure the service dashboards that are automatically built for each service in ServiceWatch.
Each metric provides guidance in the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics through primary statistical values.
OS Basic Metrics
Classification
Performance items
unit
Detailed description
meaningful statistics
CPU
CPU Usage
Percent
CPU usage
Total
Average
Maximum
Minimum
Disk
Disk Usage
Percent
Disk usage
Total
Average
Maximum
Minimum
Disk
Disk Write Bytes
Bytes/Second
Write capacity (bytes/second) on block device
Total
Average
Maximum
Minimum
Disk
Disk Read Bytes
Bytes/Second
Read throughput from block device (bytes/second)
Total
Average
Maximum
Minimum
Disk
Disk Write Requests
Count/Second
Number of write requests on block device (requests per second)
Total
Average
Maximum
Minimum
Disk
Disk Read Requests
Count/Second
Number of read requests on block device (requests per second)
Total
Average
Maximum
Minimum
Disk
Average Disk I/O Queue Size
None
Average queue length of requests issued to the block device
Total
Average
Maximum
Minimum
Disk
Disk I/O Utilization
Percent
The proportion of time the block device actually spent processing I/O operations
Total
Average
Maximum
Minimum
Memory
Memory Usage
Percent
Memory usage
Total
Average
Maximum
Minimum
Memory
Swap Out Bytes
Bytes/Second
Data transferred from memory to swap area (bytes/second)
Total
Average
Maximum
Minimum
Memory
Swap Used Bytes
Bytes
Current swap space size
Total
Average
Maximum
Minimum
Memory
Swap Cached Usage
Percent
Cached swap usage rate
Total
Average
Maximum
Minimum
Memory
Swap Total Bytes
Bytes
Total swap space size configured on the system
Total
Average
Maximum
Minimum
Memory
Swap In Bytes
Bytes/Second
Amount read from swap area to memory (bytes/second)
Total
Average
Maximum
Minimum
Memory
Swap Usage
Percent
Current usage ratio relative to total swap space
Total
Average
Maximum
Minimum
Memory
Swap Cached Bytes
Bytes
Size of pages that have been restored to memory but still have a copy in the swap area
Total
Average
Maximum
Minimum
Memory
Swap Free Bytes
Bytes
Size of unused remaining swap space
Total
Average
Maximum
Minimum
Network
Network In Bytes
Bytes/Second
Received capacity (bytes/second) on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Bytes
Bytes/Second
Transmitted capacity (bytes/second) on the network interface
Total
Average
Maximum
Minimum
Network
TCP Connections
Count/Second
Total number of TCP connections currently established correctly
Total
Average
Maximum
Minimum
Network
Network In Packets
Count
Number of packets received on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Packets
Count
Number of packets transmitted on the network interface
Total
Average
Maximum
Minimum
Network
Network In Dropped
Count
Number of packet drops received on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Dropped
Count
Number of packet drops transmitted from the network interface
Total
Average
Maximum
Minimum
Network
Network In Errors
Count
Number of packet errors received on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Errors
Count
Number of packet errors transmitted on the network interface
Total
Average
Maximum
Minimum
OS
OS Uptime
Seconds
Time elapsed (seconds) since the system was last booted
Total
Average
Maximum
Minimum
Table. OS basic metrics
Microsoft SQL Server(DBaaS) Basic Metrics
Classification
Performance items
unit
Detailed description
meaningful statistics
General
Page Life Expectancy Seconds
Seconds
Estimated time (seconds) that a data page remains in the buffer pool without disk re-reference
Total
Average
Maximum
Minimum
General
Full Scans/sec
Count/Second
Number of Table Full Scans per second
Total
Average
Maximum
Minimum
General
Range Scans/sec
Count/Second
Number of Range Scans performed per second
Total
Average
Maximum
Minimum
General
Index Searches/sec
Count/Second
Number of Index Searches performed per second
Total
Average
Maximum
Minimum
General
Buffer Cache Hit ratio
Percent
Proportion of page requests processed directly from the buffer cache
Total
Average
Maximum
Minimum
General
Cursor Requests/Sec
Count/Second
Number of SQL cursor requests received by the server per second
Total
Average
Maximum
Minimum
General
Page Fault Count
Count
Number of page faults for all processes, including system processes
Total
Average
Maximum
Minimum
Locks & Latches
Lock Requests/Sec
Count/Second
Number of lock requests per second
Total
Average
Maximum
Minimum
Locks & Latches
Lock Blocks
Count
Number of blocks where a lock occurred
Total
Average
Maximum
Minimum
Locks & Latches
Table Lock Escalation/Sec
Count/Second
The number of locked blocks per second became excessive, causing escalation to table-wide locking.
Total
Average
Maximum
Minimum
Locks & Latches
| Count/Second | Dead Lock count per second |
Total
Average
Maximum
Minimum
|
| Locks & Latches | Latch Waits/sec | Count/Second | Latch wait count per second |
Total
Average
Maximum
Minimum
|
| Locks & Latches | Page reads/sec | Count/Second | Number of database pages read from disk per second |
Total
Average
Maximum
Minimum
|
| Locks & Latches | Page writes/sec | Count/Second | Number of database pages written to disk per second |
Total
Average
Maximum
Minimum
|
| Sessions | Active sessions | Count | Number of active transactions |
Total
Average
Maximum
Minimum
|
| Sessions | Connections Count | Count | Number of connections to the DB |
Total
Average
Maximum
Minimum
|
| State | Instance state | None | DB operational status
|
| Tablespace | Disk Free Gb | Gigabytes | Available space (GB) of the block storage where the Database and Log are stored |
Total
Average
Maximum
Minimum
|
| Transactions | Batch Request/Sec | Count/Second | Number of Transact‑SQL command batches received per second |
Total
Average
Maximum
Minimum
|
Table. Microsoft SQL Server (DBaaS) basic metrics
5.2 - How-to guides
Users can create the service by entering the required information for Microsoft SQL Server (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
Cloud Monitoring 서비스 종료 안내
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026. After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Resource-Specific Monitoring Service Application Guide
New Resources: Resources created after the July 2026 service improvement work are provided with default monitoring using the ServiceWatch service.
Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
During the parallel operation period, you must prepare for the Servicewatch transition. * Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (e.g. Check the (event policy, etc.) and perform tasks such as resetting the ServiceWatch service, and complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
Console menu termination (September 2026 service improvement work)
You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
Service termination (service improvement work in November 2026)
All services of Cloud Monitoring, including the API, will be permanently discontinued.
After the service ends in November, Cloud Monitoring data cannot be viewed. * Be sure to complete the ServiceWatch migration work within the parallel operation period**
Detailed information about ServiceWatch can be found by referring to ServiceWatch 개요.
Create Microsoft SQL Server(DBaaS)
You can create and use the Microsoft SQL Server (DBaaS) service from the Samsung Cloud Platform Console.
안내
Before creating the service, configure the VPC’s Subnet type as General.
If the subnet type is Local, the corresponding Database service cannot be created.
When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning unnecessary data or migrating old data to a statistical collection environment.
This service is provided on a Single-AZ basis.
To create a Microsoft SQL Server(DBaaS), follow these steps.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) Create button. 2. Microsoft SQL Server(DBaaS) creation Navigate to the page.
On the Microsoft SQL Server(DBaaS) Creation page, enter the information required to create the service and select detailed options.
Select the required information in the Image and version selection area.
Category
required status
Detailed description
Image version
Required
Provide a version list of Microsoft SQL Server (DBaaS)
Table. Microsoft SQL Server (DBaaS) Image and version selection options
Enter or select the required information in the Service Information Input area.
Category
Required status
Detailed description
Server name Prefix
Required
The server name where the DB will be installed
must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters (-) with a length of 3 to 13 characters
Based on the server name, a postfix such as 001, 002 is appended to create the actual server name
Cluster name
Required
Cluster name of the DB servers
Enter using English letters, 3 - 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Server type for DB installation
Standard: Standard specifications commonly used
High Capacity: Large-capacity server with 24 vCores or more
For detailed information about the server types provided by Microsoft SQL Server (DBaaS), refer to Microsoft SQL Server(DBaaS) 서버 타입
Service Type > Planned Compute
Selection
Status of resources with Planned Compute set
In Use: Number of resources with Planned Compute that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied by Planned Compute per resource
Create Planned Compute Service: Go to the Planned Compute service application page
Configure Block Storage used by the DB according to its purpose
Basic OS: Area where the DB engine is installed
DATA: Storage area for table data, archive files, etc.
After selecting the storage type, enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
SSD: High‑performance general volume
HDD: General volume
SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
The configured storage type is also applied to additional storage
Enter the capacity as a multiple of 8 within the range 16 to 5,120
Additional: Data storage area
After selecting Use, enter the storage’s Purpose and Capacity
To add storage, click the Add button; to delete, click the x button
Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Redundant configuration
Selection
Redundancy configuration status
When redundancy configuration is used, the DB instance is configured as an Active DB and a Standby DB
Use AD
Selection
Set whether to use a pre-configured AD (Active Directory) server
Domain Name: Domain name
Domain NetBIOS Name: Domain NetBIOS name
DNS Server IP: Enter DNS server IP / secondary DNS server IP and click the Add button
Up to 5 entries can be entered
AD Server ID: AD user ID
AD Server Password: User password
High Availability Cluster Name: Name of the failover cluster used when configuring high availability
Displayed only when the high availability option is used
Click Port Connection Guide to view the Security Group inbound/outbound rule information required for connecting the SQL server and AD server
Network > Common Settings
Required
Network settings for servers created by the service
Select this when you want to apply the same settings to all installed servers
Select a pre‑created VPC, Subnet, IP, and Public NAT
Each server’s IP is generated automatically
The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings
Required
Network settings where servers generated by the service are installed
Select if you want to apply different settings for each installed server
Select a pre‑created VPC, Subnet, IP, and Public NAT
Enter the IP for each server
The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
IP access control
Selection
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
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 an entered IP, click the x button next to the entered IP.
maintenance period
Selection
DB maintenance window
If you select Use, you can set the day of the week, start time, and duration
The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and patch tasks within that period are performed directly by the user.
For the stable operation of the system, please set a maintenance window; we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
Table. Microsoft SQL Server (DBaaS) service configuration items
Enter required database configuration information: enter or select the required information in this area.
Category
Required status
Detailed description
Database service name
Required
Database management unit name
starts with an uppercase English letter and is entered using English characters with a length of 1 - 15
Database name > default
Required
Server name applied during DB installation
must start with an English letter and be entered using English letters, numbers, and special characters (.,_) with a length of 3 - 20 characters
Database name > Add
Required
Enter the Database name to install after selecting Use for the server name
. It must start with an English letter and be entered using English letters, numbers, and special characters (., _) with a length of 3 to 20 characters
For each Database, the drive where data is stored can be selected from the drives added in Service Type > Block Storage
Adding Databases is only possible in the Enterprise version, and up to 100 can be added
Database username
Required
DB user name
An account with the same name is also created on the OS
Enter using lowercase English letters, 2 to 20 characters
The following names cannot be used as Database user names
English letters, numbers, and special characters(“‘ except) including, enter 8-30 characters
Check database password
Required
Check DB connection password
Re-enter the DB connection password identically
Database Port number
Required
DB connection port number
Enter DB port within the range 1200 - 65535
License
Required
SQL Server License Key
Enter the issued license key
If the entered license key is invalid, the service may not be created
Backup > Use
Selection
Backup usage
Select Use to set the backup file retention period, backup start time, Full backup schedule (day of week), and Archive backup interval
Backup > Retention Period
Selection
Backup retention period
Select the backup retention period. Set the file retention period from 7 days to 35 days
Backup files incur additional charges based on size
Backup > Backup Start Period
Selection
Backup start time
Select backup start time
The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be configured
Backup > Full backup schedule (day of week)
Selection
Full backup schedule
Select the day of the week for full backup execution
Full backup is performed on a weekly basis
Backup > Archive backup schedule
Selection
Archive backup frequency
Select the Archive backup frequency
The Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log Settings
Selection
Whether to store Audit Log
Select Use to enable the Audit Log feature
DDL and user connection information records are stored
Enabling Audit may degrade DB performance
ServiceWatch log collection
Selection
ServiceWatch log collection status
Select Use to configure the ServiceWatch log collection feature
Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB
When collecting, log groups and log streams are created automatically, and they cannot be deleted until the resource is deleted
To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Parameter
Required
DB configuration parameters
Click the View button to view detailed information of the parameters
Parameters can be modified after the service creation is complete, and a DB restart is required after modification
DB Collation
Selection
Data sorting method
Data sorting, a command that specifies the method of comparison, can produce different results depending on the settings
Time zone
Required
Standard time zone used by the database
Table. Microsoft SQL Server (DBaaS) Database configuration items
In the Additional Information Input area, enter or select the required information.
Category
Required status
Detailed description
tag
Selection
Add Tag
Up to 50 per resource can be added
After clicking the Add Tag button, enter or select Key, Value values
Table. Microsoft SQL Server (DBaaS) Additional Information Input Items
Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
Once creation is complete, check the created resource on the Resource List page.
Microsoft SQL Server(DBaaS) Check detailed information
The Microsoft SQL Server (DBaaS) service allows you to view and edit the full list of resources and detailed information. Microsoft SQL Server(DBaaS) Details The page consists of Details, Secondary(DR) Information, Tags, Activity History tabs, and for databases with a configured Secondary(DR), an additional Secondary(DR) Information tab is provided.
To view detailed information about the Microsoft SQL Server (DBaaS) service, follow these steps.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List Click the resource to view detailed information on the page. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Microsoft SQL Server(DBaaS) Details At the top of the page, status information and details about additional features are displayed.
Category
Detailed description
Cluster status
Cluster status with DB installed
Creating: Cluster is being created
Editing: Cluster is transitioning to an operational state
Error: Cluster encountered a failure while performing a task
If this persists, contact the administrator
Failed: Cluster failed during creation
Restarting: Cluster is being restarted
Running: Cluster is operating normally
Starting: Cluster is being started
Stopped: Cluster is stopped
Stopping: Cluster is stopping
Synchronizing: Cluster is being synchronized
Terminating: Cluster is being terminated
Unknown: Cluster status is unknown
If this persists, contact the administrator
Upgrading: Cluster is being upgraded
Cluster control
Buttons to change the cluster state
Start: Start a stopped cluster
Stop: Stop a running cluster
Restart: Restart a running cluster
Switch-Over: Switch a standby cluster to Active
View more add-ons
Cluster management buttons
Service status synchronization: Retrieve real-time DB service status
Backup history: If backup is configured, verify successful execution and view the backup history
Database recovery: Restore the DB based on a specific point in time
Parameter management: View and modify DB configuration parameters
Secondary configuration: Configure a read‑only cluster as Secondary (DR)
Secondary configuration (Other-Region): Configure a disaster‑recovery Secondary in another region; if the account has no region to configure, the button is disabled
DB user management: View and manage DB accounts (users) registered in the DB
Export DB Log: Logs stored via Audit settings can be exported to the user’s Object Storage
Primary promotion: Promote a Secondary (DR) to Primary to ensure DB service continuity
Service cancellation
Cancel Service button
Table. Microsoft SQL Server (DBaaS) status information and additional features
Detailed Information
Microsoft SQL Server (DBaaS) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.
Category
Detailed description
Server Information
Server information configured in this cluster
Category: Server type (Primary, Secondary)
Server name: Server name
IP Port: Server IP and port
Availability Zone: Server creation location
Status: Server status
service
Service name
Resource Type
Resource Type
SRN
Unique resource ID in Samsung Cloud Platform
In the DB service, it refers to the cluster SRN
Resource Name
Resource name
In the DB service, it means the cluster name
Resource ID
Unique resource ID in the service
Constructor
User who created the service
Creation Date/Time
Service creation date and time
Modifier
User who edited the service information
Modification date and time
Date and time the service information was modified
Image version
Installed DB image and version information
If a version upgrade is required, click the Edit icon to configure
If log collection configuration is required, click the Edit icon next to Log Collection to configure
time zone
Standard time zone used by the database
DB Collation
Data sorting method
AD information
Server AD information
VIP
Virtual IP information
can be checked only when high availability is configured
Network
Network information (VPC, Subnet) of the installed DB
IP access control
Service access policy configuration
If you need to add or remove an IP, click the Edit icon to configure
Primary & Secondary
Primary/Secondary server type, base OS, additional Disk information
If you need to modify the server type, click the Edit icon next to the server type to set it. See the server type modification procedure in 서버 타입 변경하기
Modifying the server type requires a server reboot
If you need to expand storage, click the Edit icon next to the storage capacity to expand it. See the storage expansion procedure in 스토리지 증설하기
If you need to add storage, click the Add Disk button next to the additional Disk to add it. See the storage addition procedure in 스토리지 추가하기
Table. Microsoft SQL Server (DBaaS) Database detailed information items
Secondary(DR) information
Secondary(DR) Information tab is enabled only when Secondary(DR) is configured. Secondary(DR) Information Through the tab, you can view the Master cluster name, the number of Secondary(DR), and the status of Secondary(DR).
Category
Detailed description
Primary information
Name of the primary cluster
Secondary (DR) count
Number of Secondary (DR) created in the Primary cluster
Secondary(DR) status
Status of the Secondary (DR) server created in the Primary cluster
Server name, status query, status details, status check time, and region can be viewed
To view the Secondary (DR) status, click the Status Query button
While the query is in progress, the cluster remains in Synchronizing state, and once the query completes, the cluster changes to Running state
Table. Microsoft SQL Server(DBaaS) Secondary(DR) Detailed Information Tab Items
Tag
Microsoft SQL Server (DBaaS) List page allows you to view the tag information of the selected resource, and to add, modify, or delete it.
Category
Detailed description
Tag list
Tag list
You can view the Key and Value information of the tag
Up to 50 tags can be added per resource
When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Microsoft SQL Server(DBaaS) tag tab item
Job History
Microsoft SQL Server(DBaaS) List You can view the operation history of the selected resource on the page.
Table. Microsoft SQL Server(DBaaS) operation history tab detailed information items
Managing Microsoft SQL Server (DBaaS) Resources
If you need to change the existing configuration options of a created Microsoft SQL Server (DBaaS) resource, recover it, or manage parameters, you can perform the tasks on the Microsoft SQL Server(DBaaS) Details page.
Operation Control
If changes occur to a running Microsoft SQL Server (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch between Primary and Secondary servers via a switch‑over.
To control the operation of Microsoft SQL Server (DBaaS), follow the steps below.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
Microsoft SQL Server(DBaaS) List On the page, click the resource to control its operation. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Check the status of Microsoft SQL Server(DBaaS) and complete the change using the control button below.
Start: DB service is installed on the server and the DB service is running (Running).
Stop: The server where the DB service is installed and the DB service will be stopped (Stopped).
Restart: Only the DB service will be restarted.
Switch Over: You can switch the DB’s Primary server and Secondary server.
Synchronize service status
You can synchronize the real-time service status of Microsoft SQL Server (DBaaS).
To view the service status of Microsoft SQL Server(DBaaS), follow the steps below.
Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
On the Microsoft SQL Server(DBaaS) List page, click the resource to view the service status. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
Once the query completes, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
The configuration can be changed.
To change the server type, follow these steps.
Caution
If you modify the server type, a server restart is required. * Please verify separately any software license modifications or software settings and their implementation due to server specification changes.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List On the page, click the resource to change the server type. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the Edit icon for the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
Edit Server Type In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. In a redundant DB setup, all redundant servers are added simultaneously.
To add storage capacity, follow the steps below.
Caution
It is applied in the same way as the Storage type selected when creating the service.
For a high‑availability configured DB, adding storage is applied simultaneously to the storage of the Primary DB and the Secondary DB.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding Storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB setup, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server(DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
On the Microsoft SQL Server(DBaaS) List page, click the resource to change the server type. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the Edit icon for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage popup opens.
Edit Additional Storage After entering the expansion capacity in the popup window, click the Confirm button.
Terminate Microsoft SQL Server(DBaaS)
You can cancel unused Microsoft SQL Server (DBaaS) to reduce operating costs. However, terminating the service may cause the currently operating service to stop immediately, so you should proceed with the termination only after fully considering the impact of any service interruption.
Caution
If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel Microsoft SQL Server(DBaaS), follow the steps below.
Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List Select the resource to cancel on the page, and click the Cancel Service button.
After termination is complete, verify that the resource has been terminated on the Microsoft SQL Server(DBaaS) list page.
5.2.1 - Managing DB Services
Users can manage Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console.
Managing Database
For the Microsoft SQL Server Enterprise edition, you can add a new database. You can add up to 100 per cluster.
Add Database
To add a Database, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List On the page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Add button for the Database name field. 4. Add Database The popup window opens.
Add Database In the popup window, click the + button to enter the database name and select a drive, then click the Confirm button.
Delete Database
To delete the Database, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List On the page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Edit button for the Database name field. 4. Delete Additional Database A popup window opens.
Delete added Database In the request popup, check the Database you want to delete and click the Delete button. 5. Database Delete The popup window opens.
Delete Database In the popup window, after entering the name of the Database you want to delete, click the Confirm button.
Managing Parameters
Provides a feature that allows you to easily view and modify database configuration parameters.
View Parameter
To view configuration parameters, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to view or modify parameters. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
In the Parameter Management popup, click the Search button. 5. The Lookup Notification popup window opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
Edit Parameter
To modify the configuration parameters, follow the steps below.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List Click the resource on the page whose parameters you want to view and modify. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management popup window opens.
Parameter Management In the popup window, click the Search button. 5. View Notification A popup window opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
If editing is required, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
When the input is complete, click the Done button.
Manage DB Users
Provides functionality to view and manage DB user information.
Query DB Users
To look up DB users, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
Microsoft SQL Server(DBaaS) List page, click the resource whose DB users you want to view. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the More button and then click the DB User Management button. 4. Navigate to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
Changing DB User Status
To change the status of the retrieved DB user, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List page, click the resource for which you want to edit the DB user. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the More button, then click the DB User Management button. 4. Go to the DB User Management page.
On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
If modification is required, click the Edit button, and change the status area value or enter remarks.
When the input is complete, click the Complete button.
Modify Audit Settings
You can modify the Audit log storage settings for Microsoft SQL Server (DBaaS).
To change the Audit log storage settings of Microsoft SQL Server(DBaaS), follow the steps below.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
Microsoft SQL Server (DBaaS) List Click the resource to view the service status on this page. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Edit icon of Audit Settings at the bottom of the detailed information. 4. Audit Settings Modification The popup window opens.
Audit Settings Modification After modifying the usage in the popup window, click the Confirm button.
When Use is selected, the Audit log feature is enabled. * Enabling audit logging may degrade database performance.
If you disable usage, the Audit log storage file will be deleted. * Back up the Audit log file separately before disabling.
Export DB Log
Supports exporting log data that requires long-term retention among audit (Audit) logs to Object Storage. Users can directly configure the log types that need to be stored, the destination Bucket for export, and the log export interval. Copies logs to the specified Object Storage for retention according to the configured criteria.
Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for the long term.
안내
To use the DB Log export feature, you need to create an Object Storage. * To create Object Storage, please refer to the Object Storage 사용자 가이드.
Please be sure to verify the expiration date and time of the authentication key. * If the authentication key expires, logs will not be stored in the bucket.
Please ensure that authentication key information is not exposed to external parties.
Setting the DB Log export mode
To set the DB Log export mode, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to export the DB Log. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the More button, then click the Export DB Log button. 4. Export DB Log Go to the page.
Click the Register button on the DB Log Export page. 5. Go to the DB Log Export Registration page.
On the DB Log Export Registration page, after entering the required information, click the 완료 button.
Category
Required
Detailed description
Log type
Required
Log type to be saved
Save bucket name
Required
Object Storage bucket name to be saved
Authentication key > Access key
Required
Access key for accessing the Object Storage you want to store
Authentication key > Secret key
Required
Secret key for accessing the Object Storage you want to store
File creation cycle
Required
File creation frequency in Object Storage
Whether to delete the original log
Selection
Whether to delete the original logs when exporting to Object Storage
Table. Microsoft SQL Server (DBaaS) DB Log Export Configuration Items
Manage DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to manage DB Log export. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the More button, then click the DB Log Export button. 4. Export DB Log Go to the page.
On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Terminate buttons.
Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
Edit: Modify the DB Log export mode setting.
Cancel: Cancel the DB Log export mode setting.
Minor version upgrade
Provides version upgrade functionality due to feature enhancements and security patches. Only minor version upgrades are supported within the same major version.
Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.
It is recommended to perform an immediate backup in advance to prepare for any issues that may arise during the upgrade process. * If not, a failure may occur and some data may not be recoverable.
In a DB configured with Secondary(DR), the Primary DB version cannot be higher than the Secondary(DR) version. * First check the version of the Secondary (DR), and if necessary, perform a version upgrade.
The backed-up data is automatically deleted after the version upgrade is completed.
To perform a minor version upgrade, follow the steps below.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List page, click the resource to upgrade the version. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Edit button of the Image version item. 4. Version Upgrade A popup window opens.
Version Upgrade In the popup, select the updated version and whether to enable backup, then click the Confirm button.
Version Upgrade Notification Click the OK button in the popup window.
5.2.2 - Backing up and restoring the DB
Users can configure backups of Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Microsoft SQL Server(DBaaS) Backup
Microsoft SQL Server (DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
For instructions on configuring backup settings for Microsoft SQL Server (DBaaS), see the Microsoft SQL Server(DBaaS) 생성하기 guide.
To modify the backup settings of the created resource, follow the steps below.
Caution
When a backup is configured, it runs at the designated time after the set schedule, and additional fees are incurred based on the backup volume.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List page, click the resource you want to configure backup for. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
If you want to stop the backup setting, uncheck Use in the Backup Settings popup window and authenticate via the logged-in user’s mobile phone. Once user authentication is completed, the backup setting is disabled and backup execution stops.
Perform immediate backup
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
To perform an immediate backup, follow these steps.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
Microsoft SQL Server(DBaaS) List page, click the resource to perform an immediate backup. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the Immediate Backup button of the backup item. 4. Immediate backup settings popup window opens.
In the Immediate Backup Settings popup, click the Confirm button.
Check backup history
안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, refer to 알림 정책 생성하기.
To view the backup history, follow these steps.
Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
Microsoft SQL Server(DBaaS) List Click the resource to view the backup history on the page. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Backup History Click the button. 4. Backup History The popup window opens.
Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
On the Microsoft SQL Server(DBaaS) List page, click the resource to view the backup history. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
When user authentication is completed, the backup file will be deleted.
Recover Microsoft SQL Server(DBaaS)
If a failure or data loss requires restoration from a backup file, recovery can be performed based on a specific point in time using the recovery feature. When you perform a Microsoft SQL Server(DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds using the database’s configuration information and data.
To restore Microsoft SQL Server(DBaaS), follow these steps.
All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Go to the Microsoft SQL Server(DBaaS) List page.
Microsoft SQL Server(DBaaS) Resource On the list page, click the resource you want to recover. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the Database Recovery button. 4. Database Recovery Navigate to the page.
After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category
required status
Detailed description
Recovery type
Required
Set the point in time the user wants to recover
Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
Custom point: Recover to a user‑desired point within the range of recoverable backup times. The recoverable period depends on the Archive backup schedule setting, allowing recovery to 1 hour/30 minutes/10 minutes/5 minutes before the current time from the initial backup start point. Select the date and time to back up
Server name prefix
Required
Recovery DB server name
must start with a lowercase English letter and may include lowercase letters, numbers, and special characters (-) using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters and between 2~16 characters between 2~16 characters between 2~16 characters 2~ Recovery DB server name
in English English English
Cluster name
Required
Recovery DB cluster name
Enter using English letters, 3 ~ 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Recovery DB server type
Standard: standard specifications commonly used
High Capacity: large-capacity server of 24 vCore or more
Service Type > Planned Compute
Selection
Status of resources with Planned Compute set
In Use: Number of resources with Planned Compute that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Go to the Planned Compute service application page
Applied identically with the storage type set in the original cluster
Enter capacity as a multiple of 8 within the range 16 to 5,120
Additional: Data storage area
Applied identically with the storage type set in the original cluster
In the recovery DB, only DATA and TEMP purposes can be added
After selecting Use, enter the storage purpose and capacity
To add storage, click the Add button; to delete, click the x button
Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Use AD
Selection
Preconfigured AD (Active Directory) server usage setting
AD Server ID: AD User ID
AD Server Password: User Password
Database username
Required
Database username
Apply the same username set in the original cluster
Database Port number
Required
Database Port number
Apply the same Port number as configured in the original cluster
IP access control
Selection
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
Enter the IP 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 an entered IP, click the x button next to the IP
Maintenance period
Selection
DB maintenance window
If you select Use, you can set the day of the week, start time, and duration
The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch work within that period is performed directly by the user.
We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform within the window.
tag
Selection
Add Tag
After clicking the Add Tag button, enter or select Key, Value values
Table. Microsoft SQL Server (DBaaS) recovery configuration items
5.2.3 - Add Secondary
The user can enter the required information for Secondary through the Samsung Cloud Platform Console and create the service using detailed options.
Add Secondary
Through secondary configuration, you can create replica servers for read‑only or disaster‑recovery purposes. To add a Secondary, it must be created with HA redundancy configuration and Enterprise Edition, and the backup feature must be enabled.
Information
To configure a disaster recovery Secondary, please create it through Secondary Configuration (Other Region).
To set up Secondary, follow these steps.
Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
Microsoft SQL Server(DBaaS) List On the page, click the resource to configure Secondary. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the Add Secondary button. 4. Go to the Secondary Add page.
After entering information in the Secondary configuration area, click the Create button.
Category
Required status
Detailed description
Region
Required
Region to configure Secondary (DR)
Secondary configuration (Other Region) shown only when selected
Secondary number
Required
Number of Secondary to configure
Only one can be configured per cluster
Secondary name
Required
Secondary server name
must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (-) be entered with 3 ~ 15 characters
The entered Secondary name is displayed as the cluster name in the list
Service Type > Server Type
Required
Secondary server type
Apply the same as the server type set in the source DB
Service Type > Planned Compute
Selection
Status of resources with Planned Compute configured
In Use: Number of resources with Planned Compute configured that are currently in use
Configured: Number of resources with Planned Compute configured
Coverage Preview: Amount applied by Planned Compute per resource
Create Planned Compute Service: Go to the Planned Compute service application page
Network settings where the servers created by the service are installed
applied identically to the network settings configured in the original DB
Network > Server Settings
Required
Network settings for servers created in the service
Select when you want to apply different settings per installed server
Apply the same as the network settings configured in the original DB
When setting per server 10.10.10.0/24 enter an IP address within the range
License
Required
SQL Server License Key
Enter the issued license key.
If the entered license key is invalid, the service may not be created.
AD(Active Directory)
Selection
Enter AD information entered when creating the service
AD Server ID: AD User ID
AD Server Password: User Password
Table. Microsoft SQL Server (DBaaS) Secondary configuration items
Promoting Secondary (DR) to Primary
You can promote a configured Secondary (DR) to Primary.
Caution
When promoted to Primary, synchronization with the existing Cluster is halted.
To promote Secondary(DR) to Primary, follow these steps.
All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
Microsoft SQL Server(DBaaS) List On the page, click the resource to promote to Primary. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
Click the More button, then click the Primary Promotion button. 4. Primary Promotion Notification The popup window opens.
Primary Promotion Notification In the popup window, click the Confirm button.
5.2.4 - Microsoft SQL Server(DBaaS) server connection
Scenario Overview
Microsoft SQL Server(DBaaS) server connection The scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to Microsoft SQL Server (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Figure. Microsoft SQL Server(DBaaS) server connection architecture
Scenario components
You can build the scenario using the following services.
Service group
service
Detailed description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Networking
VPC > Subnet
A service that lets users segment the network within a VPC to match their purpose and scale
Networking
VPC > Public IP
A service that reserves a public IP and allocates and releases it to Compute resources.
Networking
VPC > Internet Gateway
A service that connects VPC resources to the Internet
Networking
Security Group
Virtual firewall that controls server traffic
Database
Microsoft SQL Server(DBaaS)
A service that easily creates and manages Microsoft SQL Server in a web environment
Compute
Virtual Server
Virtual server optimized for cloud computing
Compute
Virtual Server > Keypair
Encryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
The All Open(Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
All Services > Networking > FirewallClick the menu. 1. Navigate to the Firewall’s Service Home page.
On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
On the detail information page, click the Rules tab. 4. Go to the Rules tab.
Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address
Destination address
Protocol
Port
Operation
Direction
Explanation
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. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide provides instructions on how to connect using SSMS (Microsoft SQL Server Management Studio). Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB client program (SSMS) on the Bastion host
Go to the official Microsoft SQL Server page and download the SSMS program.
Add a 2nd‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For more details, see Microsoft SQL Server(DBaaS) 서버 타입.
Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
Add HDD, HDD_KMS type to the Block Storage type
2025.02.27
NEWMicrosoft SQL Server(DBaaS) service official version release
A Microsoft SQL Server (DBaaS) service that enables easy creation and management of Microsoft SQL Server in a web environment has been launched.
6 - CacheStore(DBaaS)
6.1 - Overview
Service Overview
CacheStore (DBaaS) is a service that provides the in‑memory data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that automates the installation of Redis OSS and valkey through a web-based console and performs management functions for operation.
CacheStore(DBaaS) provides a Sentinel architecture composed of a Master server that performs read/write operations and read‑only Replica servers that replicate the Master data. Sentinel checks the status of DB servers where the engine is installed, and if a failure occurs on the Master server, it automatically fails over the Replica servers to the Master server. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, allowing data recovery based on the backup point.
Figure. CacheStore(DBaaS) Architecture
Provided features
CacheStore (DBaaS) provides the following features.
Auto Provisioning: UI allows installation and configuration of Database (DB), and a redundant configuration with a Sentinel-based Single Master server and Replica servers (1 or 2) is possible.
Operation Control Feature: Provides a function that controls the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When configured for high availability (HA), you can switch the Active-Standby servers using a switch‑over.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup time window and storage location can be set by the user, and additional charges are incurred based on the backup size. * It also provides a recovery function for backed‑up data, so when the user initiates a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user.
Parameter Management: It is possible to modify DB configuration parameters related to performance improvement and security.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
Minor version upgrade: Minor version upgrades can be performed within the same Major version to apply some feature improvements and security patches.
Components
CacheStore (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it according to the scale of the service they wish to configure.
Engine version
The engine versions supported by CacheStore (DBaaS) are as follows.
Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
EoS Date (Samsung Cloud Plaform New Creation Stop Date)
EoTS date (Community technical support end date)
Redis OSS Sentinel
7.2.11
2026-07-16
2029-12-01
Redis OSS Sentinel
7.2.14
2029-06 (예정)
2029-12-01
valkey Sentinel
8.1.4
2026-07-16
TBD
valkey Sentinel
8.1.8
TBD
TBD
valkey Sentinel
9.0.4
TBD
TBD
Table. Engine versions provided by CacheStore (DBaaS)
Server type
The server types supported by CacheStore (DBaaS) are as follows.
For detailed information about the server types provided by CacheStore(DBaaS), see CacheStore(DBaaS) 서버 타입.
Standard redis1v2m4
Category
example
Detailed description
Server type
Standard
Provided server type
Standard: Standard configuration (vCPU, Memory) commonly used
Server specifications
redis1
Provided server specifications
redis1: Standard specifications (vCPU, Memory) commonly used
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. CacheStore (DBaaS) server type components
Preliminary Service
This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.
A service that provides an isolated virtual network in a cloud environment
Table. CacheStore (DBaaS) Pre-service
6.1.1 - Server type
CacheStore(DBaaS) server type
CacheStore (DBaaS) offers server types configured with various combinations such as CPU, Memory, and Network Bandwidth.
When creating a CacheStore (DBaaS), Redis is installed according to the server type selected for the intended purpose.
Reference
The server types offered may vary depending on the region and AZ.
The server types supported by CacheStore (DBaaS) are as follows.
Standard redis1v2m4
Category
example
Detailed description
Server type
Standard
Provided server type classification
Standard: composed of the commonly used standard specifications (vCPU, Memory)
Server specifications
redis1
Provided server type classification and generation
redis: means a standard specification, and 1 indicates the generation
Server specifications
v2
Number of vCores
v2: 2 virtual cores
Server specifications
m4
Memory capacity
m4: 4GB Memory
Table. CacheStore (DBaaS) server type format
redis1 server type
The redis1 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
redis1v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
redis1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
redis1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
redis1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
redis1v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
redis1v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
redis1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
redis1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
redis1v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
redis1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
redis1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
redis1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
redis1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
redis1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
redis1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
redis1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
redis1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. CacheStore (DBaaS) server type specifications - redis1 server type
redis2 server type
The redis2 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
redis2v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
redis2v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
redis2v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
redis2v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
redis2v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
redis2v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
redis2v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
redis2v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
redis2v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
redis2v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
redis2v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
redis2v96m96
6 vCore
96 GB
Up to 10 Gbps
Standard
redis2v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
redis2v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
redis2v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
redis2v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
redis2v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - redis2 server type
redis3 server type
The redis3 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
redis3v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
redis3v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
redis3v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
redis3v16
2 vCore
16 GB
Up to 10 Gbps
Standard
redis3v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
redis3v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
redis3v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
redis3v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
redis3v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
redis3v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
redis3v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
redis3v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
redis3v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
redis3v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
redis3v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
redis3v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
redis3v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. CacheStore (DBaaS) server type specifications - redis3 server type
css1 server type
The css1 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
css1v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
css1v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
css1v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
css1v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
css1v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
css1v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
css1v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
css1v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
css1v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
css1v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
css1v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
css1v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
css1v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
css1v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
css1v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
css1v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
css1v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - css1 server type
css2 server type
CacheStore(DBaaS)’s css2 server type is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
css2v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
css2v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
css2v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
css2v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
css2v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
css2v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
css2v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
css2v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
css2v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
css2v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
css2v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
css2v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
css2v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
css2v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
css2v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
css2v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
css2v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - css2 server type
css3 server type
The css3 server type of CacheStore(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps
Category
Server type
vCPU
Memory
Network Bandwidth
Standard
css3v1m2
1 vCore
2 GB
Up to 10 Gbps
Standard
css3v2m4
2 vCore
4 GB
Up to 10 Gbps
Standard
css3v2m8
2 vCore
8 GB
Up to 10 Gbps
Standard
css3v2m16
2 vCore
16 GB
Up to 10 Gbps
Standard
css3v2m24
2 vCore
24 GB
Up to 10 Gbps
Standard
css3v4m8
4 vCore
8 GB
Up to 10 Gbps
Standard
css3v4m16
4 vCore
16 GB
Up to 10 Gbps
Standard
css3v4m32
4 vCore
32 GB
Up to 10 Gbps
Standard
css3v4m48
4 vCore
48 GB
Up to 10 Gbps
Standard
css3v4m64
4 vCore
64 GB
Up to 10 Gbps
Standard
css3v6m72
6 vCore
72 GB
Up to 10 Gbps
Standard
css3v6m96
6 vCore
96 GB
Up to 10 Gbps
Standard
css3v8m128
8 vCore
128 GB
Up to 10 Gbps
Standard
css3v10m160
10 vCore
160 GB
Up to 10 Gbps
Standard
css3v12m192
12 vCore
192 GB
Up to 12.5 Gbps
Standard
css3v14m224
14 vCore
224 GB
Up to 12.5 Gbps
Standard
css3v16m256
16 vCore
256 GB
Up to 12.5 Gbps
Table. CacheStore(DBaaS) server type specifications - css3 server type
6.1.2 - Monitoring metrics
Cloud Monitoring Service Termination Notice
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026. After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
During the parallel operation period, we must prepare for the Servicewatch transition. * Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
Console menu termination (September 2026 service improvement work)
You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
Service termination (service improvement work in November 2026)
All services of Cloud Monitoring, including the API, will be permanently discontinued.
After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
CacheStore(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for CacheStore (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
Number of keys skipped in the active defragmentation removal process
cnt
Active Defragmentationd [Hits]
Number of value reallocations performed by the active defragmentation removal process
cnt
Active Defragmentations [Miss]
Count of value reallocations interrupted by the active defragmentation removal process
cnt
Allocated Bytes [OS]
Number of bytes allocated by CacheStore (DBaaS) and recognized by the operating system (resident set size)
bytes
Allocated Bytes [Redis]
Total bytes allocated by CacheStore (DBaaS)
bytes
AOF Buffer Size
AOF buffer size
bytes
AOF File Size [Current]
AOF current file size
bytes
AOF File Size [Lastest Startup]
AOF file size on recent start or rewrite
bytes
AOF Rewrite Buffer Size
AOF rewrite buffer size
bytes
AOF Rewrite Current Time
If applicable, the time of the ongoing AOF rewrite operation
sec
AOF Rewrite Last Time
Final AOF rewrite time
sec
Calls
Number of calls that reached command execution (not rejected)
cnt
Changes [Last Saved]
Number of changes after the final dump
cnt
Client Output Buffer [MAX]
Longest output list among current client connections
cnt
Clients [Sentinel]
Number of client connections (Sentinel)
cnt
Connected Slaves
Number of connected slaves
cnt
Connections [Blocked]
Number of clients pending on blocking calls (BLPOP, BRPOP, BRPOPLPUSH)
cnt
Connections [Current]
Number of client connections (excluding slave connections)
cnt
Copy On Write Allocated Size [AOF]
COW allocation size during final RBD save operation
bytes
Copy On Write Allocated Size [RDB]
COW allocation size during the final RBD save operation
bytes
CPU Time [Average]
Average CPU time used per command execution
cnt
CPU Time [Total]
Total CPU time used by these commands
usec
CPU Usage [System Process]
System CPU usage by background processes
%
CPU Usage [System]
System CPU usage on the CacheStore (DBaaS) server
%
CPU Usage [User Process]
User CPU usage used by background processes
%
CPU Usage [User]
System CPU usage by background processes
%
Dataset Used
Dataset size
bytes
Disk Used
datadir usage
MB
Evicted Keys
Number of evicted keys caused by the maxmemory limit
cnt
Fsyncs [Delayed]
Delayed fsync counter
cnt
Fsyncs [Pending]
Number of pending fsync operations in the background I/O queue
cnt
Full Resyncs
Number of full resynchronizations with the slave
cnt
Keys [Expired]
Total number of key expiration events
cnt
Keys [Keyspace]
Number of keys in the key space
cnt
Lastest Fork Duration Time
Recent fork (fork) operation time
usec
Lookup Keys [Hit]
Number of successful key lookups in the dictionary
cnt
Lookup Keys [Miss]
Number of failed key lookups in the main dictionary
cnt
Lua Engine Memory Used
Memory used by the Lua engine
bytes
Master Last Interaction Time Ago
Time elapsed since the final interaction with the master
sec
Master Last Interaction Time Ago [Sync]
Time elapsed since the final interaction with the master
sec
Master Offset
Current replication offset of the server
pid
Master Second Offset
Offset until the replication ID is accepted
pid
Master Sync Left Bytes
Remaining bytes before synchronization completes
bytes
Memory Fragmentation Rate
Ratio of used_memory_rss to used_memory
%
Memory Fragmentation Rate [Allocator]
Fragmentation ratio
%
Memory Fragmentation Used
Bytes between used_memory_rss and used_memory
bytes
Memory Fragmentation Used [Allocator]
resident byte
bytes
Memory Max Value
Memory limit
bytes
Memory Resident [Allocator]
resident memory
bytes
Memory RSS Rate [Allocator]
Resident ratio
%
Memory Used [Active]
Active memory
bytes
Memory Used [Allocated]
Allocated memory
bytes
Memory Used [Resident]
Resident byte
bytes
Network In Bytes [Total]
Total network input (bytes)
bytes
Network Out Bytes [Total]
Total network output (bytes)
bytes
Network Read Rate
Network read speed (KB/sec)
cnt
Network Write Rate
Network write speed (KB/sec)
cnt
Partial Resync Requests [Accepted]
Number of accepted partial resynchronization requests
cnt
Partial Resync Requests [Denied]
Number of rejected partial resynchronization requests
cnt
Peak Memory Consumed
Maximum memory used by CacheStore (DBaaS)
bytes
Processed Commands
Number of commands processed per second
cnt
Processed Commands [Total]
Total number of processed commands
cnt
Pub/Sub Channels
Global count of pub/sub channels with client subscriptions
cnt
Pub/Sub Patterns
Global count of publish/subscribe patterns with client subscriptions
cnt
RDB Saved Duration Time [Current]
If applicable, the time of the ongoing RDB save operation
sec
RDB Saved Duration Time [Last]
Final RDB save operation time
sec
Received Connections [Total]
Total number of received connections
cnt
Rejected Connections [Total]
Total number of rejected connections
cnt
Replication Backlog Actove Count
Replication backlog activation flag
cnt
Replication Backlog Master Offset
Master offset of the replication backlog buffer
cnt
Replication Backlog Size
Data size of the replication backlog buffer
bytes
Replication Backlog Size [Total]
Total size of the replication backlog buffer
bytes
Slave Priority
Server priority as a fault remediation target
cnt
Slave Replication Offset
Replication offset of the slave server
pid
Slow Operations
Number of slow tasks
cnt
Sockets [MIGRATE]
Number of sockets opened for migration
cnt
Tracked Keys [Expiry]
Number of keys tracked for expiration (applicable only to writable slaves)
cnt
Instance Status [PID]
redis-server process PID
pid
Sentinel Status [PID]
sentinel process PID
pid
Table. CacheStore (DBaaS) Monitoring Metrics
6.1.3 - ServiceWatch metric
CacheStore (DBaaS) sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at 1‑minute intervals.
Reference
For instructions on how to view metrics in ServiceWatch, refer to the ServiceWatch guide.
Basic Metrics
The following are the basic metrics for the namespace CacheStore(DBaaS).
The indicators whose names are shown in bold below are the key metrics selected from the basic metrics provided by CacheStore(DBaaS).
The key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.
Each metric provides guidance in the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values shown in bold are the primary statistics. In the service dashboard, you can view key metrics through primary statistical values.
OS Basic Metrics
Classification
Performance items
unit
Detailed description
meaningful statistics
CPU
CPU Usage
Percent
CPU usage
Total
Average
Maximum
Minimum
Disk
Disk Usage
Percent
Disk usage
Total
Average
Maximum
Minimum
Disk
Disk Write Bytes
Bytes/Second
Write capacity (bytes/second) on block device
Total
Average
Maximum
Minimum
Disk
Disk Read Bytes
Bytes/Second
Read throughput from block device (bytes/second)
Total
Average
Maximum
Minimum
Disk
Disk Write Requests
Count/Second
Number of write requests on block device (requests per second)
Total
Average
Maximum
Minimum
Disk
Disk Read Requests
Count/Second
Number of read requests on block device (requests per second)
Total
Average
Maximum
Minimum
Disk
Average Disk I/O Queue Size
None
Average queue length of requests issued to the block device
Total
Average
Maximum
Minimum
Disk
Disk I/O Utilization
Percent
The proportion of time the block device actually spent processing I/O operations
Total
Average
Maximum
Minimum
Memory
Memory Usage
Percent
Memory usage
Total
Average
Maximum
Minimum
Memory
Swap Out Bytes
Bytes/Second
Amount of data exported from memory to swap area (bytes/second)
Total
Average
Maximum
Minimum
Memory
Swap Used Bytes
Bytes
Current swap space size
Total
Average
Maximum
Minimum
Memory
Swap Cached Usage
Percent
Cached swap usage rate
Total
Average
Maximum
Minimum
Memory
Swap Total Bytes
Bytes
Total swap space size configured on the system
Total
Average
Maximum
Minimum
Memory
Swap In Bytes
Bytes/Second
Amount read from swap area into memory (bytes/second)
Total
Average
Maximum
Minimum
Memory
Swap Usage
Percent
Current usage ratio relative to total swap space
Total
Average
Maximum
Minimum
Memory
Swap Cached Bytes
Bytes
Size of pages that have been restored to memory but still have a copy in the swap area
Total
Average
Maximum
Minimum
Memory
Swap Free Bytes
Bytes
Size of unused remaining swap space
Total
Average
Maximum
Minimum
Network
Network In Bytes
Bytes/Second
Received capacity (bytes/second) on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Bytes
Bytes/Second
Transmitted capacity (bytes/second) on the network interface
Total
Average
Maximum
Minimum
Network
TCP Connections
Count/Second
Total number of TCP connections currently properly established
Total
Average
Maximum
Minimum
Network
Network In Packets
Count
Number of packets received on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Packets
Count
Number of packets transmitted on the network interface
Total
Average
Maximum
Minimum
Network
Network In Dropped
Count
Number of packet drops received on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Dropped
Count
Number of packet drops transmitted from the network interface
Total
Average
Maximum
Minimum
Network
Network In Errors
Count
Number of packet errors received on the network interface
Total
Average
Maximum
Minimum
Network
Network Out Errors
Count
Number of packet errors transmitted from the network interface
Total
Average
Maximum
Minimum
OS
OS Uptime
Seconds
Time elapsed (seconds) since the system was last booted
Total
Average
Maximum
Minimum
Table. OS basic metrics
CacheStore(DBaaS) basic metrics
Classification
Performance items
unit
Detailed description
meaningful statistics
Client
blocked clients
Count
client waiting due to a blocking call
Total
Average
Maximum
Minimum
Client
connected clients
Count
clients connected to Redis
Total
Average
Max
Min
Client
connected replicas
Count
Number of Replicas connected to the Master
Total
Average
Maximum
Minimum
Command
average command counts
Count/Minute
Average number of Redis commands processed per minute
Total
Average
Maximum
Minimum
keys
keys per db
Count
Number of registered keys per DB
Total
Average
Maximum
Minimum
keys
expired keys per db
Count
Number of expired keys registered per DB
Total
Average
Maximum
Minimum
keys
evicted keys
Count/Minute
Number of evicted keys per minute in Redis memory
Total
Average
Maximum
Minimum
Memory
keyspace hits on memory
Count/Minute
Number of keys retrieved from Redis memory per minute
Total
Average
Maximum
Minimum
Memory
keyspace_misses on memory
Count/Minute
Number of keys that failed to be retrieved from Redis memory per minute
Total
Average
Maximum
Minimum
Memory
memory max bytes
Count
Maximum memory bytes available in Redis
Total
Average
Maximum
Minimum
Memory
current redis memory used bytes
Count
Current memory bytes used by Redis
Total
Average
Maximum
Minimum
Memory
current allocated redis memory
Count
Current OS-allocated Redis memory size
Total
Average
Maximum
Minimum
Memory
redis_up
Count
Redis process On/Off
Total
Average
Maximum
Minimum
Memory
master replication offset
Count
Replication offset location for the Replica target within the Master server
Total
Average
Maximum
Minimum
Memory
aof buffer bytes
Count
The buffer size that Redis allocates to the AOF
Total
Average
Max
Min
Memory
Total client memory size
Count
Total size of the input/output buffer allocated to the client
Total
Average
Maximum
Minimum
Memory
Total replication buffer bytes
Count
Total buffer bytes allocated to Replication
Total
Average
Maximum
Minimum
Memory
dataset bytes
Count
memory bytes used for user data
Total
Average
Maximum
Minimum
Memory
memory peak bytes
Count
Maximum memory usage of the Redis process, in bytes
Total
Average
Maximum
Minimum
Memory
network input bytes
Count/Minute
Network bytes received by redis in 1 minute
Total
Average
Maximum
Minimum
Memory
network output bytes
Count/Minute
Network bytes transmitted by redis in 1 minute
Total
Average
Maximum
Minimum
Memory
cached script number
Count
Number of cached scripts
Total
Average
Maximum
Minimum
Memory
function number
Count
Number of cached functions
Total
Average
Maximum
Minimum
Memory
library number
Count
Number of cached libraries
Total
Average
Maximum
Minimum
Memory
last bgsave duration
Count
Time taken to create the last bgsave
Total
Average
Maximum
Minimum
Memory
slowlog queue length
Count
Number of logs stored in the slowlog queue
Total
Average
Maximum
Minimum
Table. CacheStore (DBaaS) Basic Metrics
6.2 - How-to guides
Users can create the service by entering the required information for CacheStore(DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
Cloud Monitoring 서비스 종료 안내
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026. After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Resource-specific Monitoring Service Application Guide
New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently through the Cloud Monitoring service and the ServiceWatch service.
During the parallel operation period, we must prepare for the Servicewatch transition * Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (e.g. You must verify the event policy, etc., and perform tasks such as resetting the ServiceWatch service, and then complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
Console menu termination (September 2026 service improvement work)
You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
Service termination (November 2026 service improvement work)
All services of Cloud Monitoring, including the API, will be permanently discontinued.
After the service ends in November, Cloud Monitoring data cannot be viewed. * Be sure to complete the ServiceWatch migration within the parallel operation period**
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
CacheStore(DBaaS) Create
You can create and use the CacheStore (DBaaS) service in the Samsung Cloud Platform Console.
안내
Before creating the service, configure the VPC’s Subnet type as General.
If the subnet type is Local, the creation of the corresponding Database service is not possible.
When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
This service is provided on a Single-AZ basis.
To create a CacheStore (DBaaS), follow the steps below.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
Click the Create CacheStore(DBaaS) button on the Service Home page. 2. Go to the Create CacheStore (DBaaS) page.
On the Create CacheStore (DBaaS) page, enter the information required to create the service and select detailed options.
Select the required information in the Image and version selection area.
Category
Required status
Detailed description
Image version
Required
Provide version list of CacheStore (DBaaS)
Table. CacheStore (DBaaS) Image and version selection items
Enter or select the required information in the Service Information Input area.
Category
required status
Detailed description
Server name Prefix
Required
Server name where Redis/Valkey will be installed
must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters(-) with a length of 3 to 13 characters
Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name
Required
Cluster name where Redis/Valkey is installed
Enter using English letters, 3 to 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Server type for installing Redis/Valkey
Standard: the commonly used standard specification
For detailed information about the server types provided by CacheStore (DBaaS), refer to CacheStore(DBaaS) 서버 타입
Service Type > Planned Compute
Required
Status of resources with Planned Compute set
In Use: Number of resources with Planned Compute that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Go to the Planned Compute service application page
Block Storage settings used by the DB according to purpose
Basic OS: Area where the DB engine is installed
DATA: Storage area for table data, archive files, etc.
Select the storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
SSD: High‑performance general volume
HDD: General volume
SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
The configured storage type is also applied to additional storage
Enter the capacity as a multiple of 8 within the range 16 to 5,120
High availability
Selection
High Availability (HA) configuration option
When High Availability (HA) is enabled, it is provided as a Master-Replica configuration, and the Replica can be configured with 1 or 2 instances
Sentinel Port number: The port used for connecting to Sentinel
Enter a port for Master-Replica communication within the range 1200 to 65535
Replica count: Number of Replicas to configure
If 1 is selected, it is configured as Master-Replica-Sentinel
If 2 is selected, it is configured as Master-Replica-Replica, and Sentinel is automatically installed on the server where Redis is installed
Set the server type for Sentinel to the minimum specification
Network > Common Settings
Required
Network settings for servers created by the service
Select when you want to apply the same settings to all installed servers
Select a pre‑created VPC and Subnet
Each server’s IP is generated automatically
Network > Server-specific Settings
Required
Network settings where servers generated by the service are installed
Select when you want to apply different settings for each installed server
Select a pre‑created VPC, Subnet, IP, and Public NAT
Enter the IP for each server
The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more information, refer to Public IP 생성하기
IP access control
Selection
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
Enter the IP 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 IP.
Maintenance Period
Selection
CacheStore(DBaaS) maintenance window
If you select Use, you can set the day, start time, and duration
The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch work within that period must be performed directly by the user.
We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
Table. CacheStore (DBaaS) Service Configuration Items
Enter required database configuration information In this area, enter or select the required information.
Category
Required status
Detailed description
Backup
Selection
Backup usage
If you select Use, you can set the backup file retention period and backup start time
Backup files incur additional charges based on size
The file retention period can be set from 7 days to 35 days
The minute(s) when the backup runs is set randomly, and the backup end time cannot be set
Redis/Valkey Port number
Required
Port number required for connecting to Redis/Valkey
Enter a port within the range 1200 ~ 65535
Redis/Valkey password
Required
Password required when connecting to Redis/Valkey
Enter 8 ~ 30 characters, including English letters, numbers, and special characters ($“‘ excluded)
Check Redis/Valkey password
Required
Re-enter the same password
ServiceWatch log collection
Selection
ServiceWatch log collection status
Select Use to configure the ServiceWatch log collection feature
Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB.
When collected, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed.
To prevent exceeding 5 GB, direct deletion of log data or shortening the retention period is recommended.
Parameter
Required
Parameters to use with Redis/Valkey
View button to view detailed information of the parameters
Parameters can be modified after creation is complete, and a DB restart is required after any modifications
In the Additional Information Input area, enter or select the required information.
Required status
Detailed description
tag
Selection
Add Tag
Up to 50 can be added per resource
After clicking the Add Tag button, input or select Key, Value values
Table. CacheStore (DBaaS) additional information input fields
Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
When creation is complete, check the created resource on the Resource List page.
Check detailed information of CacheStore (DBaaS)
The CacheStore (DBaaS) service allows you to view and edit the full list of resources and detailed information. CacheStore(DBaaS) Details page consists of Detail Information, Tags, Activity History tabs.
Follow the steps below to view detailed information about the CacheStore (DBaaS) service.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
CacheStore(DBaaS) List page, click the resource to view detailed information. 3. CacheStore(DBaaS) Details Go to the page.
CacheStore(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Detailed description
Cluster status
Cluster status with Redis installed
Creating: Cluster is being created
Editing: Cluster is changing to an operational state
Error: Cluster encountered an error during operation
If it occurs continuously, contact the administrator
Failed: Cluster failed during creation
Restarting: Cluster is restarting
Running: Cluster is operating normally
Starting: Cluster is starting
Stopped: Cluster is stopped
Stopping: Cluster is stopping
Synchronizing: Cluster is synchronizing
Terminating: Cluster is being terminated
Unknown: Cluster status is unknown
If it occurs continuously, contact the administrator
Cluster control
Buttons that can change the cluster state
Start: Start a stopped cluster
Stop: Stop a running cluster
Restart: Restart a running cluster
Switch-Over: Switch a replica cluster to Master
View more features
Cluster-related management buttons
Service status synchronization: Real-time Redis/Valkey service status lookup
Backup history: When backup is configured, check whether the backup runs correctly and view its history
Database recovery: Recover the DB based on a specific point in time
Parameter management: Ability to view and modify Redis/Valkey configuration parameters
Rename-Command: Change the name of a Redis/Valkey command
Service cancellation
Cancel Service button
Table. CacheStore (DBaaS) status information and additional features
Detailed Information
CacheStore(DBaaS) List page lets you view detailed information of the selected resource and modify it if needed.
Detailed description
Server Information
Server information configured in this cluster
Category: Server type (Master, Replica, Sentinel)
Server name: Server name
IP Port: Server IP and port
Availability Zone: Server creation location
Status: Server status
service
Service name
Resource Type
Resource Type
SRN
Unique resource ID in Samsung Cloud Platform
In the DB service, it refers to the cluster SRN
Resource Name
Resource name
In the DB service, it means the cluster name
Resource ID
Unique resource ID in the service
Constructor
User who created the service
Creation Date/Time
Service creation date and time
Modifier
User who edited the service information
Modification date and time
Date and time the service information was modified
Image version
Installed Redis/Valkey image and version information
If a Minor version upgrade is required, click the Edit icon to configure
Port number required for connecting to Redis/Valkey
Time zone
Redis/Valkey time zone
Sentinel Port number
Port number for communication between Master and Replica
VIP
Virtual IP information
can be checked only when high availability is configured
Network
Network information (VPC, Subnet) where CacheStore (DBaaS) is installed
IP access control
Service access policy settings
If you need to add or delete IPs, click the Edit icon to configure
Master & Replica
Master, Replica server type, default OS, additional Disk information
If you need to modify the server type, click the Edit icon next to the server type to configure
Modifying the server type requires a server reboot
Changes to the specifications may require software license updates or software configuration adjustments, which need to be verified separately
Sentinel
Sentinel server type, basic OS information
When configuring HA, it is possible to verify when selecting one Replica
Table. CacheStore (DBaaS) Database detailed information items
tag
CacheStore(DBaaS) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.
Detailed description
Tag list
Tag list
You can view the Key and Value information of the tag
Up to 50 tags can be added per resource
When entering a tag, you can search and select from the existing list of created Keys and Values
Table. CacheStore (DBaaS) tag tab item
Job History
CacheStore(DBaaS) List page allows you to view the operation history of the selected resource.
Detailed description
Task: 1. Open the file, 2. Read the data, 3. Close the file.
Resource Change History
You can view the operation timestamp, resource ID, resource name, operation details, event topic, operation result, and operator information
To perform an advanced search, click the Advanced Search button
Table. CacheStore (DBaaS) Operation History Tab Detailed Information Items
CacheStore(DBaaS) Managing Resources
If you need to change or restore the existing configuration options of a created CacheStore (DBaaS) resource, or modify commands, you can perform the work on the CacheStore(DBaaS) Details page.
Operation Control
If changes occur to a running CacheStore (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Master-Replica servers via a switch‑over.
To control the operation of CacheStore(DBaaS), follow these steps.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
On the CacheStore(DBaaS) List page, click the resource you want to control. 3. Go to the CacheStore(DBaaS) Details page.
Check the CacheStore status and complete the change using the control button below.
Start: the server where the CacheStore service is installed and the CacheStore service is running (Running).
Stop: The server on which the CacheStore service is installed and the CacheStore service can be stopped (Stopped).
Restart: Only the CacheStore service can be restarted.
Switch Over: You can switch the Master server and the Replica server.
Synchronize service status
You can synchronize the real-time service status of CacheStore(DBaaS).
To view the service status of CacheStore (DBaaS), follow the steps below.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
CacheStore(DBaaS) List page, click the resource to view the service status. 3. Navigate to the CacheStore(DBaaS) Details page.
Click the Service status synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
When the query completes, the status in the server information item is updated, and the cluster changes to Running status.
Change Server Type
You can change the configured server type.
Caution
If you modify the server type, a server restart is required. Please verify separately any software license modifications or software settings and their implementation due to server specification changes.
To change the server type, follow these steps.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
On the CacheStore(DBaaS) List page, click the resource to change the server type. 3. CacheStore(DBaaS) Details Go to the page.
Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
Server Type Edit In the popup window, after selecting the server type, click the Confirm button.
Cancel CacheStore(DBaaS)
You can reduce operating costs by terminating unused CacheStore (DBaaS). However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
To cancel CacheStore (DBaaS), follow the steps below.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
On the CacheStore(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
When the termination is complete, verify on the CacheStore(DBaaS) list page whether the resource has been terminated.
6.2.1 - Managing the CacheStore Service
Users can manage CacheStore (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows you to easily view and modify database configuration parameters.
View Parameters
To view configuration parameters, follow these steps.
Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
On the CacheStore(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. CacheStore(DBaaS) Details Go to the page.
Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. Lookup notification popup opens.
When the View Notification popup opens, click the Confirm button. 6. Retrieving may take a short amount of time.
Edit Parameter
To modify the configuration parameters, follow the steps below.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
On the CacheStore(DBaaS) List page, click the resource whose parameters you want to view or modify. 3. Go to the CacheStore(DBaaS) Details page.
Click the More button, then click the Parameter management button. 4. Parameter Management The popup window opens.
Parameter Management In the popup window, click the Search button. 5. View Notification The popup window opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
If editing is required, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
When the input is complete, click the Complete button.
Rename Command
Caution
When applying the Rename-Command, the service will be interrupted due to a CacheStore (DBaaS) restart.
Provides Redis OSS/Valkey command lookup and command name editing functionality. To view commands and rename a command, follow these steps.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
Click the CacheStore(DBaaS) menu on the Service Home page. 2. Go to the CacheStore(DBaaS) List page.
CacheStore(DBaaS) List On the page, click the resource to edit the Command name. 3. CacheStore(DBaaS) Details Go to the page.
Click the More button and then click the Rename-Command button. 4. Rename-Command go to the page.
On the Rename-Command page, click the Search button. 5. lookup notification popup opens.
When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
If you need to make changes, click the Edit button and enter the modifications in the custom value field of the Command you wish to edit.
When the input is complete, click the Done button.
Minor version upgrade
Provides version upgrade functionality resulting from feature enhancements and security patches. Only minor version upgrades are supported within the same major version.
Caution
First retrieve the service status via service status synchronization, then proceed with the version upgrade.
To upgrade the Minor version, follow these steps.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Go to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
CacheStore(DBaaS) List page, click the resource to upgrade the version. 3. CacheStore(DBaaS) Details Go to the page.
Click the Edit icon of the Image version item. 4. Version Upgrade A popup window opens.
In the Version Upgrade popup, after selecting the updated version, click the Confirm button.
Version Upgrade Notification in the popup window, click the Confirm button.
6.2.2 - Backing up and restoring CacheStore
Users can configure backups for CacheStore (DBaaS) via the Samsung Cloud Platform Console and restore using the backed‑up files.
CacheStore(DBaaS) Backup
CacheStore(DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
To modify the backup settings of a created resource, follow these steps.
Caution
If a backup is configured, it runs at the specified time after the set time, and additional fees are incurred based on the backup size.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
CacheStore(DBaaS) List on the page, click the resource to configure backup. 3. Go to the CacheStore(DBaaS) Details page.
Click the Edit icon of the backup item. 4. Backup Settings The popup window opens.
When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
If you stop the backup setting, uncheck Use in the Backup Setting popup window and click the Confirm button.
Check backup history
안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, see 알림 정책 생성하기.
To check the backup history, follow these steps.
Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
CacheStore(DBaaS) List page, click the resource to view the backup history. 3. CacheStore(DBaaS) Details Go to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
CacheStore(DBaaS) List page, click the resource to view the backup history. 3. CacheStore(DBaaS) Details Go to the page.
Click the Backup History button. 4. Backup History The popup window opens.
Backup History popup, after checking the file you want to delete, click the Delete button.
Recover CachStore(DBaaS)
If a failure or data loss requires restoration from a backup file, recovery can be performed based on a specific point in time using the recovery feature.
To restore CacheStore (DBaaS), follow these steps.
All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
On the CacheStore(DBaaS) List page, click the resource you want to recover. 3. CacheStore(DBaaS) Details Navigate to the page.
Click the Database Recovery button. 4. Go to the Database Recovery page.
After entering information in the Database recovery configuration area, click the Complete button.
required status
Detailed description
Recovery type
Required
Set the point in time the user wants to recover
Recover based on the backup file, and select from the list of timestamps displayed for the backup file
Server name prefix
Required
Recovery DB server name
Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
A postfix such as 001, 002 is appended based on the server name to generate the actual server name
Cluster name
Required
Cluster name of the recovery DB
Enter using English letters, 3 ~ 20 characters
A cluster is a unit that groups multiple servers
Service Type > Server Type
Required
Server type where the recovery 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
Selection
Status of resources with Planned Compute set
In Use: Number of resources with Planned Compute set that are currently in use
Configured: Number of resources with Planned Compute set
Coverage Preview: Amount applied per resource by Planned Compute
Create Planned Compute Service: Go to the Planned Compute service application page
Basic OS: The area where the DB engine is installed
DATA: The area where AOF (Append Only File) and RDB (Redis Database) files, etc., are stored
Apply the same Storage type as set in the original cluster
Capacity can be entered in multiples of 8 within the range 56–5,120
Redis/Valkey Port number
Required
Redis/Valkey port number configured in the source DB
IP access control
Selection
Service Access Policy Configuration
Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
Enter in jIP 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 an entered IP, click the x button next to the IP
Maintenance period
Selection
CacheStore(DBaaS) DB maintenance period
If you select Use, you can set the day, start time, and duration
The maintenance period is a feature that allows the user to set the time window for performing patch operations, and any patch work within that window is performed directly by the user.
We ask you to set a maintenance period for the stable operation of the system; we are not responsible for any issues arising from not setting it or from failure to perform tasks within the period.
tag
Selection
Add Tag
Add Tag after clicking the button, enter or select Key, Value
Connecting to CacheStore(DBaaS) The scenario creates a Bastion host (Virtual Server) and a Database service, and accesses the DB service through the Bastion host. To reliably access CacheStore (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Figure. CacheStore(DBaaS) server connection architecture
Scenario components
You can build the scenario using the following services.
Service group
service
Detailed description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Networking
VPC > Subnet
A service that lets users segment the network within a VPC to match their purpose and scale
Networking
VPC > Public IP
A service that reserves a public IP and allocates and releases it to Compute resources.
Networking
VPC > Internet Gateway
A service that connects VPC resources to the Internet
Networking
Security Group
Virtual firewall that controls server traffic
Database
CacheStore(DBaaS)
A service that easily creates and manages CacheStore in a web environment
Compute
Virtual Server
Virtual server optimized for cloud computing
Compute
Virtual Server > Keypair
Encryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
The In/Outbound All Open(Any IP, Any Port) policy can expose cloud resources directly to external threats.
By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Explains the process of configuring the network environment for accessing the Bastion Host and Database services.
Click the All Services > Networking > Firewall menu. 1. Navigate to the Firewall’s Service Home page.
On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
On the detail information page, click the Rules tab. 4. Go to the Rules tab.
Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address
Destination address
Protocol
Port
Operation
Direction
Explanation
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. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide explains how to connect using Another Redis Desktop Manager. Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB access client program (Another Redis Desktop Manager) on the Bastion host
Download the Another Redis Desktop Manager program.
Connect the user’s PC hard drive to upload the file to the Bastion host.
Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install it.
5-3. ### Connect to the database using the DB client program (Another Redis Desktop Manager)
Run Another Redis Desktop Manager and click New Connection. 1. New Connection A popup window appears.
In the New Connection popup, enter the Database server information created in 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
Required input element item
input value
Host
Database server IP
Port
Database Port
Password
Database password
Connection Name
Custom (ex. service name)
Table DB connection client program input fields
After connecting, you can check basic Redis information, manage data, and perform CRUD operations on keys.
6.3 - API Reference
API Reference
6.4 - CLI Reference
CLI Reference
6.5 - Release Note
CacheStore(DBaaS)
2026.07.16
FEATUREServiceWatch service integration and addition of third-generation server type
ServiceWatch service integration
You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.
Add third-generation server type
The third-generation server type has been newly added. * For more details, see CacheStore(DBaaS) 서버 타입.
2026.03.19
FEATUREAdd minor version upgrade feature
Provides stable service continuity through the minor version upgrade feature.
2025.07.01
FEATUREUser (access control) management, add DB Audit Log export feature, provide backup notification feature
Add CacheStore (DBaaS) feature
CacheStore(DBaaS) Add New Image
Open-source Valkey image support, developed by forking Redis OSS
Add 2nd-generation server type
Add a 2nd‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For more details, see CacheStore(DBaaS) 서버 타입.
Backup Notification Feature provided
Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
Add HDD, HDD_KMS type to the Block Storage type
2025.02.27
FEATURECommon feature change
Samsung Cloud Platform Common Feature Change
Account, IAM, Service Home, tags, and other common CX changes have been applied.
2024.10.01
NEWCacheStore(DBaaS) service official version release
Change the service name to CacheStore(DBaaS).
A volume-encrypted storage selection option has been added to the Block Storage type.
The Role Switch (Active ↔ Standby) feature for the Active DB and Standby DB configured with redundancy has been added.
By integrating with the monitoring services provided by the cloud, you can visualize CPU usage, memory usage, disk I/O, and network traffic in real time, set alerts, and when thresholds are exceeded, trigger auto-scaling or automatically collect·analyze·forward logs for troubleshooting through a unified monitoring pipeline. Additionally, by linking security logs and audit logs to a centralized log management system, you strengthen compliance and security monitoring, and by providing performance and capacitymonitoring for databases and storage, you support resource optimization and cost reduction. Such unified monitoring enhances system availability, improves operational efficiency, and ensures business continuity.
Depending on the server type selected by the customer, Planned Compute policy can be configured.
2024.07.02
NEWBeta version release
A Redis (DBaaS) service that enables easy creation and management of Redis OSS in a web environment has been launched.