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

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

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

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