DB Server
  • PDF

DB Server

  • PDF

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 for the MySQL Servers in operation, or manage admin (user) accounts.

DB server page

The basics of using MySQL Servers are as follows.

clouddbformysql-start_dbserverMain_vpc_en(3).png

Area Description
① Menu name Name of the menu currently being checked and the number of MySQL Servers in operation
② Basic features Create MySQL Servers, check details for Cloud DB for MySQL, download DB server list, refresh the DB server page
③ Post-creation features Restart, delete, monitor, and manage MySQL Servers in operation
④ Search Search the desired server by the service name from the MySQL Server list
⑤ MySQL Server list Check the list of MySQL Servers in operation and their information

Check MySQL Server list (VPC)

You can check the information of each server from the list of MySQL Servers that have been created and are in operation. The following describes how to view the information.

Note

You can see the list if you have one or more servers in operation. If you don't have any servers that have been created and are in operation, then the list is not displayed in the DB server page.

  1. From the NAVER Cloud Platform console's VPC environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
  2. Click the DB Server menu.
  3. If the list of created MySQL Servers appear, then check the summary information or click a MySQL Server to check the details.
    clouddbformysql-start_details_vpc_en.png
    • DB service name: Service name of MySQL, a group that classifies MySQL Servers by role. Generally refers to a server group that consists of one master server, one standby master server, and multiple slave servers. MySQL Servers with the same data are referred to as one service.
      • icon_database-database-5-2_namechange_vpc_ko.png: Changes the service name when clicked
    • DB Role: Role of the MySQL Server
      • Master: The master server when the high availability support is selected
      • Standby master: The standby server when the 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 its 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: Server type and available memory of MySQL Server
    • Monitoring: Directs to the Monitoring page
    • DB Status: Directs to the MySQL Server details page
    • DB access port: Port number being used by the MySQL Server
    • Multi Zone: Displays the multi zone use status with Y or N
    • Private domain: Information of private domain
    • Public domain: Information of public domain, which allows external access
      • Displayed only when it is set through the public domain management feature in 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
    • Apply data storage encryption: Displays the use status of encryption when saving to the data storage, with 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 has been completed with the information entered by user, and the access to MySQL from the application server is available
      • Deleting: Status in which the MySQL Server is being deleted with the information entered by the user
      • Stopping: Status in which the MySQL Server is being stopped with the information entered by the user
      • Restarting: Status in which the MySQL Server is being restarted with the information entered by the user
      • Restoring(standby master): Status in which the standby master server is being replaced due to a failure, with no effect to the operation of the master server
    • Creation date: Date that MySQL Server was created, the initial point when the server status became Creating
    • Running date: Date that MySQL Server started running, the initial point when the server status became Running
    • ACG: Name and ID of the ACG being used in the MySQL Server
      • clouddbforredis_ico-01_vpc_ko.png: Directs to the Server > ACG page when clicked
      • [View rules] button: Displays applied detailed rules when clicked
    • Database Config: Config applied to the MySQL Server
      • icon_database-database-5-2_namechange_vpc_ko.png: Directs to the Database config page when clicked
    • DB engine version: Version information of the MySQL installed on server
    • DB License: License information of the MySQL installed on 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: Displays whether the high availability feature is being used with Y or N
    • Backup retention period (backup time): When using the backup feature, displays the information of the configured backup file retention period and backup execution cycle
      • icon_database-database-5-2_namechange_vpc_ko.png: Sets backup feature use status, file retention period, and execution cycle when clicked
Caution

When you stop using the backup feature that was in use, all existing backup files are deleted.

Check MySQL Server list (Classic)

You can check the information of each server from the list of MySQL Servers that have been created and are in operation. The following describes how to view the information.

Note

You can see the list if you have one or more servers in operation. If you don't have any servers that have been created and are in operation, then the list is not displayed in the DB server page.

  1. From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
  2. Click the DB Server menu.
  3. If the list of created MySQL Servers appear, then check the summary information or click a MySQL Server to check the details.
    clouddbformysql-start_details_en.png
    • DB service name: Service name of MySQL, a group that classifies MySQL Servers by role. Generally refers to a server group that consists of one master server, one standby master server, and multiple slave servers. MySQL Servers with the same data are referred to as one service.
      • icon_database-database-5-2_namechange_vpc_ko.png: Changes the service name when clicked
    • DB Role: Role of the MySQL Server
      • Master: The master server when the high availability support is selected
      • Standby master: The standby server when the 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 back up. 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: Server type and available memory of MySQL Server
    • Monitoring: Directs to the Monitoring page
    • DB Status: Directs to the MySQL Server details page
    • DB access port: Port number being used by the MySQL Server
    • Zone: Displays the zone that the MySQL Server belongs to
    • Private domain: Information of private domain
    • Public domain: Information of public domain, which allows external access
      • Displayed only when it is set through the public domain management feature in 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 has been completed with the information entered by user, and the access to MySQL from the application server is available
      • Deleting: Status in which the MySQL Server is being deleted with the information entered by the user
      • Stopped: Status in which the MySQL Server has stopped with the information entered by the user
      • Restarting: Status in which the MySQL Server is being restarted with the information entered by the user
      • Restoring(standby master): Status in which the standby master server is being replaced due to a failure, with no effect to the operation of the master server
    • Creation date: Date that MySQL Server was created, the initial point when the server status became Creating
    • Running date: Date that MySQL Server started running, the initial point when the server status became Running
    • ACG: Name and ID of the ACG being used in the MySQL Server
      • clouddbforredis_ico-01_vpc_ko.png: Directs to the Server > ACG page when clicked
      • [View rules] button: Displays applied detailed rules when clicked
    • Database Config: Config applied to the MySQL Server
      • icon_database-database-5-2_namechange_vpc_ko.png: Directs to the Database config page when clicked
    • DB engine version: Version information of the MySQL installed on server
    • DB License: License information of the MySQL installed on server
    • High availability: Displays whether the high availability feature is being used with Y or N
    • Backup retention period (backup time): When using the backup feature, displays the information of the configured backup file retention period and backup execution cycle
      • icon_database-database-5-2_namechange_vpc_ko.png: Sets backup feature use status, file retention period, and execution cycle when clicked
Caution

When you stop using the backup feature that was in use, all existing backup files are deleted.

Create MySQL Server (VPC)

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

  1. From the NAVER Cloud Platform console's VPC environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
  2. Click the DB Server menu.
  3. Click the [Create DB Server] button.
    database-database-5-2_create_vpc_en.png
  4. When the subscription request screen appears, proceed with the following steps in order.
Note

Click the [Request subscription button] from NAVER Cloud Platform portal's Service > Database > Cloud DB for MySQL to directly go to the page in Step 3.

1. Set server

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

  1. When the Set server page appears, check the type of DBMS you want to install to the server from DBMS type.
    database-database-5-2_create2_vpc_en.png
  2. Check the version and license information of the MySQL to be installed.
    • DB engine version: Version information of MySQL 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 selected, the redundancy is configured with two units of MySQL Servers: Master server and standby master server.
      • When selected, set backup file retention period and backup time (default: one day, automatic).
      • When selected, disabling the storage of backup files is not possible.
      • When selected, additional charges will be incurred.
      • The standby master server is not accessible by the user.
    • Multi Zone: To secure advanced high availability, click to select whether to create the master server and standby master server separately in two different zones (one in each zone).
  4. Set items related to VPC and MySQL Server, which are 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 if you want to see the latest version of the created VPC list.
      • [Create VPC]: Click if you don't have any VPCs that have been created and need to create one.
    • Subnet: Select a private subnet to be used when accessing VPC.
      Public domain can only be used for DB servers created on the public subnet.
      Subnet transfer is not possible after DB server creation.
      • [Refresh] button: Click if you want to see the latest version of the created subnet list.
      • [Create subnet] button: Click if you don't have any subnets that have been created and need to create one.
    • 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 Support high availability is selected.
      • The settings can't be changed after the creation of 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 MySQL Server.
    • Data storage capacity: Check the storage capacity for saving DB data.
      • 10 GB is assigned upon initial creation of MySQL Server
      • The capacity is automatically added in 10 GB units and charged according to data increase.
      • Up to 6,000 GB is supported.
  5. Check the applicable pricing plan information when using Cloud DB for MySQL.
    • Pricing plan: 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 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.
      • Enter between 3 to 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 three-digit number is assigned automatically after the name entered by the user. mysql-001-xxxx
      • A duplicated name can't be used.
    • DB service name: Enter the group name that classifies the MySQL Server to be created by its role. mysql-service
      • Enter between 3 to 30 characters using Korean letters, English letters, numbers, and hyphens (-).
      • A duplicated name can't be used.
    • Private sub domain: Enter the sub domain to add to the private domain.
      The same sub domain policy will be added when adding a slave or recovery.
      • Enter between 3 to 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.
    • Set ACG: ACG (Access Control Group) is created automatically.
      • The detailed settings for the ACG is 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 Set DB page appears, set items needed for the creation of the MySQL Server.
    database-database-5-2_create3_vpc_en.png
    • USER_ID: Enter account ID of the MySQL Server admin.
      • Enter between 4 to 16 characters using English letters, numbers, "_" and "-".
      • 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 123.123.123.123/32
      • When allowing access of only a specific IP range 123.123.123.0/24
    • USER password: Enter account password of the MySQL Server admin.
      • Enter between 8 to 20 characters containing at least one character each from English letter, number, and special character.
      • The special characters ` & + \ " ' / or spaces can't be used.
    • DB access port: Enter the TCP port number between 10000 - 20000 for allowing 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.
      • Enter between 1 to 30 characters using English letters, numbers, "_" and "-".
      • 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.
      • Link Cloud Log Analytics
  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 the backup.
      • Backup file retention period: Click and select the period to store the backup file to a separate backup storage.
        • For point-in-time recovery, the backup file is stored for the maximum of set retention period + 24 hours.
        • Only back up for tables created with the InnoDB engine is supported.
      • Backup time: Select the backup execution time between automatic and user defined.
      • When selected, additional charges 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 Cloud Log Analytics service subscription appears, check the content and click the [OK] button.
    • If you need to request subscription for Cloud Log Analytics, then click the [Request Cloud Log Analytics subscription] button.
    • Please refer to the Cloud Log Analytics Guide for more information about Cloud Log Analytics.

3. Final confirmation

  1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
    database-database-5-2_create4_vpc_en.png
    • 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 has been completed with the information entered by user, and the access to MySQL from the application server is available
Note

To see the latest status from Step 3, click the [Refresh] button.

Caution

It may take several minutes or longer until it enters Running status, available for actual use, after going through Creating and Configuring statuses.

Create MySQL Server (Classic)

The following describes how to create a MySQL Server in the Classic environment.

  1. From the NAVER Cloud Platform console's Classic environment, click the Services > Database > Cloud DB for MySQL menus, in that order.
  2. Click the DB Server menu.
  3. Click the [Create DB Server] button.
    database-database-5-2_create_en.png
  4. When the subscription request screen appears, proceed with the following steps in order.
Note

Click the [Request subscription] button from NAVER Cloud Platform portal's Service > Database > Cloud DB for MySQL to directly go to the page in Step 3.

1. Set server

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

  1. When the Set server page appears, check the type of DBMS you want to install to the server from DBMS type.
    database-database-5-2_create1_en.png
  2. Check the version and license information of the MySQL to be installed.
    • DB engine version: Version information of MySQL 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 items related to zone and MySQL Server, which are needed for the creation of the MySQL Server.
    • Zone: Click and select the zone to create the MySQL Server in.
    • Secure Zone: Select whether to create the server in the Secure Zone, which provides enhanced security.
      • Link with NAVER Cloud's Secure Zone.
      • When selected, the server is created in the Secure Zone where the firewall policy is applied.
      • The Secure Zone is available only when the 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 MySQL Server.
    • Data storage capacity: Check the storage capacity for saving DB data.
      • 10 GB is assigned upon initial creation of MySQL Server
      • The capacity is automatically added in 10 GB units and charged according to data increase.
      • Up to 6,000 GB is supported.
  4. Set Support high availability for the availability of the server to be created.
    • When selected, the redundancy is configured with two units of MySQL Servers: Master server and standby master server.
    • Performs a failover for automatic recovery in case of failure.
    • When selected, set backup file retention period and backup time (default: one day, automatic).
    • When selected, disabling the storage of backup files is not possible.
    • When selected, additional charges 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: 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 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.
      • Enter between 3 to 25 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 three-digit number is assigned automatically after the name entered by the user. mysql-001-xxxx
      • A duplicated name can't be used.
    • DB service name: Enter the group name that classifies the MySQL Server to be created by its role. mysql-service
      • Enter between 3 to 30 characters using Korean letters, English letters, numbers, and hyphens (-).
      • A duplicated name can't be used.
    • Set ACG: ACG (Access Control Group) is created automatically.
      • The detailed settings for the ACG is 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 Set DB page appears, set items needed for the creation of the MySQL Server.
    database-database-5-2_create2_en.png
    • USER_ID: Enter account ID of the MySQL Server admin.
      • Enter between 4 to 16 characters using English letters, numbers, "_" and "-".
      • 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 123.123.123.123/32
      • When allowing access of only a specific IP range 123.123.123.0/24
    • USER password: Enter account password of the MySQL Server admin.
      • Enter between 8 to 20 characters containing at least one character each from English letter, number, and special character.
      • The special characters ` & + \ " ' / or spaces can't be used.
    • DB access port: Enter the TCP port number between 10000 - 20000 for allowing 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.
      • Enter between 1 to 30 characters using English letters, numbers, "_" and "-".
      • 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.
      • Link Cloud Log Analytics
  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 the backup.
      • Backup file retention period: Click and select the period to store the backup file to a separate backup storage.
        • For point-in-time recovery, the backup file is stored for the maximum of set retention period + 24 hours.
        • Only back up for tables created with the InnoDB engine is supported.
      • Backup time: Select the backup execution time between automatic and user defined.
      • When selected, additional charges 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 Cloud Log Analytics service subscription appears, check the content and click the [OK] button.
    • If you need to request subscription for Cloud Log Analytics, then click the [Request Cloud Log Analytics subscription] button.
    • Please refer to the Cloud Log Analytics Guide for more information about Cloud Log Analytics.

3. Final confirmation

  1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
    database-database-5-2_create3_en.png
    • 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 has been completed with the information entered by user, and the access to MySQL from the application server is available
Note

To see the latest status from Step 3, click the [Refresh] button.

Caution

It may take several minutes or longer until it enters Running status, available for actual use, after going through Creating and Configuring statuses.

Restart 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 a MySQL Server.

  1. From the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MySQL menus, in that 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
Caution

It may take several minutes until it enters the Running status, available for actual use, after going through Stopping and Restarting statuses.

Delete MySQL Server

You can delete the 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, then you need to first delete all slave servers of 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 a MySQL Server.

  1. From the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MySQL menus, in that order.
  2. Click the DB Server menu.
  3. Click the MySQL Server you want to delete, and then 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
Caution
  • The actual deletion from the list after going through the Deleting status may take several minutes.

MySQL Server monitoring

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.

Note

For detailed usage methods for Monitoring, please refer to Monitoring.

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

  1. From the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MySQL menus, in that 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.
    database-database-5-2_monitoring_vpc_en(1).png

Manage MySQL Server

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

Note

By default, managing MySQL Server is available when the server status is Running.

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

  1. From the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MySQL menus, in that 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 management item you need.
    database-database-5-2_tasks_vpc_en(1).png

View DB service details

You can set the use status of swap memory for the MySQL Server in the selected DB service, or reset the DB service.

Set swap memory

To set the use status of swap memory for the MySQL Server in the selected DB service, click the [Modify] button in the swap memory settings page, change the settings, and then click the [Change] and [Save] buttons, in that order.

database-database-5-2_service1_vpc_en.png

Consider the following items when change the swap memory settings.

  • When you change the swap memory settings, all MySQL Servers in that DB service are restarted.
  • The swap memory settings change task is carried out sequentially server by server, and it takes about 1 minute for each server.
  • In case of a high availability server, it is temporarily switched to the standby master server while the settings for the master server are being 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.

Reset DB service

Proceed with the DB service reset required when changing the lower_case_table_names DB config settings in the MySQL 8.0 version.

The following describes how to reset a DB service.

Caution

When you change the lower_case_table_names DB config settings after the reset, the data recovery becomes unavailable for a preceding point in time. Make sure to review carefully before resetting and changing.

Note

For MySQL 5.7 version, you can change the lower_case_table_names DB config settings in the Manage DB config menu.

  1. Delete all tables, and retain one DB in lowercase letters.
  2. In the Reset DB service page, click the [Modify] button, change the settings, and then click the [Change] button.
    database-database-5-2_service2_vpc_en.png
  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.

View MySQL Server details

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

View details tab Description Item
Process list Check the sessions currently connected to the selected MySQL Server - Session ID: Unique session number
- USER: User name of the connected session
- HOST: HOST IP of the connected session
- DB: DB name of the connected session
- Command: Command executed by the connected session
- Time: Execution time of the command (seconds)
- State: Status of the connected session
- Kill session: Force end the session
- Kill multiple session: Force end all selected sessions
Replication
(Standby Master, Slave Server)
Check the items and values of variables applied to the replication of the selected MySQL Server Refer to Check replication status
Variables Check the items and values of the variables applied to the selected MySQL Server - Variables name: Name of the applied variable
- Value: Variable value
Status Check the items and values of the status variables for the selected MySQL Server - Status name: Status variable item
- Status value: Status variable value
Manage databases Add DBs to the selected MySQL Server or delete them Refer to Manage databases
Manage DB config Change the settings for the selected MySQL Server Refer to Manage DB config
Manage DB user Add users for the selected MySQL Server or delete them Refer to Manage DB user
Manage backup settings Set the backup file retention period and backup time for the selected MySQL Server - Backup file storage period: Minimum of 1 day, maximum of 30 days
- Backup time: Backup is performed within 15 minutes from the selected time
DB Server Logs Check log file information of the selected MySQL Server - Log name: Server log file name
- File size (byte): Server log file size (byte)
- Last modified: Date when the server log file was last modified
- Send to Object Storage: Saves the selected log file to Object Storage (for a server created in the Secure Zone, add the Object Storage policy by referring to Secure Zone Firewall)
- Delete log: Delete selected log file (log files being used by the server can't be deleted)
Note
  • When sending to Object Storage, unlocking the bucket and setting appropriate access control and ACL are required.
  • Sending to Object Storage may take several minutes to be completed.
Caution

Additional fees apply when you request subscription to Object Storage. For the introduction on Object Storage and details about its pricing plans, refer to the Service > Storage > Object Storage menu in the NAVER Cloud Platform portal.

Kill process using 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. User names "agent," "radmin," "ha_admin," "repl_admin," and "system user" can't be used.

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

mysql> CALL sys.ncp_kill_session(session ID);
- Procedure where the KILL Connection feature is enabled to be executed by a user with the super permission

mysql> CALL sys.ncp_kill_query(session ID);
- Procedure where the KILL Query feature is enabled to be executed by a user with the super permission

Check replication status

You can check the replication status for the Standby Master and Slave servers, take action to skip the query where the replication error occurred, or reinstall the DB. A replication delay may occur if there is a query that writes in the master server for a long time, or if too many write tasks occur. The detailed descriptions on the replication page are as follows.

Note
  • This is the same as the result of the show slave status; command used in MySQL.
  • In the Event menu, you can set notifications for replication delays.
  • For Standby Master server, click the DB Status ![clouddbforredis_ico-01_vpc_en.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/clouddbforredis_ico-01_vpc_en. png) icon to go to the page.

database-database-5-2_replication_vpc_en.png

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

[Skip Replication Error] button
Skips the query where the replication error occurred. However, since a data mismatch with the master server may occur in the process of skipping, so it is recommended to proceed as follows in order to keep the data the same.

  • In case of Standby Master server
    • Reinstall the corresponding Standby Master DB
  • In case of Slave server
    • Add new slave and delete current slave
    • Reinstall the corresponding Slave DB

[Standby Master Reinstsallation] button
Reinstall Standby Master DB. DB reinstallation reconfigures the Standby Master DB after backing up the data from the Master DB. Console operation is not possible until complete, and it may take several tens of minutes to several hours depending on the data size.

[Slave DB Reinstallation] 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 logs] button
Checks the running binary logs. 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 databases

You can add DBs to the selected MySQL Server or delete them. Up to 1,000 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 row of the created DB to delete the DB.

database-database-5-2_db_vpc_en.png

Cloud DB for MySQL management account

The management account information for Cloud DB for MySQL used in user virtual machines is as follows.

Account name Account description
radmin Account that applies details requested by users in console to the actual database
ha_admin Database account used in case of auto failover when the master DB is failed
repl_admin Replication account to sync MySQL slave server
agent Account that collects database monitoring indicators
Caution
  • A user ID of an account that is the same as that of the management account can't be used.
  • If the management account is modified and deleted, then use of Cloud DB for MySQL features is limited.

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 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]');

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

② Both 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: The MySQL server's default settings
mysql> CALL sys.ncp_create_db('testdb','utf8',''); 

Add slave server

You can add slave servers to the MySQL Server using the high availability settings. Up to 10 slave servers can be added per master server, and added slave servers can be linked to the NAVER Cloud Platform's Load Balancer to be configured for read load balancing.

Note
  • You can't add slave servers to the standalone server.
  • For more information on read load balancing, refer to Set read load balancing.

The settings of the master server are applied identically 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 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 information for the master server and the slave server.
    • Select a subnet to create the slave server in if you're using the multi-zone configuration.
      database-database-5-2_addSlave_vpc_en.png
  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 slave server from the application server is available

Change multi-zone configuration (VPC)

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

  1. When the Change multi-zone configuration pop-up window appears, check or enter the required information for editing.
    database-database-5-2_multizone_vpc_en
  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 the access to MySQL Server from the application server is available

Change high availability settings

You can change the selected MySQL Server to have standalone or high availability configuration. The following describes how to change them.

  1. When the Change high availability settings pop-up window appears, check the basic server information.
    database-database-5-2_hachange_vpc_en.png
  2. When the existing high availability setting is Y, it can be set to Standalone, and when the existing high availability setting is N, it can be set to high availability.
    • When changing to a high availability configuration, click to select whether to use 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 the access to MySQL Server from the application server is available

Change MySQL Server specifications

You can change the server specifications for the MySQL Server you created. When changing the server specifications, the specifications for the master, standby master, slave, and recovery servers are also all changed. Additional charges will be incurred when upgrading specifications.

Caution

The servers will restart when upgrading server specifications. Since the access is unavailable during the restart, we recommend checking the data after the restart is completed.

The following describes how to change the specifications.

Note
  • The specifications change can only be done within the same type of MySQL Servers.
  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 to.
    database-database-5-2_specChange_vpc_en.png
  3. Click the [Save] button.
  4. Check the status of the MySQL Server for which you changed specifications from the MySQL Server list in the DB server page.
    • Configuring: Status in which the MySQL Server is being configured with the information entered by the user
    • Running: Status in which the configuration of the MySQL Server has been completed with the information entered by user, and the access to the MySQL Server from the application server is available

Manage DB config

You can change various settings for the MySQL Server you created. 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 change. The following describes how to change them.

Note

The same task can be performed from the View DB Server details > Manage DB config menu.

  1. When the Database config pop-up window appears, check or enter the required information for editing.
    database-database-5-2_DBconfig_vpc_en
    • Config name: Name of the settings variable
    • Config value: Variable value
    Note

    For detailed descriptions on setting config variables, refer to the MySQL official document (English).

  2. Click the [Add] button.
    • When modifying added settings variable: Click the [Modify] button
    • When deleting added settings variable (settings it to default): Click the [Delete] button
  3. Click the [Save] button.
  4. Check the status of the MySQL Server for which you changed config from the MySQL Server list in the DB server page.
    • Configuring: Status in which the MySQL Server is being configured with the information entered by the user
    • Running: Status in which the configuration of the MySQL Server has been completed with the information entered by user, and the access to the MySQL Server from the application server is available
Caution

If the set config values are not appropriate, then the MySQL Server may not operate properly. Make sure to fully understand the action of the config variable before applying the settings. If a problem occurs in the server operation due to incorrect settings, then please contact Support.

Manage public domain

You can request a public domain to allow access to MySQL Server from outside of NAVER Cloud, or remove the 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.

database-database-5-2_publicDomain_vpc_en.png

Manage DB user

When creating the 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 the 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 1,000 user accounts can be added.

Note
  • You can only use this feature in master servers and standalone servers.
  • The same task can be performed from the View DB Server details > Manage DB user menu.

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.
    database-database-5-2_user_vpc_en.png
    • 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 system DB.
      • The CRUD permission includes the READ permission, and the DDL permission includes the READ and CRUD permissions.
      • Search procedure can be performed by any account regardless of permissions (refer to the MySQL official document (English)).
    • Delete user account: Click the [Delete] button in the row of the user account to be deleted.
    • Modify user account password: Click the [Modify] button in the row of the user account to be modified, and then click the [Save] button after modifying.
  2. Click the [Save] button.
  3. Check the status of the MySQL Server for which you've set users from the MySQL Server list in the DB server page.
    • Configuring: Status in which the MySQL Server is being configured with the information entered by the user
    • Running: Status in which the configuration of the MySQL Server has been completed with the information entered by user, and the access to the MySQL Server from the application server is available
Caution
  • When deleting a user account, please note the applications using the account being deleted can't be accessed.
  • If creating a DB user using a character not permitted in the console, then it can't be changed or deleted in the console. Please directly access the DB server to change.

Create account with permissions for specific table

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

To create a new account having accessed with a user account that has a 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;

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

For detailed descriptions on directly creating accounts in MySQL Server, refer to the MySQL official document (English).

Import 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 to import the account information from, and then click the Manage DB > View DB server details > Manage DB user menus, in that order.
  2. Click the [Import DB account] button.
  3. From the confirmation pop-up window, click the [Import] button.

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

  1. When the Change DB server log settings pop-up window appears, change the settings by referring to the following content.
    database-database-5-2_serverlog_vpc_en.png
    • 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 Server for which you've set server logs from the server list in the DB server page.
    • Configuring: Status in which the MySQL Server is being configured with the information entered by the user
    • Running: Status in which the configuration of the MySQL Server has been completed with the information entered by user, and the access to the MySQL Server from the application server is available

Master DB Failover

If the master server fails, then you can directly use the failover feature to switch to the standby master server. 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.
    database-database-5-2_failover_vpc_en.png
  2. Click the [Yes] button.
  3. Check the status of the MySQL for which you've set DB failover from the MySQL Server list in the DB server page.
    • Configuring: Status in which the MySQL Server is being configured with the information entered by the user
    • Running: Status in which the configuration of the MySQL Server has been completed with the information entered by user, and the access to the MySQL Server from the application server is available

MySQL Engine 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 maintain the service access block to the 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.

database-database-5-2_upgrade_vpc_en.png

Change DB server name

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

Caution

If the server name is changed, then the DB server log before the change can't be viewed. (Monitoring > DB logs)

database-database-5-2_changeServerName_vpc_en

  1. When the DB server name change pop-up window appears, check the target of changing the DB server and 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.
    • A duplicated name can't be used.
  3. Click the [Yes] button.
  4. Check the status of the MySQL Server for which you've set the DB server name from the server list in the DB server page.
    • Configuring: status in which the MySQL Server is being configured with the information entered by the user
    • Running: status in which the configuration of the MySQL Server has been completed with the information entered by user, and access to the MySQL Server from the application server is available

Set read load balancing

To balance the read load for the MySQL Server, you can request subscription for the NAVER Cloud Platform's Load Balancer and link it to slave servers. Create a load balancer, and then add settings to the MySQL Server's ACG to allow proper access of the created load balancer.

Caution
  • Additional fees apply when you request subscription to Load Balancer. For the introduction on Load Balancer and details about its pricing plans, refer to the Service > Storage > Load Balancer menu in the NAVER Cloud Platform portal.
  • Only the slave servers can be connected to the load balancer, and only the slave servers that belong to the same DB service can be bound to a single load balancer.
Note

In this section, we will briefly introduce how to set up Load Balancer. Please refer to Load Balancer Guide for more information about setting up Load Balancer.

Create load balancer (VPC)

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

Caution
  • Cloud DB for MySQL's load balancing is processed through network load balancers and network proxy load balancers.
  • Load balancing of Cloud DB for MySQL through application load balancers is unavailable.
Note

In this section, we will briefly introduce how to create a load balancer. For details about full creation methods, please refer to the following guides.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that order.
  2. Click the [Create load balancer] button, and then 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 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 information, and then click the [Create load balancer] button.
Note

You can group slave servers created in multi-zones with one load balancer and disperse the reading load for a MySQL server. You can use one domain for the load balancer to access each slave server. The following shows how to do it.

  • Group the slave servers created in zone 1 and zone 2 when you create a target group in Step 5.

Create load balancer (Classic)

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

Note

In this section, we will briefly introduce how to create a load balancer. For more details about full creation methods, refer to the Classic Load Balancer creation guide.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that 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 guide, and then click the [Next] button.
    • Select Private IP for the network type.
      If you select the public IP network type, then the DB server won't be visible when adding servers.
    • Configure the load balancer settings as follows.
      • 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 information, and then click the [Create load balancer] button.

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.

Note

In this section, we will briefly introduce how to set up ACG. Please refer to ACG Guide for more information about setting up ACG.

  1. From the NAVER Cloud Platform console, click the Services > Compute > Server menus, in that order.
  2. Click the ACG menu.
  3. Select the ACG name of the MySQL server, and then click the [Set ACG] button.
  4. Add the following ACG rule for accessing the load balancer.
    • 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 Classic environment, check if the connection status of the applied server is displayed as Succeeded. The following describes how to check the information.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that 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 Succeeded, then check the ACG settings again.
      database-database-5-2_checklbstatus_en

Was this article helpful?

What's Next