DB Server

Available in Classic and VPC

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

DB server page

The basics of using MySQL servers are as follows:

Viewing MySQL server list (VPC)

The list of MySQL servers shows the servers that have been created and are currently operating. On this list, you can view the information of each server. The following describes how to view the MySQL server list.

1. In the VPC environment of the NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. When the list of MySQL servers appears, you can view the overview 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 high availability support is selected
     • Standby master: the standby server when high availability support is selected. If the master server fails, then it automatically performs the role of the master
     • Standalone: the single server when the high availability support 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
   • MySQL server name: name of the MySQL server
   • MySQL server type: type of the MySQL server and its available memory
   • Monitoring: directs to the monitoring page
   • DB status: directs to the View MySQL server details page
   • DB access port: port number being used by the MySQL server
   • Multi Zone: whether Multi Zone is being used (Y or N)
   • Private domain: information of the private domain
   • Public domain: information of the public domain which allows external access
     • This is displayed only when public domain is enabled through public domain management in the Manage DB menu
   • Data storage: size of the data storage in use (available capacity)
   • Data storage type: type of the data storage in use
   • Data storage usage: data storage space currently being used
   • Apply data storage encryption: whether encryption is enabled for saving to the data storage (Y or N)
   • Status: status of the MySQL server
     • Creating: status in which the MySQL server is being created with the information entered by the user
     • Configuring: status in which the MySQL server is being configured after being created with the information entered by the user
     • Running: status in which the creation and configuration of the MySQL server have been completed with the information entered by user, and access to MySQL from the application server is available
     • Deleting: MySQL server created by the user is being deleted
     • Paused: MySQL server created by the user is currently paused and not operating
     • Restarting: MySQL server created by the user 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.
         If you need to operate the MySQL server after inspection, use the Restart feature
   • Creation date: date when the MySQL server was created, namely, when the server status became Creating
   • Operation date: date when the MySQL server entered operation, namely, when the server status became Operating
   • ACG: name and ID of ACG being used in the MySQL server
     • : click to move to Server > ACG
     • [View rules] button: click to display the detailed rules applied
   • Database config: config applied to the MySQL server
     • : click to go to the Database config page
   • Server generation: generation of the server where the MySQL server is installed
   • DB engine version: version of the MySQL installed on the server
   • DB license: license information of the MySQL installed on the server
   • VPC: name of the VPC being used by the MySQL server
   • Subnet: name of the subnet being used by the MySQL server
   • High availability: whether high availability is enabled (Y or N)
   • Backup storage period (backup time): the configured backup file storage period and backup cycle, if the backup function is enabled
     • : click to enable or disable backup or set the file retention period and backup cycle

Checking MySQL server list (Classic)

The list of MySQL servers shows the servers that have been created and are currently operating. On this list, you can view the information of each server. To view the information, follow these steps:

1. From the Classic environment of the NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. When the list of MySQL servers appears, you can view the overview 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 high availability support is selected
     • Standby master: the standby server when high availability support is selected. If the master server fails, then it automatically performs the role of the master
     • Standalone: the single server when the high availability support is not selected
     • Recovery: the read-only server restored using a backup. It can be changed to a new serviceable DB server upon creating a new DB service
   • MySQL server name: name of the MySQL server
   • MySQL server type: type of the MySQL server and its available memory
   • Monitoring: directs to the monitoring page
   • DB status: directs to the View MySQL server details page
   • DB access port: port number being used by the MySQL server
   • Zone: indicates the zone to which the MySQL server belongs
   • Private domain: information of the private domain
   • Public domain: information of the public domain which allows external access
     • This is displayed only when public domain is enabled through public domain management in the Manage DB menu
   • Data storage: size of the data storage in use (available capacity)
   • Data storage type: type of the data storage in use
   • Data storage capacity: available capacity and used capacity of the data storage in use
   • Status: status of the MySQL server
     • Creating: status in which the MySQL server is being created with the information entered by the user
     • Configuring: status in which the MySQL server is being configured after being created with the information entered by the user
     • Running: status in which the creation and configuration of the MySQL server have been completed with the information entered by user, and access to MySQL from the application server is available
     • Deleting: MySQL server created by the user is being deleted
     • Stop: status in which the MySQL server is being stopped with the information entered by the user
     • Restarting: MySQL server created by the user is being restarted
     • Restoring (standby master): standby master server is being replaced due to a failure, but the master server is operating normally
   • Creation date: date when the MySQL server was created, namely, when the server status became Creating
   • Operation date: date when the MySQL server entered operation, namely, when the server status became Operating
   • ACG: name and ID of ACG being used in the MySQL server
     • : click to move to Server > ACG
     • [View rules] button: click to display the detailed rules applied
   • Database config: config applied to the MySQL server
     • : click to go to the Database config page
   • 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 high availability is enabled (Y or N)
   • Backup storage period (backup time): the configured backup file storage period and backup cycle, if the backup function is enabled
     • : click to enable or disable backup or set the file retention period and backup cycle

Creating MySQL server (VPC)

The following describes how to create a MySQL server in a VPC environment.

1. In the VPC environment of the NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. Click the [Create DB server] button.
   
4. When the service request page appears, proceed with the following steps in order.
   • 1. Set server
   • 2. Set DB
   • 3. Final confirmation

1. Set server

The following describes how to create a server to install MySQL by entering the settings.

1. When the Server settings screen appears, check the type of DBMS to install on the server and the server generation.

   • DBMS type: type of DBMS to install on the server
   • Server generation: server generations supported in NAVER Cloud Platform

2. Check 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
     • Select to use duplex configuration with two MySQL servers including a master server and standby master server
     • When selected, set backup file storage 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 the user
     • DB backup is performed 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 needed for the creation of the MySQL server.

   • VPC: select the VPC to be used for the creation of the server and MySQL
     • [Refresh] button: click to refresh the list of created VPCs
     • [Create VPC] button: click to create a new VPC
   • Subnet: select the subnet to use when accessing the VPC
     Public domains can only be subscribed to on the DB server created in the public subnet.
     Subnet transfer is not available after creating a DB server.
     • [Refresh] button: click to refresh the list of created subnets
     • [Create subnet] button: 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 use status of encryption when saving DB data to storage
     • Enabled when high availability support is selected
     • The settings can't be changed after the creation of the MySQL server
   • Data storage type: click to select the storage type for saving DB data, between SSD and HDD
     • The settings can't be changed after the creation of the MySQL server
   • Data storage capacity: check 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
     • Up to 6000 GB is supported

5. Check 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 according to the server specifications and storage capacity
   • Click Pricing information for more information

6. Set the rest of the items required for the creation of the MySQL server.

   • DB server name: enter the name of the MySQL server to be created
     • The name must be 3-20 characters long and can only include upper and lower case English letters, numbers, and the hyphen (-)
     • 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 that was entered by the user <example> mysql-001-xxxx
     • A duplicated name can't be used
   • DB service name: enter the group name that classifies MySQL servers to be created by its role <example> mysql-service
     • The name must be 3-30 characters long and can only include Korean letters, English letters, numbers, and the hyphen (-)
     • A duplicated name can't be used
   • 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.
     • The name must be 3-15 characters long and can only include upper and lower case English letters, numbers, and the hyphen (-)
     • It must start with an English letter and end with an English letter or a number
   • 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 the [Next] button.

2. Set DB

The following describes how to set the information for the MySQL to be installed.

1. When the DB settings screen appears, enter the information needed to create a MySQL server.
   
   • USER_ID: enter the account ID of the MySQL server admin
     • The ID must be 4-16 characters long and can only include English letters, numbers, the underscore (_), and the hyphen (-)
     • It must start with an English letter
     • Predefined reserved words can't be used
   • HOST (IP): enter the IP address that will access the MySQL server
     • Enter "%" to allow access to all
     • When allowing access of only a specific IP <example> 123.123.123.123
     • When allowing access of only a specific IP range <example> 123.123.%
   • USER password: enter the account password of the MySQL server admin
     • The password must be 8-20 characters long and can only include English letters, numbers, and special characters, with at least 1 of each
     • The special characters ` & + \ " ' / or spaces can't be used
     • When the password plugin is activated, the policy set by the plugin must also be satisfied.
   • DB access port: enter the TCP port number between 10000 and 20000 to which to allow access to the MySQL server to be created
     • Default: 3306
     • The port number can't be changed after it is specified
   • Default DB name: enter the name of the DB to be created by default
     • The ID must be 1-30 characters long and can only include English letters, numbers, the underscore (_), and the hyphen (-)
     • It must start with an English letter
   • DB config settings: check the optimized basic settings provided by NAVER
     • You can check and change the content from View details > DB config
   • Collect DB log: check the provision of log collection and viewer features for error logs and slow query logs
     • Cloud Log Analytics integration
2. Set whether to use the backup for the server to be created.
   • 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 execution time between automatic and user-defined
     • If you select this, additional fees will be incurred according to the storage capacity used
       • Automatic: backup is automatically started every day
       • User-defined: backup is started every day within 15 minutes from the time selected by the user
3. Click the [Next] button.
4. When the Request subscription to Cloud Log Analytics appears, check the content, and then click the [OK] button.
   • If you need to request a subscription to Cloud Log Analytics, click the [Request subscription to Cloud Log Analytics] button
   • For more information on Cloud Log Analytics, see Cloud Log Analytics guide

3. Final confirmation

1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
   
   • Click the [Previous] button to edit the settings
2. Click the [Create] button.
3. Check the status of the MySQL server that was created from the server list in the DB server page.
   • Creating: status in which the MySQL server is being created with the information entered by the user
   • Configuring: status in which the MySQL server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the MySQL server have been completed with the information entered by user, and access to MySQL from the application server is available

Creating MySQL server (Classic)

The following describes how to create a MySQL server.

1. From the Classic environment of the NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. Click the [Create DB server] button.
   
4. When the service request page appears, proceed with the following steps in order.
   • 1. Set server
   • 2. Set DB
   • 3. Final confirmation

1. Set server

The following describes how to create a server to install MySQL by entering the settings.

1. When the Server settings screen appears, check the type of DBMS to install on the server.
   

   • DBMS type: type of DBMS to install on the server

2. Check 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 the zone and MySQL server-related items required for MySQL server creation.

   • Zone: select a zone in which to create a MySQL server
   • Secure Zone: select whether to create a server in the Secure Zone that provides enhanced security
     • Integrating with NAVER Cloud Secure Zone
     • When selected, creates a server in Secure Zone where the firewall policy is applied
     • Secure Zone is available only when KR-2 zone is selected
   • DB server type: select the MySQL server type to be created and available memory according to the server type
   • Data storage type: click to select the storage type for saving DB data, between SSD and HDD
     • The settings can't be changed after the creation of the MySQL server
   • Data storage capacity: check 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
     • Up to 6000 GB is supported

4. Set Support high availability for the availability of the server to be created.

   • Select to use duplex configuration with two MySQL servers including a master server and standby master server
   • Performs a failover for automatic recovery in case of failure
   • When selected, set backup file storage 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 the user

5. Check 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 according to the server specifications and storage capacity
   • Click Pricing information for more information

6. Set the rest of the items required for the creation of the MySQL server.

   • DB server name: enter the name of the MySQL server to be created
     • The name must be 3-25 characters long and can only include upper and lower case English letters, numbers, and the hyphen (-)
     • 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 that was entered by the user <example> mysql-001-xxxx
     • A duplicated name can't be used
   • DB service name: enter the group name that classifies MySQL servers to be created by its role <example> mysql-service
     • The name must be 3-30 characters long and can only include Korean letters, English letters, numbers, and the hyphen (-)
     • A duplicated name can't be used
   • 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 the [Next] button.

2. Set DB

The following describes how to set the information for the MySQL to be installed.

1. When the DB settings screen appears, enter the information needed to create a MySQL server.
   
   • USER_ID: enter the account ID of the MySQL server admin
     • The ID must be 4-16 characters long and can only include English letters, numbers, the underscore (_), and the hyphen (-)
     • It must start with an English letter
     • Predefined reserved words can't be used
   • HOST (IP): enter the IP address that will access the MySQL server
     • Enter "%" to allow access to all
     • When allowing access of only a specific IP <example> 123.123.123.123
     • When allowing access of only a specific IP range <example> 123.123.%
   • USER password: enter the account password of the MySQL server admin
     • The password must be 8-20 characters long and can only include English letters, numbers, and special characters, with at least 1 of each
     • The special characters ` & + \ " ' / or spaces can't be used
   • DB access port: Enter the TCP port number between 10000 and 20000 to which to allow access to the MySQL server to be created
     • Default: 3306
     • The port number can't be changed after it is specified
   • Default DB name: enter the name of the DB to be created by default
     • The ID must be 1-30 characters long and can only include English letters, numbers, the underscore (_), and the hyphen (-)
     • It must start with an English letter
   • DB config settings: check the optimized basic settings provided by NAVER
     • You can check and change the content from View details > DB config
   • Collect DB log: check the provision of log collection and viewer features for error logs and slow query logs
     • Cloud Log Analytics integration
2. Set whether to use the backup for the server to be created.
   • 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 execution time between automatic and user-defined
     • If you select this, additional fees will be incurred according to the storage capacity used
       • Automatic: backup is automatically started every day
       • User-defined: backup is started every day within 15 minutes from the time selected by the user
3. Click the [Next] button.
4. When the Request subscription to Cloud Log Analytics appears, check the content, and then click the [OK] button.
   • If you need to request a subscription to Cloud Log Analytics, click the [Request subscription to Cloud Log Analytics] button
   • For more information on Cloud Log Analytics, see Cloud Log Analytics guide

3. Final confirmation

1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
   
   • Click the [Previous] button to edit the settings
2. Click the [Create] button.
3. Check the status of the MySQL server that was created from the server list in the DB server page.
   • Creating: status in which the MySQL server is being created with the information entered by the user
   • Configuring: status in which the MySQL server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the MySQL server have been completed with the information entered by user, and access to MySQL from the application server is available

Restarting MySQL server

You can easily and conveniently restart MySQL servers. You can't access servers while they're being restarted. The following describes how to restart.

1. From NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. Click the MySQL server you want to restart, and then click the [Restart DB server] button.
4. When the Restart DB server pop-up window appears, check the name of the MySQL server to restart, and then click the [Yes] button.
5. Check the status of the MySQL server from the MySQL server list in the DB server page.
   • Stopping: status in which the MySQL server is being stopped
   • Restarting: status in which the MySQL server is being restarted

Deleting MySQL server

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

If you're using high availability, then both the master server and standby master server will be deleted. If you have slave servers, you need to 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.

The following describes how to delete MySQL servers.

1. From NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. Click the MySQL server you want to delete and click the [Delete DB server] button.
4. When the Delete DB server pop-up window appears, enter the name of the MySQL server to delete, and then click the [Yes] button.
5. Check the status of the MySQL server from the MySQL server list in 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 users to intuitively check servers in operation and data status, and efficiently manage them.

The following describes how to go to the monitoring page of the MySQL server that has been created and is in operation.

1. From NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. Click the MySQL server you want to monitor, and then click the [Monitoring] button.
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.

The following describes how to manage a MySQL server that has been created and is in operation.

1. From NAVER Cloud Platform console, click Services > Database > Cloud DB for MySQL, in order.
2. Click the DB server menu.
3. Click the MySQL server you want to manage, and then click the [Manage DB] button.
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

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, click [Edit] on the Swap memory settings screen, change the settings, click [Change], and then click [Save].

Consider the following items when changing 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 change task for 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, DB failover is automatically performed to minimize impact on the service. (After the task is completed, roles of the master and the slave master 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.

Initializing DB service

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

The following describes how to reset a DB service.

1. Delete all tables, and retain one DB in lowercase letters.
2. In the Initialize DB service page, click the [Edit] button, change the settings, and then click the [Change] button.
   
3. Click the [Save] button.
4. From the confirmation pop-up window, click the [Yes] button.
   • The reset is processed. The access to the MySQL server becomes unavailable while the reset is being processed.

Setting 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 database 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 [Activate] on the password plugin setting screen, specify the desired config value.
3. Click the [Save] button.
4. On the pop-up window, check the DB service name and click [Yes].
5. If there is a config value to be edited, edit the config value and click [Save].
6. To delete a plugin, change its status to [Disabled] and click [Save].

• Password plugin config variable list

Setting audit plugin

• This is a plugin that sets logs for DDL and connections occurring in the DB.
• Stores account information to connect to the DB server.
• Audit plugin supports only MySQL 8.0 version, and a DB restart is required after setting the plugin.

1. Click Manage DB > View DB service details.
2. On the Audit plugin settings screen, change the status to Enabled and set the config value as desired.
3. Click the [Save] button.
4. On the pop-up window, check the DB service name and details and then click [Yes].
5. If there is a config value to be edited, edit the config value and click [Save].
6. To delete a plugin, change its status 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.
  • Users 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, click the [Edit] to change settings, then click the [Change] button, and then the [Yes] button on the pop-up window, in order.

Consider the following items when change the DB server system settings.

• DB server setting is only supported in MySQL version 8.0.
• Server setting changes are executed on the entire server, one by one.
• In case of a high-availability server, master DB failover process proceeds automatically to minimize the service effect. (After completing the process, 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, DB server needs to be restarted.

Viewing MySQL server details

You can check the details of the server to see if the selected MySQL server is running properly. The details are as follows:

Kill process execution through user-provided stored procedure

You can execute a kill process in the form of a stored procedure with a user account with the DDL permissions from the master and slave servers. Only existing process IDs can be killed. You can't kill processes run by the system account. The USER IDs "agent," "radmin," "ha_admin," "repl_admin," and "system user" do not have the kill process permission.

Run the following command to kill a process using the user-provided stored procedure.

mysql> CALL sys.ncp_kill_session (session ID);
- A procedure that allows the user to use the kill connection function with super privileges

mysql> CALL sys.ncp_kill_query (session ID);
- A procedure that allows the user to use the kill query function with super privileges

Check replication status

You can check the replication status of the standby master and slave servers, take actions to skip queries with replication errors, or reinstall the DB. A replication delay may occur if there is a query that writes in the master server over a long period of time, or if too many write tasks occur. The detailed descriptions on the replication page are as follows:

Variables Name / Value
Displays the replication's variable entries and values.

[Skip Replication Error] button
Skips the query where a replication error occurred. However, since data inconsistency with the master server may occur during the skipping process, it is recommended to proceed with the following method to ensure that the data remains the same.

• In case of standby master server
  • Reinstall the standby master DB
• In case of slave server
  • Adding new slaves and deleting current slaves
  • 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
Reinstalls 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 log] button
Click to view the running binary log. If the replication is being performed properly, then the following message is displayed: "There is no binary log running." If the replication is delayed or stopped, then the currently running binary log is displayed.

Manage database

You can add DBs to the selected MySQL server or delete them. Up to 1000 DBs can be added, and the addition or deletion tasks can be performed for up to 10 DBs at a time.

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

Add DB using user-provided stored procedure

You can add DBs more conveniently from the master server by using the DB addition feature in the form of a stored procedure with a user account with the 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 the GRANT command. 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 [optional]','Collation [optional]');

--Examples
① Character set and collation are specified by the user
mysql> CALL sys.ncp_create_db('testdb','utf8','utf8_general_ci'); 

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

③ Character set: specified by the user; Collation: MySQL server's default settings
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 can be integrated to 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 for the slave servers as to the master server, and the fees are charged based on the hours used. The following describes how to add slave servers.

1. When the Add slave DB server pop-up window appears, check the master server and the slave server information.
   • Select a subnet to create the slave server in if you're using the multi-zone configuration.
     
2. Click the [Yes] button.
3. Check the status of the slave server that was created from the MySQL server list in the DB server page.
   • Creating: status in which the slave server is being created with the information entered by the user
   • Configuring: status in which the slave server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the slave server has been completed with the information entered by user, and the access to the slave server from the application server is available

Changing multi-zone configuration (VPC)

You can select a master server and create it in another zone. The following describes how to change.

1. When the Change multi zone configuration pop-up appears, view or enter the information necessary for editing.
   
2. Click the [Yes] button.
   • 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. Check the status of the MySQL server from the MySQL server list in the DB server page.
   • Configuring: status in which the MySQL server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, and access to MySQL from the application server is available

Change high availability settings

You can change the selected MySQL server into a standalone or high-availability configuration. The following describes how to change.

1. When the Change high availability settings pop-up window appears, check the basic server information.
   
2. If the existing high availability setting is Y, it may be set to standalone. If the existing high availability setting is N, it may be set to high availability.
   • 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 the [Yes] button.
4. Check the status of the MySQL server from the MySQL server list in the DB server page.
   • Configuring: status in which the MySQL server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, and access to MySQL from the application server is available

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

The following describes how to change the specifications.

1. When the Change DB server specifications pop-up window appears, check the current server specifications.
2. Click and select the server specifications you want to change.
   
3. Click the [Save] button.
4. Check the status of the MySQL server with the modified specifications from the MySQL server list in the DB server page.
   • Configuring: status in which the MySQL server is being configured after the information has been entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, 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. The following describes how to change.

1. When the Database config pop-up window appears, check or enter the required information for editing.
   

   • Config name: name of the settings variable
   • Config value: variable value
   Note

   For more information on setting config variables, see MySQL official documentation (English).

2. Click the [Add] button.

   • When editing the added settings variable: click the [Edit] button
   • When deleting the added settings variable (setting it to default): click the [Delete] button

3. Click the [Save] button.

4. Check the status of the MySQL server with the modified config from the MySQL server list in the DB server page.

   • Configuring: status in which the MySQL server is being configured after the information has been entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, and access to MySQL server from the application server is available

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 the [Yes] button from the pop-up window that appears.

Manage DB user

When creating 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 feature 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 feature are applied to the entire DB service. Up to 1000 user accounts can be added.

The following describes how to add or delete user accounts or change the password of the existing admin account.

1. When the Manage DB user pop-up window appears, perform the required tasks for the user account.
   

   • Add user account: enter the information for USER_ID, HOST (IP), DB permissions, and password, and then click the [Add DB user] button
     • 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 (refer to the official MySQL document (English))
   • Delete user account: click the [Delete] button in the same row as the user account to be deleted
   • Edit user account password: click the [Edit] button in the same row as the user account to be modified, and then click the [Save] button after editing

2. Click the [Save] button.

3. Check the status of the MySQL server with the user settings from the MySQL server list in the DB server page.

   • Configuring: status in which the MySQL server is being configured after the information has been entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, 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]

GRANT PROCESS, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, CREATE USER ON *.* TO `[user name]`@`[HOST IP]` WITH GRANT OPTION 
GRANT SHOW_ROUTINE,XA_RECOVER_ADMIN 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 [user 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_leap_second` 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_type` 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` TO `[user name]`@`[HOST IP]`   

[List of permissions for an account with CRUD permissions]

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

[List of permissions for an account with READ permissions]

GRANT PROCESS, SHOW DATABASES, REPLICATION CLIENT ON *.* TO `[user name]`@`[HOST IP]`               
GRANT SELECT ON `mysql`.* TO `[user name]`@`[HOST IP]`                                              
GRANT SELECT, EXECUTE ON `sys`.* TO `[user name]`@`[HOST IP]`                                        
GRANT SELECT, LOCK TABLES, EXECUTE, SHOW VIEW ON [user DB].* TO `[user name]`@`[HOST IP]`               
GRANT SELECT ON `performance_schema`.* TO `[user name]`@`[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:

Creating 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 logged in with a user account that has the 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

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

• The expiration period can be set in days (1-65535) only.
• 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 executed with a user account with DDL privileges.
• Expiration removal can be executed 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;

Execute the command below 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.

Execute the command below 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."

Importing DB account information

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

The following describes how to import DB account information.

1. Select the MySQL server from which the account information is to be fetched, and then click the Manage DB > View DB server details > Manage DB user, in order.
2. Click the [Import DB server] button.
3. On the pop-up 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. The following describes how to change.

1. When the Change DB server log settings pop-up window appears, change the settings by referring to the following.
   
   • Log: check 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 the [Save] button.
3. Check 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 after the information has been entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, and access to MySQL server from the application server is available

Master DB Failover

If the master server fails, then the user can directly use the failover feature to switch between the master and standby master servers. The switch takes approximately 2 minutes, and the server access is unavailable during the switch. The method for switching is as follows:

1. When the Master DB failover pop-up window appears, check the displayed information.
   
2. Click the [Yes] button.
3. Check the status of the MySQL for which you've set the DB failover from the MySQL server list in the DB server page.
   • Configuring: status in which the MySQL server is being configured after the information has been entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, and access to MySQL server from the application server is available

MySQL Engine Upgrade

• MySQL engine's minor version upgrade

You can upgrade the minor version of the MySQL engine. The version upgrade is applied to the entire DB service, and the upgrade is performed one 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 pop-up window that appears, and then click the [Yes] button.

• MySQL engine's major version upgrade

You can upgrade the major version of the MySQL engine. The version upgrade is applied to the entire DB service, and the upgrade is performed one 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 minor version upgrade and select the version you want to upgrade to from the pop-up window that appears, then click the [Upgrade inspection] button.

When the following error occurs after the upgrade inspection, upgrade is not possible.

• Upgrade inspection result: error example
  

Once the upgrade inspection is completed, click the [Yes] button on the precaution pop-up window.

You can see the upgrade is in progress through DB server status.

Change DB server name

You can change the selected MySQL name. All DB server names in the DB server list are changed, and sections that are automatically generated after the server name aren't changed. All servers stop operating while DB server names are changed, so access to the DB server is limited while names are being changed.
The following describes how to change.

1. When the Change DB server name pop-up window appears, check the applicable DB server and its current server name.
2. Enter the DB server name to change.
   • The name must be 3-20 characters long and can only include upper and lower case English letters, numbers, and the hyphen (-)
   • It must start with an English letter and end with an English letter or a number
   • A duplicated name can't be used
3. Click the [Yes] button.
4. Check 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 after the information has been entered by the user
   • Running: status in which the creation and configuration of the MySQL server has been completed with the information entered by user, and access to MySQL server from the application server is available

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.

Creating a load balancer (VPC)

How to create a load balancer in the VPC environment of the NAVER Cloud Platform console is as follows:

1. Click the Services > Networking > Load Balancer menu on the VPC environment of the NAVER Cloud Platform console one by one in order.
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 referenced Load Balancer user guide, and then click the [Next] button.
4. Add load balancer listeners, and click the [Next] button.
5. Select the target group, and click the [Next] button.
6. Check the settings, and then click [Create load balancer].

Creating a load balancer (Classic)

The following describes how to create a load balancer in the Classic environment of the NAVER Cloud Platform console.

1. Click the Services > Networking > Load Balancer menu on the Classic environment of the NAVER Cloud Platform console one by one in order.
2. Click the [Create Load Balancer] button.
3. Enter the information required for the creation of the load balancer by referring to the referenced Load Balancer user guide, and then click the [Next] button.
   • For network type, select Private IP.
     If you select the public IP network type, the DB server will not be visible when adding the server.
   • Make the following load balancer settings:
     • Protocol: TCP
     • Load balancer port: load balancer port number you want to use
     • Server port: port number of the DB server you want to access
     • You can check the proxy protocol if you want to confirm the client IP.
       If a DB user is created with the load balancer IP, then it can't be accessed if the proxy protocol is activated.
4. Add servers to apply to the load balancer, and then click the [Next] button.
5. Check 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. You can configure it as follows:

1. From NAVER Cloud Platform console, click Services > Compute > Server, in order.
2. Click the ACG menu.
3. Select the ACG name of the MySQL server, and click [ACG settings].
4. Please 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 the [Add] button.
6. Click the [Apply] button.

Check load balancer

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

For the Classic environment, check if the connection status of the applied server is displayed as Success. To view the information, follow these steps:

1. Click the Services > Networking > Load Balancer menu on the Classic environment of the NAVER Cloud Platform console one by one in order.
2. Select a load balancer to check.
3. Click the [Check load balancer status] button to check the status.
   • If the status is not displayed as Success, then check the ACG settings again.