This is the multi-page printable view of this section. Click here to print.
MySQL(DBaaS)
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.
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.
- MySQL (Community): https://www.mysql.com/support/eol-notice.html
| Service | Provided Version | EOS Date(Samsung Cloud Platform New Creation Stop Date) | EoTS Date(Community Technical Support End Date) |
|---|---|---|---|
| MySQL (Community) | 8.0.28 | 2026-03 (scheduled) | 2026-04-30 |
| 8.0.30 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.32 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.33 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.34 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.35 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.36 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.37 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.41 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.42 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.4.5 | 2031-12 (planned) | 2032-04-30 |
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
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 | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Classification of provided server types
|
| Server Specification | db1 | Classification of provided server types and generations
|
| Server Specification | v2 | Number of vCores
|
| Server Specification | m4 | Memory capacity
|
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
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
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
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Up to 25 Gbps |
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 Item | Detailed Description | Unit |
|---|---|---|
| Active Locks | Active Locks count | cnt |
| Active Sessions | Active Session count | cnt |
| Binary Log Used [MB] | binary log usage | MB |
| Connection Usage [Total] | DB connection session usage rate | % |
| Connections | Connection count | cnt |
| Connections [MAX] | Connection count | cnt |
| Connections | max connected threads count | cnt |
| Data Directory Used [MB] | data directory usage | MB |
| Instance Status [PID] | mysqld process pid | pid |
| Open Files | Number of DB files in open state | cnt |
| Open Files [MAX] | number of DB files that can be opened | cnt |
| Open Files Usage | DB file maximum count usage rate | % |
| Relay Log Used [MB] | relay log usage (MB) | MB |
| Running Threads | running thread number | cnt |
| Safe PID | safe program pid | pid |
| Slave Behind Master seconds | time difference with master node | sec |
| Slowqueries | Number 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 Used | Tablespace usage | MB |
| Tablespace Used [Total] | Tablespace total usage | MB |
| Transaction Time [Long] | Transaction longest execution time | sec |
| Wait Locks | Number of sessions blocked for 60 seconds or more by lock | cnt |
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.
- 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.
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) 생성 button on the Service Home page. You will be taken to the MySQL(DBaaS) 생성 page.
- 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 RequiredDetailed description Image version Required Provide 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 RequiredDetailed description Server Name Prefix Required Server 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 Name Required Cluster 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 Type Required Server type where DB will be installed - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server of 24 vCore or more
- For detailed information about the server types provided by MySQL (DBaaS), refer to MySQL (DBaaS) Server Types
Service Type > Planned Compute Optional Status 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
- Create Planned Compute Service: Go to Planned Compute service application page
- See Apply for Planned Compute for details
Redundancy configuration Select Redundancy configuration status - If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
Network > Common Settings Required Network 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 Settings Required Network 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 Control Select Service 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 Period Select DB 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 - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
- Database configuration required information input Enter or select the required information in the area.
Category RequiredDetailed description Database name Required Server name applied when installing DB - Start with an English letter, use English letters and numbers, and enter 3 to 20 characters
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted Database usernames can be checked in the Console
Database password Required Password to use when accessing the DB - Enter 8-30 characters including letters, numbers, and special characters (
“‘excluded)
Database Password Confirmation Required Re-enter the same password to be used when accessing the DB Database Port number Required Port number required for DB connection - Enter DB port within the range 1,024 ~ 65,535
Backup > Use Select Whether to use backup - Select Use to set backup file retention period, backup start time, Archive backup cycle
Backup > Retention Period Select Backup 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 Period Select Backup 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 frequency Select Archive 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
Parameter Required Parameters 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 set Required Character encoding method to be used in the DB Table case sensitivity select DB Table case sensitivity status Time zone Required Standard 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 RequiredDetailed description Tag Select Add 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
- Select the required information in the Image and Version Selection area.
- 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.
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. You will be taken to the MySQL(DBaaS) List page.
- 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.
Category Detailed description Cluster Status Cluster 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 Control Button 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 features Cluster 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 cancellation Button 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.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in the cluster
|
| Service | Service Name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource Name
|
| Resource ID | Unique resource ID in the service |
| Creator | User who created the service |
| Creation time | Service creation time |
| Editor | User who modified the service information |
| Modification Date/Time | Date and time when service information was modified |
| Image/Version | Installed DB image and version information
|
| Cluster Type | Cluster Type (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster Name | Name of the cluster composed of DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied when installing DB |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute set
|
| Maintenance Period | DB Maintenance Period Status
|
| Backup | Backup Settings Status
|
| Time zone | Standard time zone used by the Database |
| DB character set | Encoding method to use in DB |
| Table case sensitivity | DB Table case sensitivity status |
| VIP | Virtual IP information
|
| Network | Network information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP Access Control | Service Access Policy Settings
|
| Active & Standby | Active/Standby server type, default OS, additional Disk information
|
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.
| Category | Detailed description |
|---|---|
| Master Information | Name of Master Cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status created in the Master cluster
|
Tag
MySQL(DBaaS) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag List | Tag List
|
Work History
On the MySQL(DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Work History List | Resource Change History
|
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.
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page.
- Click the resource to control operation on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- 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.
- All Services > Database > MySQL(DBaaS) Click the menu. Navigate to the Service Home page of MySQL(DBaaS).
- 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.
- Service status synchronization button. Click the button. While fetching, the cluster changes to Synchronizing state.
- When the query is completed, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
To change the server type, follow the steps below.
- 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.
- All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page.
- Click the resource to change the server type on the MySQL(DBaaS) 목록 page. It will move to the MySQL(DBaaS) 상세 page.
- 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.
- 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.
- 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.
- All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to add storage. It navigates to the MySQL(DBaaS) Details page.
- Click the Add Disk button at the bottom of the detailed information. The Add Storage Request popup window opens.
- 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.
- All Services > Database > MySQL(DBaaS) Click the menu. Navigate to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) list page.
- Click the resource to change the server type on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
- 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.
- 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.
- 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.
- All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. You will be taken to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List On the page, select the resource to cancel, and click the Cancel Service button.
- When the termination is complete, check whether the resource has been terminated on the MySQL (DBaaS) list page.
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.
Scenario Components
You can configure the scenario using the following services.
| Service Group | Service | Detailed Description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that allows users to subdivide the network into smaller sections for specific purposes/sizes within the VPC | |
| Networking | VPC > Public IP | A service that reserves a public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | MySQL(DBaaS) | A service that easily creates and manages MySQL in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to Virtual Server |
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
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information needed to create the service.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- 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
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- 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.
- 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
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- 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.
- 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
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Click the Public IP menu on the Service Home page. It moves to the Public IP list page.
- Public IP Reservation button, click. Move to the Public IP Reservation page.
- Public IP Reservation page where you enter the required information necessary for service reservation.
- 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
- Click the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
- Security Group creation page where you enter the required information necessary for service creation.
- 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
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
- Keypair creation button should be clicked. It moves to the Keypair creation page.
- Keypair creation page, please enter the required information necessary for service creation.
- 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
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- The image is Windows, please select.
- Please select the pre-created VPC and Subnet.
- Click NAT Use and select the Public IP reserved in 1-4. Creating Public IP.
- 2-1. Creating a server Keypair Connect the Keypair created from
- 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
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- 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.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
- After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to access the Bastion host later in 5-1. Bastion host 접속하기.
3. Creating a Database
It describes the process of creating a database service.
3-1. Creating a MySQL (DBaaS) Service
- Click on the menu for all services > Database > MySQL(DBaaS). It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the Create MySQL(DBaaS) button. It moves to the Create MySQL(DBaaS) page.
- 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.
- 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
- Click the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 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.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule popup window, enter the rules below, and click the OK button
| Direction | Remote | Destination Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion connection PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- 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.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule In the popup window, enter the rules below and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion connection PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User 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
- 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.
- 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
- Go to the official MySQL page and download the MySQL Workbench program.
- MySQL Workbench program download path: https://dev.mysql.com/downloads/workbench
- Connect the hard drive of the user’s PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- 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
- Run MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup window will appear.
- 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 Items Input Value Connection Name Custom (ex. Service Name) Host name Database server IP Port Database Port Username Database username DB connection client program input items - 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.
- Database > Connect to Database should be clicked. The Connect to Database popup window will appear.
- Select the Connection Name registered in Stored Connection to perform database connection. After connection, you can try simple queries, etc.
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:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to view and modify parameters on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- 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:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to view and modify parameters on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- 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.
- 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:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to view DB users on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. It moves to the DB User Management page.
- 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:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to modify DB users on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. It moves to the DB User Management page.
- Click the View button on the DB User Management page. It takes some time to view.
- If modification is necessary, click the Modify button and change the status area value or enter remarks.
- 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.
Viewing DB Access Control
To view DB users with IP access control set, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to manage access control on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- 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:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to add IP access control on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It takes some time to view.
- When the view is complete, click the Add button. The DB Access Control Add popup window opens.
- In the DB Access Control Add popup window, select the DB user name and enter the IP address.
- When the input is complete, click the Save button.
Deleting DB Access Control
To delete IP access control, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- 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.
- Click the More button and then click the DB Access Control Management button. The DB Access Control Management page will be displayed.
- Click the Inquiry button on the DB Access Control Management page. It may take some time to retrieve the data.
- Once the inquiry is complete, click the Delete button. A Delete pop-up window will appear.
- 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.
Setting Archive Mode
To set the Archive mode, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- 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.
- Click the More button and then click the Archive Settings Management button. The Archive Settings Management page will be displayed.
- Click the Inquiry button on the Archive Settings Management page. It may take some time to retrieve the data.
- Click the Modify button and select the usage and retention period.
- Once the modification is complete, click the Save button.
Deleting Archive Files
To delete Archive files, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- 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.
- Click the More button and then click the Archive Settings Management button. The Archive Settings Management page will be displayed.
- 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.
- 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:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- 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.
- Click the More button and then click the DB Log Export button. The DB Log Export page will be displayed.
- Click the Register button on the DB Log Export page. The DB Log Export Registration page will be displayed.
- Enter the required information on the DB Log Export Registration page and click the Save button.
| Category | Required | Detailed Description |
|---|---|---|
| Log Type | Required | Log type to be stored |
| Storage Bucket Name | Required | Object Storage bucket name to store the log |
| Authentication Key > Access Key | Required | Access key to access the Object Storage |
| Authentication Key > Secret Key | Required | Secret key to access the Object Storage |
| File Creation Cycle | Required | Cycle to create files in Object Storage |
| Original Log Deletion | Optional | Whether to delete the original log when exporting to Object Storage |
Managing DB Log Export
To modify, cancel, or immediately export DB log settings, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- 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.
- Click the More button and then click the DB Log Export button. The DB Log Export page will be displayed.
- 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.
- 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:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource to be upgraded on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the Modify button in the image/version item. The Version Upgrade popup window opens.
- In the Version Upgrade popup window, select the version to be modified and the backup setting, and then click the OK button.
- 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.
To configure the migration, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource to be migrated on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Configure Migration button. The Configure Migration popup window opens.
- In the Configure Migration popup window, check the instructions and click the OK button. It moves to the Configure Migration page.
- On the Configure Migration page, enter the corresponding information and click the Connect Check button.
- When the connection is complete, click the Complete button.
| Classification | Required | Detailed Description |
|---|---|---|
| Source DB Database Name | Required | Database name of the source DB that is the migration target |
| Source DB IP | Required | IP of the source DB that is the migration target |
| Source DB Port | Required | Port of the source DB that is the migration target |
| Source DB User Name | Required | User name of the source DB that is the migration target |
| Source DB Password | Required | Password of the source DB that is the migration target |
The configured migration cluster can be promoted to a master cluster.
To promote the migration cluster to a master, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource to be promoted to a master on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Promote to Master button. The Master Promotion Notification popup window opens.
- Click the OK button in the Master Promotion Notification popup window.
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.
- 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.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click the resource to set the backup. It moves to the MySQL(DBaaS) details page.
- Click the Edit button of the backup item. The Backup Settings popup window opens.
- 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
To view the backup history, follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Delete backup files
To delete the backup history, follow these steps.
- Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) detail page.
- Click the Backup History button. The Backup History popup window opens.
- 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.
To restore MySQL(DBaaS), follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- MySQL(DBaaS) resource list page, click the resource you want to restore. It moves to the MySQL(DBaaS) details page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- Enter the corresponding information in the Database Recovery Configuration area, and then click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | Set the point in time you want to recover
|
| Server name prefix | Required | Server name of the recovery DB
|
| Cluster Name | Required | Cluster name of the recovery DB
|
| Service Type > Server Type | Required | Server type where the recovery DB will be installed
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Recovery DB uses Block Storage settings
|
| Database username | required | Database username set in the original DB |
| Database Port number | required | Database Port number set in the original DB |
| IP Access Control | Select | IP address to access the recovery DB
|
| Maintenance period | Select | DB maintenance period
|
| tag | selection | add tag
|
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.
- All services > Database > MySQL(DBaaS) menu, click. It moves to the Service Home page of MySQL(DBaaS).
- Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click on the resource to configure the Replica. Move to the MySQL(DBaaS) details page.
- Click the Replica Configuration button. It moves to the Replica Configuration page.
- Enter information in the Replica Configuration area, then click the Complete button.
Classification NecessityDetailed Description Number of Replicas Required Number 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 name required Replica 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 Type Required Replica Server Type - Standard: Standard specification commonly used
- High Capacity: High-capacity server with 24vCore or more
Service Type > Planned Compute Select Current 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
- For more information, refer to Apply for Planned Compute
IP Access Control Select Set 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 period Select 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 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.
tag selection add 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.
- Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
- Click on the resource to be reconstructed as a replica on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
- Replica Reconstruction 버튼을 클릭하세요. Replica Reconstruction Notification 팝업창이 열립니다.
- 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.
To promote the Replica Cluster to Master, follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- Click the resource to be promoted to Master on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
- Click the More button and click the Master Promotion button. The Master Promotion Notification popup window opens.
- In the Master Promotion Alert popup window, click the OK button.
3 - API Reference
4 - CLI Reference
5 - Release Note
MySQL(DBaaS)
- 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
- Migration 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.
- 2nd generation server type added
- Samsung Cloud Platform common feature changes
- Account, IAM and Service Home, tags, etc. reflected common CX changes.
- A MySQL(DBaaS) service that allows you to easily create and manage MariaDB in a web environment has been released.

