DB Server

Available in VPC

In DB Server, you can create or delete MySQL Server and view the list of MySQL Server in operation. In addition, you can change the specifications of the MySQL Server in operation or manage admin (user) accounts.

DB Server interface

The basics of using MySQL Server are as follows:

View MySQL Server list

From the list of MySQL Servers that have been created and are currently operating, you can view the information on each server. To view the MySQL Server list:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
2. Click the DB Server menu.
3. When the list of MySQL Servers you created appears, view the summary information or click MySQL Server to view the details.
   
   • DB Service name: Service name of MySQL, namely, one of the MySQL Server groups classified by role. This generally refers to a server group that consists of one Master Server, one Standby Master Server, or multiple Slave Servers. MySQL servers with the same data are referred to as the same Service.
     • : Click to change the service name.
   • DB role: Roles of the MySQL Server.
     • Master: The Master Server when selecting high availability support.
     • Standby master: The Standby Server when selecting high availability support. If the Master Server fails, then it automatically performs the role of the master.
     • Stand Alone: The single Server when the Support high availability is not selected.
     • Recovery: The read only server that is restored using a backup. It can be changed to a new DB Server through the new DB Service creation feature.
   • DB Server name: Name of the MySQL Server.
   • DB Server type: Type of the MySQL Server and its available memory.
   • Data storage: Size of the data storage in use (available capacity).
   • Status: Status of the MySQL Server.
     • Creating: Status in which the MySQL Server is being created with the information you entered.
     • Configuring: Status in which the MySQL Server is being created and configured based on user input data.
     • Running: Status in which the creation and configuration of the MySQL Server have been completed based on user input data, enabling the application server access to the MySQL.
     • Deleting: Status in which the MySQL Server created with the information you entered is being deleted.
     • Stopping: Status in which the MySQL Server with the information you entered is being stopped.
     • Restarting: Status in which the MySQL Server with the information you entered is being restarted.
     • Restoring (standby master): Standby Master Server is being replaced due to a failure, but the Master Server is operating normally.
     • Unknown: MySQL Server is undergoing a problem and needs inspection.
       • The master/ slave server is in unknown state, MySQL server is undergoing a problem and needs inspection.
         If you need to operate the MySQL server after inspection, use the restart feature.
       • The Standby Master Server is in unknown state, replication has stopped or been delayed for over one hour.
         You need to either rebuild the Standby Master Server or resolve the replication delay.
   • Subnet: Name of the subnet being used by the MySQL Server.
   • Monitoring: Go to the monitoring screen.
   • DB Status: Go to the view MySQL Server details page.
   • Private domain: Information of the private domain.
   • Public domain: Information of the public domain that allows external access.
     • This is displayed only when Public domain is enabled through Public domain management features in the Manage DB menu.
   • Created date: Date when the MySQL Server was created, specifically the initial point when the server status changed to creating.
   • Operation date: Date when the MySQL Server entered operation, specifically the initial point when the server status changed to operating.
   • Data storage type: Type of data storage in use.
   • Data storage usage: Data storage space currently being used.
   • DB access port: Port number being used by the MySQL Server.
   • ACG: Name and ID of ACG being used in the MySQL Server.
     • : Click to move to Server > ACG.
     • [View rules]: Click to view the detailed rules applied.

• Apply data storage encryption: Whether encryption is enabled for saving to the data storage (Y or N).
• Return protection: Return protection setting displayed as enabled or disabled.
• Backup storage period (backup time): The configured backup file storage period and backup cycle, if the backup feature is enabled.
  : Click to enable or disable the backup feature or set the file retention period and backup cycle.
• VPC: Name of the VPC being used by the MySQL Server.
• Server generation: Generation of the server where the MySQL Server is installed.
• Multi zone: Whether multi zone is enabled (Y or N).
• Private IP: Private IP information applied to the MySQL Server.
• DB engine version: Version of the MySQL installed on the Server.
• DB License: license Information of the MySQL installed on the Server.
• High availability: Whether the high availability feature is enabled (Y or N).
• DB access port: Port number being used by the MySQL Server.
• Database Config: Config applied to the MySQL Server
  * : Click to go to the Database Config page

Create MySQL Server

To create a MySQL Server in VPC:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
2. Click the DB Server menu.
3. Click [Create DB Server].
   
4. When the service subscription page appears, take the following steps in order:
   • 1. Set server
   • 2. Set DB
   • 3. Final confirmation

1. Set server

To create a Server to install MySQL by entering the settings:

1. When the server settings screen appears, view the DBMS type to install on the server and the server generation.
   • DBMS type: Type of DBMS to install on the server.
   • Server generation: Server generations that can be created in NAVER Cloud Platform.
2. View the version and license information of the MySQL version to be installed.
   • DB engine version: Information of the MySQL version that can be created in NAVER Cloud Platform.
   • DB license: Open source license information of MySQL that can be created in NAVER Cloud Platform.
3. Set additional options for the availability of the server to be created.
   • Support high availability: Click to select whether to use the failover feature for automatic recovery in case of failure.
     • When you select it, set redundancy with 2 MySQL Servers, a Master Server and a Standby Master Server.
     • When selected, set backup file retention period and backup time (default: 1 day, automatic).
     • When selected, disabling the storage of backup files is not possible.
     • When selected, additional fees will be incurred.
     • The Standby Master Server is not accessible by individual users.
     • Proceed with DB backup on the Standby Master Server at the point of performing backup.
   • Multi zone: To secure advanced high availability, click to select whether to create a Master Server and Standby Master Server separately in 2 different zones, with 1 in each zone.
4. Set items related to VPC and MySQL Server required to create the MySQL Server.
   • VPC: Select the VPC to be used for the creation of the server and MySQL.
     • [Refresh]: Click to refresh the list of created VPC.
     • [Create VPC]: Click to create a new VPC.
   • Subnet: Select a subnet to be used when accessing VPC.
     A public domain can only be applied for usage on the DB server created in Public Subnet.
     Subnet transfer is not available after creating a DB Server.
     • [Refresh]: Click to refresh the list of created Subnets.
     • [Create subnet]: Click to create a new subnet.
   • DB Server type: Select the MySQL Server type to be created and available memory according to the server type.
   • Apply data storage encryption: Click to select the usage status of encryption when saving DB data to storage.
     • Starting from October 21, 2024, new services will no longer provide data storage encryption features.
   • Data storage type: Storage type for saving DB data.
     • The settings can't be changed after the creation of the MySQL Server.
     • When you select G2 as the server generation, select SSD or HDD.
     • When you select g3 as the server generation, automatically set to SSD.
   • Data storage capacity: view the storage capacity for saving DB data.
     • 10 GB is allocated upon initial creation of the MySQL Server.
     • The capacity is automatically added in 10 GB units and charged as data increases.
     • Supports up to 6000 GB.
5. View the applicable pricing plan information when using Cloud DB for MySQL.
   • Pricing plan: an hourly pricing plan, which is billed based on the hours used, is applied by default, and it is changed depending on the server specifications and storage capacity.
   • For more information, click Pricing information.
6. Set the rest of the items required to create the MySQL Server.
   • DB Server name: Enter the name of the MySQL Server to be created.
     • Enter between 3 and 20 characters using lowercase English letters, numbers, and hyphens (-).
     • It must start with an English letter and end with an English letter or a number.
     • To identify servers, random text and a 3-digit number are assigned automatically after the name you entered. Example: mysql-001-xxxx.
     • Duplicate names are not allowed.
   • DB name: Enter the group name that classifies MySQL Servers to be created by its role. Example: mysql-service.
     • Enter between 3 and 30 characters using Korean letters, English letters, numbers, and hyphens (-).
     • Duplicate names are not allowed.
   • Private sub domain: Enter the sub domain to be added to the private domain.
     When adding a slave or recovery, the same sub domain policy is added.
     • Enter between 3 and 15 characters using lowercase English letters, numbers, and hyphens (-).
     • It must start with an English letter and end with an English letter or a number.
   • Return protection: Click to select whether to enable return protection for the MySQL Server to be created.
     • If return protection is enabled, the Master Server and stand alone server cannot be deleted.
   • Set ACG: Access Control Group (ACG) is created automatically.
     • The detailed settings for the ACG are available from Server > ACG in the console.
7. Click [Next].

2. Set DB

To set the information for the MySQL to be installed:

1. When the DB settings screen appears, enter the information required to create a MySQL Server.
   
   • USER_ID: Enter the account ID of the MySQL Server admin.
     • Enter between 4 and 16 characters using English letters, numbers, and special characters such as _ and -.
     • The first character must be an English letter.
     • You cannot use predefined reserved words.
   • HOST (IP): Enter the IP address to access the MySQL Server.
     • Enter "%" to permit access from all IP addresses.
     • For specific IP access only, enter the designated address. Example: 123.123.123.123.
     • For specific IP range permissions, enter the range pattern. Example: 123.123.%.
   • USER password: Enter the account password of the MySQL Server admin.
     • Enter 8 to 20 characters using at least 1 English letter, number, and special character.
     • The special characters ` & + \ " ' / or spaces can't be used.
   • DB access port: Enter a number between 10,000 to 20,000 as a TCP port number to allow access to the MySQL server that will be created
     • Default: 3306.
     • The port number can't be changed after it is specified.
   • DB Data Load: Select the data load method when creating a new DB.
     • Create new: Create a DB Server without data.
     • Import from Object Storage: Restore the DB from the backup file uploaded to Object Storage.
       • Bucket: Select the Object Storage bucket where the restore file is located.
       • Restore file: Select a backup file to restore within the selected bucket.
       • Table case sensitivity: Select the lower_case_table_names value in the backup file.
   • Default DB name: Enter the name of the DB to be created by default.
     • Enter between 1 and 30 characters using English letters, numbers, and special characters such as _ and -.
     • The first character must be an English letter.
   • DB Config settings: View the optimized basic settings provided by NAVER.
     • View details > you can view and change the content from DB Config.
   • Collect DB log: View the provision of log collection and viewer features for error logs and slow query logs.
     • Cloud Log Analytics integrations.
2. Set whether to use backup for the server.
   • Backup settings: Set whether to use the backup, backup file retention period, and backup time.
     • Use the backup settings for the MySQL Server: Click and select to use for backup.
     • Backup file retention period: Click and select the period to store the backup file in a separate backup storage.
       • For point-in-time recovery, the backup file is stored for the maximum of the set retention period + 24 hours.
       • Only backups for tables created with the InnoDB engine are supported.
     • Backup time: Select the backup time between automatic and user-defined.
     • If you select this, additional fees will be incurred depending on the storage capacity used.
       • Automatic: Backup is automatically started every day.
       • User-defined: Backup is started every day within +15 minutes from the time you selected.
3. Click [Next].
4. When the Request subscription to Cloud Log Analytics appears, view the content, and click [OK].
   • If you need to subscribe to Cloud Log Analytics, click [Subscribe to Cloud Log Analytics].
   • For more information about Cloud Log Analytics, see Cloud Log Analytics user guide.

3. Final confirmation

1. When the final confirmation screen appears, view the configured server information, DB information, and Backup information.
   
   • Click [Previous] to edit the settings.
2. Click [Create].
3. View the status of the MySQL Server that was created from the server list on the DB Server page.
   • Creating: Status in which the MySQL Server is being created with the information you entered.
   • Configuring: Status in which the MySQL Server is being created and configured based on user input data.
   • Running: Status in which the creation and configuration of the MySQL Server have been completed based on user input data, enabling the application server access to the MySQL.

Restart MySQL Server

You can easily and conveniently restart MySQL Servers. You can't access servers while they're being restarted. To restart:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
2. Click the DB Server menu.
3. Click the MySQL Server you want to restart, and then click [Restart DB Server].
4. When the Restart DB Server popup window appears, view the name of the MySQL Server to restart, and then click [Yes].
5. View the status of the MySQL Server from the MySQL Server list on the DB Server page.
   • Stopping: Status in which the MySQL Server is being stopped.
   • Restarting: Status in which the MySQL Server is being restarted.

Delete MySQL Server

You can delete a MySQL Server that has been created and is in operation.

If you're using high availability, then both Master Server and Standby Master Server will be deleted. If you have Slave Servers, you must first delete all Slave Servers from the DB Service before deleting the Master Server. If you're using the backup feature, then the backup files are also deleted.

To delete MySQL Servers:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
2. Click the DB Server menu.
3. Click the MySQL Server you want to delete and click [Delete DB Server].
4. When the Delete DB Server popup window appears, enter the name of the MySQL Server to delete, and then click [Yes].
5. View the status of the MySQL Server from the MySQL Server list on the DB Server page.
   • Deleting: Status in which the MySQL Server is being deleted.

Monitoring MySQL Server

NAVER Cloud Platform's Cloud DB for MySQL provides a monitoring service through the dashboards on each server. This allows you to intuitively view servers in operation and data status, and efficiently manage them.

To go to the monitoring page of the MySQL Server that has been created and is in operation:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
2. Click the DB Server menu.
3. Click the MySQL Server you want to monitor, and then click [Monitoring].
4. Click and select the dashboard you want to monitor.
   

Manage MySQL Server

While operating the created MySQL Server, you may need to change the options of the server or DB configured upon creation. Cloud DB for MySQL supports changes or upgrades of a certain number of specifications simply through a few clicks, even for MySQL Servers that have already been created.

To manage a MySQL Server that has been created and is in operation:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MySQL.
2. Click the DB Server menu.
3. Click the MySQL Server you want to manage, and then click [Manage DB].
4. Click and select the item you want to manage.
   
   • View DB Service details
   • View DB Server details
   • Add Slave
   • Create new DB Service (see Backup)
   • Change Multi Zone configuration (VPC)
   • Change high availability settings
   • Change DB specifications
   • Manage DB Config
   • Manage public domain
   • Manage DB user
   • Change DB Server Log settings
   • Master DB Failover
   • MySQL Engine Upgrade
   • Change DB Server name
   • Change return protection settings
   • Manage operation system

View DB Service details

You can enable or disable Swap memory for the MySQL Server within the selected DB Service, or initialize the DB Service.

Set Swap Memory

To set the MySQL Server belonging to the selected DB Service to use or not use Swap Memory, navigate to [Edit] on the Swap Memory settings screen, change the settings, click [Change], and then click [Save].

Consider the following items when you change the Swap Memory settings:

• When you change the Swap Memory settings, all MySQL Servers in that DB Service are restarted.
• Also, 2 GB is added to the Swap Memory.
• The task for changing the Swap Memory settings is carried out sequentially 1 by 1, and it takes about 1 minute for each server.
• In the case of a high availability server, master DB failover is automatically performed to minimize impact on the service. (After the task is completed, master and standby master role are changed.)
• The settings change task is conducted in the following order: recovery -> slave -> master.
• While the swap settings task is in progress, connection errors to the service may occur due to the access block to the DB. Thus, conducting server checks is recommended upon completion of the change task.

Initialize DB Service

Initialize the DB Service required when changing the lower_case_table_names DB Config setting in MySQL 8.0.

To initialize a DB Service:

1. Delete all tables, and retain 1 DB in lowercase letters.
2. In the initialize DB Service page, click [Edit], change the settings, and then click [Change].
   
3. Click [Save].
4. From the confirmation popup window, click [Yes].
   • The initialization is processed. The access to the MySQL Server becomes unavailable while the initialization is being processed.

Set password plugin

• This is a plugin that sets the password complexity of the created MySQL Server DB account.
• You can improve password security by setting a DB account password policy.
• When changing the password_policy setting, the password config setting variable is automatically changed.

1. Click Manage DB > View DB Service details.
2. After changing the detailed setting value to [Enable] on the password plugin setting screen, specify the desired config value.
3. Click [Save].
4. On the popup window, view the DB Service name and click [Yes].
5. If there is a config value to be edited, edit only the config value in the enabled status and click [Save].
6. To delete a plugin, change the detailed setting value to [Disabled] and click [Save].

• Password plugin config variable list

Set audit plugin

• This plugin enables comprehensive logging of DDL and Connections occurring in the DB.
• Stores account information accessing the DB Server.
• Audit plugin exclusively supports MySQL 8.0 version and requires a DB restart following plugin configuration.

1. Click Manage DB > View DB Service details.
2. On the audit plugin settings screen, change the detailed setting value to Enabled and set the config value as desired.
3. Click [Save].
4. On the confirmation popup window, view the DB Service name and details and then click [Yes].
5. If there is a config value to be edited, edit only the config value in the enabled status and click [Save].
6. To delete a plugin, change the detailed setting value to Disabled and click [Save].

• Audit plugin config variable list

• Audit log management and backup method

  • The audit log file provided by Cloud DB for MySQL is rotated by the "audit_log_rotate_on_size" and "audit_log_rotations" config values when setting the "audit_log" plugin.
  • You can backup and manage the audit log file by referring to the postfix value and the last edited date of the audit log file.
  • The last edited date is based on the date the existing audit log file was rotated and the log was created.

• List of audit log fields

Set DB Server

To change the DB Server system settings that are included in the selected DB service, navigate to [Edit] to change settings, then click [Change], and [Yes] on the popup window.

Consider the following items when you change the DB Server system settings:

• DB Server setting is only supported in MySQL version 8.0.
• Server setting changes are performed on the entire server, 1 by 1, in order.
• For a high availability server, the master DB failover process proceeds automatically to minimize the service effect. (After completing the task, master and standby master role change.)
• You can change the library provided by default (GLIBC) in the MySQL engine to a different library.
• To change libraries, you must restart the DB Server.

View MySQL Server details

You can view the details related to the server to check if the selected MySQL Server is operating properly. The details are as follows:

Kill process execution through user-provided stored procedure

You can perform a kill process in the form of a stored procedure with a user account with the DDL permissions from the Master Server and Slave Server. You can only kill an existing process ID but cannot kill a process that is being run by system account. The user ID "agent," "radmin," "ha_admin," "repl_admin," and "system user" do not have the Kill Process permission.

Run the following command to perform kill process through the user-provided stored procedure:

mysql> call sys.ncp_kill_session (session ID);
- A procedure that allows you to use the kill connection feature with super privileges
mysql> call sys.ncp_kill_query (session ID);
- A procedure that allows you to use the kill query feature with super privileges

View Replication status

You can view the replication status of the Standby Master and Slave Servers, take action to skip query with replication errors, or reinstall the DB. Replication delays can occur if the Master Server has query that takes a long time to perform write, or if an excessive number of write tasks occur. The detailed descriptions on the replication page are as follows:

Variables Name / Value
Displays the variable items and values for the replication.

[Skip Replication Error] button
skips the query where a replication error occurred. However, data inconsistency with the Master Server may occur during the skipping process, so it is recommended to proceed with the following methods to ensure that the data remains the same:

• For Standby Master Server
  • Reinstall the applicable Standby Master DB.
• For Slave Server
  • Add a new Slave and delete the current Slave.
  • Reinstall the applicable Slave DB.

[Reinstall standby master] button
reinstalls the standby master DB. DB reinstallation takes backup data from the master DB and configures a standby master DB again. You cannot control the console until reinstallation is completed. The task may take anywhere from dozens of minutes to a few hours depending on the data size.

[Reinstall Slave DB] button
Reinstall the Slave DB. The access to the Slave Server is not available during the reinstallation. The access domain for the Slave Server does not change after the reinstallation.

[View running binary logs] button
Displays the currently running binary logs.8 If replication is operating normally, the message "There is no binary log running." is shown. If the replication is delayed or stopped, then the currently running binary log is displayed.

Manage Database

You can add DB to the selected MySQL Server or delete DB you created. Up to 1,000 DB can be added, and the addition or deletion tasks can be performed for up to 10 DB at a time.

To perform a DB addition or creation task, click [Add Database] to add a DB, or click [Delete] in the same row as the created DB to delete the DB.

Add DB using user-provided stored procedure

You can add DB more conveniently from the Master Server by using the DB addition feature in the form of a stored procedure with a user account with DDL permissions. Such an account has all permissions for the added DB, and it can grant permissions for the DB to other user accounts through GRANT commands. The added DB is also created automatically in the connected Slave Servers.

Run the following command to add a DB using the user-provided stored procedure:

mysql > call sys.ncp_create_db('name of DB to be created [required]','Character Set [select]','Collation [select]');

--Examples
① All character sets and collations are user-specified.
mysql> CALL sys.ncp_create_db('testdb','utf8','utf8_general_ci'); 

② Character set and collation are specified as mysql server default.
mysql> CALL sys.ncp_create_db('testdb','',''); 

③ Character set: user-specified; collation: mysql server default
mysql> CALL sys.ncp_create_db('testdb','utf8',''); 

Add Slave Server

You can add Slave Servers to your MySQL Servers that use the high availability settings. Up to 10 Slave Servers can be added per Master Server, and added Slave Servers could be integrated into NAVER Cloud Platform's Load Balancer to be configured for read load balancing.

The settings of the Master Server are identically applied to the Slave Servers.

• MySQL Server type
• Data storage type
• Data storage capacity
• DB Config settings

The same fees apply to the Slave Servers as to the Master Server, and the fees are charged based on the hours used. To add Slave Server:

1. When the Add Slave DB Server popup window appears, view the Master Server and the Slave Server information.
   • For Multi Zone configurations, select the subnet where you want to create the Slave Server.
     
2. Click [Yes].
3. View the status of the Slave Server that was created from the MySQL Server list on the DB Server page.
   • Creating: Status in which the Slave Server is being created with the information you entered.
   • Configuring: Status in which the Slave Server is being created and configured with the information you entered.
   • Running: Status in which the creation and configuration of the Slave Server have been completed with the information you entered, enabling the application server access to the Slave Server.

Change multi zone configuration

You can select a Master Server and create it in another zone. To change:

1. When the Change multi zone configuration popup window appears, view or enter the information necessary for editing.
   
2. Click [Yes].
   • If multi zone is not in use, multi zone will be enabled.
   • If multi zone is already in use, multi zone will be disabled.
3. View the status of the MySQL Server from the MySQL Server list on the DB Server page.
   • Configuring: Status in which the MySQL Server is being created and configured based on user input data.
   • Running: Status in which the creation and configuration of the MySQL Server have been completed based on user input data, enabling the application server access to the MySQL Server.

Change high availability settings

You can change the selected MySQL Server into a Stand Alone or high availability configuration. To change:

1. When the Change high availability settings popup window appears, view the basic server information.
   
2. Enable to set Stand Alone if the existing high availability setting is Y, and high availability if the existing high availability setting N.
   • If changing to a high availability configuration, click and select whether to use a Multi Zone.
     When selected, 1 Primary DB and 1 Secondary DB are created in different zones to provide higher availability.
3. Click [Yes].
4. View the status of the MySQL Server from the MySQL Server list on the DB Server page.
   • Configuring: Status in which the MySQL Server is being created and configured based on user input data.
   • Running: Status in which the creation and configuration of the MySQL Server have been completed based on user input data, enabling the application server access to the MySQL Server.

Change MySQL Server specifications

You can change the server specifications for the MySQL Server you've created. When changing the server specifications, the specifications for the Master, Standby Master, Slave, and Recovery Servers are also changed. Additional fees are incurred for upgrading specifications.

To change the specifications:

1. When the Change DB Server specifications popup window appears, view the current server specifications.
2. Click and select the server specifications you want to change to.
   
3. Click [Save].
4. View the status of the MySQL Server with the modified specifications from the MySQL Server list on the DB Server page.
   • Configuring: Status in which the MySQL Server is being configured based on user input data.
   • Running: Status in which the configuration of the MySQL Server has been completed with the information you entered, and access to MySQL Server from the application server is available.

Manage DB Config

You can change various settings for the created MySQL Server. The changed settings are applied to the entire DB Service, and some config variables are applied after an automatic restart of the DB Service upon the change. To change:

1. When the Database config popup window appears, view or enter the required information for editing.
   
   • Config Name: name of the config variable
   • Config Value: Variable value
2. Click [Add].
   • When editing the added config variable, click [Edit].
   • When deleting the added config variable (setting it to default), click [Delete].
3. Click [Save].
4. View the status of the MySQL Server with the modified config from the MySQL Server list on the DB Server page.
   • Configuring: Status in which the MySQL Server is being configured based on user input data.
   • Running: Status in which the configuration of the MySQL Server has been completed with the information you entered, and access to MySQL Server from the application server is available.

Config variable list

The following are descriptions of config variables:

Manage DB user

When you create a MySQL Server, the ID and password for the account that will use the server are created by default. However, while operating the server, you may need to add users or reset the passwords of existing user accounts. You may also need to delete user accounts. Cloud DB for MySQL provides a user management features that enables you to conveniently add, edit, and delete user accounts that use the server. The results of the user account change through the user management features are applied to the entire DB Service. Up to 1,000 user accounts can be added.

To add or delete user accounts or change the password of the existing admin account:

1. When the Manage DB user popup window appears, perform the required tasks for the user account.
   

   • Add user account: Enter information in USER_ID, HOST (IP), DB permissions, password, and system table, and click [Add DB user].
     • All DB permissions include the execute permission of the system DB.
     • The CRUD permission includes the READ permission, and the DDL permission includes the READ and CRUD permissions.
     • View procedure can be performed by any account regardless of permissions. For more information, see Official MySQL document (English).
     • Selecting a system table allows you to grant/reclaim SELECT permission for mysql DB.
   • Delete user account: Click [Delete] in the same row as the user account to be deleted.
   • Edit user account password: Click [Edit] in the same row as the user account to be edited, and click [Save] after editing.

2. Click [Save].

3. View the status of the MySQL Server to set user from the MySQL Server list on the DB Server page.

   • Configuring: Status in which the MySQL Server is being configured based on user input data.
   • Running: Status in which the configuration of the MySQL Server has been completed with the information you entered, and access to MySQL Server from the application server is available.

List of permissions for an account with DDL/CRUD/READ permissions

[List of permissions for an account with DDL permissions]

• If MySQL DB version is below 8.0.23

GRANT PROCESS, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, CREATE USER ON *.* TO '[user name]'@'[HOST IP]' WITH GRANT OPTION
GRANT SELECT ON `mysql`.* TO '[user name]'@'[HOST IP]' WITH GRANT OPTION
GRANT SELECT, EXECUTE ON `sys`.* TO '[user name]'@'[HOST IP]' WITH GRANT OPTION
GRANT ALL PRIVILEGES ON `[사용자 DB]`.* TO '[user name]'@'[HOST IP]' WITH GRANT OPTION
GRANT SELECT ON `performance_schema`.* TO '[user name]'@'[HOST IP]' WITH GRANT OPTION
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_transition_type` TO '[user name]'@'[HOST IP]'
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone` TO '[user name]'@'[HOST IP]'
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_name` TO '[user name]'@'[HOST IP]'
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_transition` TO '[user name]'@'[HOST IP]'
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_leap_second` TO '[user name]'@'[HOST IP]'

• If MySQL DB version is 8.0.23 or higher

GRANT PROCESS, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, CREATE USER ON *.* TO '[user name]'@'[HOST IP]' WITH GRANT OPTION
GRANT BACKUP_ADMIN,FLUSH_TABLES,SHOW_ROUTINE,XA_RECOVER_ADMIN ON *.* TO `[사용자명]`@`[HOST IP]` WITH GRANT OPTION
GRANT SELECT ON `mysql`.* TO `[사용자명]`@`[HOST IP]` WITH GRANT OPTION
GRANT ALL PRIVILEGES ON `[사용자 DB]`.* TO `[사용자명]`@`[HOST IP]` WITH GRANT OPTION
GRANT SELECT, EXECUTE ON `sys`.* TO `[사용자명]`@`[HOST IP]` WITH GRANT OPTION
GRANT SELECT ON `performance_schema`.* TO `[사용자명]`@`[HOST IP]` WITH GRANT OPTION
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_leap_second` TO `[사용자명]`@`[HOST IP]`
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_name` TO `[사용자명]`@`[HOST IP]`
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_transition_type` TO `[사용자명]`@`[HOST IP]`
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone_transition` TO `[사용자명]`@`[HOST IP]`
GRANT INSERT, UPDATE, DELETE ON `mysql`.`time_zone` TO `[사용자명]`@`[HOST IP]`

[List of permissions for an account with CRUD permissions]

GRANT PROCESS, SHOW DATABASES, REPLICATION CLIENT ON *.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT ON `mysql`.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT, INSERT, UPDATE, DELETE, REFERENCES, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, SHOW VIEW, EVENT ON `[사용자 DB]`.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT, EXECUTE ON `sys`.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT ON `performance_schema`.* TO `[사용자명]`@`[HOST IP]`             

[List of permissions for an account with READ permissions]

GRANT PROCESS, SHOW DATABASES, REPLICATION CLIENT ON *.* TO `[사용자명]`@`[HOST IP]` 
GRANT SELECT ON `mysql`.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT, EXECUTE ON `sys`.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT, LOCK TABLES, EXECUTE, SHOW VIEW ON `[사용자 DB]`.* TO `[사용자명]`@`[HOST IP]`
GRANT SELECT ON `performance_schema`.* TO `[사용자명]`@`[HOST IP]`

Cloud DB for MySQL management account

The Cloud DB for MySQL management account information used for the user virtual machine is as follows:

Create accounts with permissions for specific tables.

If you want to add a user account with permissions only for a specific table, then create an account with DDL permission, access the system with the account, and create a new account.

To create a new account while accessing a user account that has DDL permission, run the following command:

create user '[user name]'@'[HOST IP]' identified by '[password]';
grant SELECT on [DB name].[table name] to 'user name'@'[HOST IP]';
flush privileges;

-- Examples
create user 'test'@'1.1.1.1' identified by 'test123';
grant SELECT on test_db.test_table to 'test'@'1.1.1.1';

Expiration of Cloud DB for MySQL account passwords

You can directly set the password expiration period for the DB account.

• The expiration period can be set only in number of days (DAY, 1 to 65535).
• The expiration period is based on when the account was created or when the account's password was last changed.
• Expiration settings can only be performed with a user account with DDL privileges.
• Expiration removal can be performed only for yourself and other users when executing with a user account with DDL privileges, and only for yourself when executing with a user account with CRUD and READ privileges.

Run the following command when setting password expiration:

# Set expiration immediately upon execution  
CREATE USER '[user name]'@'[HOST IP]' IDENTIFIED BY '[password]' PASSWORD EXPIRE;
ALTER USER '[user name]'@'[HOST IP]' PASSWORD EXPIRE;
ㅤ
# Set with custom value 
CREATE USER '[user name]'@'[HOST IP]' IDENTIFIED BY '[password]' PASSWORD EXPIRE INTERVAL [ ] DAY;
ALTER USER '[user name]'@'[HOST IP]' PASSWORD EXPIRE INTERVAL [ ] DAY;

Run the following command when removing password expiration:

ALTER USER '[user name]'@'[HOST IP]' IDENTIFIED BY '[password]';

• When removing expiration with the above statement, the password expiration period is reset to the previously set lifetime value.

Run the following command to view the expiration period set for a password:

SELECT password_last_changed, password_lifetime
FROM mysql.user
WHERE user='[user name]' AND host='[HOST IP]';

• password_last_changed: The time when the account was created or the password was last changed
• password_lifetime: Expiration period set for the password
• password_last_changed + password_lifetime: Time when the password expires
• When password_lifetime is "0," the password never expires.
• When password_lifetime is "NULL," it automatically has the default value of the MySQL Server. Currently, the default value for Cloud DB for MySQL is "0."

Tracking login failures and account locking in Cloud DB for MySQL

Users can set up tracking for login failures and account locking directly on the DB account.

• This setting is available from Cloud DB for MySQL version 8.0.19 and above.
• Only user accounts with DDL privileges can run this setting.
• If the DB Server restarts, the login failure count will be initialized, and any locked accounts will be unlocked.

To configure login failure tracking and account locking, run the following command:

CREATE USER '[user name]'@'[HOST IP]' IDENTIFIED BY '[password]' FAILED_LOGIN_ATTEMPTS [] PASSWORD_LOCK_TIME [];
ALTER USER '[user name]'@'[HOST IP]' FAILED_LOGIN_ATTEMPTS [] PASSWORD_LOCK_TIME [];

Run the following command to immediately unlock an account:

ALTER USER '[user name]'@'[HOST IP]' ACCOUNT UNLOCK;

Run the following command to check the values set for an account:

SELECT User_attributes
FROM mysql.user
WHERE user='[user name]' AND host='[HOST IP]';

Apply and reclaim role with user-provided stored procedure

In MySQL 8.0 and later, in VPC, you can apply and reclaim role in a stored procedure form with a user account with DDL permissions. You cannot use Cloud DB for MySQL administration accounts and MySQL default accounts, and you must create Role and grant permission to role directly.

Use the following commands to apply role to a user account with the user-provided stored procedure, or to reclaim an applied role:

• Apply role to user account.

mysql> call sys.ncp_grant_role('role user[required]', 'role host[required]', 'user account user[required]', 'user account host[required]');

• Reclaim applied role to user account.

mysql> call sys.ncp_revoke_role('role user[required]', 'role host[required]', 'user account user[required]', 'user account host[required]');

• Example

① Create role and grant permissions to role.

mysql> CREATE ROLE 'new_role';
mysql> GRANT SELECT, INSERT ON `testdb`.* TO 'new_role';

② Apply role to user account.

mysql> CALL sys.ncp_grant_role('new_role', '%', 'ddl_user', '10.100.%');

③ Enable role.

mysql> SET ROLE 'new_role';

④ Reclaim role from user account.

mysql> CALL sys.ncp_revoke_role('new_role', '%', 'ddl_user', '10.100.%');

mandatory_roles, activate_all_roles_on_login, and edit variables features are not supported.
For each variable, see the following:

• mandatory_roles: use it after granting permission with ncp_grant_role before using DB account.
• activate_all_roles_on_login: Specify role to enable access on log in using the set default role syntax.

Import DB account information

By importing account information, you can view and delete the information of accounts created directly by users in MySQL Server from the console.

To import DB account information:

1. Select the MySQL Server from which the account information is to be fetched, and then navigate to Manage DB > View DB Server details > Manage DB user.
2. Click [Import DB account].
3. On the confirmation popup window, click [Import].

Change DB Server log settings

You can change the log rotation and storage settings for the MySQL Server you created. The changes are applied to the entire DB Service. To change:

1. When the Change DB Server log settings popup window appears, see the following to change the settings:
   
   • Log: View server log name
   • Log rotate: Set the log rotation to be performed daily or by size
   • Log file: number of log files to save
2. Click [Save].
3. View the status of the MySQL for which you've set server logs from the server list on the DB Server page.
   • Configuring: Status in which the MySQL Server is being configured based on user input data.
   • Running: Status in which the configuration of the MySQL Server has been completed with the information you entered, and access to MySQL Server from the application server is available.

Log table backup with user-provided stored procedure

User account that has the DDL permission can execute log table backup feature in the form of stored procedure. This can be executed in the slow query log and general query log, which can store logs in table. Log table backup is stored in mysql database.

If you want to backup the current log table with manual rotation, run the command below:

mysql> call sys.ncp_backup_log_table('Log Table name[required]');
- Log table name: Enter slow_log or general_log

-- Examples
CALL sys.ncp_backup_log_table('slow_log');

If you want to delete the backup log table run the command below:

mysql> call sys.ncp_drop_log_backup_table('backup Log Table name[required]');
- Backup log table name: ^(slow_log|general_log)_([0-9]{4}(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])|backup)$

-- Examples
CALL sys.ncp_drop_log_backup_table('slow_log_backup');

Manage public domain

You can request a Public domain to allow access to a MySQL Server from the outside of NAVER Cloud or to remove a configured public domain. Upon configuring a public domain, the data communicated from the outside is charged based on network usage.

To set or remove a Public domain, click the Manage public domain, and then click [Yes] from the popup window that appears.

Master DB Failover

If the Master Server fails, you can directly use the failover feature to switch from the master to Standby Master Servers. The switch takes approximately 3 minutes, and the server access is unavailable during the switch. To switch:

1. When the Master DB failover popup window appears, view the displayed information.
   
2. Click [Yes].
3. View the status of the MySQL for which you've set the DB failover from the MySQL Server list on the DB Server page.
   • Configuring: Status in which the MySQL Server is being configured based on user input data.
   • Running: Status in which the configuration of the MySQL Server has been completed with the information you entered, and access to MySQL Server from the application server is available.

MySQL Engine Upgrade

MySQL Engine's Minor version upgrade

The MySQL Engine minor version can be upgraded. The version upgrade is applied to the entire DB Service, and the upgrade is performed 1 server at a time in the following order: recovery -> slave -> master. The server access becomes unavailable during the upgrade, and the Master Server is switched to the Standby Master Server to keep the service access block to a minimum.

To upgrade the minor version of the MySQL Engine, click the MySQL engine upgrade, select the version you want to upgrade to from the popup window that appears, and then click [Yes].

MySQL Engine's major version upgrade

You can upgrade major version of the MySQL Engine. The version upgrade is applied to the entire DB Service, and the upgrade is performed 1 server at a time in the following order: recovery -> slave -> master. The server access becomes unavailable during the upgrade, and the Master Server is switched to the Standby Master Server to keep the service access block to a minimum.

1. When the Change DB Server name popup window appears, view the applicable DB Server and its current server name.
2. Enter the DB Server name to change.
   • Enter between 3 and 20 characters using lowercase English letters, numbers, and hyphens (-).
   • It must start with an English letter and end with an English letter or a number.
   • Duplicate names are not allowed.
3. Click [Yes].
4. View the status of the MySQL Server for which the DB Server name was set in the server list on the DB Server screen.
   • Configuring: Status in which the MySQL Server is being configured based on user input data.
   • Running: Status in which the configuration of the MySQL Server has been completed with the information you entered, and access to MySQL Server from the application server is available.

Change return protection settings

You can change the return protection settings of the selected MySQL Server. The return protection settings apply only to master DB and stand alone DB Servers. When return protection is enabled, the corresponding DB Server cannot be deleted. During the change of return protection settings, no server downtime occurs, and the DB Server remains accessible.
To change:

• For DB Servers with return protection disabled, the Configure return protection popup window appears. Confirm the DB Service name and click [Yes].
  

• For DB Servers with return protection enabled, the Disable return protection popup window appears. Confirm the DB Service name and click [Yes].
  

For servers with high availability enabled, return protection can only be set on the Master Server. The Master Server with return protection enabled can return the server in the following cases:

• Disabling high availability returns Standby Master Server automatically.
• Changing multi zone returns the current Standby Master Server automatically, and creates the same server on a new Subnet.

With return protection enabled, creating a new service transfers return protection settings. Return protection settings are delegated in the following cases:

• Create a new service with recovery server set up for MySQL Server recovery.
• Create a new service based on a backup file.

Manage operation system

Update operating system of created DB Server to the latest version. The operating system update is applied to the entire DB Service, and proceeds one server at a time in the following order: hidden -> recovery -> slave -> master. During the update process, server access is not available. To update the Master Server, click [Failover and OS version upgrade]. For more information, see the guide below.

Updating the operating system of non-Master Servers

Updates the operating systems of the Hidden Server, Slave Server, and Recovery Server, excluding the Master Server.
The update proceeds one server at a time in the following order: Hidden Server, Recovery Server, then Slave Server.

1. To update the operating system of non-Master Servers, click [OS management], review the popup window, and then click [Next].
   • Operating System Update
     
   • Kernel Update
     
2. After reviewing the precautions for the operating system update, click the checkbox.
3. Once you have reviewed all precautions, click [Yes].
   • Operating System Update
     
   • Kernel Update
     
4. After reviewing the precautions for updating the operating system of the Master Server, click [Yes].
   
5. You can view the update in progress through DB Server status.
   

Updating the operating system of the Master Server

Updates the operating system of the Master Server.

1. To update the operating system of the Master Server, select the Master Server and click [Failover and OS version upgrade].

   

2. After reviewing the precautions for updating the operating system of the Master Server, click [Upgrade].

   

3. You can view the update in progress through DB Server status.
   

Set read load balancing

You can apply for NAVER Cloud Platform's Load Balancer to distribute the read load on the MySQL Server and connect it to a Slave Server. After creating the Load Balancer, proceed in the order of adding settings to the ACG of MySQL Server so that the created Load Balancer can have normal access.

Create Load Balancer

To create a Load Balancer within the VPC environment on the NAVER Cloud Platform console:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Networking > Load Balancer.
2. Click [Create Load Balancer] and select the desired Load Balancer type.
3. Enter the information required for the creation of the Load Balancer by referring to the Load Balancer user guide in the Note section, and then click [Next].
4. Add Load Balancer listeners, and click [Next].
5. Select the target group, and click [Next].
6. View the settings, and then click [Create Load Balancer].

Set ACG

Adds ACG rules to the Access Control Group (ACG) of the DB Server so that the Load Balancer can access it properly. To set:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Compute > Server.
2. Click the ACG menu.
3. Select the ACG name of the MySQL Server, and click [Set ACG].
4. Enter the following ACG rules for Load Balancer access:
   • Protocol: TCP
   • Access source
     • VPC: IP address range of the Load Balancer subnet
     • Classic: ncloud-load-balancer
   • Allowed port: MySQL Server port
5. Click [Add].
6. Click [Apply].

View Load Balancer

Views the details and access information of created Load Balancers. The access information is used to confirm the IP for accessing the Load Balancer and when accessing it for read balancing.