Login
      Contents x
      Cloud DB for MySQL overview
        • Print
        • PDF
        Contents

        Cloud DB for MySQL overview

          • Print
          • PDF
          Article Summary

          The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.

          Available in Classic and VPC

          Cloud DB for MySQL is a fully managed cloud database service using MySQL, the world's most widely used relational database. The service allows you to easily build a MySQL database, ensures its stable management through NAVER's optimization features, and recovers the database automatically in case of failures.

          Cloud DB for MySQL features

          Cloud DB for MySQL provides the following features:

          • Quick and easy installation: you can use the service right away after a few simple inputs and clicks.
          • Optimization settings validated by NAVER services: MySQL settings that have long been validated by different NAVER services are provided by default for fast and stable operation without the need for additional database configuration.
          • Automatic data backup and creation of MySQL server using the backed up data: data is automatically backed up once a day at the time designated by the customer, and data restoration is available by creating a new MySQL server with the backed up data.
          • Performance monitoring and notifications: various performance monitoring figures and graphs related to MySQL and operating system are provided.
          • Read load balancing: replicates up to 10 slave server DBs and distributes the database read load by integrating them with a load balancer.
          • Automatic failover support: if you use the high availability (HA) settings, then the server redundancy is configured with the master server and standby master server. If the master server fails, then it automatically fails over to the standby master server, enabling more stable operation of the server.

          About the Cloud DB for MySQL user guide

          The Cloud DB for MySQL user guide is composed of the following topics to help you use Cloud DB for MySQL effectively. The content that users can view in each topic is as follows:

          NAVER Cloud Platform provides a variety of related resources as well as the user guide to help customers better understand Cloud DB for MySQL. If you are a developer or marketer in need of detailed information while you are considering adopting Cloud DB for MySQL for your company or establishing data related policies, then please make good use of the resources below.

          Check FAQs first.

          You can get your questions answered quickly by referring to the answers in the FAQs before reading the user guide. If you haven't found the answer to your question in the following FAQs, then search the user guide for what you would like to know.

          Q. What is the difference between VPC and Classic environments?
          A. The Classic environment is a general cloud environment, while the VPC environment is a cloud environment that provides logically separated virtual private clouds (VPC).
          Through VPCs, you can implement an environment similar to the existing data center network your company was using. Up to 3 VPCs can be created for each account. Each VPC provides a network address space with a maximum netmask of 0.0.255.255/16 (65,536 IPs).

          Q. How do I access the MySQL servers I created?
          A. You can access by using a private domain in the NAVER Cloud Platform server, or access from outside of the cloud by using an SSL VPN or public domain.
          For more information on access methods using a private domain from a NAVER Cloud Platform server, see Getting started with Cloud DB for MySQL. For more information on access methods from outside of the cloud, see Access using SSL VPN and Access using public domain respectively.

          Q. How can I manage databases by directly accessing an MySQL server rather than accessing through the application server?
          A. You can directly access your MySQL server through MySQL Workbench or phpMyAdmin.
          For more information on how to use each utility, see Accessing DB Server from outside cloud.

          Q. Can I start or stop an individual MySQL server like a regular server?
          A. We don't support start or stop of an individual MySQL server. Only restart and delete options are available.
          You cannot stop an individual MySQL server to temporarily avoid charges. When you restart, the virtual server on which the MySQL server is installed and the server itself restarts simultaneously.

          Q. When using the high availability settings, what is the difference between a master server and a standby master server?
          A. While an MySQL server is being operated normally, the standby master server does not play any roles and replicates the master server's data as it is. If the master server fails and can no longer be operated normally, then it automatically performs a failover where the standby master server takes over the role of the master server.

          Q. If I restart the master server, does it automatically perform a failover?
          A. A failover automatically starts only when there is a failure. Your restart command does not start the process.

          Q. Can users directly perform a failover?
          A. Users can directly perform failovers. You can reproduce a failover situation caused by a master server failure to check any effects on applications prior to opening the service.
          You may not be able to access the server during the failover. For more information on usage methods, see Master DB failover of DB Server.

          Q. After restarting the MySQL server, the storage capacity decreased. What should I do?
          A. When transactions are used extensively, the size of the temporary tablespace storage may increase, causing the decrease in storage capacity of the MySQL server.
          This is normal, and upon restarting the MySQL Server, the temporary storage space will be returned.

          Q. When monitoring the server through the Monitoring menu, the memory usage seems to continue increasing. Is there an issue with the server?
          A. For performance optimization of the MySQL server, memory usage may increase beyond the innodb_buffer_pool_size setting value. However, it is normal for memory usage to increase up to approximately 90% of the actual memory size.

          Q. Regarding the performance or operating system of MySQL servers, is there a feature that enables the configuration of thresholds and notifies the admin of the events that occurred when they are exceeded?
          A. By default, Cloud DB for MySQL provides monitoring service and event collection service for the performance and operating system of the server.
          In addition, you can directly set thresholds and notifications via email or SMS for occurring events by integrating with Cloud Insight. For more information on usage methods, see Monitoring and Event.

          Q. Replication stopped with a replication error. What do I need to do?
          A. Depending on the situation, you can either skip the replication error temporarily using the Skip replication error feature or reinstall the DB where the replication error occurred.
          However, using the Skip replication error feature may not guarantee the perfect alignment with the master server's data, potentially leading to recurring errors and further replication stops. By reinstalling the DB, you can rebuild the database from the last backup and ensure data alignment with the master server. Rebuilding takes time, but once the process is complete, the server will have the same data as the master server.
          For more information on Skip replication error and DB re-installation, see Check replication status.

          Q. Why does replication delay occur?
          A. Replication delay is not a failure of Cloud DB for MySQL but rather a result caused by the replication specifications of MySQL and the behavior of user applications. Typically, replication delays occur due to high write loads on the master DB, a large amount of write queries, many change operations committed in a single transaction, performing queries that modify many rows in tables without a primary key, a large volume of queries requiring prolonged execution, and waiting due to locks.
          You can identify queries causing delays in the Query timeline graph chart of Monitoring. Search for points where delays increase in the Query timeline or check the Query timeline of the server experiencing delays.

          Q. How can I mitigate or resolve replication delays?
          A. When delays occur, change the innodb_flush_log_at_trx_commit Config value and add a primary key to tables without one, which may be causing replication delays on the master DB, before rebuilding the standby master server.
          For more information on the innodb_flush_log_at_trx_commit value of the master DB and how to change it, see MySQL guide and DB server's DB Config management, respectively.
          There are two methods to add a primary key to tables without one and rebuild the standby master. You can either reinstall from Check replication status or disable and reconfigure High Availability settings on the master server.

          Q. Can I integrate external solutions?
          A. Yes, you can integrate external solutions such as Zero Board, GNU Board, etc. You can also use InnoDB as the storage engine during installation.
          If you require a different storage engine, consider using the MySQL installation-type service.

          Was this article helpful?
          What's Next
          Change password!
          Changing your password will log you out immediately. Use the new password to log back in.
          Change profile
          Success!
          First name must have atleast 2 characters. Numbers and special characters are not allowed.
          Last name must have atleast 1 characters. Numbers and special characters are not allowed.
          Enter a valid email
          Enter a valid password
          Your profile has been successfully updated.
          Logout