This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Database

It provides a service to easily create and manage relational, unstructured, and data analysis 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 content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas are provided for read load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user-specified times, supporting data recovery at the desired point in time.

Architecture
Figure. EPAS (DBaaS) Architecture

Provided Features

EPAS(DBaaS) provides the following functions.

  • Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) is possible via UI, and provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, automatic failover to Standby occurs.
  • Operation Control Management: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. In case of high availability (HA) configuration, the user can directly perform node switching of Active-Standby via Switch-over.
  • Backup and Recovery: Provides data backup functionality based on its own backup command. Backup time slots and storage agencies can be set by the user, and additional fees are incurred depending on backup volume. It also provides a recovery function for backed‑up data, and when the user performs a recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup save point, user‑specified point). If recovery is set to a user‑specified point, the recovery point can be set to 5 minutes/10 minutes/30 minutes/1 hour before based on the stored backup file and archive file.
  • Version Management: Provides version upgrade (Minor) functionality according to some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
  • Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
  • Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
  • Parameter management: Performance improvement and security-related DB configuration parameter modifications are possible.
  • Service status query: Retrieve the final status of the current DB service.
  • Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
  • DB User Management: Query 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 IPs for access.
  • Archive Management: You can set the archive file retention period (1 day~35 days) within the DB server and configure the archive mode (On/Off).
  • DB Log Export: Through Audit settings, saved logs can be exported to the user’s Object Storage.
  • Migration: Synchronize data in real-time with the operating database, and support migration using the Replication method without service interruption.

Components

EPAS (DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they want to configure.

Engine Version

The engine versions supported by EPAS (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 stopped is set to six months before the EoTS date.

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

Provided versionEOS Date(Samsung Cloud Platform New creation stop date)EoTS Date(Community Technical support end date)
14.172026-06 (scheduled)2026-12-01
14.182026-06 (scheduled)2026-12-01
15.122027-09 (scheduled)2028-02-13
15.132027-09 (scheduled)2028-02-13
16.82028-06 (scheduled)2028-11-09
16.92028-06 (scheduled)2028-11-09
Table. EPAS (DBaaS) Engine Versions Provided

Server Type

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

For detailed information about the server types provided by EPAS(DBaaS), please refer to EPAS(DBaaS) server type.

Standard db1v2m4
CategoryExampleDetailed Description
Server TypeStandardProvided Server Types
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
  • High Capacity: large-capacity server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) configuration commonly used
  • dbh2: Large-scale server specifications
    • Provide servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server Specificationsm4Memory 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. For details, please refer to the guide provided for each service and prepare in advance.

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
Table. EPAS(DBaaS) Preliminary Service

1.1.1 - Server Type

EPAS(DBaaS) Server Type

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

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

Standard db1v2m4
Classification
ExampleDetailed Description
Server TypeStandardClassification of provided server types
  • Standard: Composed of standard specifications (vCPU, Memory) commonly used
  • High Capacity: Server with higher capacity than Standard
Server Specificationdb1Classification of provided server types and generations
  • db1: Means general specifications, and 1 means the generation
  • dbh2: h means high-capacity server specifications, and 2 means the generation
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory capacity
  • m4: 4GB Memory
Table. EPAS(DBaaS) Server Type Format

db1 Server Type

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

  • Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. EPAS(DBaaS) Server Type Specifications - db1 Server Type

dbh2 Server Type

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

  • Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
  • Supports up to 128 vCPUs and 1,536 GB of memory
  • Up to 25Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBUp to 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBUp to 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBUp to 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBUp to 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBUp to 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBUp to 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBUp to 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBUp to 25 Gbps
Table. EPAS(DBaaS) Server Type Specifications - dbh2 Server Type

1.1.2 - Monitoring Metrics

EPAS(DBaaS) Monitoring Metrics

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

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

Performance ItemDetailed DescriptionUnit
Active Locks [Access Exclusive]Access Exclusive Locks countcnt
Active Locks [Access Share]Access Share Lock countcnt
Active LocksActive Locks countcnt
Active Locks [Total]Active Locks total countcnt
Active SessionsNumber of Sessions in Active statecnt
Active Sessions [Total]Total number of Sessions in Active statecnt
Apply Lag TimeApply lag timemin
Check No ReplicationCheck No Replication valuecnt
Check ReplicationCheck Replication Status valuestatus
Connection UsageDB connection usage rate(%)%
Connection Usage [Total]DB connection count usage rate(%)%
DB Age MaxDatabase age (frozen XID) valueage
Exclusive LocksExclusive Locks countcnt
Idle In Transaction SessionsNumber of sessions in idle in transaction statecnt
Idle In Transaction Sessions [Total]Idle in transaction state Session total countcnt
Idle SessionsNumber of idle sessionscnt
Idle Sessions [Total]Total number of idle sessionscnt
Row Exclusive LocksRow Exclusive Locks countcnt
Row Share LocksRow Share Locks countcnt
Share LocksShare Locks countcnt
Share Row Exclusive LocksShare Row Exclusive Locks countcnt
Share Update Exclusive LocksShare Update Exclusive Locks countcnt
SlowqueriesNumber of SQL queries running for a long time (5 minutes or more)cnt
Tablespace UsedTable space sizebytes
Tablespace Used [Total]Table space sizebytes
Tablespace Used Bytes [MB]File system directory usage (MB)MB
Tablespaces [Total]File system directory usage (MB)MB
Transaction Time Max [Long]Long-running Transaction time (minutes)min
Transaction Time Max Total [Long]Long-running Transaction time (minutes)min
Wait LocksNumber of waiting lock sessions (by DB)cnt
Wait Locks [Long Total]Long duration (300 seconds) Lock waiting session countcnt
Wait Locks [Long]Number of Sessions waiting due to lock occurrencecnt
Wait Locks [Total]Total number of sessions waiting due to lock occurrencecnt
Waiting SessionsNumber of Sessions in Waiting statecnt
Waiting Sessions [Total]Total number of Sessions in Waiting statecnt
Table. EPAS(DBaaS) Monitoring Metrics

1.2 - How-to guides

The user can enter the required information for EPAS (DBaaS) and select detailed options through the Samsung Cloud Platform Console to create the service.

Creating EPAS(DBaaS)

You can create and use the EPAS (DBaaS) service from the Samsung Cloud Platform Console.

Guide
  • Please configure the VPC’s Subnet type as General before creating the service.
    • If the Subnet type is Local, the creation of the corresponding Database service is not possible.
  • If you load more than 2 TB of large data, backups may take a long time or the DB’s performance may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.

To create EPAS (DBaaS), follow the steps below.

  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Service Home on the page click the EPAS(DBaaS) Creation button. Navigate to the EPAS(DBaaS) Creation page.
  3. Create EPAS (DBaaS) page, enter the information required to create the service, and select detailed options.
    • Image and Version Selection Select the required information in the area.
      Category
      Required
      Detailed description
      Image versionRequiredProvide version list of EPAS (DBaaS)
      Table. EPAS(DBaaS) Image and Version Selection Items
    • Service Information Input area, please enter or select the required information.
      Category
      Required
      Detailed description
      Server Name PrefixRequiredServer name where DB will be installed
      • Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (-) to input 3 to 13 characters
      • Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
      Cluster NameRequiredCluster name of DB servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type where DB will be installed
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server with 24 vCore or more
      Service Type > Planned ComputeSelectStatus 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 by Planned Compute per resource
      • Create Planned Compute Service: Go to the Planned Compute service application page
      Service Type > Block StorageRequiredBlock Storage settings used by DB according to purpose
      • Base 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. (For details on each Block Storage type, refer to Create Block Storage)
          • SSD: High‑performance general volume
          • HDD: General volume
          • SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption keys
      • The configured storage type is applied identically to additional storage
      • Capacity must be entered as a multiple of 8 within the range 16–5,120
      • Since large sorts during SQL execution or monthly batch processes can cause service interruption, a separate TEMP storage must be allocated and used
      • Add: DATA, Archive, TEMP, Backup data storage areas
        • Select Use, then enter the storage purpose and capacity
        • The storage type is applied the same as set for DATA, and capacity can be entered as a multiple of 8 within the range 16–5,120
        • Click the + button to add storage, and the x button to delete. Up to 9 can be added
        • Backup data is temporarily stored in BACKUP storage before transmission
          • If the data to be backed up exceeds 100 GB and changes frequently, it is recommended to add a separate BACKUP storage for reliable backup; set the backup capacity to about 60 % of the DATA capacity
          • If no BACKUP storage is added, using the /tmp area is recommended
      • For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
      Redundancy ConfigurationSelectRedundancy Configuration Status
      • If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
      Network > Common SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply the same settings to all servers being installed
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be auto‑generated
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP pool. For more information, see Create Public IP.
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply different settings per installed server
      • Select a pre-created VPC, Subnet, IP, Public NAT
        • Enter each server’s IP
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. For more details, see Create Public IP
      IP Access ControlSelectService Access Policy Settings
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      Maintenance PeriodSelectDB Maintenance Period
      • Use is selected, set the day of the week, start time, and duration
      • It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption
      • If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied
      Table. EPAS (DBaaS) Service Information Input Items
  • Database configuration required information input area, please input or select the required information.
    Category
    Required
    Detailed description
    Database nameRequiredServer name applied when installing DB
    • Start with an English letter, and use English letters and numbers, input 3 to 20 characters
    Database usernameRequiredDB user name
    • An account with the same name is also created on the OS
    • Enter using lowercase English letters, 2 ~ 20 characters
    • Restricted Database usernames can be checked in the Console
    Database passwordRequiredPassword to use when accessing the DB
    • Enter 8-30 characters including letters, numbers, and special characters ( excluded)
    Database Password verificationRequiredRe-enter the same password to be used when accessing the DB
    Database Port numberRequiredPort number required for DB connection
    • Enter DB port within the range 1,024 ~ 65,535
    Backup > UseSelectWhether to use backup
    • Select Use to set backup file retention period, backup start time, and Archive backup cycle.
    Backup > Retention PeriodSelectBackup Retention Period
    • Select the backup retention period. File retention period can be set from 7 days to 35 days.
    • Backup files incur additional charges based on size.
    Backup > Backup Start PeriodSelectBackup Start Time
    • Select backup start time
    • The minutes (minutes) when the backup is performed are set randomly, and the backup end time cannot be set
    Backup > Archive backup frequencySelectArchive backup frequency
    • Select the Archive backup frequency
    • Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
    Audit Log SettingsSelectWhether to store Audit Log
    • Select Use to configure the Audit Log feature
    • DDL, DML, SELECT, and user connection information records are stored
      • Users can specify the types of SQL statements to audit via the edb_audit_statement parameter, and can modify it through the Parameter screen
    • Enabling Audit may degrade DB performance
    ParameterRequiredDB configuration parameters
    • View button click to view detailed information of the parameter
    • Parameters can be modified after the service creation is completed, and after modification, the DB must be restarted
    Database EncodingRequiredCharacter 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 LocaleRequiredLocale to use for the DB
    • Settings related to string processing, number/currency/date/time display formats, etc.
    • The DB is created with the selected Locale as the default setting
    Time zoneRequiredStandard time zone to be used by the Database
    LicenseRequiredCheck EPAS License
    • As a verification item for license usage, you cannot proceed to the next step unless you click confirm.
    Table. EPAS(DBaaS) Database configuration items
    • Enter additional information area, please input or select the required information.
      Category
      Required or not
      Detailed description
      TagSelectAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. EPAS (DBaaS) Additional Information Input Items
  1. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Resource List page.

EPAS(DBaaS) Check detailed information

EPAS(DBaaS) service can view and edit the full resource list and detailed information. EPAS(DBaaS) Detail page consists of Detail Information, Tag, Operation History tabs, and for a DB with a Replica configured, a Replica Information tab is additionally provided.

To view detailed information about the EPAS (DBaaS) service, follow the steps below.

  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. Click the resource to view detailed information on the EPAS(DBaaS) List page. Move to the EPAS(DBaaS) Details page.
    • EPAS(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
      CategoryDetailed description
      Cluster StatusCluster status with DB installed
      • Creating: Creating cluster
      • Editing: Cluster is changing to operation execution state
      • Error: Cluster error occurred during operation execution
        • If it occurs continuously, contact the administrator
      • Failed: Cluster failed during creation process
      • Restarting: Restarting cluster
      • Running: Cluster is operating normally
      • Starting: Starting cluster
      • Stopped: Cluster is stopped
      • Stopping: Cluster is in stopping state
      • Synchronizing: Synchronizing cluster
      • Terminating: Terminating cluster
      • Unknown: Unknown cluster status
        • If it occurs continuously, contact the administrator
      • Upgrading: Cluster is changing to upgrade execution state
      Cluster ControlButtons 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 featuresCluster related management buttons
      • Service status synchronization: Real-time DB service status lookup
      • Backup history: If backup is set, check whether backup runs normally and view history
      • Database recovery: Recover DB based on a specific point in time
      • Parameter management: View and modify DB configuration parameters
      • Replica configuration: Set up a read-only cluster as a Replica
      • 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 period and archive mode
      • Export DB Log: Through Audit settings, export stored logs to user’s Object Storage
      • Migration configuration: Provide Migration function using Replication method
      Service terminationButton to cancel the service
      Table. EPAS (DBaaS) status information and additional features

Detailed Information

EPAS(DBaaS) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
Server InformationServer information configured in the respective cluster
  • Category: Server type (Active, Standby, Replica)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In DB service, it means cluster SRN
Resource NameResource Name
  • In DB service, it means the cluster name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
EditorUser who modified the service information
Modification TimeDate and time when service information was modified
Image/VersionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to set
Cluster TypeCluster Type (Master Cluster, Replica Cluster, Migration Cluster)
Cluster NameName of the cluster composed of DB servers
Master cluster nameReplica’s Master cluster name
  • If detailed information of the Replica is present, it can be verified
Database nameServer name applied when installing DB
Database usernameDB user name
Planned ComputeResource status with Planned Compute configured
Maintenance PeriodDB Maintenance Period Status
  • If maintenance period setting is required, click the Edit icon to set
BackupBackup Settings Status
  • If backup configuration is needed, click the Edit icon to set it
Audit Log SettingsAudit Log Settings Status
  • If Audit Log settings are needed, click the Edit icon to configure
Time zoneStandard time zone used by the Database
DB LocaleLocale to use for DB
Database EncodingCharacter encoding method to be used in DB
VIPVirtual IP information
  • Can be checked only when high availability is configured
NetworkNetwork information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP Access ControlService Access Policy Settings
  • If you need to add or delete an IP, click the Edit icon to set
Active & StandbyActive/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 set it. Refer to Change Server Type for the server type modification procedure
    • 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 Expand Storage for the storage expansion procedure
  • If you need to add storage, click the Add Disk button next to Additional Disk to add. Refer to Add Storage for the storage addition procedure
Table. EPAS(DBaaS) Database detailed information items

Replica Information

Replica information tab is enabled only when a Replica is configured in the cluster. Through the Replica information tab, you can check the master cluster name, replica count, and Replica status.

CategoryDetailed description
Master InformationName of Master Cluster
Replica countNumber of Replicas created in the Master cluster
Replica StatusReplica server status created in the Master cluster
  • Server name, status query, status details, and status check time can be viewed
  • To view the Replica status, click the Status Query button
    • While querying, the cluster remains in Synchronizing state, and once the query is complete, 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 you can add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • You can view the tag’s Key, Value information
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the previously created Key and Value list
Table. EPAS(DBaaS) Tag Tab Items

Work History

On the EPAS(DBaaS) List page, you can view the operation history of the selected resource.

CategoryDetailed description
Work History ListResource Change History
  • Work date/time, Resource ID, Resource name, Work details, Event topic, Work result, Check worker information
Table. Work History Tab Detailed Information Items

EPAS(DBaaS) Manage Resources

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 work on the EPAS (DBaaS) Details page.

Operating Control

If changes occur to the running EPAS (DBaaS) resources, you can start, stop, or restart them. Also, if HA is configured, you can switch the Active-Standby servers via Switch-over.

To control the operation of EPAS (DBaaS), follow the steps below.

  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. Navigate to the EPAS(DBaaS) List page.
  3. Click the resource to control operation on the EPAS(DBaaS) List page. It moves to the EPAS(DBaaS) Detail page.
  4. Check the EPAS (DBaaS) status and complete the change using the control button below.
    • Start: The server where the DB service is installed and the DB service is running.
    • Stop: The server where the DB service is installed and the DB service are 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.

  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. Click the resource to view the service status on the EPAS(DBaaS) List page. It will navigate to the EPAS(DBaaS) Details page.
  4. Service Status Synchronization Click the button. While it is being queried, the cluster will change to Synchronizing state.
  5. 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.

To change the server type, follow the steps below.

Caution
If you modify the server type, a server reboot is required. Please separately check any SW license changes or SW settings and reflections due to changes in server specifications.
  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. Go to the EPAS(DBaaS) List page.
  3. Click the resource to change the server type on the EPAS (DBaaS) List page. It will navigate to the EPAS (DBaaS) Details page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
  5. Server Type Edit In the popup window, after selecting the server type, click the Confirm button.

Add storage

If more than 5 TB of data storage space is required, additional storage can be added. In the case of a redundant DB configuration, both redundant servers are added simultaneously.

To add storage, follow these steps.

Caution
  • It is applied the same way as the Storage type selected when creating the service.
  • In the case of a redundant DB, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
  • If a Replica exists, the Master cluster’s storage cannot be larger than the Replica’s storage. Expand the Replica storage first, then expand the Master cluster storage.
  • When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List Click the resource to add storage on the page. EPAS(DBaaS) Details Navigate to the page.
  4. Click the Add Disk button at the bottom of the detailed information. The Request Additional Storage popup window opens.
  5. Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.

Expanding Storage

You can expand the storage added to the data area 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.

  1. All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) 목록 Click the resource to change the server type on the page. EPAS(DBaaS) 상세 Navigate to the page.
  4. Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. The Edit Additional Storage popup window opens.
  5. Add Storage Modification After entering the expansion capacity in the popup window, click the Confirm button.

EPAS(DBaaS) Cancel

You can cancel unused EPAS (DBaaS) to reduce operating costs. However, if you cancel the service, the service currently in operation may be stopped immediately, so you should proceed with the cancellation after fully considering the impact that may occur when the service is discontinued.

Caution
  • In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, please terminate it separately from the resource list.
  • If you cancel the DB, stored data and, if backup is set, backup data will also be deleted.

To cancel EPAS (DBaaS), follow the steps below.

  1. Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) list on the page, select the resource to cancel, and click the Cancel Service button.
  4. Once the termination is complete, check whether the resource has been terminated on the EPAS(DBaaS) list page.

1.2.1 - EPAS(DBaaS) server connection

Scenario Overview

The EPAS(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created to access the DB service through the Bastion host. To securely access EPAS(DBaaS) in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.

This scenario largely describes the process of creating a Bastion host and Database service, configuring the network environment for Bastion host and Database connection, and accessing it through a DB connection client.

Architecture
Figure. EPAS(DBaaS) connection architecture

Scenario Components

You can configure the scenario using the following services.

Service Group
Service
Detailed Description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that allows users to subdivide the network into smaller segments for specific purposes/sizes within the VPC
NetworkingVPC > Public IPA service that reserves public IP and assigns and returns it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the internet
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
DatabaseEPAS(DBaaS)A service that easily creates and manages EPAS in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to access Virtual Server
Table. List of scenario components
Reference
The default policy of the * Security Group is Deny All, so only allowed IPs should be registered. The In/Outbound’s All Open policy (Any IP, Any Port) can expose cloud resources to external threats. * By specifying the necessary IP and Port to set the policy, you can enhance security.

Scenario composition method

To configure the scenario, create the necessary services through the following procedure.

1. Configuring the Network

This describes the process of configuring the network environment for Bastion Host and Database service connection.

1-1. Creating a VPC

For detailed creation methods, please refer to the Networking > VPC > How-to guides guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
  3. VPC Creation page, please enter the information required for service creation.
    • IP range should be entered as 192.168.x.0/16.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the VPC list page.

1-2. Creating a Subnet

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Subnet menu. It moves to the Subnet list page.
  3. Click the Subnet Creation button. It moves to the Subnet Creation page.
  4. Subnet creation page where you enter the information needed to create a service.
    • Subnet type should be selected as General.
    • Please select a pre-created VPC.
    • IP range should be entered as 192.168.x.0/24.
  5. In the Summary panel, review the detailed information and estimated charge, then click the Complete button.
    • After creation is complete, check the created resource in the Subnet list page.

1-3. Creating an Internet Gateway

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Internet Gateway menu. Move to the Internet Gateway list page.
  3. Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
  4. Internet Gateway creation page, please enter the required information necessary for service creation.
    • Please select a pre-created VPC.
    • Select use in the Firewall usage item.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the Internet Gateway list page.

1-4. Creating a Public IP

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Public IP menu. It moves to the Public IP list page.
  3. Public IP Reservation button, click. Move to the Public IP Reservation page.
  4. Public IP Reservation page, enter the required information necessary for service reservation.
  5. Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
    • Once creation is complete, check the created resource on the Public IP List page.

1-5. Creating a Security Group

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
  2. Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
  3. Security Group creation page where you enter the required information necessary for service creation.
  4. Check the input information and click the Complete button.
    • Once creation is complete, check the created resource on the Security Group list page

2. Creating a Bastion Host

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

2-1. Creating a Server Keypair

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
  3. Create Keypair button should be clicked. It moves to the Create Keypair page.
  4. Keypair creation page, please enter the required information necessary for service creation.
  5. Check the creation information and click the Complete button.
    • The key can only be downloaded for the first time, and re-issuance is not provided.
    • Please keep the downloaded key in a safe place.

2-2. Creating a Bastion Host

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
  3. Virtual Server Creation page, please enter the required information necessary for service creation.
  4. Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
    • After creation is complete, check the created resource on the Virtual Server list page.

2-3. Check Bastion host connection ID and PW

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
  3. Virtual Serve list page, click on the resource created in 2-2. Bastion host creation. It moves to the detailed information page of the corresponding resource.
  4. Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window will open.
  5. RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
  6. After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.

3. Creating a Database

Describes the process of creating a Database service.

3-1. Creating EPAS(DBaaS) Service

For detailed creation methods, please refer to the Database > EPAS(DBaaS) > How-to guides guide.
  1. Click on the menu for all services > Database > EPAS(DBaaS). It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) creation button. It moves to the EPAS(DBaaS) creation page.
  3. EPAS(DBaaS) creation page, please enter the required information necessary for service creation.
    • Select and connect the pre-created VPC and Subnet.
    • Enter Database related creation information on the required information input screen.
    • Add the Bastion host IP to the IP access control items.
    • Database Port is 2866 by default, but you can specify it as you want.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once the creation is complete, check the created resource on the EPAS(DBaaS) list page.

4. Setting Rules

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

4-1. Adding Security Group Security Rules

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click All services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Security Group menu. It moves to the Security Group list page.
  3. 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule popup window, enter the rules below, and click the OK button
DirectionRemoteDestination AddressProtocolPortDescription
InboundCIDRUser PC IPTCP3389 (RDP)Bastion access PC → Bastion host
OutboundCIDRDB IPTCPDatabase Port (direct input)Bastion host → Database
Fig. Security Group security rules to be added

4-2. Adding IGW Firewall Rules

For detailed creation methods, please refer to the Networking > Firewall > How-to guides guide.
  1. Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
  2. Service Home page, click the Firewall menu. It moves to the Firewall list page.
  3. Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule popup window, enter the rules below, and click the OK button.
Departure AddressDestination AddressProtocolPortActionDirectionDescription
Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
Fig. Internet Gateway Firewall rules to be added

5. Connect to Database

This explains the process of a user accessing the Database through a DB connection client program.

This guide provides instructions on how to connect using pgAdmin. There are various database client programs and CLI utilities, so you can install and use the tools that suit you.

5-1. Connecting to the Bastion host

  1. Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
  2. After a successful remote desktop connection, the user credential input window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion host access ID and PW and click the Confirm button.

5-2. Installing DB connection client program (pgAdmin) on the Bastion host

  1. Go to the official pgAdmin page and download the pgAdmin program.
  2. Connect the hard drive of the user PC to upload the file to the Bastion host.
  3. Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
  4. Select the local disk where the file was downloaded to the drive and click the Confirm button.
  5. Copy the downloaded file and upload it to the Bastion Host, then click the pgAdmin installation file to install it.

5-3. Using DB connection client program (pgAdmin) to connect to the database

  1. Run pgAdmin and click the Add New Server button.
  2. In the Register - Server popup window, enter the Database server information created in 3-1. Creating EPAS(DBaaS) service in the General tab and Connection tab, and click the Save button.
    Screen (Tab)Required Input Element ItemsInput Value
    GeneralNameCustom (ex. Service Name)
    ConnectionHost name/addressDatabase server IP
    ConnectionPortDatabase Port
    ConnectionMaintenance databaseDatabase name
    ConnectionPasswordDatabase password
    DB Connection Client Program Input Items
  3. Click the database name created on pgAdmin to connect.
    • You can try simple queries after connecting.

1.2.2 - Managing DB Service

The user can manage EPAS(DBaaS) through the Samsung Cloud Platform Console.

Managing Parameters

It provides a function to easily query and modify database configuration parameters.

Parameter Inquiry

To view the configuration parameters, follow these steps.

  1. Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. EPAS(DBaaS) List page, click the resource you want to query and modify parameters. It moves to the EPAS(DBaaS) Details page.
  4. Click the More button and click the Parameter Management button. The Parameter Management popup window opens.
  5. In the Parameter Management popup window, click the Inquiry button. The Inquiry Notification popup window opens.
  6. When the query notification pop-up window opens, click the OK button. It may take a little time to query.

Modifying Parameters

To modify the configuration parameters, follow these steps.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource you want to query and modify parameters. It moves to the EPAS(DBaaS) detail page.
  4. Click the More button and click the Parameter Management button. The Parameter Management popup window opens.
  5. In the Parameter Management popup window, click the Search button. The Search Notification popup window opens.
  6. When the query notification popup window opens, click the OK button. It may take some time to query.
  7. If modification is needed, click the Modify button and enter the modification details in the customized value area of the parameter to be modified.
  8. When the input is complete, click the Save button.

Manage DB users

It provides management functions that can query DB user information and change status information.

Querying DB Users

To query DB users, follow the following procedure.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. Click on the resource you want to query the DB user on the EPAS(DBaaS) list page. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the DB User Management button. It moves to the DB User Management page.
  5. On the DB User Management page, click the Search button. It may take some time to retrieve the results.

Change DB User Status

To change the status of the retrieved DB user, follow the next procedure.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource you want to modify the DB user. It moves to the EPAS(DBaaS) detail page.
  4. Click the More button and click the DB User Management button. It moves to the DB User Management page.
  5. On the DB User Management page, click the Search button. It may take some time to retrieve the results.
  6. If modification is needed, click the Modify button and enter the status area value change or note contents.
  7. When the input is complete, click the Save button.

DB Access Control Management

It provides IP-based DB user access control management function. Users can directly specify the IP that can access the database, so that only allowed IPs can access.

Notice
Please perform DB user inquiry before setting DB access control. For DB user inquiry, please refer to DB user management.

Checking DB Access Control

To view DB users with IP access control set, follow the next procedure.

  1. All services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource for which you want to manage access control. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. DB Access Control Management page, click the Search button. It takes a little time to search.

Add DB Access Control

To add IP access control, follow the next procedure.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource for which you want to add IP access control. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. DB Access Control Management page, click the Search button. It takes a little time to search.
  6. When the inquiry is complete, click the Add button. The Add DB Access Control popup window will open.
  7. Add DB Access Control popup window, select DB username and enter IP Address.
  8. When the input is complete, click the Save button.

Delete DB Access Control

To delete IP access control, follow these steps.

  1. All services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource for which you want to delete IP access control. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. DB Access Control Management page, click the Inquiry button. It takes a little time to inquire.
  6. When the inquiry is complete, click the Delete button. The Delete popup window will open.
  7. Delete popup window, click the OK button.

Managing Archives

It provides archive mode setting and archive log storage period setting functions, allowing users to flexibly set archive log management policies according to their operating environment. Additionally, it provides a function to manually delete Archive logs, allowing you to clean up unnecessary log data and effectively manage system resources.

Notice
When creating a service, the default setting is to use Archive mode, and the retention period is 3 days.

Setting Archive Mode

To set the archive mode, follow the next procedure.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource for which you want to set the Archive mode. It moves to the EPAS(DBaaS) detail page.
  4. Click the More button and click the Archive Settings Management button. It moves to the Archive Settings Management page.
  5. Archive settings management page, click the Inquiry button. It takes a little time to inquire.
  6. Click the Modify button and select whether to use it and the storage period.
  7. When the modification is complete, click the Save button.

Delete Archive Files

To delete an Archive file, follow these steps.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource for which you want to set the Archive mode. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the Archive Settings Management button. It moves to the Archive Settings Management page.
  5. Archive settings management page, if you want to delete all Archive files, click the Delete all Archives, if you want to delete only the backed up Archive files, click the Delete backed up Archives button.

DB Log export

It supports exporting log data that requires long-term storage in the 감사(Audit) log to Object Storage. Users can directly set the type of log to be stored, the destination bucket to be exported, and the cycle of exporting logs. It copies and stores logs to the specified Object Storage according to the set criteria. Additionally, to efficiently manage disk space, it provides an option to automatically delete the original log files while exporting logs to Object Storage at the same time. By utilizing this option, you can effectively secure the storage capacity while safely storing the necessary log data for a long time.

Notice
  • To use the DB Log export function, Object Storage creation is required. Please refer to the Object Storage user guide for Object Storage creation.
  • Please make sure to check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the Bucket.
  • Please be careful not to expose the authentication key information to the outside.

Set DB Log Export Mode

To set the DB log export mode, follow the following procedure.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. EPAS(DBaaS) list page, click on the resource you want to export DB Log. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the Export DB Log button. It moves to the Export DB Log page.
  5. On the DB Log Export page, click the Register button. It moves to the DB Log Export Registration page.
  6. On the DB Log Export Registration page, enter the corresponding information and click the Save button.
ClassificationEssential
Detailed Description
Log TypeRequiredType of log to be stored
Storage bucket nameRequiredName of the Object Storage bucket to store
Authentication key > Access keyRequiredAccess key to access the Object Storage to be stored
Authentication key > Secret keyRequiredSecret key for accessing the Object Storage to be stored
File Creation CycleRequiredCycle of creating files in Object Storage
Whether to delete the original logSelectWhether to delete the original log 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 these steps.

  1. Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource you want to manage DB log export. It moves to the EPAS(DBaaS) detail page.
  4. Click the More button and click the Export DB Log button. It moves to the Export DB Log page.
  5. On the DB Log Export page, click the More button according to the type of log you want to manage, and then click the Export Now, Modify, or Cancel button.
    • Immediate Export: The selected log is exported to the existing Object Storage’s Bucket.
    • Modify: Modifies the DB log export mode setting.
  • Cancel: Cancels the DB log export mode setting.

Minor Version Upgrade

It provides a version upgrade feature due to some functional improvements and security patches. Only minor version upgrade is supported within the same major version.

Caution
  • Please perform the version upgrade after checking the service status through service status synchronization.
  • Please proceed with the version upgrade after setting up the backup. If you do not set up the backup, you may not be able to recover some data when a problem occurs during the upgrade.
  • In the DB where Replica is configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and perform a version upgrade if necessary.
  • The backed-up data will be automatically deleted after the version upgrade is completed.

To perform a Minor Version upgrade, follow the procedure below.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. Click on the resource to be upgraded on the EPAS(DBaaS) list page. It moves to the EPAS(DBaaS) details page.
  4. Click the Edit button in the Image/Version item. The Version Upgrade popup window opens.
  5. In the 버전 업그레이드 popup window, select the modified version and whether to back up the settings, then click the 확인 button.
  6. In the Version Upgrade Notification popup window, click the OK button.

Configuring Migration

It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.

Notice
Please refer to Architecture Center > Migration Guide for detailed Migration configuration guide.

To configure the migration, follow the next procedure.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. Click on the resource to be migrated on the EPAS(DBaaS) list page. It moves to the EPAS(DBaaS) details page.
  4. Click the More button and click the Migration Settings button. The Migration Settings popup window opens.
  5. Check the instructions in the Migration Configuration popup window and click the OK button. It moves to the Migration Configuration page.
  6. On the Migration Configuration page, enter the information and click the Check Connection button.
  7. Once the connection is complete, click the Complete button.
ClassificationEssential
Detailed Description
Source DB Database namerequiredThe name of the Source DB database that is the target of migration
Source DB IPRequiredIP of the Source DB that is the target of Migration
Source DB PortRequiredPort of the Source DB that is the target of Migration
Source DB usernamerequiredUsername of the Source DB that is the target of migration
Source DB passwordrequiredPassword of the Source DB that is the target of migration
Table. EPAS(DBaaS) Migration Configuration Items

Migrating Cluster to Master Cluster

You can promote a fully configured Migration Cluster to a Master Cluster.

Caution
When Master is promoted, synchronization with the Source DB that becomes the Migration target is stopped.

To promote the Migration Cluster to Master, follow these steps.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. On the EPAS(DBaaS) list page, click the resource to be promoted to Master. It moves to the EPAS(DBaaS) detail page.
  4. Click the More button and click the Master Promotion button. The Master Promotion Notification popup window opens.
  5. In the Master Promotion Alert popup window, click the Confirm button.

1.2.3 - DB Backup and Recovery

The user can set up the backup of EPAS(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.

EPAS(DBaaS) Backup

To ensure that the user’s data is safely stored, EPAS(DBaaS) provides a data backup function based on its own backup command, and also provides a backup history function to check if the backup was done normally, and can also delete the backed-up files.

Setting up backup

The method of setting up a backup for EPAS(DBaaS) is described in EPAS(DBaaS) creation guide.

To modify the backup settings of the generated resource, follow these steps.

Caution
  • For stable backup, it is recommended to add a separate BACKUP storage or sufficiently increase the storage capacity. Especially when the backup target data exceeds 100 GB and there are many data changes, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, refer to the EPAS(DBaaS) Add Storage, EPAS(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.

To set up a backup, follow these steps.

  1. All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. EPAS(DBaaS) list page, click the resource to set the backup. Move to the EPAS(DBaaS) details page.
  4. Click the Edit button of the backup item. The Backup Settings popup window opens.
  5. If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
    • If you want to stop the backup settings, uncheck Backup Settings in the popup window and click the OK button.

Check Backup History

Notice
Additionally, to set up notifications for backup success and failure, you can set them up through the Notification Manager product. For a detailed usage guide on setting up notification policies, please refer to Creating a Notification Policy.

To view the backup history, follow these steps.

  1. All services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. EPAS(DBaaS) list page, click the resource to check the backup history. It moves to the EPAS(DBaaS) detail page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting Backup Files

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please make sure to check if the data is unnecessary before deleting it.
  1. Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. EPAS(DBaaS) list page, click the resource to check the backup history. It moves to the EPAS(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window, check the file you want to delete, and then click the Delete button.

EPAS(DBaaS) Recovery

In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing EPAS (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, and the DB is installed with the version at the backup point, and the recovery proceeds with the DB configuration information and data.

Caution
To perform recovery, a data type with the same capacity as Disk capacity is required. If the Disk capacity is insufficient, recovery may fail.

To recover EPAS(DBaaS), follow these procedures.

  1. Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
  2. Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
  3. EPAS(DBaaS) Resource list page, click the resource you want to restore. It moves to the EPAS(DBaaS) detail page.
  4. Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
  5. Database Recovery Configuration area, enter the corresponding information, and then click the Complete button.
Classification
Necessity
Detailed Description
Recovery TypeRequiredSet the point in time to recover
  • Backup Point (Recommended): Recover based on the backup file. Select from the list of backup file timestamps displayed
  • Custom Point: Recover to the desired point in time within the range where backup is possible. The recoverable period is from the initial backup start time to the current time, 1 hour/30 minutes/10 minutes/5 minutes ago, depending on the Archive backup cycle setting value. Select the date and time you want to backup
Server name prefixRequiredRecovery DB server name
  • Start with lowercase English letters, using lowercase letters, numbers, and special characters (-) to input 3-16 characters
  • A postfix such as 001, 002 is attached based on the server name, and the actual server name is created
Cluster NameRequiredRecovery DB Cluster Name
  • Enter in English, 3-20 characters
  • A cluster is a unit that bundles multiple servers
Service Type > Server TypeRequiredRecovery DB Server Type
  • Standard: Generally used standard specification
  • High Capacity: High-capacity server with 24vCore or more
Service Type > Planned ComputeSelectCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are in use
  • Setting: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by resource-based Planned Compute
  • Create Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
  • Default OS: Area where the DB engine is installed
  • DATA: Storage area for table data, archive files, etc.
    • Applied identically to the Storage type set in the original cluster
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Additional: Storage area for DATA, Archive, TEMP, Backup data
    • Applied identically to the Storage type set in the original cluster
    • Only DATA, TEMP, and Archive purposes can be added in the recovery DB
    • Select Use and enter the purpose and capacity of the storage
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Database usernamerequiredDatabase username
  • Applied identically to the username set in the original cluster
Database Port NumberrequiredDatabase Port Number
  • Apply the same port number set in the original cluster
IP Access ControlSelectSet Service Access Policy
  • Set access policy for IP entered on the page, so separate Security Group policy setting is not required
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectDB maintenance period
  • Use Select the day, start time, and duration
  • It is recommended to set the maintenance period for stable DB management. Patch work will be carried out at the set time and service interruption will occur
  • If set to not in use, the company will not be responsible for any problems that occur due to non-application of patches.
TagSelectAdd Tag
  • Click the Add Tag button and enter or select Key, Value
Fig. EPAS(DBaaS) Recovery Configuration Items

1.2.4 - Configuring Read Replica

Users can create a Read Replica by entering the required information through the Samsung Cloud Platform Console and configuring detailed options.

Configuring Replica

Replica configuration allows you to create a read-only replica server. You can create up to 5 replicas per database.

To configure a replica, follow these steps:

  1. All Services > Database > EPAS(DBaaS) menu, click. Move to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. Move to the EPAS(DBaaS) List page.
  3. On the EPAS(DBaaS) List page, click the resource you want to configure the replica for. Move to the EPAS(DBaaS) Details page.
  4. Click the Configure Replica button. Move to the Configure Replica page.
  5. Enter the information in the Configure Replica section and click the Complete button.
Category
Required
Detailed Description
Number of ReplicasRequiredThe number of replicas to configure
  • Up to 5 replicas can be configured per cluster.
  • If you select 2 or more values, you need to enter additional information such as replica name and service type.
Replica NameRequiredThe name of the replica server
  • Start with a lowercase letter, and use lowercase letters, numbers, and special characters (-) to enter 3-19 characters.
  • The entered replica name will be exposed as the cluster name in the list.
Service Type > Server TypeRequiredThe type of replica server
  • Standard: Standard specification commonly used
  • High Capacity: High-capacity server with 24vCore or more
Service Type > Planned ComputeOptionalThe current status of resources with Planned Compute set
  • In Use: The number of resources with Planned Compute set that are in use
  • Set: The number of resources with Planned Compute set
  • Coverage Preview: The amount applied to each resource with Planned Compute
  • Apply for Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredBlock storage settings for the replica DB
  • Basic OS: The area where the DB engine is installed
  • DATA: The storage area for table data and archive files, etc.
    • Applied equally to the storage type set in the original cluster
    • Capacity settings are not available
  • Additional: Storage area for DATA, Archive, TEMP, and Backup data
    • Applied equally to the storage type set in the original DB
    • Only DATA and TEMP purposes can be added in the replica.
    • Select Use and enter the purpose and capacity of the storage. The capacity can be entered in the range of 16 to 5,120 in multiples of 8.
    • To add storage, click the + button, and to delete, click the x button. Up to 9 can be added.
IP Access ControlOptionalService access policy setting
  • Access policy is set for the IP entered on the page, so you do not need to set a separate Security Group policy.
  • Enter the 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 the entered IP, click the x button next to the entered IP
Maintenance PeriodOptionalDB maintenance period
  • Use: Select the day of the week, start time, and period
  • It is recommended to set the maintenance period for stable DB management. Patch work will be done during the set time, and the service will be suspended.
  • If not used, the company is not responsible for any problems that occur due to non-application of patches.
Table. EPAS(DBaaS) Replica Configuration Items

Reconfiguring Replica

If a network failure or replication delay occurs between the master cluster, you can reconfigure the replica to re-replicate the master cluster’s data.

To reconfigure a replica, follow these steps:

  1. All Services > Database > EPAS(DBaaS) menu, click. Move to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. Move to the EPAS(DBaaS) List page.
  3. On the EPAS(DBaaS) List page, click the resource you want to reconfigure the replica for. Move to the EPAS(DBaaS) Details page.
  4. Click the Reconfigure Replica button. The Reconfigure Replica Notification popup window opens.
  5. In the Reconfigure Replica Notification popup window, click the Confirm button.

Promoting Replica Cluster to Master

You can promote a configured replica cluster to a master cluster.

Note
When promoting to a master, synchronization with the existing master cluster will be terminated.

To promote a replica cluster to a master, follow these steps:

  1. All Services > Database > EPAS(DBaaS) menu, click. Move to the Service Home page of EPAS(DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. Move to the EPAS(DBaaS) List page.
  3. On the EPAS(DBaaS) List page, click the resource you want to promote to a master. Move to the EPAS(DBaaS) Details page.
  4. Click the More button and then click the Promote to Master button. The Promote to Master Notification popup window opens.
  5. In the Promote to Master Notification popup window, click the Confirm button.

1.2.5 - Extension use

EPAS(DBaaS) Extension usage

Note
The list of extensions included in each EPAS version can be found on the PostgreSQL official page.

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

SQL> select * from pg_available_extensions;

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

Extension NameDescription
pg_crona scheduler that allows job scheduling with cron syntax within the database
pgvectorVector data type and similarity search, etc. AI vector operation function provided
postgisGIS (Geographic Information System) provides spatial object storage and spatial query functionality
Table. EPAS(DBaaS) Extension Basic Installation Items

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

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

1.3 - API Reference

API

1.4 - CLI Reference

CLI Reference

1.5 - Release Note

EPAS(DBaaS)

2025.07.01
FEATURE User (Access Control) Management, Archive Setting Function, DB Audit Log Export Function Added, Backup Notification Function Provided, Migration Function Added
  • EPAS(DBaaS) feature added
    • 2nd generation server type added
  • Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see EPAS(DBaaS) server type
    • DB user and access control management and Archive setting function added
  • For more information, see DB User Management, DB Access Control Management, Archive Management
    • DB Audit Log Export feature added
  • For more information, see DB Log Export
    • Backup Notification Feature provided
  • Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
    • Migration feature added
  • Provides replication-based zero-downtime data migration feature. For more information, see Migration 구성하기
    • Block Storage type added HDD, HDD_KMS type
2025.02.27
NEW EPAS(DBaaS) Service Official Version Release
  • EPAS(DBaaS) service that can easily create and manage EPAS in a web environment has been released.

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 can automate PostgreSQL installation through a web-based console and perform 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 content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read‑only servers called Replicas are provided for read‑load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user‑specified times, enabling data recovery to a desired point in time.

Architecture
Figure. PostgreSQL(DBaaS) Architecture

Provided Features

PostgreSQL (DBaaS) provides the following features.

  • Auto Provisioning (Auto Provisioning): It is possible to install and configure the Database (DB) via UI, and it provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, 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, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Active-Standby via Switch-over.
  • Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage organization can be set by the user, and additional fees are incurred based on backup size. It also provides a recovery function for backed-up data, so when the user performs a recovery, a separate DB is created and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). If the user restores to a specified point, the recovery point can be set to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup file and archive file.
  • Version Management: Provides version upgrade (Minor) functionality due to some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
  • Replica configuration: For read load balancing and disaster recovery (DR), up to 5 Read Replicas can be configured in the same/different region.
  • Audit Settings: Supports audit (Audit) functionality for major activities within the database.
  • Parameter Management: Performance improvement and security-related DB configuration parameters can be modified.
  • Service Status Query: Retrieve the final status of the current DB service.
  • Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
  • DB User Management: Retrieve 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 IPs.
  • Archive Management: You can set the retention period of Archive files (1 day~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: Synchronize data in real time with the operating database, and support migration using the Replication method without service interruption.

Components

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

Engine Version

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

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped 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.

Provided VersionEOS Date(Samsung Cloud Platform New Creation Stop Date)EoTS Date(Community Technical Support End Date)
14.172026-06 (scheduled)2026-11-12
14.182026-06 (scheduled)2026-11-12
15.122027-06 (scheduled)2027-11-11
15.132027-06 (scheduled)2027-11-11
16.82028-06 (scheduled)2028-11-09
16.92028-06 (scheduled)2028-11-09
Table. PostgreSQL (DBaaS) provided engine versions

Server Type

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

For detailed information about the server types provided by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) server type.

Standard db1v2m4







Category Example Detailed description
Server Type Standard Provided Server Types
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
  • High Capacity: Large-capacity server specifications of 24 vCores or more
Server specifications db1 Provided server specifications
  • db1: Standard specifications (vCPU, Memory) configuration 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. PostgreSQL (DBaaS) server type components
# Preliminary Service This is a list of services that must be pre-configured before creating the service. For details, please refer to the guide provided for each service and prepare in advance.<br>
Service Category Service Detailed Description
Networking VPC A service that provides an isolated virtual network in a cloud environment
Table. PostgreSQL(DBaaS) Pre-service

2.1.1 - Server Type

PostgreSQL(DBaaS) server type

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

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

Standard db1v2m4
Classification
ExampleDetailed Description
Server TypeStandardProvided server type distinction
  • Standard: Composed of standard specifications (vCPU, Memory) commonly used
  • High Capacity: Server specifications with higher capacity than Standard
Server specificationdb1Provided server type distinction and generation
  • db: means general specification, and 1 means generation
  • dbh: h means large-capacity server specification, and 2 means generation
Server specificationv2Number of vCores
  • v2: 2 virtual cores
Server specificationm4Memory capacity
  • m4: 4GB Memory
Fig. PostgreSQL(DBaaS) server type format

db1 server type

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

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

ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. PostgreSQL(DBaaS) server type specifications - db1 server type

dbh2 server type

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

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

ClassificationServer TypevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBUp to 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBUp to 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBUp to 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBUp to 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBUp to 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBUp to 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBUp to 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBUp to 25 Gbps
Table. PostgreSQL(DBaaS) server type specifications - dbh2 server type

2.1.2 - Monitoring Metrics

PostgreSQL(DBaaS) Monitoring Metrics

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

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

Performance ItemDetailed DescriptionUnit
Active LocksNumber of Active Lockscnt
Active Locks [Access Exclusive]Number of Access Exclusive Lockscnt
Active Locks [Access Share]Number of Access Share Lockscnt
Active Locks [Total]Total Number of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Active Sessions [Total]Total Number of Active Sessionscnt
Apply Lag TimeApply Lag Timemin
Check No ReplicationCheck No Replication Valuecnt
Check ReplicationCheck Replication Status Valuestatus
Connection UsageDB Connection Usage Rate (%)%
Connection Usage [Total]DB Connection Usage Rate (%)%
DB Age MaxDatabase Age (Frozen XID) Valueage
Exclusive LocksNumber of Exclusive Lockscnt
Idle In Transaction SessionsNumber of Idle In Transaction Sessionscnt
Idle In Transaction Sessions [Total]Total Number of Idle In Transaction Sessionscnt
Idle SessionsNumber of Idle Sessionscnt
Idle Sessions [Total]Total Number of Idle Sessionscnt
Row Exclusive LocksNumber of Row Exclusive Lockscnt
Row Share LocksNumber of Row Share Lockscnt
Share LocksNumber of Share Lockscnt
Share Row Exclusive LocksNumber of Share Row Exclusive Lockscnt
Share Update Exclusive LocksNumber of Share Update Exclusive Lockscnt
SlowqueriesNumber of Long-Running SQL Queries (over 5 minutes)cnt
Tablespace UsedTable Space Sizebytes
Tablespace Used [Total]Table Space Sizebytes
Tablespace Used Bytes [MB]File System Directory Usage (MB)MB
Tablespaces [Total]File System Directory Usage (MB)MB
Transaction Time Max [Long]Longest Running Transaction Time (minutes)min
Transaction Time Max Total [Long]Longest Running Transaction Time (minutes)min
Wait LocksNumber of Sessions Waiting for Locks (per DB)cnt
Wait Locks [Long Total]Number of Sessions Waiting for Locks for a Long Time (over 300 seconds)cnt
Wait Locks [Long]Number of Sessions Waiting for Lockscnt
Wait Locks [Total]Total Number of Sessions Waiting for Lockscnt
Waiting SessionsNumber of Waiting Sessionscnt
Waiting Sessions [Total]Total Number of Waiting Sessionscnt
Table. PostgreSQL(DBaaS) Monitoring Metrics

2.2 - How-to guides

Users can enter the required information for PostgreSQL (DBaaS) through the Samsung Cloud Platform Console, select detailed options, and create the service.

Creating PostgreSQL(DBaaS)

You can create and use PostgreSQL (DBaaS) services from the Samsung Cloud Platform Console.

Guide
  • Please configure the VPC’s Subnet type as General before creating the service.
    • If the Subnet type is Local, the creation of the corresponding Database service is not possible.
  • If you load more than 2 TB of large data, backup may take a long time or the DB performance itself may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.

To create PostgreSQL (DBaaS), follow the steps below.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Go to the Service Home page of PostgreSQL(DBaaS).

  2. Click the PostgreSQL(DBaaS) Create button on the Service Home page. Navigate to the PostgreSQL(DBaaS) Create page.

  3. PostgreSQL(DBaaS) Creation on the page, enter the information required to create the service, and select detailed options.

    • Image and version selection Select the required information in the area.
      Category
      Required or not
      Detailed description
      Image versionRequiredProvide version list of PostgreSQL (DBaaS)
      Table. PostgreSQL (DBaaS) image and version selection items
    • Service Information Input Enter or select the required information in the area.
      Category
      Required or not
      Detailed description
      Server Name PrefixRequiredServer name where DB will be installed
      • Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (-) to input 3 to 13 characters
      • Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
      Cluster NameRequiredCluster name of DB servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type where DB will be installed
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server of 24 vCore or more
      Service Type > Planned ComputeSelectStatus 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 by Planned Compute per resource
      • Create Planned Compute Service: Go to the Planned Compute service application page
      Service Type > Block StorageRequiredSet Block Storage used by DB according to purpose
      • Base OS: Area where DB engine is installed
      • DATA: Storage area for table data, archive files, etc.
        • After selecting storage type, enter capacity (refer to Create Block Storage for details of each Block Storage type)
          • SSD: High-performance general volume
          • HDD: General volume
          • SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption keys
        • The configured storage type is applied identically to additional storage
        • Capacity must be entered as a multiple of 8 within the range 16 ~ 5,120
        • Because large sorts from SQL execution or monthly batch may cause service interruption, a separate TEMP storage must be allocated and used
        • Add: DATA, Archive, TEMP, Backup data storage areas
          • After selecting Use, enter the storage’s purpose and capacity
          • The storage type is the same as set for DATA, and capacity can be entered as a multiple of 8 within 16 ~ 5,120
          • Click the + button to add storage, x button to delete. Up to 9 can be added
          • Backup data is temporarily stored in BACKUP storage before transmission
            • If backup data exceeds 100 GB and changes frequently, it is recommended to add a separate BACKUP storage for reliable backup; set backup capacity to about 60% of DATA capacity
            • If BACKUP storage is not added, using the /tmp area is recommended
          • For each service, Archive, TEMP, BACKUP storages are allocated only one Block Storage
      Redundancy ConfigurationSelectRedundancy Configuration Status
      • If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
      Network > Common SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply the same settings to all servers being installed
      • Select a pre-created VPC, Subnet, IP, Public NAT
        • IP can only be auto-generated
        • 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 details, see Create Public IP
      Network > Server-specific SettingsRequiredNetwork 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 details, see Create Public IP.
      IP Access ControlSelectService Access Policy Settings
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      Maintenance PeriodSelectDB Maintenance Period
      • If Use is selected, set the day of the week, start time, and duration.
      • It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption.
      • If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied.
      Table. PostgreSQL(DBaaS) Service Information Input Items
    • Database Configuration Required Information Input In the area, please enter or select the required information.
      Category
      Required or not
      Detailed description
      Database nameRequiredServer name applied when installing DB
      • Start with English letters, use English letters and numbers, input 3 ~ 20 characters
      Database usernameRequiredDB user name
      • An account with that name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted Database usernames can be checked in the Console
      Database PasswordRequiredPassword to use when accessing the DB
      • Enter 8~30 characters including letters, numbers, and special characters (excluding “ and ‘)
      Database password verificationRequiredRe-enter the same password to be used for DB access
      Database Port numberRequiredPort number required for DB connection
      • Enter DB port within the range 1,024 ~ 65,535
      Backup > UseSelectWhether to use backup
      • Use to set backup file retention period, backup start time, Archive backup cycle
      Backup > Retention PeriodSelectBackup Retention Period
      • Select the backup retention period, set the file retention period from 7 days to 35 days
      • Backup files are charged separately based on size
      Backup > Backup Start PeriodSelectBackup Start Time
      • Select backup start time
      • The minutes at which the backup runs are set randomly, and the backup end time cannot be set
      Backup > Archive Backup FrequencySelectArchive Backup Frequency
      • Select the Archive Backup Frequency
      • Archive Backup Frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
      Audit Log SettingsSelectWhether to store Audit Log
      • Enable to configure the Audit Log feature
        • DDL, DML, and user connection information records are stored
          • Users can specify the type of SQL statements to audit via the log_statement parameter, and can modify it through the Parameter screen
        • Enabling Audit may degrade DB performance
      ParameterRequiredParameters to use in the DB
      • Click the Search button to view detailed information of the parameters
      • Parameters can be modified after DB creation is complete, and the DB must be restarted after modification
      Database EncodingRequiredCharacter 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 LocaleRequiredLocale to use for DB
      • Settings related to string processing, number/currency/date/time display formats, etc.
      • The DB is created with default settings using the selected Locale
      Time zoneRequiredStandard time zone to be used by the Database
      Table. PostgreSQL(DBaaS) Database configuration items
    • Additional Information Input Enter or select the required information in the area.
      Category
      Required or not
      Detailed description
      TagSelectAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. PostgreSQL(DBaaS) Additional Information Input Items
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.

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

PostgreSQL(DBaaS) Check detailed information

PostgreSQL(DBaaS) service can view and edit the full resource list and detailed information. PostgreSQL(DBaaS) Details page consists of Details, Tags, Activity History tabs, and for databases with a Replica configured, a Replica Information tab is additionally provided.

To view detailed information of the PostgreSQL (DBaaS) service, follow the steps below.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Move to the PostgreSQL(DBaaS) List page.
  3. Click the resource to view detailed information on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  • PostgreSQL(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
    CategoryDetailed description
    Cluster StatusCluster status with DB installed
    • Creating: Cluster is being created
    • Editing: Cluster is changing to operation execution state
    • Error: Cluster encountered an error while performing tasks
      • If it occurs continuously, 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 being stopped
    • Synchronizing: Cluster is being synchronized
    • Terminating: Cluster is being deleted
    • Unknown: Cluster status is unknown
      • If it occurs continuously, contact the administrator
    • Upgrading: Cluster is changing to upgrade execution state
    Cluster ControlButtons to change 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 functionsCluster related management buttons
    • Service status synchronization: View real-time DB service status
    • Backup history: If backup is set, check whether backup runs normally and view history
    • Database recovery: Recover DB based on a specific point in time
    • Parameter management: View and modify DB configuration parameters
    • Replica configuration: Configure a read-only cluster Replica; if there is no region to configure for the account, the button is disabled
    • Replica configuration (Other Region): Configure a disaster recovery Replica in another region
    • 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 period and archive mode
    • Export DB Log: Export logs stored via audit settings to the user’s Object Storage
    • Migration configuration: Provide migration function using replication method
    Service cancellationButton to cancel the service
    Table. PostgreSQL(DBaaS) status information and additional features

Detailed Information

PostgreSQL(DBaaS) List On the page, you can view detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
Server InformationServer information configured in the respective cluster
  • Category: Server type (Active, Standby, Replica)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In DB service, it means cluster SRN
Resource NameResource Name
  • In DB service, it means the cluster name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
EditorUser who modified the service information
Modification DateTimeDate and time the service information was modified
Image/VersionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to set
Cluster TypeCluster Type (Master Cluster, Replica Cluster, Migration Cluster)
Cluster NameName of the cluster composed of DB servers
Master cluster nameReplica’s Master cluster name
  • If it is detailed information of the Replica, it can be checked.
Database nameServer name applied when installing DB
Database usernameDB user name
Planned ComputeResource status with Planned Compute set
Maintenance PeriodDB Patch Work Period Setting Status
  • If maintenance period setting is required, click the Edit icon to set
BackupBackup configuration status
  • If backup configuration is needed, click the Edit icon to set
Audit Log SettingsAudit Log Settings Status
  • If Audit Log settings are needed, click the Edit icon to configure
Time zoneStandard time zone used by the Database
DB LocaleLocale to use for DB
Database EncodingCharacter encoding method to be used in DB
VIPVirtual IP information
  • Can be checked only when redundancy is configured
NetworkNetwork information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP Access ControlService Access Policy Settings
  • If you need to add or delete an IP, click the Edit icon to set
Active & StandbyActive/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 set it. Refer to Change Server Type for the server type modification procedure
    • 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 Expand Storage for the storage expansion procedure
  • If you need to add storage, click the Add Disk button next to Additional Disk to add. Refer to Add Storage for the storage addition procedure
Table. PostgreSQL(DBaaS) Database detailed information items

Replica Information

Replica Information tab is enabled only when a Replica is configured in the cluster. Through the Replica Information tab, you can check the master cluster name, the number of replicas, and the replication status of the Replica.

CategoryDetailed description
Master informationName of the Master cluster
Replica countNumber of Replicas created in the Master cluster
Replica statusReplica server status created in the Master cluster
  • Server name, status query, status details, and status check time can be viewed
  • To query the Replica status, click the Status Query button
    • While querying, the cluster remains in Synchronizing state, and once the query is complete, 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.

CategoryDetailed description
Tag ListTag List
  • Tag Key and Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from existing Key and Value lists
Table. PostgreSQL(DBaaS) Tag tab items

Work History

You can view the operation history of the selected resource on the PostgreSQL(DBaaS) List page.

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, Resource ID, Resource name, Work details, Event topic, Work result, Operator information verification
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 work on the PostgreSQL (DBaaS) Details page.

Operating Control

If changes occur to the running PostgreSQL (DBaaS) resources, you can start, stop, or restart them. Also, if 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.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) List Click the resource to control operation on the page. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Check the PostgreSQL(DBaaS) status and complete the change using the control button below.
    • Start: The server where the DB service is installed and the DB service is 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.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Go to the Service Home page of PostgreSQL(DBaaS).
  2. Service Home page, click the PostgreSQL(DBaaS) menu. Navigate to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) List Click the resource to view the service status on the page. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Service status synchronization Click the button. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query is completed, the status is updated in the server information item, 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 reboot is required. Please separately verify any changes to SW licenses or SW settings and reflections due to changes in server specifications.

To change the server type, follow the steps below.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
  3. PostgreSQL(DBaaS) 목록 Click the resource to change the server type on the page. PostgreSQL(DBaaS) 상세 Navigate to the page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
  5. Server Type Edit After selecting the server type in the popup window, click the Confirm button.

Add storage

If you need more than 5 TB of data storage space, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.

Caution
  • It is applied the same way as the selected Storage type when creating a service.
  • In the case of a DB configured for redundancy, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
  • If a Replica exists, the Master cluster’s storage cannot be larger than the Replica’s storage. Expand the Replica storage first, then expand the Master cluster storage.
  • When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.

To add storage, follow the steps below.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Go to the PostgreSQL(DBaaS) List page.
  3. PostgreSQL(DBaaS) List on the page, click the resource to add storage. PostgreSQL(DBaaS) Details navigate to the page.
  4. At the bottom of the detailed information, click the Add Disk button. The Add Storage Request popup window opens.
  5. Additional Storage Request After entering purpose and capacity in the popup window, click the Confirm button.

Expanding storage

You can expand the storage added to the data area 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.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Go to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) List page, click the resource to change the server type. You will be taken to the PostgreSQL(DBaaS) Details page.
  4. Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. Edit Additional Storage popup window opens.
  5. Add Storage Modification In the popup window, after entering the expansion capacity, click the Confirm button.

PostgreSQL(DBaaS) Cancel

You can cancel unused PostgreSQL (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, terminate it separately from the resource list.
  • If you terminate the DB, stored data and, if backup is set, all backup data will be deleted.

To cancel PostgreSQL (DBaaS), follow the steps below.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Service Home page, click the PostgreSQL(DBaaS) menu. Navigate to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
  4. When the 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

It provides a feature to easily view and modify database configuration parameters.

Viewing Parameters

To view configuration parameters, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.

Modifying Parameters

To modify configuration parameters, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.
  7. If modification is required, click the Modify button and enter the modification details in the custom value area of the parameter to be modified.
  8. When the input is complete, click the Save button.

Managing DB Users

It provides a management feature that allows you to view DB user information and change status information.

Viewing DB Users

To view DB users, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
  3. Click the resource you want to view DB users on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. It moves to the DB User Management page.
  5. Click the View button on the DB User Management page. It takes some time to view.

Changing DB User Status

To change the status of the viewed DB user, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
  3. Click the resource you want to modify DB users on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. It moves to the DB User Management page.
  5. Click the View button on the DB User Management page. It takes some time to view.
  6. If modification is required, click the Modify button and change the status value or enter notes.
  7. When the input is complete, click the Save button.

Managing DB Access Control

It provides an IP-based DB user access control management feature. Users can directly specify the IP that can access the database, allowing only allowed IPs to access.

Notice
Before setting DB access control, perform DB user inquiry. For DB user inquiry, refer to Managing DB Users.

Viewing DB Access Control

To view DB users with IP access control set, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
  3. Click the resource you want to manage access control on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. Click the View button on the DB Access Control Management page. It takes some time to view.

Adding DB Access Control

To add IP access control, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
  3. Click the resource you want to add IP access control on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. Click the View button on the DB Access Control Management page. It takes some time to view.
  6. When the view is complete, click the Add button. The DB Access Control Add popup window opens.
  7. In the DB Access Control Add popup window, select the DB user name and enter the IP address.
  8. When the input is complete, click the Save button.

Deleting DB Access Control

To delete IP access control, follow these steps:

  1. All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource for which you want to delete IP access control. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the Inquire button. It takes some time to inquire.
  6. Once the inquiry is complete, click the Delete button. The Delete pop-up window opens.
  7. In the Delete pop-up window, click the Confirm button.

Managing Archive

It provides functions to set Archive mode and Archive log retention period, allowing users to flexibly set Archive log management policies according to their operating environment. Additionally, it provides a function to manually delete Archive logs, allowing users to clean up unnecessary log data and effectively manage system resources.

Notice
When creating a service, the default setting is to use Archive mode, with a retention period of 3 days.

Setting Archive Mode

To set Archive mode, follow these steps:

  1. All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource for which you want to set Archive mode. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the Archive Settings Management button. It moves to the Archive Settings Management page.
  5. On the Archive Settings Management page, click the Inquire button. It takes some time to inquire.
  6. Click the Modify button and select the usage and retention period.
  7. Once the modification is complete, click the Save button.

Deleting Archive Files

To delete Archive files, follow these steps:

  1. All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource for which you want to set Archive mode. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the Archive Settings Management button. It moves to the Archive Settings Management page.
  5. On the Archive Settings Management page, click the Delete All Archives button to delete all Archive files, or click the Delete Backed-up Archives button to delete only backed-up Archive files.

Exporting DB Logs

It supports exporting audit logs that require long-term storage to Object Storage. Users can directly set the type of log to be stored, the target Bucket, and the frequency of log export. According to the set criteria, it copies the logs to the specified Object Storage for storage. Additionally, to efficiently manage disk space, it provides an option to automatically delete the original log files when exporting logs to Object Storage. By utilizing this option, users can effectively secure storage capacity while safely storing necessary log data for long-term storage.

Notice
  • To use the DB Log export function, Object Storage creation is required. Refer to the Object Storage User Guide for Object Storage creation.
  • Be sure to check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the Bucket.
  • Be cautious not to expose authentication key information to the outside.

Setting DB Log Export Mode

To set DB Log export mode, follow these steps:

  1. All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource for which you want to export DB logs. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the DB Log Export button. It moves to the DB Log Export page.
  5. On the DB Log Export page, click the Register button. It moves to the DB Log Export Registration page.
  6. On the DB Log Export Registration page, enter the corresponding information and click the Save button.
CategoryRequired
Detailed Description
Log TypeRequiredType of log to be stored
Storage Bucket NameRequiredName of the Object Storage Bucket to store
Authentication Key > Access KeyRequiredAccess key to access the Object Storage to store
Authentication Key > Secret KeyRequiredSecret key to access the Object Storage to store
File Creation CycleRequiredCycle to create files in Object Storage
Original Log DeletionOptionalWhether to delete the original log when exporting to Object Storage
Table. PostgreSQL(DBaaS) Migration Configuration Items

Managing DB Log Export

To modify, cancel, or immediately export DB log settings, follow these steps:

  1. All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource for which you want to manage DB log export. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the DB Log Export button. It moves to the DB Log Export page.
  5. On the DB Log Export page, click the More button for the log type you want to manage, and then click the Immediate Export, Modify, or Cancel button.
    • Immediate Export: Exports the selected log to the Object Storage Bucket set earlier.
    • Modify: Modifies the DB log export mode setting.
    • Cancel: Cancels the DB log export mode setting.

Upgrading DB Version

It provides a version upgrade function due to some feature improvements and security patches. Only minor version upgrades are supported within the same major version.

Caution
  • Please perform version upgrades after checking the service status through service status synchronization.
  • Please set up backups before performing version upgrades. If backups are not set up, some data may not be recoverable in case of problems during updates.
  • In DBs with Replicas configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and perform version upgrades if necessary.
  • Backed-up data will be automatically deleted after version upgrade completion.

To upgrade the version, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource to upgrade the version. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the Modify button in the image/version item. The Version Upgrade popup window opens.
  5. In the Version Upgrade popup window, select the version to modify and whether to set backup, and then click the Confirm button.
  6. In the Version Upgrade Notification popup window, click the Confirm button.

Configuring Migration

It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.

Notice
For a detailed migration configuration guide, please refer to Architecture Center > Migration Guide > Database Migration Procedure and Considerations.

To configure migration, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource to migrate. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the Configure Migration button. The Configure Migration popup window opens.
  5. In the Configure Migration popup window, check the instructions and click the Confirm button. It moves to the Configure Migration page.
  6. On the Configure Migration page, enter the corresponding information and click the Connect Check button.
  7. When the connection is complete, click the Complete button.
ClassificationRequired
Detailed Description
Source DB Database NameRequiredDatabase name of the source DB that is the migration target
Source DB IPRequiredIP of the source DB that is the migration target
Source DB PortRequiredPort of the source DB that is the migration target
Source DB User NameRequiredUser name of the source DB that is the migration target
Source DB PasswordRequiredPassword of the source DB that is the migration target
Table. PostgreSQL(DBaaS) Migration Configuration Items

The configured migration cluster can be promoted to a master cluster.

Caution
When promoting to master, synchronization with the source DB that is the migration target will be terminated.

To promote the migration cluster to master, follow these steps:

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. On the PostgreSQL(DBaaS) list page, click the resource to promote to master. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the More button and then click the Promote to Master button. The Promote to Master Notification popup window opens.
  5. In the Promote to Master Notification popup window, click the Confirm button.

2.2.2 - DB Backup and Recovery

The user can set up a backup of PostgreSQL(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.

PostgreSQL(DBaaS) backup

PostgreSQL(DBaaS) provides a data backup feature based on its own backup command, and also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.

Setting up backup

The method of setting up a backup of PostgreSQL(DBaaS) is described in PostgreSQL(DBaaS) creation guide.

To modify the backup settings of the generated resource, follow these steps.

Caution
  • For stable backup, it is recommended to add a separate BACKUP storage or to sufficiently expand the storage capacity. Especially when the backup target data exceeds 100 GB and there are many data changes, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, refer to the PostgreSQL(DBaaS) Add Storage, PostgreSQL(DBaaS) Expand Storage guides.
  • If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.

To set up a backup, follow these steps.

  1. All Services > Database > PostgreSQL(DBaaS) menu is clicked. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) list page, click the resource to set the backup. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the Edit button of the backup item. The Backup Settings popup window will open.
  5. If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the Confirm button.
    • If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.

Check Backup History

Notice
To set up notifications for backup success and failure, you can set it up through the Notification Manager product. For a detailed usage guide on setting up notification policies, please refer to Creating a Notification Policy.

To view the backup history, follow these steps.

  1. 모든 서비스 > Database > PostgreSQL(DBaaS) menu should be clicked. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) list page, click the resource to check the backup history. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window will open.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting backup files

Caution
Backup files cannot be restored after deletion. Please make sure to confirm if the data is unnecessary before deleting it.

To delete the backup history, follow these steps.

  1. All services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) list page, click the resource to check the backup history. It moves to the PostgreSQL(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window, check the file you want to delete, and then click the Delete button.

PostgreSQL(DBaaS) recovery

In the event of a failure or data loss that requires restoration from a backup file, the recovery function can be used to restore to a specific point in time. When performing a PostgreSQL (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, the DB is installed with the version at the backup point, and the recovery proceeds with the DB configuration information and data.

Caution
To perform recovery, at least the same capacity as the data type Disk capacity is required. If the Disk capacity is insufficient, recovery may fail.

To restore PostgreSQL(DBaaS), follow these steps.

  1. All services > Database > PostgreSQL(DBaaS) menu is clicked. It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) resource list page, click the resource you want to restore. It moves to the PostgreSQL(DBaaS) detail page.
  4. Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
  5. Database Recovery Configuration area, enter the corresponding information, and then click the Complete button.
Classification
Necessity
Detailed Description
Recovery TypeRequiredSet the point in time 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 in time within the range where backup is possible. The recoverable period is based on the Archive backup cycle setting value, and can be recovered up to 1 hour/30 minutes/10 minutes/5 minutes before the current time from the initial backup start time. Select the date and time you want to back up
Server name prefixRequiredServer name of the recovery DB
  • Start with lowercase English letters, using lowercase letters, numbers, and special characters (-) to input 3-16 characters
  • A postfix such as 001, 002 is attached based on the server name, and the actual server name is created
Cluster NameRequiredCluster name of the recovery DB
  • Enter in English, 3-20 characters
  • Cluster is a unit that bundles multiple servers
Service Type > Server TypeRequiredServer type where the recovery DB will be installed
  • Standard: Standard specification commonly used
  • High Capacity: High-capacity server with 24vCore or more
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are in use
  • Settings: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
  • Create Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredRecovery DB uses Block Storage settings
  • Basic OS: Area where the DB engine is installed
  • DATA: Area for storing table data, archive files, etc.
    • The storage type set in the original cluster is applied identically
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Additional: DATA, Archive, TEMP, Backup data storage area
    • The storage type set in the original cluster is applied identically
    • In the recovery DB, only DATA, TEMP, and Archive purposes can be added.
    • After selecting Use, enter the purpose and capacity of the storage
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Database usernamerequiredDatabase username set in the original DB
Database Port numberrequiredDatabase Port number set in the original DB
IP Access ControlSelectIP address to access the recovery DB
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.1/32, 192.168.10.1/32) and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectDB maintenance period
  • Use is selected, set the day of the week, start time, and duration
  • It is recommended to set the maintenance period for stable management of the DB. Patch work is performed at the set time and service interruption occurs
  • If set to unused, Samsung SDS is not responsible for any problems that occur due to non-application of patches.
TagSelectAdd Tag
  • Click the Add Tag button and enter or select Key, Value
Fig. PostgreSQL(DBaaS) Recovery Configuration Items

2.2.3 - Read Replica Setup

The user can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.

Replica Configure

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

Notice
To configure a replica for disaster recovery, please create it via Replica Configuration (Other Region).

To configure a replica, follow these steps.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Go to the PostgreSQL(DBaaS) List page.
  3. PostgreSQL(DBaaS) List Click the resource to configure the replica on the page. PostgreSQL(DBaaS) Detail Navigate to the page.
  4. Click the Replica configuration button. Navigate to the Replica configuration page.
  5. Replica configuration After entering information in the area, click the Complete button.
    Category
    Required
    Detailed description
    RegionRequiredRegion to configure Replica
    • Replica configuration (Other Region) displayed only when selected
    Number of ReplicasRequiredNumber of Replicas to configure
    • Up to 5 can be configured per cluster
    • If selecting more than 2 values, additionally input Replica name and service type information
    Replica nameRequiredReplica server name
    • Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (-) to input 3 to 19 characters
    • The entered Replica name is displayed as the cluster name in the list
    Service Type > Server TypeRequiredReplica Server Type
    • Standard: Standard specifications commonly used
    • High Capacity: Large-capacity server with 24 vCore or more
    Service Type > Planned ComputeOptionalStatus 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
    IP Access ControlSelectService Access Policy Settings
    • Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required
    • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    Maintenance PeriodSelectDB Maintenance Period
    • If Use is selected, set the day of the week, start time, and duration.
    • It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption.
    • If set to not use, we are not responsible for issues arising from patches not being applied.
    TagSelectAdd Tag
    • Add Tag button click then input or select Key, Value values
    Table. PostgreSQL(DBaaS) Replica configuration items

Replica Reconstruct

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 function.

To reconstruct the Replica, follow these steps.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Go to the Service Home page of PostgreSQL(DBaaS).
  2. Service Home page, click the PostgreSQL(DBaaS) menu. Move to the PostgreSQL(DBaaS) list page.
  3. PostgreSQL(DBaaS) list page, click the resource to reconfigure the Replica. PostgreSQL(DBaaS) details page will be opened.
  4. Replica reconstruction Click the button. Replica reconstruction notification A popup window opens.
  5. Replica Reconstruction Notification in the popup window click the Confirm button.

Promote Replica Cluster to Master Cluster

You can promote a Replica Cluster that has completed configuration to a Master Cluster.

Caution
When Master promotion occurs, synchronization with the existing Master Cluster is stopped.

To promote a Replica Cluster to Master, follow these steps.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
  3. Click the resource to promote to Master on the PostgreSQL(DBaaS) List page. You will be taken to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and click the Master promotion button. The Master promotion notification popup window opens.
  5. Master Promotion Notification in the popup window click the Confirm button.

2.2.4 - Connect to DB Server

Scenario Overview

The PostgreSQL(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To securely access PostgreSQL(DBaaS) in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.

This scenario largely describes the process of creating Bastion host and Database services, and configuring the network environment for Bastion host and Database connection, to connect through a DB access client.

Architecture
Figure. PostgreSQL(DBaaS) server connection architecture

Scenario Components

You can configure the scenario using the following services.

Service Group
Service
Detailed Description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that allows users to subdivide the network into smaller parts for specific purposes/scales within the VPC
NetworkingVPC > Public IPA service that reserves public IP and assigns and returns it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the internet
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
DatabasePostgreSQL(DBaaS)A service that easily creates and manages EPAS in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to Virtual Server
Table. List of scenario components
Reference
The default policy of the * Security Group is Deny All, so only allowed IPs must be registered. The All Open policy of In/Outbound can expose cloud resources to external threats as is, with any IP and any port. * By specifying the necessary IP and Port to set the policy, you can enhance security.

Scenario composition method

To configure the scenario, create the necessary services through the following procedure.

1. Configuring the Network

This describes the process of configuring the network environment for Bastion Host and Database service connection.

1-1. Creating a VPC

For detailed creation methods, please refer to the Networking > VPC > How-to guides guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
  3. VPC Creation page, please enter the information required for service creation.
    • IP range should be entered as 192.168.x.0/16.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the VPC list page.

1-2. Creating a Subnet

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click on the menu for all services > Networking > VPC. It moves to the Service Home page of VPC.
  2. Service Home page, click the Subnet menu. It moves to the Subnet list page.
  3. Click the Subnet Creation button. It moves to the Subnet Creation page.
  4. Subnet Creation page where you enter the information needed to create a service.
    • Subnet type should be selected as General.
    • Please select a pre-created VPC.
    • IP range should be entered as 192.168.x.0/24.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once creation is complete, check the created resource on the Subnet list page.

1-3. Creating an Internet Gateway

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
  3. Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
  4. Internet Gateway creation page, please enter the required information necessary for service creation.
    • Please select a pre-created VPC.
    • Select Use in the Firewall usage item.
  5. In the Summary panel, review the detailed information and the estimated charge, then click the Complete button.
    • Once the creation is complete, check the created resource on the Internet Gateway list page.

1-4. Creating a Public IP

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Public IP menu. It moves to the Public IP list page.
  3. Public IP Reservation button, click. Move to the Public IP Reservation page.
  4. Public IP Reservation page, enter the required information necessary for service reservation.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the Public IP List page.

1-5. Creating a Security Group

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
  2. Click the Security Group creation button on the Service Home page. It moves to the Security Group creation page.
  3. Security Group creation page where you enter the required information necessary for service creation.
  4. Check the input information and click the Complete button.
    • After creation is complete, check the created resource on the Security Group list page

2. Creating a Bastion Host

This describes the process of configuring the Bastion Host where the database connection client should be installed.

2-1. Creating a Server Keypair

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
  3. Keypair creation button should be clicked. It moves to the Keypair creation page.
  4. Keypair creation page, please enter the required information necessary for service creation.
  5. Check the creation information and click the Complete button.
    • The key can only be downloaded for the first time, and re-issuance is not provided.
    • Please keep the downloaded key in a safe place.

2-2. Creating a Bastion Host

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
  3. Virtual Server creation page where you enter the required information necessary for service creation.
  4. Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
    • Once creation is complete, check the created resource on the Virtual Server list page.

2-3. Check Bastion host connection ID and PW

  1. Click on the menu for all services > Compute > Virtual Server. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
  3. Virtual Serve list page, click on the resource created in 2-2. Bastion host creation. It moves to the detailed information page of the corresponding resource.
  4. Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window will open.
  5. RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
  6. After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.

3. Creating a Database

Describes the process of creating a database service.

3-1. Creating PostgreSQL(DBaaS) Service

For detailed creation methods, please refer to the Database > PostgreSQL(DBaaS) > How-to guides guide.
  1. Click on the menu for all services > Database > PostgreSQL(DBaaS). It moves to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the Create PostgreSQL(DBaaS) button. It moves to the Create PostgreSQL(DBaaS) page.
  3. PostgreSQL(DBaaS) creation page, please enter the required information needed for service creation.
    • Select and connect the pre-created VPC and Subnet.
    • Enter database-related creation information on the essential information input screen.
    • Add the Bastion host IP to the IP access control items.
    • Database Port is 2866 by default, but you can specify it as you want.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the PostgreSQL(DBaaS) list page.

4. Setting Rules

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

4-1. Adding Security Group Security Rules

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Security Group menu. Move to the Security Group list page.
  3. 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the resource.
  4. Click the Rules tab on the detail information page. It moves to the Rules tab.
  5. Click the Rules tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule popup window, enter the rules below, and click the OK button
DirectionRemoteDestination AddressProtocolPortDescription
InboundCIDRUser PC IPTCP3389 (RDP)Bastion access PC → Bastion host
OutboundCIDRDB IPTCPDatabase Port (direct input)Bastion host → Database
Fig. Security Group security rules to be added

4-2. Adding IGW Firewall Rules

For detailed creation methods, please refer to the Networking > Firewall > How-to guides guide.
  1. Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
  2. Service Home page, click the Firewall menu. It moves to the Firewall list page.
  3. Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule In the popup window, enter the rules below and click the OK button.
Departure AddressDestination AddressProtocolPortActionDirectionDescription
Bastion access PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
Table. Internet Gateway Firewall rules to be added

5. Connect to Database

This describes the process of a user accessing the Database through a DB connection client program.

This guide provides instructions on how to connect using pgAdmin. There are various database client programs and CLI utilities, so you can install and use the tools that are suitable for the user.

5-1. Connect to the Bastion host

  1. Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
  2. After a successful remote desktop connection, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Access ID and PW and click the Confirm button.

5-2. Installing DB connection client program (pgAdmin) on the Bastion host

  1. Go to the official pgAdmin page and download the pgAdmin program.
  2. Connect the hard drive of the user PC to upload the file to the Bastion host.
  3. Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
  4. Select the local disk where the file was downloaded to the drive and click the Confirm button.
  5. Copy the downloaded file and upload it to the Bastion Host, then click the pgAdmin installation file to install it.

5-3. Using DB connection client program (pgAdmin) to connect to the database

  1. Run pgAdmin and click the Add New Server button.
  2. In the Register - Server popup window, enter the Database server information created in 3-1. PostgreSQL(DBaaS) service creation in the General tab and Connection tab, and click the Save button.
    Screen (Tab)Required Input Element ItemsInput Value
    GeneralNameCustom (ex. Service Name)
    ConnectionHost name/addressDatabase server IP
    ConnectionPortDatabase Port
    ConnectionMaintenance databaseDatabase name
    ConnectionPasswordDatabase password
    DB connection client program input items
  3. Click the database name created on pgAdmin to connect.
    • You can try simple queries after connecting.

2.2.5 - Using Extensions

PostgreSQL(DBaaS) Extension usage

Note
The list of extensions included in each version of PostgreSQL can be found on the PostgreSQL official page.

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

SQL> select * from pg_available_extensions;

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

Extension namedescription
pgauditprovides detailed audit logging functionality at the session and object level
pg_crona scheduler that allows job scheduling with cron syntax within the database
pg_hint_planProvides a feature to apply hint clauses to SQL execution plans
pgvectorVector data type and similarity search, etc. AI vector operation function provided
postgisGIS (Geographic Information System) provides spatial object storage and spatial query functionality
Table. PostgreSQL(DBaaS) Extension Additional Installation Items

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

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

2.3 - API Reference

API Reference

2.4 - CLI Reference

CLI Reference

2.5 - Release Note

PostgreSQL(DBaaS)

2025.12.16
FEATURE Add Replica Configuration Feature for Disaster Recovery
  • You can configure a disaster recovery Replica using the Replica configuration (Other Region) feature.
2025.07.01
FEATURE User (access control) management, Archive configuration feature, DB Audit Log export feature added, backup notification feature provided, Migration feature added
  • PostgreSQL(DBaaS) Add feature
2025.02.27
FEATURE New version, addition of server types and per-server IP settings, Block Storage capacity expansion feature added
  • PostgreSQL(DBaaS) feature change
    • PostgreSQL new version added: 13.16, 14.13, 15.8
    • Add 2nd generation server type
      • Intel 4th generation (Sapphire Rapids) Processor based 2nd generation (dbh2) server type added. For more details, see PostgreSQL(DBaaS) Server Type.
    • After creating the service Block Storage capacity expansion is possible.
  • Server-specific network IP configuration feature added allowing common or server-specific settings depending on the usage purpose.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM and Service Home, tags etc. have reflected the common CX changes.
2024.10.01
NEW PostgreSQL(DBaaS) Official Service Version Release
  • Block Storage type volume-encrypted storage selection option has been added.
  • Redundant Active DB and Standby DB’s Role Switch (Active ↔ Standby) feature has been added.
  • Linked with the cloud monitoring service, performance and log monitoring of DB instances is possible.
  • Depending on the server type selected by the customer, Planned Compute policy setting is possible.
2024.07.02
NEW Beta version release
  • PostgreSQL (DBaaS) service that can easily create and manage 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 content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas are provided for read load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers a feature that automatically backs up at a user-specified time, supporting data recovery at the desired point in time.

Architecture
Figure. MariaDB(DBaaS) Architecture

Provided Features

MariaDB (DBaaS) provides the following features.

  • Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) via UI is possible, and it provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, 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, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Active-Standby via Switch-over.
  • Backup and Recovery: Provides data backup functionality based on its own backup command. The backup time window and storage organization can be set by the user, and additional fees may be incurred depending on backup volume. It also provides a recovery function for backed-up data, so when the user performs recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup save point, user-defined point). When recovering to a user-specified point, the recovery point can be set to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
  • Version Management: Provides version upgrade (Minor) functionality due to some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
  • Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
  • Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
  • Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
  • Service status query: Retrieves the final status of the current DB service.
  • Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
  • 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 IPs for access.
  • Archive Management: You can set the Archive file retention period (1 day~35 days) within the DB server and configure the Archive mode (On/Off).
  • DB Log Export: Through Audit settings, you can export stored logs to the user’s Object Storage.
  • Migration: Synchronize data in real time with the operating database, and support migration using replication method without service interruption.

Components

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

Engine Version

The engine versions supported by MariaDB (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 stopped is set to 6 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.

ServiceProvided VersionEOS Date(Samsung Cloud Platform New Creation Stop Date)EoTS Date(Community Technical Support End Date)
MariaDB (Community)10.6.52026-03 (planned)2026-07-06
10.6.92026-03 (scheduled)2026-07-06
10.6.102026-03 (scheduled)2026-07-06
10.6.122026-03 (scheduled)2026-07-06
10.6.142026-03 (scheduled)2026-07-06
10.6.152026-03 (scheduled)2026-07-06
10.6.162026-03 (scheduled)2026-07-06
10.6.172026-03 (scheduled)2026-07-06
10.6.192026-03 (scheduled)2026-07-06
10.6.222026-03 (scheduled)2026-07-06
10.11.82027-09 (scheduled)2028-02-16
10.11.92027-09 (scheduled)2028-02-16
10.11.132027-09 (scheduled)2028-02-16
11.42029-09 (scheduled)2030-01-16
Table. MariaDB (DBaaS) Provided Engine Versions

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) Server Type.

Standard db1v2m4
CategoryExampleDetailed Description
Server TypeStandardProvided Server Types
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) configuration commonly used
  • dbh2: Large-scale server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server Specificationsm4Memory Capacity
  • m4: 4GB Memory
Table. MariaDB (DBaaS) server type components

Preliminary Service

This is a list of services that must be pre-configured before creating the service. For details, please refer to the guide provided for each service and prepare in advance.

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
Table. MariaDB (DBaaS) Preliminary Service

3.1.1 - Server Type

MariaDB(DBaaS) Server Type

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

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

Standard db1v2m4
Classification
ExampleDetailed Description
Server TypeStandardClassification of provided server types
  • Standard: Standard specification (vCPU, Memory) composition
  • High Capacity: High-capacity server specification above Standard
Server Specificationdb1Classification of provided server types and generation
  • db1: General specification, 1 represents the generation
  • dbh2: h represents high-capacity server specification, 2 represents the generation
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory capacity
  • m4: 4GB Memory
Table. MariaDB(DBaaS) Server Type Format

db1 Server Type

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

  • Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standarddb1v1m21 vCore2 GBUp to 10 Gbps
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MariaDB(DBaaS) Server Type Specifications - db1 Server Type

dbh2 Server Type

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

  • Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
  • Supports up to 128 vCPUs and 1,536 GB of memory
  • Up to 25Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBUp to 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBUp to 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBUp to 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBUp to 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBUp to 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBUp to 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBUp to 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBUp to 25 Gbps
Table. MariaDB(DBaaS) Server Type Specifications - dbh2 Server Type

3.1.2 - Monitoring Metrics

MariaDB(DBaaS) Monitoring Metrics

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

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

Performance ItemDetailed DescriptionUnit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Connection Usage [Total]DB connection session usage rate%
ConnectionsNumber of connectionscnt
Connections [MAX]Maximum number of connected threadscnt
Binary Log Used [MB]Binary log usageMB
Data Directory Used [MB]Data directory usageMB
Open FilesNumber of open DB filescnt
Open Files [MAX]Maximum number of openable DB filescnt
Open Files UsageDB file maximum usage rate%
Relay Log Used [MB]Relay log usageMB
Instance Status [PID]mariadbd processpid
Safe PIDmariadbd_safe processpid
Slave Behind Master secondsTime difference between Master and Slave data (only executed on slave)sec
Tablespace UsedTablespace usageMB
Tablespace Used [Total]Total Tablespace usageMB
Running ThreadsNumber of running threadscnt
SlowqueriesNumber of sessions that execute SQL for more than 10 secondscnt
Slowqueries [Total]Total number of sessions that execute SQL for more than 10 secondscnt
Transaction Time [Long]Longest transaction execution timesec
Wait LocksNumber of sessions blocked by lock for more than 60 secondscnt
Table. MariaDB(DBaaS) Monitoring Metrics

3.2 - How-to guides

The user can enter the required information for MariaDB (DBaaS) and select detailed options through the Samsung Cloud Platform Console to create the service.

Creating MariaDB(DBaaS)

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

Notice
  • Please configure the VPC’s Subnet type as General before creating the service.
    • If the Subnet type is Local, the creation of the corresponding Database service is not possible.
  • If you load more than 2 TB of large data, backups may take a long time or the DB’s performance may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.

To create MariaDB (DBaaS), follow the steps below.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. You will be taken to the Service Home page of MariaDB(DBaaS).
  2. Service Home on the page click the MariaDB(DBaaS) creation button. Navigate to the MariaDB(DBaaS) creation page.
  3. MariaDB(DBaaS) creation on the page, enter the information required to create the service, and select detailed options.
    • Please select the required information in the Image and version selection area.
      Category
      Required
      Detailed description
      Image versionRequiredProvide version list of MariaDB (DBaaS)
      Table. MariaDB(DBaaS) Image and Version Selection Items
    • Service Information Input Enter or select the required information in the area.
      Category
      Required or not
      Detailed description
      Server name PrefixRequiredName of the server where the DB will be installed
      • Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (-) to input 3 to 13 characters
      • Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
      Cluster NameRequiredCluster name composed of DB servers
      • Enter using English letters, 3 to 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type where DB will be installed
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server of 24 vCore or more
      Service Type > Planned ComputeSelectStatus 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 by Planned Compute per resource
      • Create Planned Compute Service: Go to the Planned Compute service application page
      Service Type > Block StorageRequiredBlock Storage settings used by DB according to purpose
      • Base 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. (For detailed information on each Block Storage type, refer to Create Block Storage)
          • SSD: High-performance general volume
          • HDD: General volume
          • SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption keys
        • The configured storage type is applied identically to additional storage
        • Capacity must be entered as a multiple of 8 within the range 16 ~ 5,120
        • Since large sorts during SQL execution or monthly batch processes can cause service interruptions, a separate TEMP storage must be allocated and used
      • Additional: Data storage areas for DATA, Archive, TEMP, Backup
        • After selecting Use, enter the storage’s purpose and capacity
        • The storage type is applied the same as set for DATA, and capacity can be entered as a multiple of 8 within the range 16 ~ 5,120
        • Click the + button to add storage, and the x button to delete. Up to 9 can be added
        • Temporarily store backup data in BACKUP storage before transmitting backup data
          • If the data to be backed up exceeds 100 GB and changes frequently, it is recommended to add a separate BACKUP storage for reliable backup. It is advised to set the backup capacity to about 60% of the DATA capacity
          • If a BACKUP storage is not added, using the /tmp area is recommended
        • For each service, only one Block Storage is allocated for Archive, TEMP, BACKUP
      Redundancy ConfigurationSelectionRedundancy Configuration Status
      • If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
      Network > Common SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply the same settings to all servers being installed
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be auto‑generated
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. See Create Public IP for details.
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply different settings per installed server
      • Select a pre-created VPC, Subnet, IP, Public NAT
        • Enter each server’s IP
        • 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 details, see Create Public IP.
      IP Access ControlSelectService Access Policy Settings
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      Maintenance PeriodSelectDB Maintenance Period
      • Use is selected, set day of week, start time, and duration
      • It is recommended to set a maintenance period for stable DB management. Patch work is performed at the set time, causing service interruption
      • If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
      Table. MariaDB (DBaaS) Service Information Input Items
    • Database configuration required information input area, please enter or select the required information.
      Category
      Required or not
      Detailed description
      Database nameRequiredServer name applied when installing DB
      • Start with English letters, use English letters and numbers, input 3 ~ 20 characters
      Database usernameRequiredDB user name
      • An account with the same name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted Database usernames can be checked in the Console
      Database passwordRequiredPassword to use when accessing the DB
      • Enter 8~30 characters including letters, numbers, and special characters ( excluded)
      Database Password ConfirmationRequiredRe-enter the same password to be used when accessing the DB
      Database Port NumberRequiredPort number required for DB connection
      • Enter DB port within the range 1,024 ~ 65,535
      Backup > UseSelectWhether to use backup
      • Select Use to set the backup file retention period, backup start time, and Archive backup cycle
      Backup > Retention PeriodSelectBackup retention period
      • Select backup retention period. File retention period can be set from 7 days to 35 days
      • Backup files incur separate charges based on size
      Backup > Backup Start PeriodSelectBackup 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 frequencySelectArchive backup frequency
      • Select the Archive backup frequency
      • Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
      Audit Log SettingsSelectWhether to store Audit Log
      • Enable를 선택하여 Audit Log 기능을 설정
        • 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
        • Enabling Audit may degrade DB performance
      ParameterRequiredParameters to use in the DB
      • Lookup Click the button to view detailed information of the parameter
      • Parameters can be modified after DB creation is complete, and after modification the DB must be restarted
      DB character setRequiredCharacter encoding method to use for the DB
      • The character set used when storing text data, and the DB is created with this encoding set as the default.
      Time zoneRequiredStandard time zone to be used by the Database
      Table. MariaDB(DBaaS) Database configuration items
    • Additional Information Input area: enter or select the required information.
      Category
      Required or not
      Detailed description
      TagSelectAdd 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
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Resource List page.

MariaDB(DBaaS) Check detailed information

MariaDB(DBaaS) service can view and edit the full resource list and detailed information. The MariaDB(DBaaS) Details page consists of Details, Tags, Activity Log tabs, and for DBs with a Replica configured, an additional Replica Information tab is included.

To view detailed information about the MariaDB (DBaaS) service, follow the steps below.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. Click the MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
  3. Click the resource to view detailed information on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Details page.
  • MariaDB(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
    CategoryDetailed description
    Cluster StatusCluster status with DB installed
    • Creating: Cluster is being created
    • Editing: Cluster is being changed to operation execution state
    • Error: Cluster encountered a failure while performing tasks
      • If it occurs continuously, 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 being stopped
    • Synchronizing: Cluster is being synchronized
    • Terminating: Cluster is being deleted
    • Unknown: Cluster status is unknown
      • If it occurs continuously, contact the administrator
    • Upgrading: Cluster is changing to upgrade execution state
    Cluster ControlButton to change 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 additional featuresCluster related management buttons
    • Service status synchronization: Real-time DB service status lookup
    • Backup history: If backup is set, check whether backup runs normally and view history
    • Database recovery: Recover DB based on a specific point in time
    • Parameter management: DB configuration parameters can be queried and modified
    • Replica configuration: Set up a read-only cluster called Replica
    • 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 IPs
    • Archive management: Can set archive file retention period and archive mode
    • DB Log export: Through audit settings, stored logs can be exported to the user’s Object Storage
    • Migration configuration: Provides migration functionality using replication method
    Service terminationButton to cancel the service
    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 necessary, edit the information.

CategoryDetailed description
Server InformationServer information configured in the respective cluster
  • Category: Server type (Active, Standby, Replica)
  • Server name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In DB service, it means cluster SRN
Resource NameResource Name
  • In DB service, it means the cluster name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
EditorUser who modified the service information
Modification date/timeDate and time when the service information was modified
Image/VersionInstalled DB image and version information
  • If a version upgrade is needed, click the Edit icon to set
Cluster TypeCluster Type (Master Cluster, Replica Cluster, Migration Cluster)
Cluster NameName of the cluster composed of DB servers
Master Cluster NameMaster Cluster Name of the Replica
  • If detailed information of the Replica is present, it can be checked
Database nameServer name applied when installing DB
Database usernameDB user name
Planned ComputeResource status with Planned Compute set
Maintenance PeriodDB Maintenance Period Status
  • If maintenance period setting is required, click the Edit icon to set
BackupBackup configuration status
  • If backup configuration is needed, click the Edit icon to set
Audit Log SettingsAudit Log Settings Status
  • If Audit Log settings are needed, click the Edit icon to configure
Time zoneStandard time zone used by the Database
DB character setcharacter encoding method to be used in DB
VIPVirtual IP information
  • Can be checked only when high availability is configured
NetworkNetwork information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP Access ControlService Access Policy Settings
  • If you need to add or delete an IP, click the Edit icon to set
Active & StandbyActive/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 set it. Refer to Change Server Type for the server type modification procedure
    • 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 Expand Storage for the storage expansion procedure
  • If you need to add storage, click the Add Disk button next to Additional Disk to add. Refer to Add Storage for the storage addition procedure
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 allows you to check the master cluster name, number of replicas, and replica status.

CategoryDetailed description
Master InformationName of Master Cluster
Replica countNumber of Replicas created in the Master cluster
Replica statusReplica server status created in the Master cluster
  • Server name, status query, status details, status check time can be verified
  • To view the Replica status, click the Status Query button
    • While querying, the cluster remains in Synchronizing state, and once the query is complete, the cluster changes to 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.

CategoryDetailed description
Tag ListTag List
  • Can check Tag’s Key, Value information
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from previously created Key and Value lists
Table. MariaDB(DBaaS) Tag Tab Items

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Work date/time, Resource ID, Resource name, Work details, Event topic, Work result, Verify operator information
Table. Work History Tab Detailed Information Items

MariaDB(DBaaS) Manage Resources

If you need to change or restore the existing configuration options of a created MariaDB (DBaaS) resource, or need a Replica configuration, you can perform the work on the MariaDB(DBaaS) Details page.

Control Operation

If changes occur to the running MariaDB (DBaaS) resources, you can start, stop, or restart them. Also, if HA is configured, you can switch the Active-Standby servers via Switch-over.

To control the operation of MariaDB (DBaaS), follow the steps below.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. Click the MariaDB(DBaaS) menu on the Service Home page. Go to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) 목록 Click the resource to control operation. MariaDB(DBaaS) 상세 Navigate to the page.
  4. Check the status of MariaDB (DBaaS) and complete the change using the control button below.
    • Start: The server where the DB service is installed and the DB service are 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 check the service status of MariaDB (DBaaS), follow the steps below.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. Click the MariaDB(DBaaS) menu on the Service Home page. Navigate to the MariaDB(DBaaS) List page.
  3. Click the resource to view the service status on the MariaDB(DBaaS) List page. Move to the MariaDB(DBaaS) Details page.
  4. Click the Service Status Synchronization button. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query is completed, 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 reboot is required. Check separately for SW license changes or SW settings and reflections due to server specification changes.

To change the server type, follow the steps below.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. You will be taken to the Service Home page of MariaDB(DBaaS).
  2. Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) List page, click the resource to change the server type. Move to the MariaDB(DBaaS) Details page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
  5. Edit Server Type After selecting the server type in the popup window, click the Confirm button.

Add Storage

If more than 5TB of data storage space is required, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.

Caution
  • It will be applied the same way as the selected Storage type when creating the service.
  • For a DB with redundancy configured, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
  • If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. Expand the Replica storage first, then expand the Master cluster storage.
  • When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.

To add storage, follow the steps below.

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

Expanding Storage

You can expand the storage added to the data area 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.

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

MariaDB(DBaaS) Cancel

You can cancel unused MariaDB (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, please terminate it separately from the resource list.
  • If you cancel the DB, stored data and, if backup was set, all backup data will be deleted.

To cancel MariaDB (DBaaS), follow the steps below.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
  4. Once the termination is complete, check whether the resource has been terminated on the MariaDB(DBaaS) list page.

3.2.1 - MariaDB(DBaaS) server connection

Scenario Overview

The MariaDB(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To access MariaDB (DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and network connection using it. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.

This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, to connect through a DB access client.

Architecture
Figure. MariaDB(DBaaS) server connection architecture

Scenario Components

You can configure the scenario using the following services.

Service Group
Service
Detailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
NetworkingVPC > SubnetA service that allows users to subdivide the network into smaller parts for their purpose/scale within the VPC
NetworkingVPC > Public IPA service that reserves a public IP and assigns and returns it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the internet
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
DatabaseMariaDB(DBaaS)A service that easily creates and manages MariaDB in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to Virtual Server
Table. List of scenario components
Reference
The default policy of the * Security Group is Deny All, so only allowed IPs must be registered. The All Open policy of In/Outbound can expose cloud resources to external threats as is, with any IP and any port. * By specifying the necessary IP and Port to set the policy, you can enhance security.

Scenario composition method

To configure the scenario, create the necessary services through the following procedure.

1. Configuring the Network

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

1-1. Creating a VPC

For detailed creation methods, please refer to the Networking > VPC > How-to guides guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
  3. VPC Creation page, please enter the information required for service creation.
    • IP range should be entered as 192.168.x.0/16.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once the creation is complete, check the created resource on the VPC List page.

1-2. Creating a Subnet

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Subnet menu. It moves to the Subnet list page.
  3. Click the Subnet Creation button. It moves to the Subnet Creation page.
  4. Subnet creation page where you enter the information needed to create a service.
    • Subnet type should be selected as General.
    • Please select a pre-created VPC.
    • IP range should be entered as 192.168.x.0/24.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the Subnet list page.

1-3. Creating an Internet Gateway

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
  3. Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
  4. Internet Gateway creation page, please enter the required information necessary for service creation.
    • Please select a pre-created VPC.
    • Select Use in the Firewall usage item.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once the creation is complete, check the created resource on the Internet Gateway list page.

1-4. Creating a Public IP

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Public IP menu. It moves to the Public IP list page.
  3. Public IP Reservation button, click. Move to the Public IP Reservation page.
  4. Public IP Reservation page, enter the required information necessary for service reservation.
  5. In the Summary panel, review the details generated and the expected charge amount, then click the Complete button.
    • Once creation is complete, check the created resource on the Public IP List page.

1-5. Creating a Security Group

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click All services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
  2. Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
  3. Security Group creation page, please enter the required information necessary for service creation.
  4. Check the input information and click the Complete button.
    • After creation is complete, check the created resource on the Security Group list page

2. Creating a Bastion Host

This describes the process of configuring the Bastion Host where the database connection client should be installed.

2-1. Creating a Server Keypair

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Keypair menu. It moves to the Keypair list page.
  3. Create Keypair button should be clicked. It moves to the Create Keypair page.
  4. Keypair creation page, please enter the required information necessary for service creation.
  5. Check the creation information and click the Complete button.
    • The key can only be downloaded for the first time, and re-issuance is not provided.
    • Please keep the downloaded key in a safe place.

2-2. Creating a Bastion Host

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
  3. Virtual Server Creation page, please enter the required information necessary for service creation.
  4. In the Summary panel, review the details generated and the expected charge amount, then click the Complete button.
    • After creation is complete, check the created resource on the Virtual Server list page.

2-3. Check Bastion host connection ID and PW

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server menu. It moves to the Virtual Server list page.
  3. Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
  4. Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
  5. RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
  6. After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.

3. Creating a Database

It describes the process of creating a database service.

3-1. Creating the MariaDB (DBaaS) Service

For detailed creation methods, please refer to the Database > MariaDB(DBaaS) > How-to guides guide.
  1. Click on the menu for all services > Database > MariaDB(DBaaS). It moves to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the Create MariaDB(DBaaS) button. It moves to the Create MariaDB(DBaaS) page.
  3. MariaDB(DBaaS) creation page, please enter the required information needed for service creation.
    • Select and connect the pre-created VPC and Subnet.
    • Enter database-related creation information on the required information input screen.
    • Add the Bastion host IP to the IP access control item.
    • Database Port is 2866 by default, but you can specify it as you want.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once the creation is complete, check the created resource on the MariaDB(DBaaS) list page.

4. Setting Rules

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

4-1. Adding Security Group Security Rules

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Security Group menu. Move to the Security Group list page.
  3. 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule In the popup window, enter the rules below and click the OK button
DirectionRemoteDestination AddressProtocolPortDescription
InboundCIDRUser PC IPTCP3389 (RDP)Bastion access PC → Bastion host
OutboundCIDRDB IPTCPDatabase Port (direct input)Bastion host → Database
Fig. Security Group security rules to be added

4-2. Adding IGW Firewall Rules

For detailed creation methods, please refer to the Networking > Firewall > How-to guides guide.
  1. Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
  2. Service Home page, click the Firewall menu. It moves to the Firewall list page.
  3. Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Rule tab, click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule In the popup window, enter the rules below and click the OK button.
Departure AddressDestination AddressProtocolPortActionDirectionDescription
Bastion access PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
Fig. Internet Gateway Firewall rules to be added

5. Connecting to the Database

This describes the process of a user accessing the Database through a DB connection client program.

This guide provides instructions on how to connect using MySQL Workbench. There are various database client programs and CLI utilities, so you can also install and use the tools that are suitable for users.

5-1. Connect to Bastion host

  1. Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
  2. After a successful remote desktop connection, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Access ID and PW and click the Confirm button.

5-2. Installing DB connection client program (MySQL Workbench) on the Bastion host

  1. Go to the official MySQL page and download the MySQL Workbench program.
  2. Connect the hard drive of the user’s PC to upload the file to the Bastion host.
  3. Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
  4. Select the local disk where the file was downloaded to the drive and click the Confirm button.
  5. Copy the downloaded file and upload it to the Bastion Host, then click the MySQL Workbench installation file to install it.

5-3. Using DB connection client program (MySQL Workbench) to connect to the Database

  1. Run MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup window will appear.
  2. Manage Server Connection popup window, click the New button at the bottom left and enter the database server information created in 3-1. MariaDB(DBaaS) service creation, then click the Test Connection button. A Password popup window will appear.
    Required Input Element ItemsInput Value
    Connection NameCustom (ex. Service Name)
    Host nameDatabase server IP
    PortDatabase Port
    UsernameDatabase user name
    DB connection client program input items
  3. Password popup window, enter the password set in 3-1. MariaDB(DBaaS) service creation and click the OK button. When the success is complete, click the OK button in the Manage Server Connection popup window.
  4. Database > Connect to Database를 클릭하세요. Connect to Database popup window will appear.
  5. Select the Connection Name registered in Stored Connection to perform database connection. After connection, you can try simple queries, etc.

3.2.2 - Managing DB Services

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

Managing Parameters

It provides a feature to easily view and modify database configuration parameters.

Viewing Parameters

To view configuration parameters, follow these steps:

  1. Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
  2. Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window will open.
  6. When the View Notification popup window opens, click the OK button. It may take some time to view.

Modifying Parameters

To modify configuration parameters, follow these steps:

  1. Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
  2. Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window will open.
  6. When the View Notification popup window opens, click the OK button. It may take some time to view.
  7. If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the parameter to be modified.
  8. When the input is complete, click the Save button.

Managing DB Users

It provides a management feature that allows you to view DB user information and change status information.

Viewing DB Users

To view DB users, follow these steps:

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

Changing DB User Status

To change the status of the viewed DB user, follow these steps:

  1. Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
  2. Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
  3. Click the resource you want to modify DB users on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
  5. Click the View button on the DB User Management page. It may take some time to view.
  6. If modification is necessary, click the Modify button and change the status value or enter notes.
  7. When the input is complete, click the Save button.

Managing DB Access Control

It provides an IP-based DB user access control management feature. Users can directly specify the IP that can access the database, allowing only authorized IPs to access.

Notice
Before setting up DB access control, perform DB user inquiry. Refer to Managing DB Users for DB user inquiry.

Viewing DB Access Control

To view DB users with IP access control set, follow these steps:

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

Adding DB Access Control

To add IP access control, follow these steps:

  1. Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
  2. Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
  3. Click the resource you want to add IP access control on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. Click the View button on the DB Access Control Management page. It may take some time to view.
  6. When the view is complete, click the Add button. The DB Access Control Add popup window will open.
  7. In the DB Access Control Add popup window, select the DB user name and enter the IP address.
  8. When the input is complete, click the Save button.

Deleting DB Access Control

To delete IP access control, follow these steps:

  1. All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. On the MariaDB(DBaaS) list page, click the resource for which you want to delete IP access control. Move to the MariaDB(DBaaS) details page.
  4. Click the More button and then click the DB Access Control Management button. Move to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the Inquire button. It takes some time to inquire.
  6. Once the inquiry is complete, click the Delete button. The Delete pop-up window opens.
  7. In the Delete pop-up window, click the Confirm button.

Managing Archives

The Archive mode setting and Archive Log storage period setting functions are provided to allow users to flexibly set the Archive log management policy according to their operating environment. In addition, the function to manually delete Archive logs is provided together, allowing users to clean up unnecessary log data and effectively manage system resources.

Notice
The default setting when creating a service is Archive mode enabled, storage period 3 days.

Setting Archive Mode

To set the Archive mode, follow these steps:

  1. All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. On the MariaDB(DBaaS) list page, click the resource for which you want to set the Archive mode. Move to the MariaDB(DBaaS) details page.
  4. Click the More button and then click the Archive Settings Management button. Move to the Archive Settings Management page.
  5. On the Archive Settings Management page, click the Inquire button. It takes some time to inquire.
  6. Click the Modify button and select the usage and storage period.
  7. Once the modification is complete, click the Save button.

Deleting Archive Files

To delete Archive files, follow these steps:

  1. All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. On the MariaDB(DBaaS) list page, click the resource for which you want to set the Archive mode. Move to the MariaDB(DBaaS) details page.
  4. Click the More button and then click the Archive Settings Management button. Move to the Archive Settings Management page.
  5. On the Archive Settings Management page, click the Delete All Archives button to delete all Archive files, or click the Delete Backed-up Archives button to delete only the backed-up Archive files.

Exporting DB Logs

Supports exporting log data that requires long-term storage among audit logs to Object Storage. Users can directly set the type of log to be stored, the target bucket to be exported, and the cycle of exporting logs. According to the set criteria, logs are copied to the specified Object Storage for storage. In addition, an option to automatically delete the original log file while exporting logs to Object Storage is provided to efficiently manage disk space. By utilizing this option, users can safely store necessary log data for a long time while effectively securing storage capacity.

Notice
  • To use the DB Log export function, Object Storage creation is required. Refer to the Object Storage User Guide for Object Storage creation.
  • Be sure to check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
  • Be careful not to expose authentication key information to the outside.

Setting DB Log Export Mode

To set the DB Log export mode, follow these steps:

  1. All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. On the MariaDB(DBaaS) list page, click the resource for which you want to export DB logs. Move to the MariaDB(DBaaS) details page.
  4. Click the More button and then click the DB Log Export button. Move to the DB Log Export page.
  5. On the DB Log Export page, click the Registration button. Move to the DB Log Export Registration page.
  6. On the DB Log Export Registration page, enter the corresponding information and click the Save button.
CategoryRequired
Detailed Description
Log TypeRequiredType of log to be stored
Storage Bucket NameRequiredName of the Object Storage bucket to be stored
Authentication Key > Access KeyRequiredAccess key to access the Object Storage to be stored
Authentication Key > Secret KeyRequiredSecret key to access the Object Storage to be stored
File Creation CycleRequiredCycle of creating files in Object Storage
Original Log DeletionOptionalWhether to delete the original log when exporting to Object Storage
Table. MariaDB(DBaaS) Migration Configuration Items

Managing DB Log Export

To modify, cancel, or immediately export DB log export settings, follow these steps:

  1. All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. On the MariaDB(DBaaS) list page, click the resource for which you want to manage DB log export. Move to the MariaDB(DBaaS) details page.
  4. Click the More button and then click the DB Log Export button. Move to the DB Log Export page.
  5. On the DB Log Export page, click the More button according to the log type you want to manage, and then click the Immediate Export, Modify, or Cancel button.
    • Immediate Export: Exports the selected log to the Object Storage bucket set earlier.
    • Modify: Modifies the DB log export mode setting.
    • Cancel: Cancels the DB log export mode setting.

Upgrading DB Version

Provides a version upgrade function due to some feature improvements and security patches. Only minor version upgrades are supported within the same major version.

Caution
  • Please perform version upgrades after checking the service status through service status synchronization.
  • Please set up backups before performing version upgrades. If backups are not set, some data may not be recoverable in case of problems during the upgrade.
  • In DBs with replicas configured, the master DB version cannot be higher than the replica version. Please check the replica version first and perform version upgrades as needed.
  • Backed-up data will be automatically deleted after the version upgrade is complete.

To upgrade the version, follow the procedure below.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
  2. Click the MariaDB(DBaaS) menu on the Service Home page. It moves to the MariaDB(DBaaS) list page.
  3. Click the resource to be upgraded on the MariaDB(DBaaS) list page. It moves to the MariaDB(DBaaS) details page.
  4. Click the Modify button in the image/version item. The version upgrade popup window opens.
  5. In the version upgrade popup window, select the version to be modified and the backup setting, and then click the Confirm button.
  6. Click the Confirm button in the version upgrade notification popup window.

Configuring Migration

It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.

Guide
For a detailed migration configuration guide, please refer to Architecture Center > Migration Guide > Database Migration Procedure and Considerations.

To configure the migration, follow the procedure below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) list page.
  3. Click the resource to be migrated on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
  4. Click the More button to click the Configure Migration button. The Configure Migration popup window opens.
  5. In the Configure Migration popup window, check the instructions and click the Confirm button. It moves to the Configure Migration page.
  6. On the Configure Migration page, enter the corresponding information and click the Connect Check button.
  7. When the connection is complete, click the Complete button.
ClassificationRequired
Detailed Description
Source DB Database NameRequiredDatabase name of the source DB that is the migration target
Source DB IPRequiredIP of the source DB that is the migration target
Source DB PortRequiredPort of the source DB that is the migration target
Source DB User NameRequiredUser name of the source DB that is the migration target
Source DB PasswordRequiredPassword of the source DB that is the migration target
Table. MySQL(DBaaS) Migration Configuration Items

The configured migration cluster can be promoted to a master cluster.

Caution
When promoting to a master, synchronization with the source DB that is the migration target will be discontinued.

To promote the migration cluster to a master, follow the procedure below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) list page.
  3. Click the resource to be promoted to a master on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
  4. Click the More button to click the Promote to Master button. The Master Promotion Notification popup window opens.
  5. Click the Confirm button in the Master Promotion Notification popup window.

3.2.3 - DB Backup and Recovery

The user can set up a backup of MariaDB(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.

Backing up MariaDB(DBaaS)

PostgreSQL(DBaaS) provides a data backup feature based on its own backup command, and also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.

Setting up backup

The backup setting method of MariaDB(DBaaS) is referred to MariaDB(DBaaS) creation.

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

Caution
  • For stable backup, it is recommended to add a separate BACKUP storage or sufficiently increase the storage capacity. Especially when the backup target data exceeds 100 GB and there are many data changes, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, please refer to the MariaDB(DBaaS) Add Storage, MariaDB(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
  1. All Services > Database > MariaDB(DBaaS) menu is clicked. It moves to the Service Home page of MariaDB(DBaaS).
  2. Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) list page, click the resource to set the backup. Move to the MariaDB(DBaaS) details page.
  4. Click the Edit button of the backup item. The Backup Settings popup window opens.
  5. If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
    • If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.

Check backup history

Notice
To set up notifications for backup success and failure, you can set it up through the Notification Manager product. For a detailed usage guide on setting up notification policies, please refer to Creating a Notification Policy.

To check the backup history, follow these steps.

  1. Click All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) list page, click the resource to check the backup history. It moves to the MariaDB(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting backup files

To delete a backup file, follow these steps.

Caution
Backup files cannot be restored after deletion. Please make sure to confirm whether the data is unnecessary before deleting it.
  1. All Services > Database > MariaDB(DBaaS) menu is clicked. It moves to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) list page, click the resource to check the backup history. It moves to the MariaDB(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. In the Backup History popup window, check the files you want to delete and click the Delete button.

Restore MariaDB(DBaaS)

In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing MariaDB (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, and the DB is installed with the version at the backup point in time, and the recovery proceeds with the DB configuration information and data.

Caution
To perform recovery, a capacity of twice the data type Disk capacity is required. If the Disk capacity is insufficient, recovery may fail.

To restore MariaDB(DBaaS), follow these procedures.

  1. Click All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
  2. Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
  3. MariaDB(DBaaS) list page, click the resource you want to restore. Move to the MariaDB(DBaaS) details page.
  4. Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
  5. After entering information in the database recovery configuration area, click the Complete button.
Classification
Necessity
Detailed Description
Recovery TypeRequiredSet the point in time to recover
  • Backup Point (Recommended): Recover based on the backup file. Select from the list of backup file points displayed in the list
  • Custom Point: Recover to the desired point in time within the range where backup is possible. The recoverable period is from the initial backup start time to 1 hour/30 minutes/10 minutes/5 minutes before the current time based on the Archive backup cycle setting value. Select the date and time you want to back up
Server name prefixRequiredServer name of the recovery DB
  • Starts with lowercase English letters, using lowercase letters, numbers, and special characters (-) to input 3 ~ 16 characters
  • A postfix such as 001, 002 is attached based on the server name, and the actual server name is created
Cluster NameRequiredCluster name of the recovery DB
  • Enter in English, 3-20 characters
  • Cluster is a unit that bundles multiple servers
Service Type > Server TypeRequiredServer type where the recovery DB will be installed
  • Standard: Standard specification commonly used
  • High Capacity: High-capacity server with 24vCore or more (to be provided later)
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are in use
  • Settings: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
  • Create Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
  • Basic OS: Area where the DB engine is installed
  • DATA: Area for storing table data, archive files, etc.
    • The storage type set in the original cluster is applied in the same way
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Additional: DATA, Archive, TEMP, Backup data storage area
    • The storage type set in the original cluster is applied in the same way
    • Only DATA, TEMP, and Archive purposes can be added in the recovery DB
    • After selecting Use, enter the purpose and capacity of the storage
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Database usernamerequiredDatabase username set in the original DB
Database Port numberrequiredDatabase Port number set in the original DB
IP Access ControlSelectIP address to access the recovery DB
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.1/32, 192.168.10.1/32) and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectionDB maintenance period
  • Use is selected to set the day of the week, start time, and duration
  • It is recommended to set the maintenance period for stable DB management. Patch work is performed at the set time and service interruption occurs
  • If not used, problems that occur due to non-application of patches are not the responsibility of our company.
tagselectionadd tag
  • add tag button, enter or select Key, Value
Fig. MariaDB(DBaaS) Recovery Configuration Items

3.2.4 - Configuring Read Replica

Users can create a Read Replica by entering the required information through the Samsung Cloud Platform Console and configuring detailed options.

Configuring Replica

Replica configuration allows you to create a read-only replica server. You can create up to 5 replicas per database.

To configure a replica, follow these steps:

  1. Click All Services > Database > MariaDB(DBaaS). This will take you to the MariaDB(DBaaS) Service Home page.
  2. Click MariaDB(DBaaS) on the Service Home page. This will take you to the MariaDB(DBaaS) list page.
  3. Click the resource you want to configure a replica for on the MariaDB(DBaaS) list page. This will take you to the MariaDB(DBaaS) details page.
  4. Click the Replica Configuration button. This will take you to the Replica Configuration page.
  5. Enter the information in the replica configuration area and click the Complete button.
Category
Required
Detailed Description
Number of ReplicasRequiredThe number of replicas to configure
  • Up to 5 replicas can be configured per cluster.
  • If you select 2 or more values, you need to enter additional information such as replica name and service type.
Replica NameRequiredThe name of the replica server
  • Start with a lowercase letter, and use lowercase letters, numbers, and special characters (-) to enter a 3-19 character string.
  • The entered replica name will be displayed as the cluster name in the list.
Service Type > Server TypeRequiredThe type of replica server
  • Standard: Standard specification commonly used
  • High Capacity: High-capacity server with 24vCore or higher (to be provided later)
Service Type > Planned ComputeOptionalThe current status of resources with Planned Compute set
  • In Use: The number of resources with Planned Compute set that are in use
  • Set: The number of resources with Planned Compute set
  • Coverage Preview: The amount applied to each resource based on Planned Compute
  • Apply for Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredBlock storage settings for the replica DB
  • Basic OS: The area where the DB engine is installed
  • DATA: The storage area for table data and archive files, etc.
    • Applied equally to the storage type set in the original cluster
    • Capacity settings are not available
  • Additional: Storage area for DATA, Archive, TEMP, and Backup data
    • Applied equally to the storage type set in the original cluster
    • Only DATA and TEMP purposes can be added in the replica.
    • Select Use and enter the storage purpose and capacity
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 within the range of 16 to 5,120, and up to 9 can be created, including the number set in the original cluster
IP Access ControlOptionalService access policy setting
  • Access policy is set for the IP entered on the page, so you do not need to set a separate Security Group policy.
  • Enter the 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 the entered IP, click the x button next to the entered IP
Maintenance PeriodOptionalDB maintenance period
  • Use is selected, and the day, start time, and period are set
  • It is recommended to set a maintenance period for stable DB management. Patch work is performed during the set time, and service interruption occurs
  • If not used, the company is not responsible for problems that occur due to non-application of patches.
Table. MariaDB(DBaaS) Replica Configuration Items

Reconfiguring Replica

If a network failure or replication delay occurs between the master cluster and the replica, you can reconfigure the replica to re-replicate the master cluster’s data.

To reconfigure a replica, follow these steps:

  1. Click All Services > Database > MariaDB(DBaaS). This will take you to the MariaDB(DBaaS) Service Home page.
  2. Click MariaDB(DBaaS) on the Service Home page. This will take you to the MariaDB(DBaaS) list page.
  3. Click the resource you want to reconfigure a replica for on the MariaDB(DBaaS) list page. This will take you to the MariaDB(DBaaS) details page.
  4. Click the Reconfigure Replica button. The Reconfigure Replica notification popup will open.
  5. Click the Confirm button in the Reconfigure Replica notification popup.

Promoting Replica Cluster to Master

You can promote a configured replica cluster to a master cluster.

Note
When promoting to a master, synchronization with the existing master cluster is terminated.

To promote a replica cluster to a master, follow these steps:

  1. Click All Services > Database > MariaDB(DBaaS). This will take you to the MariaDB(DBaaS) Service Home page.
  2. Click MariaDB(DBaaS) on the Service Home page. This will take you to the MariaDB(DBaaS) list page.
  3. Click the resource you want to promote to a master on the MariaDB(DBaaS) list page. This will take you to the MariaDB(DBaaS) details page.
  4. Click the More button and then click the Promote to Master button. The Promote to Master notification popup will open.
  5. Click the Confirm button in the Promote to Master notification popup.

3.3 - API Reference

API Reference

3.4 - CLI Reference

CLI Reference

3.5 - Release Note

MariaDB(DBaaS)

2025.07.01
FEATURE User (Access Control) Management, Archive Setting Function, DB Audit Log Export Function Added, Backup Notification Function Provided, Migration Function Added
  • MariaDB(DBaaS) feature added
    • 2nd generation server type added
  • Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see MariaDB(DBaaS) server type
    • DB user and access control management and Archive setting function added
  • For more information, see DB User Management, DB Access Control Management, Archive Management
    • DB Audit Log Export feature added
  • For more detailed information, please refer to DB Log Export
  • Backup Notification Feature provided
  • Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
    • Migration feature added
      • Provides a Migration function that replicates the database in the Samsung Cloud Platform environment in Replication mode. For more information, see Configuring Migration
    • Block Storage type added HDD, HDD_KMS type
2025.02.27
FEATURE Server type addition and server-specific IP setting, Block Storage capacity expansion feature added
  • MariaDB(DBaaS) feature change
  • 2nd generation server type added * Added 2nd generation (dbh2) server type based on Intel 4th generation (Sapphire Rapids) processor. For more information, see MariaDB(DBaaS) server type
    • After creating a service, it is possible to increase the Block Storage capacity that has been set.
    • The server-based network IP setting function has been added, allowing for common settings or server-based settings according to the purpose of use.
  • Samsung Cloud Platform common feature changes
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.10.01
NEW MariaDB(DBaaS) Service Official Version Release
  • Block Storage type has an option to select encrypted storage for volume added
  • A feature that can switch the role (Active ↔ Standby) of Active DB and Standby DB composed of duplication has been added.
  • Cloud monitoring service is linked, so DB instance performance and log monitoring are possible.
  • Depending on the server type selected by the customer, Planned Compute policy settings are possible.
2024.07.02
NEW Beta version release
  • A MariaDB(DBaaS) service that can easily create and manage MariaDB in a web environment has been released.

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 content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user-specified times, supporting data recovery at the desired point in time.

Architecture
Figure. MySQL(DBaaS) Architecture

Provided Features

MySQL(DBaaS) provides the following features.

  • Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) is possible via UI, and it provides an Active-standby redundancy configuration based on storage replication. In case of an Active server failure, automatic failover to Standby occurs.
  • Operation Control Management: Provides functionality to control the status of running servers. In addition to start and stop, restart is possible if there is a DB issue or to apply configuration values. When configured for high availability (HA), users can directly perform node switching between Active-Standby via Switch-over.
  • Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage agency can be set by the user, and additional fees are incurred based on backup size. It also provides a recovery function for backed-up data, creating a separate DB when the user performs a recovery, and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). When recovering to a user-specified point, the recovery point can be set up to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
  • Version Management: Provides version upgrade (Minor) functionality for some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, then the DB engine is updated.
  • Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
  • Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
  • Service Status Query: Retrieves the final status of the current DB service.
  • Monitoring: CPU, memory, DB performance monitoring information can be checked via the Cloud Monitoring service.
  • 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 IPs.
  • Archive Management: You can set the Archive file retention period (1 day~35 days) within 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: Synchronize data in real time with the operating database, and support migration using the Replication method without service interruption.

Components

MySQL (DBaaS) provides pre-validated engine versions and various server types according to the open-source support policy. Users can select and use them according to the scale of the service they want 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 stopped 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.

ServiceProvided VersionEOS Date(Samsung Cloud Platform New Creation Stop Date)EoTS Date(Community Technical Support End Date)
MySQL (Community)8.0.282026-03 (scheduled)2026-04-30
8.0.302026-03 (scheduled)2026-04-30
8.0.322026-03 (scheduled)2026-04-30
8.0.332026-03 (scheduled)2026-04-30
8.0.342026-03 (scheduled)2026-04-30
8.0.352026-03 (scheduled)2026-04-30
8.0.362026-03 (scheduled)2026-04-30
8.0.372026-03 (scheduled)2026-04-30
8.0.412026-03 (scheduled)2026-04-30
8.0.422026-03 (scheduled)2026-04-30
8.4.52031-12 (planned)2032-04-30
Table. MySQL(DBaaS) Engine Versions Provided

Server Type

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

For detailed information about the server types provided by MySQL(DBaaS), please refer to MySQL(DBaaS) Server Types.

Standard db1v2m4






Category Example Detailed Description
Server Type Standard Provided Server Types
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server Specifications db1 Provided Server Specifications
  • db1: Standard specifications (vCPU, Memory) configuration 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. MySQL(DBaaS) server type components
# Pre-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 for details and prepare in advance.<br>
Service Category Service Detailed Description
Networking VPC A service that provides an independent 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 with various combinations of CPU, Memory, and Network Bandwidth. When creating a MySQL(DBaaS), the database engine is installed according to the selected server type, which is chosen based on the intended use.

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

Standard db1v2m4
Classification
ExampleDetailed Description
Server TypeStandardClassification of provided server types
  • Standard: Composed of standard specifications (vCPU, Memory) for general use
  • High Capacity: Composed of high-capacity server specifications above Standard
Server Specificationdb1Classification of provided server types and generations
  • db1: Represents standard specifications, and 1 represents the generation
  • dbh2: h represents high-capacity server specifications, and 2 represents the generation
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory capacity
  • m4: 4GB Memory
Table. MySQL(DBaaS) Server Type Format

db1 Server Type

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

  • Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MySQL(DBaaS) Server Type Specifications - db1 Server Type

dbh2 Server Type

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

  • Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
  • Supports up to 128 vCPUs and 1,536 GB of memory
  • Up to 25Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBUp to 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBUp to 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBUp to 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBUp to 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBUp to 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBUp to 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBUp to 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBUp to 25 Gbps
Table. MySQL(DBaaS) Server Type Specifications - dbh2 Server Type

4.1.2 - Monitoring Metrics

MySQL(DBaaS) Monitoring Metrics

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

MySQL(DBaaS)’s server monitoring metrics, please refer to the Virtual Server Monitoring Metrics guide.

Performance ItemDetailed DescriptionUnit
Active LocksActive Locks countcnt
Active SessionsActive Session countcnt
Binary Log Used [MB]binary log usageMB
Connection Usage [Total]DB connection session usage rate%
ConnectionsConnection countcnt
Connections [MAX]Connection countcnt
Connectionsmax connected threads countcnt
Data Directory Used [MB]data directory usageMB
Instance Status [PID]mysqld process pidpid
Open FilesNumber of DB files in open statecnt
Open Files [MAX]number of DB files that can be openedcnt
Open Files UsageDB file maximum count usage rate%
Relay Log Used [MB]relay log usage (MB)MB
Running Threadsrunning thread numbercnt
Safe PIDsafe program pidpid
Slave Behind Master secondstime difference with master nodesec
SlowqueriesNumber of SQL queries running for a long time (5 minutes or more) (by DB)cnt
Slowqueries [Total]Number of SQL queries running for a long time (5 minutes or more) (total)cnt
Tablespace UsedTablespace usageMB
Tablespace Used [Total]Tablespace total usageMB
Transaction Time [Long]Transaction longest execution timesec
Wait LocksNumber of sessions blocked for 60 seconds or more by lockcnt
Table. MySQL(DBaaS) Monitoring Metrics

4.2 - How-to guides

Users can enter the required information for MySQL (DBaaS) through the Samsung Cloud Platform Console, select detailed options, and create the service.

Creating MySQL(DBaaS)

You can create and use the MySQL (DBaaS) service in the Samsung Cloud Platform Console.

Notice
  • Please configure the VPC’s Subnet type as General before creating the service.
    • If the Subnet type is Local, the creation of the corresponding Database service is not possible.
  • If you load more than 2 TB of large-scale data, backups may take a long time or the DB’s performance may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.

To create MySQL(DBaaS), follow the steps below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) 생성 button on the Service Home page. You will be taken to the MySQL(DBaaS) 생성 page.
  3. MySQL(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
      Detailed description
      Image versionRequiredProvide version list of MySQL (DBaaS)
      Table. MySQL(DBaaS) image and version selection items
    • Service Information Input area, please enter or select the required information.
      Category
      Required
      Detailed description
      Server Name PrefixRequiredServer name where DB will be installed
      • Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (-) to input 3 to 13 characters
      • Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
      Cluster NameRequiredCluster name composed of DB servers
      • Enter using English letters, 3 to 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type where DB will be installed
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server of 24 vCore or more
      Service Type > Planned ComputeOptionalStatus of resources with Planned Compute set
      • In Use: Number of resources with Planned Compute that are in use
      • Configured: Number of resources with Planned Compute set
      • Coverage preview: Amount applied per resource by Planned Compute
      Redundancy configurationSelectRedundancy configuration status
      • If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
      Network > Common SettingsRequiredNetwork settings where servers created by the service are deployed
      • Select if you want to apply the same settings to all servers being installed
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be auto‑generated
        • 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 details, see Create Public IP.
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply different settings per installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter each server’s IP
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. For more details, see Create Public IP.
      IP Access ControlSelectService Access Policy Settings
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      Maintenance PeriodSelectDB Maintenance Period
      • Use: set day of week, start time, and duration
      • It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption.
      • If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
      Table. MySQL(DBaaS) Service Configuration Items
    • Database configuration required information input Enter or select the required information in the area.
      Category
      Required
      Detailed description
      Database nameRequiredServer name applied when installing DB
      • Start with an English letter, use English letters and numbers, and enter 3 to 20 characters
      Database usernameRequiredDB user name
      • An account with the same name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted Database usernames can be checked in the Console
      Database passwordRequiredPassword to use when accessing the DB
      • Enter 8-30 characters including letters, numbers, and special characters ( excluded)
      Database Password ConfirmationRequiredRe-enter the same password to be used when accessing the DB
      Database Port numberRequiredPort number required for DB connection
      • Enter DB port within the range 1,024 ~ 65,535
      Backup > UseSelectWhether to use backup
      • Select Use to set backup file retention period, backup start time, Archive backup cycle
      Backup > Retention PeriodSelectBackup Retention Period
      • Select the backup retention period. File retention period can be set from 7 days to 35 days
      • Backup files incur additional charges depending on size
      Backup > Backup Start PeriodSelectBackup Start Time
      • Select backup start time
      • The minutes (minutes) at which the backup is performed are set randomly, and the backup end time cannot be set
      Backup > Archive backup frequencySelectArchive backup frequency
      • Select the Archive backup frequency
      • Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
      ParameterRequiredParameters to use in the DB
      • View button to click to view detailed information of the parameter
      • Parameters can be modified after DB creation is completed, and after modification the DB must be restarted
      DB character setRequiredCharacter encoding method to be used in the DB
      Table case sensitivityselectDB Table case sensitivity status
      Time zoneRequiredStandard time zone to be used by the Database
      Table. MySQL(DBaaS) Database configuration items
    • Enter additional information in the area, please enter or select the required information.
      Category
      Required
      Detailed description
      TagSelectAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. MySQL(DBaaS) Additional Information Input Items
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Resource List page.

MySQL(DBaaS) Check detailed information

The MySQL (DBaaS) service allows you to view and edit the full resource list and detailed information. The MySQL (DBaaS) Details page consists of Details, Tags, Activity History tabs, and for databases with a Replica configured, a Replica Information tab is additionally provided.

To view detailed information of the MySQL (DBaaS) service, follow the steps below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. You will be taken to the MySQL(DBaaS) List page.
  3. Click the resource to view detailed information on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  • MySQL(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
    CategoryDetailed description
    Cluster StatusCluster status with DB installed
    • Creating: Cluster is being created
    • Editing: Cluster is changing to operation execution 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 being restarted
    • Running: Cluster is operating normally
    • Starting: Cluster is being started
    • Stopped: Cluster is stopped
    • Stopping: Cluster is being stopped
    • Synchronizing: Cluster is being synchronized
    • Terminating: Cluster is being deleted
    • Unknown: Cluster status is unknown
      • If it occurs continuously, contact the administrator
    • Upgrading: Cluster is changing to upgrade execution state
    Cluster ControlButton to change 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 additional featuresCluster related management buttons
    • Service status synchronization: Real-time DB service status lookup
    • Backup history: If backup is set, check whether backup runs normally and view history
    • Database recovery: Recover DB based on a specific point in time
    • Parameter management: DB configuration parameters can be queried and modified
    • Replica configuration: Set up a read-only cluster called Replica
    • 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 IPs
    • Archive management: Can set archive file retention period and archive mode
    • DB Log export: Through audit settings, stored logs can be exported to the user’s Object Storage
    • Migration configuration: Provides migration functionality using replication method
    Service cancellationButton to cancel the service
    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, if needed, modify the information.

CategoryDetailed description
Server InformationServer information configured in the cluster
  • Category: Server type (Active, Standby, Replica)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In DB service, it means cluster SRN
Resource NameResource Name
  • In DB service, it means the cluster name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
EditorUser who modified the service information
Modification Date/TimeDate and time when service information was modified
Image/VersionInstalled DB image and version information
  • If a version upgrade is needed, click the Edit icon to set
Cluster TypeCluster Type (Master Cluster, Replica Cluster, Migration Cluster)
Cluster NameName of the cluster composed of DB servers
Master cluster nameReplica’s Master cluster name
  • If detailed information of Replica, can be confirmed
Database nameServer name applied when installing DB
Database usernameDB user name
Planned ComputeResource status with Planned Compute set
Maintenance PeriodDB Maintenance Period Status
  • If maintenance period setting is required, click the Edit icon to set
BackupBackup Settings Status
  • If backup settings are needed, click the Edit icon to set
Time zoneStandard time zone used by the Database
DB character setEncoding method to use in DB
Table case sensitivityDB Table case sensitivity status
VIPVirtual IP information
  • Can be checked only when high availability is configured
NetworkNetwork information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP Access ControlService Access Policy Settings
  • If you need to add or delete an IP, click the Edit icon to set
Active & StandbyActive/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 set it. Refer to the server type modification procedure Change Server Type
    • 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 Expand Storage
  • If you need to add storage, click the Add Disk button next to Additional Disk to add. Refer to the storage addition procedure Add Storage
Table. MySQL(DBaaS) Database detailed information items

Replica Information

Replica Information tab is enabled only when a Replica is configured in the cluster. Through the Replica Information tab, you can check the Master cluster name, number of replicas, and Replica status.

CategoryDetailed description
Master InformationName of Master Cluster
Replica countNumber of Replicas created in the Master cluster
Replica statusReplica server status created in the Master cluster
  • Server name, status query, status details, status check time can be verified
  • To query the Replica status, click the Status Query button
    • While querying, the cluster remains in Synchronizing status, and once the query is complete, the cluster changes to Running status
Table. Replica Information Tab Detailed Information Items

Tag

MySQL(DBaaS) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • You can view the Key and Value information of tags
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the previously created Key and Value list
Table. MySQL(DBaaS) Tag Tab Items

Work History

On the MySQL(DBaaS) List page, you can view the operation history of the selected resource.

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, Resource ID, Resource name, Work details, Event topic, Work result, Check worker information
Table. Work History Tab Detailed Information Items

MySQL(DBaaS) Resource Management

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 tasks on the MySQL (DBaaS) Details page.

Operating Control

If changes occur to the running MySQL (DBaaS) resources, you can start, stop, or restart them. Also, if 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page.
  3. Click the resource to control operation on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Check the status of MySQL (DBaaS) and complete the change using the control button below.
    • Start: The server where the DB service is installed and the DB service are running (Running).
    • Stop: The server where the DB service is installed and the DB service are 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 check the service status of MySQL (DBaaS), follow the steps below.

  1. All Services > Database > MySQL(DBaaS) Click the menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page. 3. MySQL(DBaaS) List Click the resource to view the service status. MySQL(DBaaS) Detail Navigate to the page.
  3. Service status synchronization button. Click the button. While fetching, the cluster changes to Synchronizing state.
  4. 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.

To change the server type, follow the steps below.

Caution
  • If you modify the server type, a server reboot is required. Please separately verify any SW license changes or SW settings and their application due to spec changes.
  1. All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page.
  3. Click the resource to change the server type on the MySQL(DBaaS) 목록 page. It will move to the MySQL(DBaaS) 상세 page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window will open.
  5. Server Type Edit 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 space, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.

Caution
  • It is applied the same way as the selected Storage type when creating a service.
  • If a DB is configured for high availability, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
  • If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. Please expand the Replica storage first, then expand the Master cluster storage.
  • When adding Archive/Temp storage, the DB restarts and is temporarily unavailable

To add storage, follow the steps below.

  1. All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to add storage. It navigates to the MySQL(DBaaS) Details page.
  4. Click the Add Disk button at the bottom of the detailed information. The Add Storage Request popup window opens.
  5. Additional Storage Request After entering purpose and capacity in the popup window, click the Confirm button.

Expanding storage

The 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.

  1. All Services > Database > MySQL(DBaaS) Click the menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) list page.
  3. Click the resource to change the server type on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. The Edit Additional Storage popup window opens.
  5. Add Storage Modification In the popup window, after entering the expansion capacity, click the Confirm button.

MySQL(DBaaS) Cancel

You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, please terminate it separately from the resource list.
  • If you cancel the DB, any stored data and, if backup is set, all backup data will be deleted.

To cancel MySQL (DBaaS), follow the steps below.

  1. All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. You will be taken to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List On the page, select the resource to cancel, and click the Cancel Service button.
  4. When the termination is complete, check whether the resource has been terminated on the MySQL (DBaaS) list page.

4.2.1 - MySQL(DBaaS) server connection

Scenario Overview

The MySQL(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To connect to MySQL(DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.

This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, so that it can be accessed through a DB connection client.

Architecture
Figure. MySQL(DBaaS) server connection architecture

Scenario Components

You can configure the scenario using the following services.

Service Group
Service
Detailed Description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that allows users to subdivide the network into smaller sections for specific purposes/sizes within the VPC
NetworkingVPC > Public IPA service that reserves a public IP and assigns and returns it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the internet
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
DatabaseMySQL(DBaaS)A service that easily creates and manages MySQL in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to Virtual Server
Table. List of scenario components
Reference
The default policy of the * Security Group is Deny All, so only allowed IPs should be registered. The In/Outbound’s All Open policy (Any IP, Any Port) can expose cloud resources to external threats. * By specifying the necessary IP and Port, you can enhance security by setting up a policy.

Scenario composition method

To configure the scenario, create the necessary services through the following procedure.

1. Configuring the Network

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

1-1. Creating a VPC

For detailed creation methods, please refer to the Networking > VPC > How-to guides guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
  3. VPC Creation page, please enter the information needed to create the service.
    • IP range should be entered as 192.168.x.0/16.
  4. In the Summary panel, review the detailed information and estimated charge, then click the Complete button.
    • Once the creation is complete, check the created resource on the VPC list page.

1-2. Creating a Subnet

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Subnet menu. It moves to the Subnet list page.
  3. Click the Subnet Creation button. It moves to the Subnet Creation page.
  4. Subnet creation page where you enter the information needed to create a service.
    • Subnet type should be selected as General.
    • Please select a pre-created VPC.
    • IP range should be entered as 192.168.x.0/24.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • After creation is complete, check the created resource on the Subnet list page.

1-3. Creating an Internet Gateway

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
  3. Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
  4. Internet Gateway creation page, please enter the required information necessary for service creation.
    • Please select a pre-created VPC.
    • Select use in the Firewall usage item.
  5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once the creation is complete, check the created resource on the Internet Gateway list page.

1-4. Creating a Public IP

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Click the Public IP menu on the Service Home page. It moves to the Public IP list page.
  3. Public IP Reservation button, click. Move to the Public IP Reservation page.
  4. Public IP Reservation page where you enter the required information necessary for service reservation.
  5. Check the detailed information generated in the Summary panel and the expected bill amount, and click the Complete button.
    • After creation is complete, check the created resource on the Public IP List page.

1-5. Creating a Security Group

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
  2. Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
  3. Security Group creation page where you enter the required information necessary for service creation.
  4. Check the input information and click the Complete button.
    • Once creation is complete, check the created resource on the Security Group list page

2. Creating a Bastion Host

This describes the process of configuring the Bastion Host where the database connection client should be installed.

2-1. Creating a Server Keypair

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
  3. Keypair creation button should be clicked. It moves to the Keypair creation page.
  4. Keypair creation page, please enter the required information necessary for service creation.
  5. Check the creation information and click the Complete button.
    • The key can only be downloaded for the first time, and re-issuance is not provided.
    • Please keep the downloaded key in a safe place.

2-2. Creating a Bastion Host

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
  3. Virtual Server Creation page, please enter the required information necessary for service creation.
  4. Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
    • Once creation is complete, check the created resource on the Virtual Server list page.

2-3. Check Bastion host connection ID and PW

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
  3. Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
  4. Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
  5. RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
  6. After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.

3. Creating a Database

It describes the process of creating a database service.

3-1. Creating a MySQL (DBaaS) Service

For detailed creation methods, please refer to the Database > MySQL(DBaaS) > How-to guides guide.
  1. Click on the menu for all services > Database > MySQL(DBaaS). It moves to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the Create MySQL(DBaaS) button. It moves to the Create MySQL(DBaaS) page.
  3. MySQL(DBaaS) creation page, please enter the required information needed for service creation.
    • Select and connect the pre-created VPC and Subnet.
    • Enter database-related creation information on the required information input screen.
    • Add the Bastion host IP to the IP access control item.
    • Database Port is 2866 by default, but you can specify it as you want.
  4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
    • Once the creation is complete, check the created resource on the MySQL(DBaaS) list page.

4. Setting Rules

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

4-1. Adding Security Group Security Rules

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Security Group menu. Move to the Security Group list page.
  3. 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule popup window, enter the rules below, and click the OK button
DirectionRemoteDestination AddressProtocolPortDescription
InboundCIDRUser PC IPTCP3389 (RDP)Bastion connection PC → Bastion host
OutboundCIDRDB IPTCPDatabase Port (direct input)Bastion host → Database
Fig. Security Group security rules to be added

4-2. Adding IGW Firewall Rules

For detailed creation methods, please refer to the Networking > Firewall > How-to guides guide.
  1. Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
  2. Service Home page, click the Firewall menu. It moves to the Firewall list page.
  3. Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
  6. Add Rule In the popup window, enter the rules below and click the OK button.
Departure AddressDestination AddressProtocolPortActionDirectionDescription
Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
Fig. Internet Gateway Firewall rules to be added

5. Connect to Database

This describes the process of a user accessing the Database through a DB connection client program.

This guide provides instructions on how to connect using MySQL Workbench. There are various database client programs and CLI utilities, so you can install and use the tools that suit you.

5-1. Connecting to the Bastion host

  1. Run Remote Desktop Connection in the Windows environment of the PC you want to access the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
  2. After a successful remote desktop connection, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Access ID and PW and click the Confirm button.

5-2. Install DB connection client program (MySQL Workbench) on the Bastion host

  1. Go to the official MySQL page and download the MySQL Workbench program.
  2. Connect the hard drive of the user’s PC to upload the file to the Bastion host.
  3. Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
  4. Select the local disk where the file was downloaded to the drive and click the Confirm button.
  5. Copy the downloaded file and upload it to the Bastion Host, then click the MySQL Workbench installation file to install it.

5-3. Using DB connection client program (MySQL Workbench) to connect to the Database

  1. Run MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup window will appear.
  2. Manage Server Connection popup window, click the New button at the bottom left and enter the database server information created in 3-1. MySQL(DBaaS) service creation, then click the Test Connection button. A Password popup window will appear.
    Required Input Element ItemsInput Value
    Connection NameCustom (ex. Service Name)
    Host nameDatabase server IP
    PortDatabase Port
    UsernameDatabase username
    DB connection client program input items
  3. Password popup window, enter the password set in 3-1. MySQL(DBaaS) service creation and click the OK button. When the success is complete, click the OK button in the Manage Server Connection popup window.
  4. Database > Connect to Database should be clicked. The Connect to Database popup window will appear.
  5. Select the Connection Name registered in Stored Connection to perform database connection. After connection, you can try simple queries, etc.

4.2.2 - Managing DB Services

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

Managing Parameters

It provides a feature to easily view and modify database configuration parameters.

Viewing Parameters

To view configuration parameters, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.

Modifying Parameters

To modify configuration parameters, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.
  7. If modification is necessary, click the Modify button and enter the modification contents in the user-defined value area of the parameter to be modified.
  8. When the input is complete, click the Save button.

Managing DB Users

It provides a management feature that allows you to view DB user information and change status information.

Viewing DB Users

To view DB users, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource you want to view DB users on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. It moves to the DB User Management page.
  5. Click the View button on the DB User Management page. It takes some time to view.

Changing DB User Status

To change the status of the viewed DB user, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource you want to modify DB users on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. It moves to the DB User Management page.
  5. Click the View button on the DB User Management page. It takes some time to view.
  6. If modification is necessary, click the Modify button and change the status area value or enter remarks.
  7. When the input is complete, click the Save button.

Managing DB Access Control

It provides an IP-based DB user access control management feature. Users can directly specify the IP that can access the database, allowing only allowed IPs to access.

Guide
Before setting DB access control, perform DB user inquiry. For DB user inquiry, refer to Managing DB Users.

Viewing DB Access Control

To view DB users with IP access control set, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource you want to manage access control on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. Click the View button on the DB Access Control Management page. It takes some time to view.

Adding DB Access Control

To add IP access control, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource you want to add IP access control on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
  5. Click the View button on the DB Access Control Management page. It takes some time to view.
  6. When the view is complete, click the Add button. The DB Access Control Add popup window opens.
  7. In the DB Access Control Add popup window, select the DB user name and enter the IP address.
  8. When the input is complete, click the Save button.

Deleting DB Access Control

To delete IP access control, follow these steps:

  1. Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
  2. Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
  3. Click the resource for which you want to delete IP access control on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
  4. Click the More button and then click the DB Access Control Management button. The DB Access Control Management page will be displayed.
  5. Click the Inquiry button on the DB Access Control Management page. It may take some time to retrieve the data.
  6. Once the inquiry is complete, click the Delete button. A Delete pop-up window will appear.
  7. Click the Confirm button in the Delete pop-up window.

Managing Archive

The Archive mode setting and Archive Log retention period setting functions are provided, allowing users to flexibly set the Archive log management policy according to their operating environment. Additionally, the function to manually delete Archive logs is provided together, allowing users to clean up unnecessary log data and effectively manage system resources.

Notice
The default setting when creating a service is Archive mode enabled, with a retention period of 3 days.

Setting Archive Mode

To set the Archive mode, follow these steps:

  1. Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
  2. Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
  3. Click the resource for which you want to set the Archive mode on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
  4. Click the More button and then click the Archive Settings Management button. The Archive Settings Management page will be displayed.
  5. Click the Inquiry button on the Archive Settings Management page. It may take some time to retrieve the data.
  6. Click the Modify button and select the usage and retention period.
  7. Once the modification is complete, click the Save button.

Deleting Archive Files

To delete Archive files, follow these steps:

  1. Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
  2. Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
  3. Click the resource for which you want to set the Archive mode on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
  4. Click the More button and then click the Archive Settings Management button. The Archive Settings Management page will be displayed.
  5. Click the Archive All Delete button to delete all Archive files, or click the Backup Archive Delete button to delete only the backed-up Archive files.

Exporting DB Logs

The function to export audit logs to Object Storage is supported, allowing users to set the log type, target bucket, and export cycle. According to the set criteria, the logs are copied to the specified Object Storage for storage. Additionally, an option to automatically delete the original log files when exporting logs to Object Storage is provided, allowing users to effectively secure storage capacity while safely storing necessary log data.

Notice
  • To use the DB Log export function, Object Storage creation is required. Refer to the Object Storage user guide for Object Storage creation.
  • Be sure to check the expiration date of the authentication key. If the authentication key expires, the log will not be stored in the bucket.
  • Be careful not to expose the authentication key information to the outside.

Setting DB Log Export Mode

To set the DB Log export mode, follow these steps:

  1. Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
  2. Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
  3. Click the resource for which you want to export DB logs on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
  4. Click the More button and then click the DB Log Export button. The DB Log Export page will be displayed.
  5. Click the Register button on the DB Log Export page. The DB Log Export Registration page will be displayed.
  6. Enter the required information on the DB Log Export Registration page and click the Save button.
CategoryRequired
Detailed Description
Log TypeRequiredLog type to be stored
Storage Bucket NameRequiredObject Storage bucket name to store the log
Authentication Key > Access KeyRequiredAccess key to access the Object Storage
Authentication Key > Secret KeyRequiredSecret key to access the Object Storage
File Creation CycleRequiredCycle to create files in Object Storage
Original Log DeletionOptionalWhether to delete the original log when exporting to Object Storage
Table. MySQL(DBaaS) Migration Configuration Items

Managing DB Log Export

To modify, cancel, or immediately export DB log settings, follow these steps:

  1. Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
  2. Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
  3. Click the resource for which you want to manage DB log export on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
  4. Click the More button and then click the DB Log Export button. The DB Log Export page will be displayed.
  5. Click the More button for the log type you want to manage on the DB Log Export page, and then click the Immediate Export, Modify, or Cancel button.
    • Immediate Export: Exports the selected log to the Object Storage bucket.
    • Modify: Modifies the DB log export mode setting.
    • Cancel: Cancels the DB log export mode setting.

Upgrading DB Version

The function to upgrade the version for some feature improvements and security patches is provided. Only minor version upgrades are supported within the same major version.

Caution
  • Please perform a service status synchronization to check the service status before upgrading the version.
  • Please set up a backup before upgrading the version. If you do not set up a backup, you may not be able to recover some data in case of problems during the update.
  • In the case of a DB with a replica configured, the master DB version must be higher than or equal to the replica version. Please check the replica version first and perform a version upgrade if necessary.
  • The backed-up data will be automatically deleted after the version upgrade is complete.

To upgrade the version, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource to be upgraded on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the Modify button in the image/version item. The Version Upgrade popup window opens.
  5. In the Version Upgrade popup window, select the version to be modified and the backup setting, and then click the OK button.
  6. Click the OK button in the Version Upgrade Notification popup window.

Configuring Migration

It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.

Notice
For a detailed migration configuration guide, please refer to Architecture Center > Migration Guide > Database Migration Procedure and Considerations.

To configure the migration, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource to be migrated on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Configure Migration button. The Configure Migration popup window opens.
  5. In the Configure Migration popup window, check the instructions and click the OK button. It moves to the Configure Migration page.
  6. On the Configure Migration page, enter the corresponding information and click the Connect Check button.
  7. When the connection is complete, click the Complete button.
ClassificationRequired
Detailed Description
Source DB Database NameRequiredDatabase name of the source DB that is the migration target
Source DB IPRequiredIP of the source DB that is the migration target
Source DB PortRequiredPort of the source DB that is the migration target
Source DB User NameRequiredUser name of the source DB that is the migration target
Source DB PasswordRequiredPassword of the source DB that is the migration target
Table. MySQL(DBaaS) Migration Configuration Items

The configured migration cluster can be promoted to a master cluster.

Caution
When promoting to a master, synchronization with the source DB that is the migration target will be stopped.

To promote the migration cluster to a master, follow these steps:

  1. Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
  3. Click the resource to be promoted to a master on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Promote to Master button. The Master Promotion Notification popup window opens.
  5. Click the OK button in the Master Promotion Notification popup window.

4.2.3 - DB Backup and Recovery

The user can set up a backup of MySQL(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.

MySQL(DBaaS) Backup

PostgreSQL(DBaaS) provides a data backup feature based on its own backup command. It also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.

Setting up backup

The method of setting up a backup for MySQL(DBaaS) is described in MySQL(DBaaS) creation guide.

To modify the backup settings of the generated resource, follow these steps.

Caution
  • For stable backup, it is recommended to add a separate BACKUP storage or to sufficiently expand the storage capacity. Especially when the backup target data exceeds 100 GB and the data change is frequent, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, please refer to the MySQL(DBaaS) Add Storage, MySQL(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.

To set up backup, follow these steps.

  1. All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
  2. Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
  3. MySQL(DBaaS) list page, click the resource to set the backup. It moves to the MySQL(DBaaS) details page.
  4. Click the Edit button of the backup item. The Backup Settings popup window opens.
  5. If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the Confirm button.
    • If you want to stop the backup settings, uncheck Use in the Backup Settings popup window and click the OK button.

Check Backup History

Notice
To set up notifications for backup success and failure, you can set it up through the Notification Manager product. For detailed usage guidelines on notification policy settings, please refer to Creating a Notification Policy.

To view the backup history, follow these steps.

  1. All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
  3. MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Delete backup files

Caution
Backup files cannot be restored after deletion. Please make sure to confirm that the data is unnecessary before deleting it.

To delete the backup history, follow these steps.

  1. Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
  3. MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) detail page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window, check the file you want to delete, and then click the Delete button.

Recovering MySQL(DBaaS)

In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing MySQL (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, the DB is installed with the version at the backup point in time, and the recovery proceeds with the DB configuration information and data.

Caution
To perform recovery, at least 2 times the capacity of the data type Disk capacity is required. If the disk capacity is insufficient, recovery may fail.

To restore MySQL(DBaaS), follow these steps.

  1. All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
  3. MySQL(DBaaS) resource list page, click the resource you want to restore. It moves to the MySQL(DBaaS) details page.
  4. Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
  5. Enter the corresponding information in the Database Recovery Configuration area, and then click the Complete button.
Classification
Necessity
Detailed Description
Recovery TypeRequiredSet the point in time you want to recover
  • Backup Point (Recommended): Recover based on the backup file. Select from the list of backup file points displayed in the list
  • Custom Point: Recover to the desired point within the range of possible backup times. The recoverable period is from the initial backup start time to the current time, based on the Archive backup cycle setting value, and can be recovered up to 1 hour/30 minutes/10 minutes/5 minutes ago. Select the date and time you want to back up
Server name prefixRequiredServer name of the recovery DB
  • Start with lowercase English letters, using lowercase letters, numbers, and special characters (-) to input 3 ~ 16 characters
  • A postfix such as 001, 002 is attached based on the server name, and the actual server name is created
Cluster NameRequiredCluster name of the recovery DB
  • Enter in English, 3-20 characters
  • Cluster is a unit that bundles multiple servers
Service Type > Server TypeRequiredServer type where the recovery DB will be installed
  • Standard: Standard specification commonly used
  • High Capacity: High-capacity server with 24vCore or more (to be provided later)
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are currently in use
  • Setting: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
  • Create Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredRecovery DB uses Block Storage settings
  • Basic OS: Area where the DB engine is installed
  • DATA: Storage area for table data, archive files, etc.
    • The storage type set in the original cluster is applied in the same way
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Additional: DATA, Archive, TEMP, Backup data storage area
    • The storage type set in the original cluster is applied in the same way
    • Only DATA, TEMP, and Archive purposes can be added in the recovery DB
    • After selecting Use, enter the purpose and capacity of the storage
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Database usernamerequiredDatabase username set in the original DB
Database Port numberrequiredDatabase Port number set in the original DB
IP Access ControlSelectIP address to access the recovery DB
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.1/32, 192.168.10.1/32) and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectDB maintenance period
  • Use is selected to set the day, start time, and duration
  • It is recommended to set the maintenance period for stable management of the DB, and patch work is performed at the set time, resulting in service interruption
  • If not used, Samsung SDS is not responsible for any problems that occur due to non-application of patches.
tagselectionadd tag
  • add tag button, click after Key, Value value input or selection
Fig. MySQL(DBaaS) Recovery Configuration Items

4.2.4 - Setting up Read Replica

The user can enter the necessary information for the Read Replica through the Samsung Cloud Platform Console and create the service through detailed options.

Configuring Replica

You can create a read-only replica server through Replica configuration. Up to 5 Replicas can be created per Database.

To configure a replica, follow these procedures.

  1. All services > Database > MySQL(DBaaS) menu, click. It moves to the Service Home page of MySQL(DBaaS).
  2. Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
  3. MySQL(DBaaS) list page, click on the resource to configure the Replica. Move to the MySQL(DBaaS) details page.
  4. Click the Replica Configuration button. It moves to the Replica Configuration page.
  5. Enter information in the Replica Configuration area, then click the Complete button.
    Classification
    Necessity
    Detailed Description
    Number of ReplicasRequiredNumber of Replicas to configure
    • Up to 5 can be configured per cluster
    • If selecting 2 or more values, additional input of Replica name and service type information is required
    Replica namerequiredReplica server name
    • Starts with lowercase English letters, using lowercase letters, numbers, and special characters (-) to input 3 ~ 19 characters
    • The entered Replica name is exposed as the cluster name in the list
    Service Type > Server TypeRequiredReplica Server Type
    • Standard: Standard specification commonly used
    • High Capacity: High-capacity server with 24vCore or more
    Service Type > Planned ComputeSelectCurrent status of resources with Planned Compute set
    • In Use: Number of resources with Planned Compute set that are in use
    • Settings: Number of resources with Planned Compute set
    • Coverage Preview: Amount applied by Planned Compute for each resource
    • Create Planned Compute Service: Move to the Planned Compute service application page
    IP Access ControlSelectSet service access policy
    • Set access policy for IP entered on the page, so separate Security Group policy setting is not required
    • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button
    • To delete the entered IP, click the x button next to the entered IP
    Maintenance periodSelectDB maintenance period
    • Use is selected, set the day of the week, start time, and duration
    • It is recommended to set the maintenance period for stable management of the DB. Patch work is performed at the set time and service interruption occurs
    • If set to not used, the company is not responsible for the problems that occur due to non-application of patches.
    tagselectionadd tag
    • add tag button click after Key, Value value input or selection
    Table. MySQL(DBaaS) Replica Configuration Items

Replica reconstruction

In the event of a network failure or replication delay with the Master Cluster, the Replica reconstruction function can be used to re-replicate the Master Cluster’s data.

To reassemble the replica, follow the procedure below.

  1. Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
  2. Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
  3. Click on the resource to be reconstructed as a replica on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
  4. Replica Reconstruction 버튼을 클릭하세요. Replica Reconstruction Notification 팝업창이 열립니다.
  5. Replica Reconstruction Alert popup window, click the Confirm button.

Promote Replica Cluster to Master Cluster

You can promote a fully configured Replica Cluster to a Master Cluster.

Caution
When Master is promoted, synchronization with the existing Master Cluster is discontinued.

To promote the Replica Cluster to Master, follow these steps.

  1. All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
  3. Click the resource to be promoted to Master on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
  4. Click the More button and click the Master Promotion button. The Master Promotion Notification popup window opens.
  5. In the Master Promotion Alert popup window, click the OK button.

4.3 - API Reference

API Reference

4.4 - CLI Reference

CLI Reference

4.5 - Release Note

MySQL(DBaaS)

2025.07.01
FEATURE User (Access Control) Management, Archive Setting Function, DB Audit Log Export Function Added, Backup Notification Function Provided, Migration Function Added
  • MySQL(DBaaS) feature added
    • 2nd generation server type added
  • Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see MySQL(DBaaS) server type
    • DB user and access control management and Archive setting function added
  • For more detailed information, please refer to DB User Management, DB Access Control Management, Archive Management
    • DB Audit Log Export feature added
  • For more information, see Exporting DB Log
    • Backup Notification Feature provided
  • Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
    • Migration feature added
      • Provides replication-based zero-downtime data migration feature. For more information, see Migration 구성하기
    • Block Storage type added HDD, HDD_KMS type
2025.02.27
FEATURE Server type addition and server-specific IP setting, Block Storage capacity expansion feature added
  • MySQL(DBaaS) feature change
    • 2nd generation server type added
      • Added 2nd generation (dbh2) server type based on Intel 4th generation (Sapphire Rapids) processor. For more information, see mysql(DBaaS) server type
    • After creating a service, it is possible to increase the Block Storage capacity that has been set.
    • Server-specific network IP setting feature has been added, allowing for common settings or server-specific settings depending on the purpose of use.
  • Samsung Cloud Platform common feature changes
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.10.01
NEW MySQL(DBaaS) Service Official Version Release
  • A MySQL(DBaaS) service that allows you to easily create and manage MariaDB in a web environment has been released.

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 the installation of Microsoft SQL Server through a web-based console and perform management functions for operation.

Microsoft SQL Server(DBaaS) is designed with an Always On based availability architecture, and when the content of the Primary server changes, it is synchronously replicated to the Secondary server. Additionally, it provides an automatic backup function at user-specified times to prepare for issues with the DB server or data, supporting data recovery at the desired point in time.

Provided Features

Microsoft SQL Server(DBaaS) provides the following features.

  • Auto Provisioning: Allows installation and configuration of Database (DB) via UI, provides a Primary-Secondary redundancy configuration built on Always On. In case of Primary server failure, it automatically fails over to Secondary.
  • Operation Control Management: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Primary-Secondary via Switch-over.
  • Backup and Recovery: Provides data backup functionality based on its own backup commands. Backup time windows, retention agencies, and full backup days can be set by the user, and additional fees may apply based on backup volume. It also provides a recovery function for backed-up data, creating a separate database when the user performs a recovery, and the recovery proceeds to the point in time selected by the user (backup storage point, user-specified point). When restoring to a user-specified point, the restore point can be set to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
  • Version Management: Provides version upgrade (Minor) functionality due to some feature improvements and security patches. Whether to perform backup for the version upgrade can be selected by the user, and if backup is performed, data is backed up before applying the patch, then the DB engine is updated.
  • Secondary configuration: You can additionally configure a read-only Read Replica (Secondary Replica), enabling read performance scaling and load balancing.
  • Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
  • Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
  • Service status query: Retrieves the final status of the current DB service.
  • Monitoring: CPU, Memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
  • DB User Management: View and manage DB account (user) information registered in the DB.
  • DB Log Export: Through Audit settings, you can export the stored logs to the user’s Object Storage.

Components

Microsoft SQL Server(DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they want to configure.

Engine Version

The engine versions supported by Microsoft SQL Server (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 stopped is set to six months before the EoTS date.

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

Provided versionEOS Date(Samsung Cloud Platform New creation stop date)EoTS Date(Community Technical support end date)
Microsoft SQL Server 2019 Enterprise2029-06 (Planned)2030-01-08(Extended Support)
2025-02-28(Standard Support)
Microsoft SQL Server 2019 Standard2029-06 (planned)2030-01-08(Extended Support)
2025-02-28(Standard Support)
Microsoft SQL Server 2022 Enterprise2032-06 (planned)2033-01-11(Extended Support)
2028-01-11(Standard Support)
Microsoft SQL Server 2022 Standard2032-06 (planned)2033-01-11(Extended Support)
2028-01-11(Standard Support)
Table. Microsoft SQL Server (DBaaS) Engine Versions Provided

Server Type

Microsoft SQL Server(DBaaS) supported server types are as follows.

For detailed information about the server types provided by Microsoft SQL Server(DBaaS), refer to Microsoft SQL Server(DBaaS) Server Type.

Standard db1v2m4
CategoryExampleDetailed description
Server TypeStandardProvided Server Types
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) configuration commonly used
  • dbh2: Large-scale server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. Microsoft SQL Server (DBaaS) server type components

Preliminary 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 for details and prepare in advance.

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
Table. Microsoft SQL Server(DBaaS) Preliminary Service

5.1.1 - Server Type

Microsoft SQL Server(DBaaS) server type

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

The server types supported by Microsoft SQL Server (DBaaS) are as follows.

Standard db1v2m4
Classification
ExampleDetailed Description
Server TypeStandardProvided server type distinction
  • Standard: Composed of standard specifications (vCPU, Memory) commonly used
  • High Capacity: Server specifications with high capacity over Standard
Server Specificationsdb1Classification of provided server type and generation
  • db1: means general specifications, and 1 means generation
  • dbh2: h means large-capacity server specifications, and 2 means generation
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory 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 provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBup to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBup to 12.5 Gbps
Table. Microsoft SQL Server(DBaaS) server type specifications - db1 server type

DB2 server type

The db2 server type of Microsoft SQL Server(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v2m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v6m726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBup to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBup to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBup to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Microsoft SQL Server(DBaaS) server type specifications - db2 server type

DBH2 Server Type

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

  • Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
  • Supports up to 128 vCPUs and 1,536 GB of memory
  • up to 25Gbps of networking speed
ClassificationServer TypevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBUp to 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBUp to 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBUp to 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBUp to 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBUp to 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBUp to 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBUp to 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBUp to 25 Gbps
Table. Microsoft SQL Server(DBaaS) server type specifications - dbh2 server type

5.1.2 - Monitoring Metrics

Microsoft SQL Server(DBaaS) Monitoring Metrics

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

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

Performance ItemDetailed DescriptionUnit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Active Transactions [Total]Number of active transactionscnt
Blocking Session IDLong-running query (slow query)ID
Connected UsersNumber of users connected to the systemcnt
Datavolume Size [Free]Available spacebytes
DBFiles [Not Online]Query to check if all data files are ONLINEcnt
Instance State [Cluster]State when configuring MSSQL clusterstate
Instance State [PID]sqlservr.exe process pidPID
Lock Processes [Blocked]Number of SQL processes blocked by other processescnt
Lock Waits [Per Second]Average number of lock waits per secondcnt
Page IO Latch Wait TimeAverage wait time for Page IO latch waitsms
SlowqueriesLong-running query (slow query)cnt
Slowquery CPU TimeLong-running query (slow query)ms
Slowquery Execute Context IDLong-running query (slow query)ID
Slowquery Memory UsageLong-running query (slow query)bytes
Slowquery Session IDLong-running query (slow query)ID
Slowquery Wait Duration TimeLong-running query (slow query)ms
Tablespace UsedDatavolume sizebytes
Transaction Time [MAX]Long-running transactioncnt
Table. Microsoft SQL Server(DBaaS) Monitoring Metrics

5.2 - How-to guides

Users can enter the required information for Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console, select detailed options, and create the service.

Creating Microsoft SQL Server(DBaaS)

You can create and use the Microsoft SQL Server (DBaaS) service from the Samsung Cloud Platform Console.

Notice

Before creating the service, please configure the VPC’s Subnet type as General.

  • If the Subnet type is Local, the creation of the corresponding Database service is not possible.

Microsoft SQL Server (DBaaS)를 생성하려면 다음 절차를 따르세요.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) Create button on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) Create page.
  3. Microsoft SQL Server(DBaaS) creation On the page, enter the information required to create the service, and select detailed options.
    • Select image and version area, select the required information.
      Category
      Required
      Detailed description
      Image versionRequiredProvide version list of Microsoft SQL Server (DBaaS)
      Table. Microsoft SQL Server (DBaaS) image and version selection items
    • Service Information Input area, enter or select the required information.
      Category
      Required
      Detailed description
      Server Name PrefixRequiredServer name where DB will be installed
      • Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (-) to input 3 to 13 characters
      • Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
      Cluster NameRequiredCluster name of DB servers
      • Enter using English letters, 3 to 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type where DB will be installed
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server with 24 vCore or more
      Service Type > Planned ComputeSelectResource status 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: Move to Planned Compute service application page
      Redundancy ConfigurationSelectionRedundancy Configuration Status
      • If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
      Network > Common SettingsRequiredNetwork settings where servers generated by the service are deployed
      • Select if you want to apply the same settings to all servers being installed
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be auto‑generated
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If Use is checked, you can select from reserved IPs in the VPC product’s Public IP. For details, see Create Public IP
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select if you want to apply different settings per installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter each server’s IP
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. For more information, see Creating a Public IP.
      IP Access ControlSelectService Access Policy Settings
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      Maintenance PeriodSelectDB Maintenance Period
      • Use is selected, set the day of the week, start time, and duration
      • It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption
      • If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied
      Table. Microsoft SQL Server (DBaaS) Service Configuration Items
  • Database Configuration Required Information Input In the area, please enter or select the required information.
    Category
    Required
    Detailed description
    Database service namerequiredDatabase management unit name
    • Start with an uppercase English letter and use English letters to input 1 - 15
    Database name > defaultrequiredServer name applied when installing DB
    • Start with an English letter, and use English letters, numbers, and special characters (.,_) to input 3-20 characters
    Database name > AddRequiredServer name applied when installing DB
    • Select Use, then enter the name of the Database to install. It must start with an English letter, and be 3-20 characters using English letters, numbers, and special 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, up to a maximum of 100
    Database usernameRequiredDB 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 a Database username
      • root, user, sdscmpif, hacluster, adm, games, nobody, sshd, system, mail, postfix, sa, maxigent_cl
    Database passwordRequiredDB connection password
    • Enter 8-30 characters including letters, numbers, and special characters (excluding “ ‘)
    Database Password VerificationRequiredCheck DB connection password
    • Re-enter the DB connection password identically
    Database Port numberRequiredDB connection port number
    • Enter DB port within the range 1,024 - 65,535
    LicenseRequiredSQL Server License Key
    • Enter the issued license key
    • If the entered license key is not valid, the service may not be created
    Backup > UseSelectWhether to use backup
    • Select Use to set backup file retention period, backup start time, Full backup schedule (day of week), Archive backup cycle.
    Backup > Retention PeriodSelectBackup Retention Period
    • Select the backup retention period. File retention period can be set from 7 days to 35 days
    • Backup files incur additional charges based on size
    Backup > Backup Start PeriodSelectBackup Start Time
    • Select backup start time
    • The minutes when the backup runs are set randomly, and the backup end time cannot be set
    Backup > Full Backup Schedule(Day)SelectFull Backup Schedule
    • Select the day to run Full Backup
    • Full Backup is performed on a weekly cycle
    Backup > Archive backup frequencySelectArchive backup frequency
    • Select the Archive backup frequency
    • Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
    Audit Log SettingsSelectWhether to save Audit Log
    • Select Use to configure the Audit Log function
    • DDL, user connection information records are saved
    • If Audit is set, DB performance may degrade
    ParameterRequiredDB configuration parameters
    • Query button can be clicked to view detailed information of the parameter
    • Parameters can be modified after the service creation is completed, and after modification a DB Restart is required
    DB CollationSelectData sorting method
    • A command that specifies the data sorting and comparison method, and the result of the operation may differ depending on the setting.
    Time zoneRequiredStandard time zone to be used by the Database
    Table. Microsoft SQL Server (DBaaS) Database configuration items
    • Enter additional information area, input or select the required information.
      Category
      Required or not
      Detailed description
      TagSelectAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. Microsoft SQL Server (DBaaS) Additional Information Input Items
  1. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Resource List page.

Microsoft SQL Server(DBaaS) Check detailed information

Microsoft SQL Server(DBaaS) service allows you to view and edit the full resource list and detailed information. Microsoft SQL Server(DBaaS) Details page consists of Details, Tags, Operation History tabs, and for databases with a configured Replica, a Replica Information tab is additionally provided.

To view detailed information of the Microsoft SQL Server (DBaaS) service, follow the steps below.

  1. All Services > Database > Microsoft SQL Server(DBaaS) menu, please click. Go to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) List page.
  3. Click the resource to view detailed information on the Microsoft SQL Server(DBaaS) List page. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
  • Microsoft SQL Server(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
    CategoryDetailed description
    Cluster StatusCluster status with DB installed
    • Creating: Cluster is being created
    • Editing: Cluster is changing to operation execution 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 being restarted
    • Running: Cluster is operating normally
    • Starting: Cluster is being started
    • Stopped: Cluster is stopped
    • Stopping: Cluster is being stopped
    • Synchronizing: Cluster is being synchronized
    • Terminating: Cluster is being deleted
    • Unknown: Cluster status is unknown
      • If it occurs continuously, contact the administrator
    • Upgrading: Cluster is changing to upgrade execution state
    Cluster ControlButton to change 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 additional featuresCluster-related management button
    • Service status synchronization: View real-time DB service status
    • Backup history: If backup is configured, check whether backup 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
    • Add secondary: Configure a read-only cluster Replica
    • 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
    Service terminationButton to cancel the service
    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.

CategoryDetailed description
Server InformationServer information configured in the respective cluster
  • Category: Server type (Primary, Secondary)
  • Server name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In DB service, it means cluster SRN
Resource NameResource Name
  • In DB service, it means the cluster name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation TimeService Creation Time
EditorUser who modified the service information
Modification TimeService information modification time
Image/VersionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to set
Cluster NameName of the cluster composed of servers
Databse service nameDatabase management unit name
Database usernameDB user name
Database name > Default DatabaseServer name applied during DB installation
Database name > Add DatabaseServer name applied when installing DB
  • When adding a Database, click the Add button to add. Refer to Add Database for adding a Database.
  • If you want to delete an added Database, click the Edit icon to add. Refer to Delete Database for deleting a Database.
Planned ComputeResource status with Planned Compute set
Maintenance PeriodDB Maintenance Period Status
  • If maintenance period setting is required, click the Edit icon to set
BackupBackup configuration status
  • If backup configuration is needed, click the Edit icon to set
Audit Log SettingsAudit Log Settings Status
  • If Audit Log settings are needed, click the Edit icon to configure
Time zoneStandard time zone used by the Database
DB CollationData sorting method
VIPVirtual IP information
  • Can be checked only when high availability is configured
NetworkNetwork information where DB is installed (VPC, Subnet)
IP Access ControlService Access Policy Settings
  • If you need to add or delete an IP, click the Edit icon to set
Primary & SecondaryPrimary/Secondary 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 set it. Refer to Change Server Type for the server type modification procedure
    • 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 Expand Storage for the storage expansion procedure
  • If you need to add storage, click the Add Disk button next to Additional Disk to add. Refer to Add Storage for the storage addition procedure
Table. Microsoft SQL Server(DBaaS) Database detailed information items

Tag

Microsoft SQL Server(DBaaS) List page you can view the tag information of the selected resource, and you can add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • You can view the tag’s Key, Value information
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the previously created Key and Value list
Table. Microsoft SQL Server(DBaaS) Tag Tab Items

Work History

Microsoft SQL Server(DBaaS) List You can view the operation history of the selected resource on the page.

CategoryDetailed description
Work History ListResource Change History
  • Work date/time, Resource ID, Resource name, Work details, Event topic, Work result, Check worker information
Table. Microsoft SQL Server (DBaaS) Job History Tab Detailed Information Items

Microsoft SQL Server(DBaaS) Managing Resources

If you need to change or recover the existing configuration options of a created Microsoft SQL Server (DBaaS) resource, or manage parameters, you can perform the tasks on the Microsoft SQL Server (DBaaS) Details page.

Operating Control

If changes occur to a running Microsoft SQL Server (DBaaS) resource, you can start, stop, or restart it. Also, if HA is configured, you can switch the Primary-Secondary servers via a switch-over.

To control the operation of Microsoft SQL Server (DBaaS), follow the steps below.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) list page.
  3. Microsoft SQL Server(DBaaS) List On the page, click the resource to control operation. Microsoft SQL Server(DBaaS) Details Navigate to the page.
  4. Check the status of Microsoft SQL Server (DBaaS) and complete the change using the control button below.
    • Start: The server where the DB service is installed and the DB service are 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 check the service status of Microsoft SQL Server (DBaaS), follow the steps below.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) List page.
  3. Microsoft SQL Server(DBaaS) List Click the resource to view the service status on the page. Microsoft SQL Server(DBaaS) Details Navigate to the page.
  4. Service Status Synchronization Click the button. While it is being queried, the cluster will change to Synchronizing state.
  5. When the query is completed, the status is updated in the server information item, and the cluster changes to Running state.

Change Server Type

You can change the configured server type.

To change the server type, follow the steps below.

Caution
  • If you modify the server type, a server reboot is required. Please separately verify any SW license changes or SW settings and implementations due to server specification changes.
  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) list page.
  3. Click the resource to change the server type on the Microsoft SQL Server(DBaaS) List page. Navigate to the Microsoft SQL Server(DBaaS) Details page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
  5. Edit Server Type After selecting the server type in the popup window, click the Confirm button.

Add Storage

If you need more than 5 TB of data storage space, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.

To add storage capacity, follow the steps below.

Caution
  • It will be applied 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.
  1. All Services > Database > Microsoft SQL Server(DBaaS) Please click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) list page.
  3. Click the resource to add storage on the Microsoft SQL Server(DBaaS) List page. Navigate to the Microsoft SQL Server(DBaaS) Detail page.
  4. Click the Add Disk button at the bottom of the detailed information. The Add Storage Request popup window opens.
  5. Additional Storage Request In the popup window, after entering 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.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) list page.
  3. Microsoft SQL Server(DBaaS) List Click the resource to change the server type on the page. Microsoft SQL Server(DBaaS) Detail Navigate to the page.
  4. Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. The Edit Additional Storage popup window opens.
  5. Add Storage Modification After entering the expansion capacity in the popup window, click the Confirm button.

Microsoft SQL Server(DBaaS) Cancel

You can cancel the unused Microsoft SQL Server (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be immediately stopped, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
If you terminate the DB, any stored data and, if a backup has been set, the backup data will all be deleted.

To cancel Microsoft SQL Server (DBaaS), follow the steps below.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) List page.
  3. On the Microsoft SQL Server(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
  4. After termination is completed, check whether 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 Databases

For Microsoft SQL Server Enterprise version, you can add new databases. Up to 100 databases can be added per cluster.

Adding a Database

To add a database, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to add storage to. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the Add button in the Database Name field. The Add Database popup window will open.
  5. In the Add Database popup window, click the + button to enter the database name and select the drive, then click the Confirm button.

Deleting a Database

To delete a database, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to add storage to. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the Modify button in the Database Name field. The Delete Additional Database popup window will open.
  5. In the Delete Additional Database Request popup window, check the database you want to delete and click the Delete button. The Delete Database popup window will open.
  6. In the Delete Database popup window, enter the name of the database you want to delete and click the Confirm button.

Managing Parameters

It provides a feature to easily view and modify database configuration parameters.

Viewing Parameters

To view configuration parameters, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to view and modify parameters for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
  5. In the Parameter Management popup window, click the View button. The View Notification popup window will open.
  6. When the View Notification popup window opens, click the Confirm button. It may take some time to view.

Modifying Parameters

To modify configuration parameters, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to view and modify parameters for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
  5. In the Parameter Management popup window, click the View button. The View Notification popup window will open.
  6. When the View Notification popup window opens, click the Confirm button. It may take some time to view.
  7. If modification is necessary, click the Modify button and enter the modification details in the user-defined value field of the parameter to be modified.
  8. After entering the modification details, click the Save button.

Managing DB Users

It provides a feature to view and manage DB user information.

Viewing DB Users

To view DB users, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to view DB users for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. You will be moved to the DB User Management page.
  5. On the DB User Management page, click the View button. It may take some time to view.

Exporting DB Logs

It supports exporting audit logs that need to be stored for a long time to Object Storage. Users can set the log type to be stored, the target bucket to export to, and the export cycle. According to the set criteria, the logs are copied and stored in the designated Object Storage.

Additionally, to efficiently manage disk space, an option to automatically delete the original log files when exporting logs to Object Storage is provided. By utilizing this option, users can effectively secure storage capacity while safely storing necessary log data for a long time.

Note
  • To use the DB Log Export feature, Object Storage creation is required. Refer to the Object Storage User Guide for Object Storage creation.
  • Please check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
  • Please be careful not to expose authentication key information to the outside.

Setting DB Log Export Mode

To set the DB Log export mode, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to export DB logs from. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the More button and then click the DB Log Export button. You will be moved to the DB Log Export page.
  5. On the DB Log Export page, click the Register button. You will be moved to the DB Log Export Registration page.
  6. On the DB Log Export Registration page, enter the required information and click the Save button.
CategoryRequired
Detailed Description
Log TypeRequiredLog type to be stored
Storage Bucket NameRequiredObject Storage bucket name to store logs
Authentication Key > Access KeyRequiredAccess key to access Object Storage
Authentication Key > Secret KeyRequiredSecret key to access Object Storage
File Creation CycleRequiredCycle to create files in Object Storage
Original Log DeletionOptionalWhether to delete original logs when exporting to Object Storage
Table. Microsoft SQL Server (DBaaS) Migration Configuration Items

Managing DB Log Export

To modify, cancel, or immediately export DB log settings, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to manage DB log export for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the More button and then click the DB Log Export button. You will be moved to the DB Log Export page.
  5. On the DB Log Export page, click the More button for the log type you want to manage and click the Immediate Export, Modify, or Cancel button.
    • Immediate Export: Exports the selected log to the Object Storage bucket.
    • Modify: Modifies the DB log export mode setting.
    • Cancel: Cancels the DB log export mode setting.

Upgrading Microsoft SQL Server (DBaaS) Version

It provides a feature to upgrade versions due to functional improvements and security patches. Only minor version upgrades are supported within the same major version.

Caution
  • Please perform version upgrades after checking the service status through service status synchronization.
  • Please set up backups before performing version upgrades. If backups are not set up, some data may not be recoverable in case of problems during the upgrade.
  • Backed-up data will be automatically deleted after the version upgrade is complete.

To upgrade the version, follow these steps:

  1. Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
  3. On the Microsoft SQL Server (DBaaS) List page, click the resource you want to upgrade the version for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
  4. Click the Modify button in the Image/Version field. The Version Upgrade popup window will open.
  5. In the Version Upgrade popup window, select the version to upgrade to and whether to set up backups, then click the Confirm button.
  6. In the Version Upgrade Notification popup window, click the Confirm button.

5.2.2 - DB Backup and Recovery

The user can set up a backup of Microsoft SQL Server(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.

Microsoft SQL Server(DBaaS) backup

Microsoft SQL Server(DBaaS) provides a data backup feature based on its own backup command, and also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.

Setting up backup

The method of setting up a backup for Microsoft SQL Server(DBaaS) is described in the Microsoft SQL Server(DBaaS) creation guide, please refer to it.

To modify the backup settings of the generated resource, follow these steps.

Caution

If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.

  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
  1. All services > Database > Microsoft SQL Server(DBaaS) menu, click. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
  3. Click the resource to set up backup on the Microsoft SQL Server(DBaaS) list page. It moves to the Microsoft SQL Server(DBaaS) details page.
  4. Click the Edit button of the backup item. The Backup Settings popup window opens.
  5. If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
    • If you want to stop the backup setting, uncheck 사용 in the 백업 설정 popup window and click the 확인 button.

Check Backup History

Notice
To set up notifications for backup success and failure, you can set them up through the Notification Manager product. For a detailed usage guide on setting up notification policies, please refer to Creating a Notification Policy.

To view the backup history, follow these steps.

  1. Click All Services > Database > Microsoft SQL Server(DBaaS) menu. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
  3. Microsoft SQL Server(DBaaS) list page, click the resource to check the backup history. It moves to the Microsoft SQL Server(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting backup files

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please make sure to check if the data is unnecessary before deleting it.
  1. Click All Services > Database > Microsoft SQL Server(DBaaS) menu. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
  3. Microsoft SQL Server(DBaaS) list page, click the resource to check the backup history. It moves to the Microsoft SQL Server(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window, check the file you want to delete, and then click the Delete button.

Microsoft SQL Server(DBaaS) Recovery

In the event of a disability or data loss that requires restoration with a backup file, recovery is possible based on a specific point in time through the recovery function. When performing Microsoft SQL Server (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, and the DB is installed with the version at the backup point, and the recovery proceeds with the DB configuration information and data.

To restore Microsoft SQL Server(DBaaS), follow these procedures.

  1. Click All Services > Database > Microsoft SQL Server(DBaaS) menu. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Service Home page, click the Microsoft SQL Server(DBaaS) menu. Move to the Microsoft SQL Server(DBaaS) list page.
  3. Microsoft SQL Server(DBaaS) resource list page, click the resource you want to restore. Move to the Microsoft SQL Server(DBaaS) details page.
  4. Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
  5. Database Recovery Configuration area, enter the corresponding information and click the Complete button.
Classification
Necessity
Detailed Description
Recovery TypeRequiredSet the point in time 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 the desired point in time within the range where backup is possible. The recoverable period is from the initial backup start time to 1 hour/30 minutes/10 minutes/5 minutes before the current time, based on the Archive backup cycle setting value. Select the date and time you want to back up
Server name prefixRequiredRecovery DB server name
  • Start with lowercase English letters, using lowercase letters, numbers, and special characters (-) to input 3-16 characters
  • A postfix such as 001, 002 is attached based on the server name, and the actual server name is created
Cluster NameRequiredRecovery DB Cluster Name
  • Enter in English, 3-20 characters
  • A cluster is a unit that bundles multiple servers
Service Type > Server TypeRequiredRecovery DB Server Type
  • Standard: Generally used standard specification
  • High Capacity: High-capacity server with 24vCore or more
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are in use
  • Setting: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by resource-based Planned Compute
  • Create Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredRecovery DB uses Block Storage settings
  • Basic OS: Area where the DB engine is installed
  • DATA: Data storage area
    • The storage type set in the original cluster is applied in the same way
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120
  • Additional: Data storage area
    • The storage type set in the original cluster is applied in the same way
    • Only DATA and TEMP purposes can be added in the recovery DB
    • Select Use and enter the purpose and capacity of the storage
    • To add storage, click the + button, and to delete, click the x button
    • Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Database usernamerequiredDatabase username
  • Applied identically to the username set in the original cluster
Database Port numberrequiredDatabase Port number
  • Apply the same port number set in the original cluster
IP Access ControlSelectSet service access policy
  • Set access policy for IP entered on the page, so Security Group policy setting is not required separately
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectDB maintenance period
  • Use is selected, set the day of the week, start time, and duration
  • It is recommended to set the maintenance period for stable management of the DB. Patch work is performed at the set time and service interruption occurs
  • If not used, Samsung SDS is not responsible for the problems that occur due to non-application of patches.
TagSelectAdd Tag
  • Click the Add Tag button and enter or select Key, Value
Fig. Microsoft SQL Server(DBaaS) Recovery Configuration Items

5.2.3 - Add Secondary

The user can enter the required information of the Secondary through the Samsung Cloud Platform Console and create the service through detailed options.

Add Secondary

You can create a read-only replica server through Secondary configuration. To configure additional Secondary, it must be created with duplication configuration (HA) and Enterprise Edition, and the backup function must be enabled.

To configure Secondary, follow these procedures.

  1. Click on the menu for all services > Database > Microsoft SQL Server(DBaaS). It moves to the Service Home page of Microsoft SQL Server(DBaaS).
  2. Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
  3. Click the resource to configure Secondary on the Microsoft SQL Server(DBaaS) list page. It moves to the Microsoft SQL Server(DBaaS) details page.
  4. Secondary Add 버튼을 클릭하세요. Secondary Add 페이지로 이동합니다.
  5. Secondary configuration area, enter information after, Complete button, click.
Classification
Mandatory
Detailed Description
Secondary numberEssentialNumber of Secondary configurations
  • Only one can be configured per cluster
Secondary nameRequiredSecondary server name
  • Start with lowercase English letters, use lowercase letters, numbers, and special characters (-) to input 3 ~ 15 characters
  • The entered Secondary name is exposed as a cluster name in the list
Service Type > Server TypeRequiredSecondary Server Type
  • Applied equally according to the server type set in the original DB
Service Type > Planned ComputeSelectCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are in use
  • Setting: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by Planned Compute for each resource
  • Create Planned Compute Service: Move to the Planned Compute service application page
Network > Common SettingsRequiredNetwork settings for servers created by the service
  • Applies the same network settings as set in the original DB
Network > Server SettingsRequiredNetwork settings for servers created by the service
  • Select to apply different settings for each server being installed
  • Apply network settings set in the original DB as is
  • When setting up server settings, enter the IP address within the range of 10.10.10.0/24
LicenseRequiredSQL Server License Key
  • Enter the issued license key
  • If the entered license key is not valid, the service may not be created
Fig. Microsoft SQL Server(DBaaS) Secondary configuration items

5.2.4 - Microsoft SQL Server(DBaaS) server connection

Scenario Overview

The Microsoft SQL Server(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and a Database service are created, and the DB service is accessed through the Bastion host. To securely access Microsoft SQL Server (DBaaS) in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.

This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, and accessing it through a DB connection client.

Architecture
Figure. Microsoft SQL Server(DBaaS) server connection architecture

Scenario Components

You can configure the scenario using the following services.

Service Group
Service
Detailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
NetworkingVPC > SubnetA service that allows users to subdivide the network into smaller segments according to purpose/size within the VPC
NetworkingVPC > Public IPA service that reserves public IP and assigns and returns it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the internet
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
DatabaseMicrosoft SQL Server(DBaaS)A service that easily creates and manages Microsoft SQL Server in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to the Virtual Server
Table. Scenario Component List
Note
  • The default policy of Security Group is Deny All, so only allowed IPs must be registered.
  • In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources to external threats.
    • By specifying the necessary IP and Port to set the policy, you can enhance security.

Scenario composition method

To configure the scenario, create the necessary services through the following procedure.

1. Configuring the Network

This describes the process of configuring the network environment for connecting to the Bastion Host and Database services.

1-1. Creating a VPC

For detailed creation methods, please refer to the Networking > VPC > How-to guides guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
  3. VPC Creation page, please enter the information required for service creation.
    • IP range should be entered as 192.168.x.0/16.
  4. In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
    • Once creation is complete, check the resource you created on the VPC list page.

1-2. Creating a Subnet

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Subnet menu. It moves to the Subnet list page.
  3. Click the Subnet Creation button. It moves to the Subnet Creation page.
  4. Subnet Creation page where you enter the information needed to create a service.
    • Subnet type should be selected as General.
    • Please select a pre-created VPC.
    • IP range should be entered as 192.168.x.0/24.
  5. In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
    • Once creation is complete, check the created resource on the Subnet list page.

1-3. Creating an Internet Gateway

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
  3. Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
  4. Internet Gateway Creation page, please enter the required information necessary for service creation.
    • Please select a pre-created VPC.
    • Select Use in the Firewall usage item.
  5. In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
    • Once the creation is complete, check the created resource on the Internet Gateway list page.

1-4. Creating a Public IP

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Public IP menu. It moves to the Public IP list page.
  3. Public IP Reservation button, click. Move to the Public IP Reservation page.
  4. Public IP Reservation page where you enter the required information necessary for service reservation.
  5. In the Summary panel, review the detailed information and estimated billing amount, and click the Complete button.
    • Once creation is complete, check the created resource on the Public IP list page.

1-5. Creating a Security Group

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click All services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Create Security Group button. Move to the Create Security Group page.
  3. Security Group Creation page, please enter the required information necessary for service creation.
  4. Check the input information and click the Complete button.
    • Once creation is complete, check the created resource on the Security Group list page

2. Creating a Bastion host

This describes the process of configuring the Bastion Host where the database connection client should be installed.

2-1. Creating Server Keypair

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Keypair menu. It moves to the Keypair list page.
  3. Create Keypair button will be clicked. It moves to the Create Keypair page.
  4. Keypair creation page where you enter the required information necessary for service creation.
  5. Check the creation information and click the Complete button.
    • The key can only be downloaded for the first time, and re-issuance is not provided.
    • Please make sure to store the downloaded key in a safe place.

2-2. Creating a Bastion Host

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server creation button. Move to the Virtual Server creation page.
  3. Virtual Server Creation page, please enter the required information necessary for service creation.
  4. Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
    • After creation is complete, check the created resource on the Virtual Server list page.

2-3. Check Bastion host connection ID and PW

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
  3. Virtual Serve list page, click on the resource created in 2-2. Bastion host creation. It moves to the detailed information page of the corresponding resource.
  4. In the detailed information page, click the RDP password inquiry button in the Keypair name item. The RDP password inquiry pop-up window opens.
  5. RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Server Keypair creation.
  6. After attaching, click the Password check button. The ID and password required to access the resource will be displayed.

3. Creating a Database

It describes the process of creating a Database service.

3-1. Creating Microsoft SQL Server (DBaaS) Service

For detailed creation methods, please refer to the Database > Microsoft SQL Server(DBaaS) > How-to guides guide.
  1. Click on the menu for all services > Database > Microsoft SQL Server(DBaaS). It moves to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Create Microsoft SQL Server(DBaaS) button. It moves to the Create Microsoft SQL Server(DBaaS) page.
  3. Microsoft SQL Server(DBaaS) creation page, please enter the required information needed for service creation.
    • Select and connect to the pre-created VPC and Subnet.
    • Enter Database related creation information on the required information input screen.
    • Add the Bastion host IP in the IP access control item.
    • Database Port is 2866 by default, but users can also specify it.
  4. In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
    • Once creation is complete, check the created resource from the Microsoft SQL Server(DBaaS) list page.

4. Setting Rules

This describes the process of setting rules for users to connect to the Bastion host and rules for the Bastion host to connect to the Database.

4-1. Security Group Add Security Rules

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Security Group menu. Move to the Security Group list page.
  3. 1-5. Creating a Security Group Select the Security Group resource created from 1-5. Creating a Security Group. It moves to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Rule tab where you click the Add Rule button. Move to the Add Rule popup window.
  6. In the Add Rule popup window, enter the rules below and click the OK button
DirectionRemoteDestination AddressProtocolPortDescription
InboundCIDRUser PC IPTCP3389 (RDP)Bastion connection PC → Bastion host
OutboundCIDRDB IPTCPDatabase Port (direct input)Bastion host → Database
Fig. Security Group security rules to be added

4-2. Adding IGW Firewall Rules

For detailed creation methods, please refer to the Networking > Firewall > How-to guides guide.
  1. Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
  2. Service Home page, click the Firewall menu. It moves to the Firewall list page.
  3. Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway. It moves to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Rule tab, click the Add Rule button. Move to the Add Rule popup window.
  6. Add Rule In the popup window, enter the following rules and click the OK button.
Departure AddressDestination AddressProtocolPortActionDirectionDescription
Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
Table. Internet Gateway Firewall rules to be added

5. Connect to Database

This describes the process of a user accessing the Database through a DB connection client program.

This guide provides instructions on how to connect using SSMS (Microsoft SQL Server Management Studio). Since there are various database client programs and CLI utilities, you can also install and use the tools that are suitable for you.

5-1. Connect to the Bastion host

  1. Run Remote Desktop Connection in the Windows environment of the PC that wants to access the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
  2. When the remote desktop connection is successful, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Check Bastion host access ID and PW and click the Confirm button.

5-2. Install DB connection client program (SSMS) on Bastion host

  1. Go to the official Microsoft SQL Server page and download the SSMS program.
  2. Connect the hard drive of the user PC to upload the file to the Bastion host.
  3. Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
  4. Select the local disk where the file was downloaded to the drive and click the Confirm button.
  5. Download the file, copy it to the Bastion Host, and upload it, then click the SSMS (Microsoft SQL Server Management Studio) installation file to install it.

5-3. Using DB Connection Client Program (SSMS) to Connect to Database

  1. Run SSMS (Microsoft SQL Server Management Studio). The Connect to Server popup window will appear.
  2. Connect to Server popup window, enter the database server information created in 3-1. Microsoft SQL Server(DBaaS) service creation and click the Connect button.
    Required Input Element ItemsInput Value
    Server typeDatabase Engine
    Server nameDatabase server IP, Database Port (ex. 192.168.10.1,2866)
    AuthenticationSQL Server Authentication
    LoginDatabase username
    PasswordDatabase password
    EncryptionOptional
    DB Connection Client Program Input Items
  3. Once the connection is complete, the Database will be connected. After connection, you can try performing simple queries, etc.

5.3 - API Reference

API Reference

5.4 - CLI Reference

CLI Reference

5.5 - Release Note

Microsoft SQL Server(DBaaS)

2025.07.01
FEATURE User (Access Control) Management, DB Audit Log Export Function Added, Backup Notification Function Provided
2025.02.27
NEW Microsoft SQL Server(DBaaS) Service Official Version Release
  • A Microsoft SQL Server (DBaaS) service that allows you to easily create and manage Microsoft SQL Server in a web environment has been released.

6 - CacheStore(DBaaS)

6.1 - Overview

Service Overview

CacheStore(DBaaS) is a service that provides the in‑memory based data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that can automate the installation of Redis OSS and Valkey through a web‑based console and perform management functions for operation.

CacheStore (DBaaS) provides a Sentinel method consisting of a Master server that performs read/write operations and read-only Replica servers that replicate 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 failovers the Replica servers to become the Master server. Additionally, to prepare for issues with the DB server or data, it offers a function that automatically backs up at a user-specified time, supporting data recovery based on the backup point.

Architecture
Figure. CacheStore(DBaaS) Architecture

Provided Features

CacheStore(DBaaS) provides the following features.

  • Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and a redundant configuration is possible with a Sentinel-based Single Master server and Replica server (1 or 2).
  • Operation Control Function: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), you can switch Active-Standby servers via Switch-over.
  • Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage agency can be set by the user, and additional fees are incurred depending on the backup volume. It also provides a recovery function for backed-up data, so when the user performs a recovery, a separate DB is created and the recovery proceeds to the point in time selected by the user.
  • Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
  • Service status query: Retrieves the final status of the current DB service.
  • Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.

Components

CacheStore (DBaaS) provides pre‑validated engine versions and various server types according to the open‑source support policy. Users can select and use them based on the scale of the service they wish to configure.

Engine Version

The engine versions supported by CacheStore(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 stopped is set to six months before the EoTS date.

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

ImageProvided VersionEoS DateEoTS Date
Redis OSS Sentinel7.2.11TBDTBD
valkey Sentinel8.1.4TBDTBD
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) server type.

Standard redis1v2m4






Category Example Detailed description
Server Type Standard Provided Server Type
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
Server specifications redis1 Provided server specifications
  • redis1: Standard specifications (vCPU, Memory) configuration commonly used
Server Specification 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. Please refer to the guide provided for each service for details and prepare in advance.<br>
Service Category Service Detailed Description
Networking VPC A service that provides an independent virtual network in a cloud environment
Table. CacheStore(DBaaS) Preliminary Service

6.1.1 - Server Type

CacheStore(DBaaS) server type

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

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

Standard redis1v2m4
Classification
ExampleDetailed Description
Server TypeStandardProvided server type distinction
  • Standard: Configured with standard specifications (vCPU, Memory) commonly used
Server Specificationredis1Provided server type distinction and generation
  • redis: means general specification, and 1 means generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationm4Memory capacity
  • m4: 4GB Memory
Fig. CacheStore(DBaaS) server type format

redis1 server type

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

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

ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standardredis1v1m21 vCore2 GBUp to 10 Gbps
Standardredis1v2m42 vCore4 GBUp to 10 Gbps
Standardredis1v2m82 vCore8 GBUp to 10 Gbps
Standardredis1v2m162 vCore16 GBUp to 10 Gbps
Standardredis1v2m242 vCore24 GBUp to 10 Gbps
Standardredis1v4m84 vCore8 GBUp to 10 Gbps
Standardredis1v4m164 vCore16 GBUp to 10 Gbps
Standardredis1v4m324 vCore32 GBUp to 10 Gbps
Standardredis1v4m484 vCore48 GBUp to 10 Gbps
Standardredis1v4m644 vCore64 GBUp to 10 Gbps
Standardredis1v6m726 vCore72 GBUp to 10 Gbps
Standardredis1v6m966 vCore96 GBUp to 10 Gbps
Standardredis1v8m1288 vCore128 GBUp to 10 Gbps
Standardredis1v10m16010 vCore160 GBUp to 10 Gbps
Standardredis1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardredis1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardredis1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore(DBaaS) server type specification - redis1 server type

css1 server type

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

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

ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standardcss1v1m21 vCore2 GBUp to 10 Gbps
Standardcss1v2m42 vCore4 GBUp to 10 Gbps
Standardcss1v2m82 vCore8 GBUp to 10 Gbps
Standardcss1v2m162 vCore16 GBUp to 10 Gbps
Standardcss1v2m242 vCore24 GBUp to 10 Gbps
Standardcss1v4m84 vCore8 GBUp to 10 Gbps
Standardcss1v4m164 vCore16 GBUp to 10 Gbps
Standardcss1v4m324 vCore32 GBUp to 10 Gbps
Standardcss1v4m484 vCore48 GBUp to 10 Gbps
Standardcss1v4m644 vCore64 GBUp to 10 Gbps
Standardcss1v6m726 vCore72 GBUp to 10 Gbps
Standardcss1v6m966 vCore96 GBUp to 10 Gbps
Standardcss1v8m1288 vCore128 GBUp to 10 Gbps
Standardcss1v10m16010 vCore160 GBUp to 10 Gbps
Standardcss1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardcss1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardcss1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore(DBaaS) server type specification - css1 server type

6.1.2 - Monitoring Metrics

CacheStore(DBaaS) Monitoring Metrics

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

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

Performance ItemDetailed DescriptionUnit
Active Defragmentation Keys [Hits]Number of keys defragmentedcnt
Active Defragmentation Keys [Miss]Number of keys skipped in the active defragmentation processcnt
Active Defragmentationd [Hits]Number of value reassignments performed by the active defragmentation processcnt
Active Defragmentations [Miss]Number of value reassignments started and aborted by the active defragmentation processcnt
Allocated Bytes [OS]Number of bytes allocated by CacheStore(DBaaS) and recognized by the operating system (resident set size)bytes
Allocated Bytes [Redis]Total number of bytes allocated by CacheStore(DBaaS)bytes
AOF Buffer SizeAOF buffer sizebytes
AOF File Size [Current]Current AOF file sizebytes
AOF File Size [Lastest Startup]AOF file size at the latest startup or rewritebytes
AOF Rewrite Buffer SizeAOF rewrite buffer sizebytes
AOF Rewrite Current TimeTime of the ongoing AOF rewrite operation, if anysec
AOF Rewrite Last TimeTime of the last AOF rewrite operationsec
CallsNumber of calls that reached command execution (not rejected)cnt
Changes [Last Saved]Number of changes since the last dumpcnt
Client Output Buffer [MAX]Longest output list among current client connectionscnt
Clients [Sentinel]Number of client connections (Sentinel)cnt
Connected SlavesNumber of connected slavescnt
Connections [Blocked]Number of clients waiting for 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 the last RDB save operationbytes
Copy On Write Allocated Size [RDB]COW allocation size during the last RDB save operationbytes
CPU Time [Average]Average CPU time used per command executioncnt
CPU Time [Total]Total CPU time used by these commandsusec
CPU Usage [System Process]System CPU usage by background processes%
CPU Usage [System]System CPU usage by the CacheStore(DBaaS) server%
CPU Usage [User Process]User CPU usage by background processes%
CPU Usage [User]System CPU usage by background processes%
Dataset UsedDataset sizebytes
Disk UsedDatadir usageMB
Evicted KeysNumber of evicted keys due to maxmemory limitcnt
Fsyncs [Delayed]Delayed fsync countercnt
Fsyncs [Pending]Number of fsync operations pending in the background I/O queuecnt
Full ResyncsNumber of full resynchronizations with slavescnt
Keys [Expired]Total number of key expiration eventscnt
Keys [Keyspace]Number of keys in the keyspacecnt
Lastest Fork Duration TimeTime of the latest fork (fork) operationusec
Lookup Keys [Hit]Number of successful key lookups in the main dictionarycnt
Lookup Keys [Miss]Number of failed key lookups in the main dictionarycnt
Lua Engine Memory UsedMemory used by the Lua enginebytes
Master Last Interaction Time AgoTime since the last interaction with the mastersec
Master Last Interaction Time Ago [Sync]Time since the last interaction with the mastersec
Master OffsetCurrent replication offset of the serverpid
Master Second OffsetOffset until the replication ID is acceptedpid
Master Sync Left BytesNumber of bytes left to synchronizebytes
Memory Fragmentation RateRatio of used_memory_rss to used_memory%
Memory Fragmentation Rate [Allocator]Fragmentation ratio%
Memory Fragmentation UsedDifference between used_memory_rss and used_memory in bytesbytes
Memory Fragmentation Used [Allocator]Resident bytesbytes
Memory Max ValueMemory limitbytes
Memory Resident [Allocator]Resident memorybytes
Memory RSS Rate [Allocator]Resident ratio%
Memory Used [Active]Active memorybytes
Memory Used [Allocated]Allocated memorybytes
Memory Used [Resident]Resident bytesbytes
Network In Bytes [Total]Total network input (bytes)bytes
Network Out Bytes [Total]Total network output (bytes)bytes
Network Read RateNetwork read rate per second (KB/sec)cnt
Network Write RateNetwork write rate per second (KB/sec)cnt
Partial Resync Requests [Accepted]Number of accepted partial resynchronization requestscnt
Partial Resync Requests [Denied]Number of denied partial resynchronization requestscnt
Peak Memory ConsumedMaximum memory used by CacheStore(DBaaS)bytes
Processed CommandsNumber of commands processed per secondcnt
Processed Commands [Total]Total number of processed commandscnt
Pub/Sub ChannelsGlobal number of pub/sub channels with client subscriptionscnt
Pub/Sub PatternsGlobal number of pub/sub patterns with client subscriptionscnt
RDB Saved Duration Time [Current]Time of the ongoing RDB save operation, if anysec
RDB Saved Duration Time [Last]Time of the last RDB save operationsec
Received Connections [Total]Total number of received connectionscnt
Rejected Connections [Total]Total number of rejected connectionscnt
Replication Backlog Actove CountFlag indicating whether replication backlog is activecnt
Replication Backlog Master OffsetMaster offset of the replication backlog buffercnt
Replication Backlog SizeSize of data in the replication backlog bufferbytes
Replication Backlog Size [Total]Total size of the replication backlog bufferbytes
Slave PriorityPriority of the server as a failover targetcnt
Slave Replication OffsetReplication offset of the slave serverpid
Slow OperationsNumber of slow operationscnt
Sockets [MIGRATE]Number of sockets open for migrationcnt
Tracked Keys [Expiry]Number of keys tracked for expiration (only for writable slaves)cnt
Instance Status [PID]PID of the redis-server processpid
Sentinel Status [PID]PID of the sentinel processpid
Table. CacheStore(DBaaS) Monitoring Metrics

6.2 - How-to guides

The user can enter the necessary information of CacheStore(DBaaS) through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating CacheStore(DBaaS)

You can create and use the CacheStore(DBaaS) service in the Samsung Cloud Platform Console.

Notice

Please configure the Subnet type of VPC to General before creating the service.

  • If the Subnet type is Local, the creation of the corresponding Database service is not allowed.

To create a CacheStore(DBaaS), follow these steps.

  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).

  2. On the Service Home page, click the CacheStore(DBaaS) creation button. It moves to the CacheStore(DBaaS) creation page.

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

    • Image and Version Selection area, please select the necessary information.

      Classification
      Necessity
      Detailed Description
      Image VersionRequiredProvides a list of CacheStore (DBaaS) versions
      Fig. CacheStore(DBaaS) image and version selection items

    • Enter Service Information Enter or select the required information in the area.

      Classification
      Necessity
      Detailed Description
      Server Name PrefixRequiredServer name where Redis/Valkey will be installed
      • Starts with lowercase English letters, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (-)
      • A postfix such as 001, 002 is attached based on the server name to create the actual server name
      Cluster NameRequiredName of the cluster where Redis/Valkey is installed
      • Enter in English, 3-20 characters
      • Cluster is a unit that bundles multiple servers
      Service Type > Server TypeRequiredServer type where Redis/Valkey will be installed
      • Standard: Standard specification commonly used
      Service Type > Planned ComputeRequiredCurrent status of resources with Planned Compute set
      • In Use: Number of resources with Planned Compute set that are currently in use
      • Settings: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied by Planned Compute for each resource
      • Create Planned Compute Service: Move to the Planned Compute service application page
      Service Type > Block StorageRequiredBlock Storage settings used by DB according to purpose
      • Basic OS: Area where DB engine is installed
      • DATA: Storage area for table data, archive files, etc.
        • Please select the storage type and enter the capacity. (For more information on each Block Storage type, see Creating Block Storage)
          • SSD: High-performance general volume
          • HDD: General volume
          • SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption key
        • The set Storage type will be applied equally to additional storage
        • Capacity should be entered in multiples of 8 within the range of 16 to 5,120
      High AvailabilityOptionalWhether to configure High Availability (HA)
      • Using High Availability (HA) configuration provides Master-Replica configuration, and Replica can be configured with 1 or 2
      • Sentinel Port Number: Port number used when connecting to Sentinel
        • Port for Master-Replica communication, enter within the range of 1,024 to 65,535
      • Number of Replicas: Number of Replicas to be configured
        • 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
        • The server type of Sentinel is set to the minimum specification
      NetworkRequiredThe network where CacheStore(DBaaS) is installed
      • Select and connect the pre-created VPC and Subnet
      • IP can only be generated automatically
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select if you want to apply the same settings to all servers being installed
      • Select pre-created VPC and Subnet
        • IP can only be generated automatically
      Network > Server-specific settingsRequiredNetwork settings for servers created by the service
      • Select to apply different settings for each server being installed
      • Select pre-created VPC and Subnet, IP, Public NAT
        • Enter the IP for each server
        • The Public NAT function is only available if the VPC is connected to the Internet Gateway. If Use is checked, you can select from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
      IP Access ControlSelectSet service access policy
      • Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately
      • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button
      • To delete the entered IP, click the x button next to the entered IP
      Maintenance periodSelectionCacheStore(DBaaS) maintenance period
      • Use is selected to set the day of the week, start time, and duration
      • It is recommended to set the maintenance period for stable DB management, and patch work is performed at the set time, resulting in service interruption
      • If not used, Samsung SDS is not responsible for any problems that occur due to non-application of patches
      Fig. CacheStore(DBaaS) Service Configuration Items

    • Database Configuration Required Information Input area, please enter or select the required information.

      Classification
      Necessity
      Detailed Description
      BackupSelectionWhether to use backup
      • Use is selected to set the backup file storage period and backup start time
      • Backup files are charged separately according to capacity
        • The file storage period can be set from 7 to 35 days
      • The minute (minutes) when the backup is performed is set randomly, and the backup end time cannot be set
      Redis/Valkey Port numbermandatoryPort number required for Redis/Valkey connection
      • Port must be entered within the range of 1,024 ~ 65,535
      Redis/Valkey passwordmandatoryPassword required when connecting to Redis/Valkey
      • Enter 8-30 characters, including English, numbers, and special characters (excluding $ " )
      Redis/Valkey password confirmationrequiredRe-enter the password identically
      ParameterRequiredRedis/Valkey parameters to use
      • Query button can be clicked to check detailed information of parameters
      • Parameters can be modified after creation is completed, and DB restart is required after modification
      Time ZoneRequiredTime zone where the Database will be used
      Fig. CacheStore(DBaaS) Database Configuration Items

    • Enter Additional Information Enter or select the required information in the area.

      Classification
      Mandatory
      Detailed Description
      TagSelectionAdd Tag
      • Up to 50 can be added per resource
      • Click the Add Tag button and enter or select Key, Value
      Table. Additional information input items for CacheStore(DBaaS)

  4. In the Summary panel, review the detailed information and estimated charges, and click the Complete button.

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

Check CacheStore(DBaaS) detailed information

The CacheStore(DBaaS) service allows you to view and modify the entire resource list and detailed information. The CacheStore(DBaaS) details page consists of detailed information, tags, and operation history tabs.

To check the detailed information of the CacheStore(DBaaS) service, follow the next procedure.

  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
  2. Service Home page, click the CacheStore(DBaaS) menu. Move to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource to check the detailed information. Move to the CacheStore(DBaaS) details page.
    • CacheStore(DBaaS) details page top shows status information and additional features.
DivisionDetailed Description
Cluster StatusRedis cluster status installed
  • Creating: The cluster is being created
  • Editing: The cluster is changing to the operation performance state
  • Error: The cluster has an error occurred during operation
    • If it occurs continuously, contact the administrator
  • Failed: The cluster failed during the creation process
  • Restarting: The cluster is being restarted
  • Running: The cluster is operating normally
  • Starting: The cluster is being started
  • Stopped: The cluster is stopped
  • Stopping: The cluster is being stopped
  • Synchronizing: The cluster is being synchronized
  • Terminating: The cluster is being deleted
  • Unknown: The cluster status is unknown
    • If it occurs continuously, contact the administrator
Cluster ControlButtons that can change the cluster status
  • Start: Start a stopped cluster
  • Stop: Stop a running cluster
  • Restart: Restart a running cluster
  • Switch-Over: Switch a Replica cluster to Master
Additional features moreCluster-related management buttons
  • Service status synchronization: Real-time Redis/Valkey service status inquiry
  • Backup history: If backup is set, check the normal execution of backup and history
  • Database recovery: Recover DB based on a specific point in time
  • Parameter management: Possible to inquire and modify Redis/Valkey configuration parameters
  • Rename-Command: Change the name of Redis/Valkey Command
Service CancellationA button to cancel the service
Fig. CacheStore(DBaaS) Status Information and Additional Features

Detailed Information

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

ClassificationDetailed Description
Server InformationServer information configured in the corresponding cluster
  • Category: Server type (Master, Replica, Sentinel)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In DB service, it means cluster SRN
Resource NameResource Name
  • In DB service, it means cluster name
Resource IDUnique resource ID in the service
CreatorThe user who created the service
Creation TimeTime when the service was created
ModifierService information modified user
Modified TimeTime when service information was modified
Image/VersionInstalled Redis/Valkey Image and Version Information
Cluster NameRedis/Valkey server cluster name
Planned ComputePlanned Compute settings for current resources
Maintenance periodDB patch work period setting status
  • If maintenance period setting is required, click the Edit icon to set
BackupBackup setting status
  • If backup setting is required, click the Edit icon to set
Redis/Valkey Port numberPort number required for Redis/Valkey connection
Time ZoneRedis/Valkey Time Zone
Sentinel Port numberPort number for Master and Replica to communicate
VIPVirtual IP information
  • Only available when high availability is set
NetworkNetwork information (VPC, Subnet) where CacheStore (DBaaS) is installed
IP Access ControlService Access Policy Setting
  • If IP addition or deletion is required, click the Modify icon to set
Master & ReplicaMaster, Replica server type, default OS, additional Disk information
  • In case of server type modification, click the Modify icon next to the server type to set
  • Modifying the server type requires a server restart. Please check separately for SW license modifications and SW settings due to specification changes.
SentinelSentinel server type, basic OS information
  • When configuring HA, it is possible to check when 1 replica is selected
Table. CacheStore(DBaaS) Database detailed information items

Tag

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

ClassificationDetailed Description
Tag ListTag list
  • Check Key, Value information of tag
  • Up to 50 tags can be added per resource
  • Search and select existing Key and Value lists when entering tags
Fig. CacheStore(DBaaS) Tags Tab Items

Work History

CacheStore(DBaaS) list page where you can check the operation history of the selected resource.

DivisionDetailed Description
Work History ListResource Change History
  • Work time, resource ID, resource name, work details, event topic, work result, and worker information can be checked
  • To perform a detailed search, click the Detailed Search button
Fig. CacheStore(DBaaS) Work History Tab Detailed Information Items

CacheStore(DBaaS) resource management

If you need to change or restore the existing setting options of the generated CacheStore(DBaaS) resource, or change the command, you can perform the task from the CacheStore(DBaaS) details page.

Operating Control

If changes occur in the running CacheStore (DBaaS) resource, you can start, stop, and restart it. Also, if HA is configured, you can switch the Master-Replica server through Switch-over.

To control the operation of CacheStore(DBaaS), follow the next procedure.

  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource to control the operation. Move to the CacheStore(DBaaS) details page.
  4. Check the CacheStore status and complete the change through the control button below.
    • Start: The CacheStore service is installed on the server and the CacheStore service is running.
    • Stop: CacheStore service can stop the server where CacheStore service is installed.
    • Restart: Only the CacheStore service can be restarted.
    • Switch Over: You can switch between the Master server and the Replica server.

Synchronizing Service Status

You can synchronize the real-time service status of CacheStore(DBaaS).

To check the service status of CacheStore(DBaaS), follow the next procedure.

  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
  2. Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource to query the service status. Move to the CacheStore(DBaaS) details page.
  4. Click the 서비스 상태 동기화 button. During the query, the cluster changes to Synchronizing status.
  5. When the query is complete, the status is updated in the server information item, and the cluster changes to Running status.

Changing Server Type

You can change the configured server type.

Caution
Modifying the server type requires a server restart. Please check separately for SW license modifications and SW settings due to server specification changes.

To change the server type, follow these steps.

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

Cancel CacheStore(DBaaS)

You can cancel unused CacheStore (DBaaS) to reduce operating costs. However, when canceling the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel CacheStore(DBaaS), follow the procedure below.

  1. All Services > Database > CacheStore(DBaaS) menu is clicked. It moves to the Service Home page of CacheStore(DBaaS).
  2. Service Home page, click the CacheStore(DBaaS) menu. Move to the CacheStore(DBaaS) list page.
  3. On the CacheStore(DBaaS) list page, select the resource to be canceled and click the Service Cancellation button.
  4. Once the cancellation is complete, please check if the resource has been cancelled on the CacheStore(DBaaS) list page.

6.2.1 - Managing CacheStore Service

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

Managing Parameters

It provides a feature to easily view and modify database configuration parameters.

Viewing Parameters

To view configuration parameters, follow these steps:

  1. Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
  2. Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.

Modifying Parameters

To modify configuration parameters, follow these steps:

  1. Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
  2. Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
  3. Click the resource you want to view and modify parameters on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
  5. Click the View button in the Parameter Management popup window. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.
  7. If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the parameter to be modified.
  8. When the input is complete, click the Save button.

Renaming Commands

Note
When applying Rename-Command, the CacheStore (DBaaS) service is interrupted due to restart.

It provides a function to view and modify Redis OSS/Valkey Command names. To view and modify Command names, follow these steps:

  1. Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
  2. Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
  3. Click the resource you want to modify the Command name on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
  4. Click the More button and then click the Rename-Command button. It moves to the Rename-Command page.
  5. Click the View button on the Rename-Command page. The View Notification popup window opens.
  6. When the View Notification popup window opens, click the OK button. It takes some time to view.
  7. If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the Command to be modified.
  8. When the input is complete, click the Complete button.

6.2.2 - CacheStore Backup and Recovery

The user can set up backups of CacheStore(DBaaS) through the Samsung Cloud Platform Console and recover with the backed-up files.

CacheStore(DBaaS) backup

CacheStore(DBaaS) provides a data backup function based on its own backup command. It also provides an optimized backup environment for data protection and management through backup history check and backup file deletion functions.

Setting up backup

The method of setting up a backup for CacheStore(DBaaS) is described in CacheStore(DBaaS) creation guide, please refer to it.

To modify the backup settings of the generated resource, follow these steps.

Caution

If backup is set, backup will be performed at the specified time after the set time, and additional fees will be incurred depending on the backup capacity.

  • If the backup setting is changed to unset, the backup operation will be stopped immediately, and the stored backup data will be deleted and can no longer be used.
  1. All Services > Database > CacheStore(DBaaS) menu, click. It moves to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource to set the backup. It moves to the CacheStore(DBaaS) detail page.
  4. Click the Edit icon of the backup item. The Backup Settings popup window opens.
  5. If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
    • If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.

Check Backup History

Notice
To set up notifications for backup success and failure, you can set them up through the Notification Manager product. For detailed usage guidelines on setting up notification policies, please refer to Creating a Notification Policy.

To check the backup history, follow these steps.

  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource to check the backup history. It moves to the CacheStore(DBaaS) details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting Backup Files

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please make sure to check if the data is unnecessary before deleting it.
  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource to check the backup history. It moves to the CacheStore(DBaaS) detail page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. Backup History popup window, check the file you want to delete and click the Delete button.

CachStore(DBaaS) recovery

In the event of a failure or data loss, where recovery from a backup file is necessary, the recovery function allows recovery based on a specific point in time.

To recover CacheStore(DBaaS), follow these steps.

  1. Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
  3. CacheStore(DBaaS) list page, click the resource you want to restore. It moves to the CacheStore(DBaaS) details page.
  4. Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
  5. After entering information in the Database recovery configuration area, click the Complete button.
Classification
Necessity
Detailed Description
Recovery TypeRequiredUser sets the point in time to recover
  • Recover based on backup files, and select from the list of backup file timestamps displayed
Server name prefixRequiredServer name of the recovery DB
  • Start with lowercase English letters, using lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
  • A postfix such as 001, 002 is attached based on the server name to create the actual server name
Cluster NameRequiredCluster name of the recovery DB
  • Enter in English, 3-20 characters
  • A cluster is a unit that bundles multiple servers
Service Type > Server TypeRequiredServer type where the recovery DB will be installed
  • Standard: Standard specification commonly used
  • High Capacity: High-capacity server with 24vCore or more (to be provided later)
Service Type > Planned ComputeSelectionCurrent status of resources with Planned Compute set
  • In Use: Number of resources with Planned Compute set that are in use
  • Settings: Number of resources with Planned Compute set
  • Coverage Preview: Amount applied by resource-based Planned Compute
  • Create Planned Compute Service: Move to the Planned Compute service application page
Service Type > Block StorageRequiredBlock Storage setting used by recovery DB
  • Basic OS: Area where DB engine is installed
  • DATA: Area where files such as AOF (Append Only File) and RDB (Redis Database) are stored
    • Applied equally to the storage type set in the original cluster
    • Capacity can be entered in multiples of 8 within the range of 56 to 5,120
Redis/Valkey Port numberrequiredRedis/Valkey Port number set in the original DB
IP Access ControlSelectSet service access policy
  • Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately
  • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button
  • To delete the entered IP, click the x button next to the entered IP
Maintenance periodSelectCacheStore(DBaaS) DB maintenance period
  • Use is selected, set the day of the week, start time, and duration
  • It is recommended to set the maintenance period for stable DB management. Patch work is performed at the set time and service interruption occurs
  • If not used, Samsung SDS is not responsible for problems that occur due to non-application of patches.
TagSelectionAdd Tag
  • Click the Add Tag button and enter or select Key, Value
Fig. CacheStore(DBaaS) recovery configuration items

6.2.3 - CacheStore(DBaaS) server connection

Scenario Overview

CacheStore(DBaaS) connection scenario is a scenario where Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To connect to CacheStore (DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.

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

Architecture
Figure. CacheStore(DBaaS) server connection architecture

Scenario Components

You can configure the scenario using the following services.

Service Group
Service
Detailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
NetworkingVPC > SubnetA service that allows users to subdivide the network according to purpose,size in VPC
NetworkingVPC > Public IPA service that reserves public IP and assigns and returns it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the internet
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
DatabaseCacheStore(DBaaS)A service that easily creates and manages CacheStore in a web environment
ComputeVirtual ServerCloud computing optimized virtual server
ComputeVirtual Server > KeypairEncryption file used to connect to the Virtual Server
Table. Scenario Component List
Note
  • The default policy of Security Group is Deny All, so only allowed IPs should be registered.
  • In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources to external threats.
    • By specifying the necessary IP and Port to set the policy, you can enhance security.

Scenario composition method

To configure the scenario, create the necessary services through the following procedure.

1. Configuring the Network

This describes the process of configuring the network environment for connecting to the Bastion Host and Database services.

1-1. Creating a VPC

For detailed creation methods, please refer to the Networking > VPC > How-to guides guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
  3. VPC Creation page, please enter the information required for service creation.
    • IP range should be entered as 192.168.x.0/16.
  4. In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
    • Once creation is complete, check the created resource on the VPC list page.

1-2. Creating a Subnet

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Subnet menu. It moves to the Subnet list page.
  3. Click the Subnet Creation button. It moves to the Subnet Creation page.
  4. Subnet Creation page where you enter the information needed to create a service.
    • Subnet type should be selected as General.
    • Please select a pre-created VPC.
    • IP range should be entered as 192.168.x.0/24.
  5. In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
    • Once creation is complete, check the created resource on the Subnet list page.

1-3. Creating an Internet Gateway

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Internet Gateway menu. Move to the Internet Gateway list page.
  3. Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
  4. Internet Gateway creation page, please enter the required information necessary for service creation.
    • Please select a pre-created VPC.
    • Select Use in the Firewall usage item.
  5. In the Summary panel, review the detailed information and the estimated charge amount, and then click the Complete button.
    • Once the creation is complete, check the created resource on the Internet Gateway list page.

1-4. Creating a Public IP

For detailed creation methods, please refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
  2. Service Home page, click the Public IP menu. It moves to the Public IP list page.
  3. Public IP Reservation 버튼을 클릭하세요. Public IP Reservation 페이지로 이동합니다.
  4. Public IP Reservation page, please enter the required information necessary for service reservation.
  5. In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
    • Once creation is complete, check the created resource on the Public IP list page.

1-5. Creating a Security Group

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Create Security Group button. Move to the Create Security Group page.
  3. Security Group Creation page, please enter the required information necessary for service creation.
  4. Check the input information and click the Complete button.
    • Once creation is complete, check the created resource on the Security Group list page

2. Creating a Bastion host

This describes the process of configuring the Bastion Host where the database connection client should be installed.

2-1. Creating a Server Keypair

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Keypair menu. It moves to the Keypair list page.
  3. Create Keypair button will be clicked. It moves to the Create Keypair page.
  4. Keypair creation page where you enter the required information necessary for service creation.
  5. Check the creation information and click the Complete button.
    • The key download is only available for the first time, and re-issuance is not provided.
    • Please make sure to store the downloaded key in a safe place.

2-2. Creating a Bastion Host

For detailed creation methods, please refer to the Compute > Virtual Server > How-to guides guide.
  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server creation button. Move to the Virtual Server creation page.
  3. Virtual Server Creation page, please enter the required information necessary for service creation.
  4. In the Summary panel, review the detailed information and estimated billing amount, and click the Complete button.
    • Once the creation is complete, check the created resource on the Virtual Server list page.

2-3. Check Bastion host connection ID and PW

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
  3. Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
  4. Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
  5. RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Server Keypair creation.
  6. After attaching, click the Password confirmation button. The ID and password required to access the resource will be displayed.

3. Creating a Database

It describes the process of creating a Database service.

3-1. Creating CacheStore (DBaaS) Service

For detailed creation methods, please refer to the Database > CacheStore(DBaaS) > How-to guides guide.
  1. All services > Database > CacheStore(DBaaS) menu is clicked. It moves to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) creation button. It moves to the CacheStore(DBaaS) creation page.
  3. CacheStore(DBaaS) creation page, please enter the required information needed for service creation.
    • Select and connect to the pre-created VPC and Subnet.
    • Enter database-related creation information on the essential information input screen.
    • Add the Bastion host IP to the IP access control item.
    • Database Port is 2866 by default, but users can also specify it.
  4. In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
    • Once creation is complete, check the created resource on the CacheStore(DBaaS) list page.

4. Setting Rules

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

4-1. Security Group Add Security Rules

For detailed creation methods, please refer to the Networking > Security Group > How-to guides guide.
  1. Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
  2. Service Home page, click the Security Group menu. Move to the Security Group list page.
  3. 1-5. Creating a Security Group Select the Security Group resource created from 1-5. Creating a Security Group. It moves to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Rule tab, click the Add Rule button. It moves to the Add Rule popup window.
  6. In the Add Rule popup window, enter the following rules and click the OK button
DirectionRemoteTarget AddressProtocolPortDescription
InboundCIDRUser PC IPTCP3389 (RDP)Bastion connection PC → Bastion host
OutboundCIDRDB IPTCPDatabase Port (direct input)Bastion host → Database
Fig. Security Group security rules to be added

4-2. Adding IGW Firewall Rules

For detailed creation methods, please refer to the Networking > Firewall > How-to guides guide.
  1. Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
  2. Service Home page, click the Firewall menu. It moves to the Firewall list page.
  3. Firewall list page, select the Internet Gateway resource name created in 1-3. Internet Gateway creation. It moves to the detailed information page of the corresponding resource.
  4. Click the Rules tab on the detailed information page. It moves to the Rules tab.
  5. Rule tab, click the Add Rule button. Move to the Add Rule popup window.
  6. In the Add Rule popup window, enter the following rules and click the OK button.
Departure AddressDestination AddressProtocolPortActionDirectionDescription
Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
Fig. Internet Gateway Firewall rules to be added

5. Connecting to the Database

This explains the process of a user accessing the Database through a DB connection client program.

This guide provides instructions on how to connect using Another Redis Desktop Manager. There are various database client programs and CLI utilities, so you can also install and use the tools that are suitable for the user.

5-1. Connecting to the Bastion host

  1. Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
  2. When the remote desktop connection is successful, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Check Bastion host access ID and PW and click the Confirm button.

5-2. Install DB connection client program (Another Redis Desktop Manager) on the Bastion host

  1. Download another Redis Desktop Manager program.
  2. Connect the hard drive of the user PC to upload the file to the Bastion host.
  3. Click the Details button for local devices and resources items in the Local Resources tab of the remote desktop connection.
  4. Select the local disk where the file was downloaded to the drive and click the Confirm button.
  5. Download the file, copy it to the Bastion Host, and upload it, then click on the pgAdmin installation file to install it.

5-3. Using DB connection client program(Another Redis Desktop Manager) to connect to Database

  1. Run Another Redis Desktop Manager and click New Connection. The New Connection popup window will appear.
  2. New Connection popup window, enter the Database server information created in 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
    Required Input Element ItemsInput Value
    HostDatabase Server IP
    PortDatabase Port
    PasswordDatabase password
    Connection NameCustom (ex. Service Name)
    DB Connection Client Program Input Items
  3. After connecting, you can perform basic information checks on Redis, data management, and CRUD operations on keys.

6.3 - API Reference

API

6.4 - CLI Reference

CLI Reference

6.5 - Release Note

CacheStore(DBaaS)

2025.07.01
FEATURE User (Access Control) Management, DB Audit Log Export Function Added, Backup Notification Function Provided
  • CacheStore(DBaaS) feature added
    • CacheStore(DBaaS) New Image Added
  • Redis OSS was forked and developed as an open-source, Valkey image support
    • 2nd generation server type added
  • Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see CacheStore(DBaaS) server type
    • Backup Alert Feature provided
  • Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
    • Block Storage type added HDD, HDD_KMS type
2025.02.27
FEATURE Common Feature Changes
  • Samsung Cloud Platform common feature changes
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.10.01
NEW CacheStore(DBaaS) Service Official Version Release
  • The service name is changed to CacheStore(DBaaS).
  • Block Storage type has an option to select encrypted storage for volumes added.
  • The Role Switch (Active ↔ Standby) function has been added to the Active DB and Standby DB composed of duplication.
  • The cloud monitoring service is linked, so DB instance performance and log monitoring are possible.
  • Depending on the server type selected by the customer, Planned Compute policy setting is possible.
2024.07.02
NEW Beta version release
  • A Redis(DBaaS) service that can easily create and manage Redis OSS in a web environment has been released.