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

Return to the regular view of this page.

Overview

Service Overview

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

MySQL(DBaaS) is designed with a high availability architecture that considers storage-based data replication and minimization of failover time. To prevent data loss, when content in the Active server is changed, it is synchronously replicated to the Standby server, and up to 5 read-only servers called Replicas are provided for read load distribution and disaster recovery (DR). Additionally, to prepare for problems with the DB server or data, it provides automatic backup at a user-specified time, enabling data recovery at a desired point in time.

Architecture
Figure. MySQL(DBaaS) Architecture

Provided Features

MySQL(DBaaS) provides the following features.

  • Auto Provisioning: Database (DB) installation and configuration is possible through UI, and Active-standby redundancy configuration based on storage replication is provided. When the Active server fails, it automatically fails over to Standby.
  • Operation Control Management: Provides functionality to control the status of running servers. In addition to start and stop, restart is possible when there is an issue with the DB or to reflect configuration values. When configured with high availability (HA), users can directly switch between Active-Standby nodes through Switch-over.
  • Backup and Recovery: Provides data backup functionality based on its own backup commands. Backup time and retention period can be set by the user, and additional charges occur according to backup capacity. Additionally, it provides recovery functionality for backed-up data, and when the user performs recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup storage point, user-specified point). When recovering to a user-specified point, the recovery point can be set up to 5 minutes/10 minutes/30 minutes/1 hour ago based on stored backup files and archive files.
  • Version Management: Provides version upgrade (Minor) functionality for some feature improvements and security patches. Users can select whether to perform backup according to version upgrade, and if backup is performed, the data is backed up before patching and then the DB engine is updated.
  • Replica Configuration: Up to 5 Read Replicas can be configured in the same/different region for read load distribution and disaster recovery (DR).
  • Parameter Management: DB configuration parameters for performance improvement and security can be modified.
  • Service Status Check: Checks the final status of the current DB service.
  • Monitoring: CPU, memory, and performance monitoring information can be checked through Cloud Monitoring and Servicewatch.
  • DB User Management: Manages by checking DB account (user) information registered in the DB.
  • DB Access Control Management: Access allowed IP registration and cancellation based on DB accounts registered in the DB is possible.
  • Archive Management: Archive file retention period (1 day ~ 35 days) in the DB server and Archive mode (On/Off) can be set.
  • DB Log Export: Logs stored through Audit settings can be exported to the user’s Object Storage.
  • Migration: Supports migration using Replication method by synchronizing data in real-time with the operating database without service interruption.
  • OS Kernel Upgrade: OS Kernel can be upgraded for some feature improvements and security patch application.

Components

MySQL(DBaaS) provides pre-verified 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 stops is set to 6 months before the EoTS date.

According to the supplier’s policy, EOS and EoTS dates may change, so 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-192026-04-30
8.0.302026-03-192026-04-30
8.0.322026-03-192026-04-30
8.0.332026-03-192026-04-30
8.0.342026-03-192026-04-30
8.0.352026-03-192026-04-30
8.0.362026-03-192026-04-30
8.0.372026-03-192026-04-30
8.0.412026-03-192026-04-30
8.0.422026-03-192026-04-30
8.4.52031-12 (Scheduled)2032-04-30
Table. MySQL(DBaaS) Provided Engine Versions

Server Type

The server type supported by MySQL(DBaaS) is in the following format.

For details on the server types provided by MySQL(DBaaS), refer to MySQL(DBaaS) Server Types.

Standard db1v2m4
ClassificationExampleDetailed Description
Server TypeStandardProvided server types
  • Standard: Standard specifications (vCPU, Memory) generally used
  • High Capacity: Large capacity server specifications with 24 vCore or more
Server Specificationdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) generally used
  • dbH2: Large capacity server specifications
    • Provides servers with 24 vCore or more
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory capacity
  • m4: 4GB Memory
Table. MySQL(DBaaS) Server Type Components

Prerequisite Services

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

Service CategoryServiceDetailed Description
NetworkingVPCService that provides an independent virtual network in a cloud environment
Table. MySQL(DBaaS) Prerequisite Services

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

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

3 - ServiceWatch Metrics

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

Reference
To check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the MySQL namespace.

OS Basic Metrics

CategoryPerformance ItemDetailed DescriptionUnitMeaningful Statistics
CPUCPU UsageCPU UsagePercent
DiskDisk UsageDisk Usage RatePercent
DiskDisk Write BytesWrite capacity on block device (bytes/second)Bytes/Second
DiskDisk Read BytesAmount read from block device (bytes/second)Bytes/Second
DiskDisk Write RequestNumber of write requests in block device (requests/second)Count/Second
DiskDisk Read RequestsNumber of read requests on block device (requests/second)Count/Second
DiskAverage Disk I/O Queue SizeAverage queue length of requests issued to the block deviceNone
DiskDisk I/O UtilizationPercentage of time the block device actually processes I/O operationsPercent
MemoryMemory UsageMemory Usage RatePercent
NetworkNetwork In BytesReceived capacity on network interface (bytes/second)Bytes/Second
NetworkNetwork Out BytesAmount transmitted from the network interface (bytes/second)Bytes/Second
NetworkTCP ConnectionsTotal number of TCP connections currently properly establishedCount/Second
NetworkNetwork In PacketsNumber of packets received on the network interfaceCount
NetworkNetwork Out PacketsNumber of packets transmitted from the network interfaceCount
NetworkNetwork In DroppedNumber of packet drops received on the network interfaceCount
NetworkNetwork Out DroppedNumber of packet drops transmitted from the network interfaceCount
NetworkNetwork In ErrorsNumber of packet errors received on the network interfaceCount
NetworkNetwork Out ErrorsNumber of packet errors transmitted from the network interfaceCount
Table. OS Basic Metrics

MySQL Basic Metrics

CategoryPerformance ItemDetailed DescriptionUnitMeaningful Statistics
ActivelockActive locksNumber of active locksCount
ActivesessionActive sessionsNumber of active sessionsCount
ActivesessionConnection usageDB connection session usage ratePercent
ActivesessionConnectionsDB connection sessionCount
ActivesessionConnections(MAX)Maximum number of connections that can be attached to the DBCount
DatafileBinary log usedbinary log usage (MB)Megabytes
DatafileOpen filesNumber of DB files in open stateCount
DatafileOpen files(MAX)Number of DB files that can be openedCount
DatafileOpen files usageDB file maximum count usage ratePercent
DatafileRelay log usedRelay log usage(MB)Megabytes
InnoDBInnoDB buffer pool hit ratioPercent
InnoDBInnoDB row lock waitsNumber of InnoDB transactions currently waiting for a lock (Lock-wait)Count
InnoDBInnoDB row lock timeTotal time waited due to InnoDB row lock (in milliseconds)Count
InnoDBInnoDB table locks waitsNumber of times waiting occurred to acquire table lock (cumulative)Count
StateInstance stateMariaDB Process status up/down checkCount
StateSlave behind master seconds (Replica Only)Replica’s delay amount (unit: seconds)Seconds
StateReplica Thread running (Replica Only)
StateReplica io thread running (Replica Only)
StateReplica SQL thread running (Replica Only)
TablespaceTablespace usedTablespace usageMegabytes
TablespaceTablespace used(TOTAL)Tablespace usage (total)Megabytes
TransactionsSlow queriesNumber of slow queriesCount
TransactionsTransaction timeLong Transaction timeSeconds
TransactionsWait locksNumber of sessions waiting for lockCount
TransactionsSQL Queries/SecTotal number (cumulative) of all queries (statements) received from clients since the server startedCount
Table. MySQL basic metrics