DB Server

Available in VPC

In DB Server, you can create or delete Cloud DB Server, as well as check the list of DB Server in operation. In addition, you can change the specifications of the DB Server in operation.

DB Server interface

The basic description of using DB Server is as follows:

View DB Service list

The list shows the DB services that have been created and are currently operating. On this list, you can view the information of each service. To view the information:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to > Services > Database > Cloud DB for Cache.
2. Click the DB Server menu.
3. When the list of created DB services appears, view the overview or click a DB Service name to see details.
   
   • Service name: Service name of the DB Server
   • Memory: available memory size on DB Server
   • DB Server prefix: name of the DB Server
   • Mode: Type of DB Server (cluster/simple)
   • Number of master nodes: number of master node
   • Status: Status of the DB Server.
     • Creating: Status in which the DB Server is being created with the information entered by the user.
       
     • Configuring: Status in which the DB Server is being created and configured with the information entered by the user.
       
     • Running: Status in which the creation and configuration of the DB Server have been completed with the information entered by the user, enabling the application server access to the DB.
       
     • Deleting: Status in which the DB Server is being deleted with the information entered by the user.
       
     • Upgrade: Upgrading to the spec that user chose/upgrading to DB version that user chose.
       
   • Creation date: Date when the DB Server was created, the initial point when the server entered creating status.
   • Running date: Date when the DB Server started running; the initial point when the server entered "running" status.
   • ACG: ACG name and ID used in the DB Server.
     • : Click to move to Server > ACG.
     • [View rules]: Click to view the detailed rules applied.
   • Zone: Name of the zone to which the DB Server belongs.
   • DBMS: DBMS type
   • DB Version: DB version information
   • Server generation: Generation information of DB Server.
   • VPC: VPC name used in the DB Server.
   • Subnet: Name of Subnet being used by the DB Server.
   • License: Open source license information applied to the DB
   • High availability: Whether the high availability feature is enabled (Y or N).
   • Port / access port: Number of ports being used by the DB Server.
   • DB Config: Name of Config Group to which the DB Server belongs.
     • : Click to change the config Group.
   • Backup storage period (backup time): Storage period and backup cycle of the backup file, if the backup feature is enabled.
     • : Click to enable or disable the backup feature or set the file retention period and backup cycle.

Creating DB Server

To create a DB Service on NAVER Cloud Platform's console:

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

1. Making server and DB settings

To enter settings to create a DB Server:

1. When the server and DB settings page appears, click to select the mode for the DB to create.
   

   • DB cluster: DB that uses master and slave methods and allows traffic distribution through data sharding.
   • DB simple: Default DB using the Master and standby-master methods.

2. Check the DBMS to be created, server generation, DB version, and license information.

   • DBMS: Information on the DBMS information that can be created in NAVER Cloud Platform.
   • Server generation: Server generation information supported in NAVER Cloud Platform information.
   • DB version: Information of the DB version that can be created in NAVER Cloud Platform.
   • License: Open source license information of DB that can be created in NAVER Cloud Platform.

3. Make VPC, DB Server, and Config Group settings required to create DB Server.

   • VPC: Select the VPC to be used for the creation of the server and DB.
     • [Refresh]: Click to refresh the list of created VPCs.
     • [Create VPC]: Click if you haven't created any VPC and need to create one.
   • Subnet: Select a private subnet to be used when accessing VPC.
     • [Refresh]: Click to refresh the list of created Subnet list.
     • [Create Subnet]: Click if you haven't created any Subnet and need to create one.
   • Node Memory: Set memory size for each node if the DB mode is set to Cluster.
   • Number of shards: Click to select the number of master nodes to create if the DB mode is set to Cluster.
   • Replicas per shard: Click to select the number of slave nodes to create as master node replicas if the DB mode is set to Cluster.
   Note

   For server redundancy (HA), DB Cluster consists of master and slave nodes. If a replica is added, a slave node is assigned for each master node.
   Example: if there are 3 shards and replicas per shard is 1 -> 3 master nodes and 3 slave nodes are created.

   • DB Server type: Select the type of DB Server to create and available memory size according to the selected server type, if the DB mode is simple.
     • Set memory size for each node.
     • Total available memory: Sum of all master nodes' memory sizes
   • Config group: Select a group to efficiently manage the DB Server settings.
     • [Refresh]: Click to refresh the list of created Config Groups.
     • [Create Config Group]: Click to create a new Config Group.

4. View the applicable pricing plan information when using Cloud DB for Cache.

   • Pricing plan: An hourly pricing plan, which is billed based on the hours used, is applied by default, and it is changed depending on the server specifications and storage capacity.
   • For detailed pricing information, see (Cloud DB for Cache is only available at hourly rates.) for more information on the pricing plans.

5. Set the rest of the items required for the creation of DB Server.

   • DB Server name: Enter the name of the DB Server.
     • Enter between 3 and 15 characters using lowercase English letters, numbers, and hyphens (-).
     • It must start with an English letter and end with an English letter or a number.
     • To identify a server, a random 3-digit number is automatically attached following the name entered by the user. Example: mydb-001, mydb-002, and so on.
     • Duplicate names are not allowed.
   • DB Service name: Enter a group name specifying the role of the DB Server to create. Example: mydb-ranking, mydb-game user, etc.
     • Enter between 3 and 15 characters using Korean letters, English letters, numbers, and hyphens (-).
     • Duplicate names are not allowed.
   • Set ACG: Access Control Group (ACG) is created automatically.
     • The detailed settings for the ACG are available from Server > ACG in the console.
   • DB access port: Enter 6379 or a number between 10000 and 20000 as the number of TCP port for accessing the DB to create.
     • Default: 6379.
     • The port number can't be changed after it is specified.
   • Support high availability: Click to select whether to use the failover feature for automatic recovery in the event of a failure, if the DB mode is Simple.
     • Configure redundancy with two DB Servers, an active Master Server and a Standby Master Server if you select.
     • When selected, set backup file retention period and backup time (default: 1 day, automatic).
     • When selected, additional fees will be incurred.
     • The Standby Master Server is not accessible by individual users.

6. Set whether to use backup for the server.

   • BACKUP settings: Set whether to use the backup, backup file retention period, and backup time.
     • Use backup for DB Server.: Click and select to use backup.
     • Backup file retention period: Click and select the period to store the backup file in a separate backup storage.
     • Backup time: Select the backup time between automatic and user-defined.
     • If you select this, additional fees will be incurred depending on the storage capacity used.
       • Automatic: Backup is automatically started every day.
       • User-defined: Backup is started every day within +15 minutes from the time you selected.

7. Click [Next].

2. Final confirmation

1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
   

   • Click [Previous] to edit the settings.

2. Click [Create].

3. Check the status of the DB created in the DB Server page's DB Server list.

   • Creating: Creating DB in progress with the information entered by the user.
   • Configuring: Status in which the DB Server is being created and configured based on user input data.
   • Running: Status in which the creation and configuration of the DB Server have been completed based on user input data, enabling the application server access to the DB.

Deleting DB Service

You can delete a DB Service that has been created and is in operation. If you are using high availability, deleting a DB Service deletes both active Master Server and Standby Master Server. If you're using the backup feature, then the backup files are also deleted. To delete:

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

DB Service monitoring

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

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

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

DB Service management

While operating a created DB Service, there may come situations where you need to upgrade or change the specifications set initially. Cloud DB for Cache provides a feature that allows you to change or upgrade certain specifications of a created DB Service with just a few clicks.

To manage DB Service that has been created and is in operation:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to > Services > Database > Cloud DB for Cache.
2. Click the DB Server menu.
3. Click the DB Service you want to manage, and then click [Manage].
4. Click and select the item you want to manage.
   
   • Change specifications
   • Config Group
   • View DB Service details
   • Set Backup
   • Manual Backup
   • Change server name
   • DB Version Upgrade
   • Manage operation system
   • Change high availability settings

Change specifications

You can change the server specifications for the DB Server you created. By default, it is only possible to upgrade the server specifications to higher specifications. Thus, downgrades are unavailable. Additional fees are incurred for upgrading specifications.

To change the specifications:

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

Config Group

You can create, edit, or delete Config Group. In step 5 in DB Service management, you can click a Config Group to move to the Config Group page. For more information on how to create, edit, and delete Config Groups, see Config Group.

View DB Service details

You can view the details of the DB Server created. To view details:

1. When the view details page appears for the DB Server selected, view the details.
   • Hostname: Host name of the DB Server
   • Memory: Available memory size on DB Server
   • Status: Status of the DB Server
   • Role: Roles of the DB Server
     • Stand Alone: A stand-alone server that does not use the high availability feature.
     • Master: The main server when the high availability feature is being used.
     • Standby-master: A backup server when the high availability feature is being used.
     • Slave: A server for backup and read load distribution when the high availability feature is being used (only applicable for Cluster).
   • Slot: Number of slots assigned to the DB Server
   • Dns: DNS name used in the DB Server
2. For DB Cluster, you can add nodes. To add a node, click [Add node].
   
3. When the Add Cluster node popup window appears, enter the required information.
   
   • Number of shards: Click to select the number of shards (master nodes) to add.
   • Replicas per shard: Add replicas (slave nodes) as well as per the existing DB Cluster settings.
4. Click [OK].

5. Both Cluster and Simple types support server restart. If a restart is required, click [Restart server].
6. When the Restart server popup window appears, enter the hostname of the server to restart.
   
7. Click [OK].

8. Both Cluster and Simple types support data initialization. If data initialization is required, click [Flush All].
9. When the Flush All popup window appears, enter the hostname of the server whose data you want to initialize.
   
10. Click [OK].

Set Backup

You can set the backup options for the DB Server created. To make backup settings:

1. When the Set backup popup window appears, make backup settings.
   
   • Backup: Enable or disable backup feature
   • Backup file retention period: Maximum retention period for the backup files when using the backup feature
   • Backup time: Backup cycle if backup feature is used,
2. Click [Yes].

Manual Backup

You can perform manual backup of the DB Server created. You can make a manual backup request whether or not automatic backup is enabled. If the server has high availability, backup is performed from the hidden or Slave Server. If it is stand alone, backup is performed from the master.

To request a manual backup:

1. When the Manual backup popup window appears, check the displayed information.
   
2. Click [Yes].
3. Check the status of the DB in the DB Server page's DB Server list.
   • Configuring: DB Server is performing backup
   • Running: Status in which the backup of the DB Server has been completed, and the access to DB Server from the application server is available

Change Server name

You can change the name of created DB Severs.

To change the name of the server:

1. When the Change Server name popup window appears, check the displayed information and enter the name you want to change in changing DB Server Prefix.
   • Changing DB Server prefix: Field for server name to change
2. Click [Yes].
3. Check the status of the DB in the DB Server page's DB Server list.
   • Configuring: Changing DB Servers to their hostnames.
   • Running: The hostname change for DB Server is complete.

DB Version Upgrade

You can execute minor version upgrades of the created DB Server.

To upgrade minor versions of DB Server:

1. When the DB version upgrade popup window appears, select the DB version to change and corresponding Config Group.
   • DB Version: Check the version of DB to upgrade
   • Config group: Corresponding Config Group to the DB to upgrade
2. Click [OK].
3. Check the status of the DB in the DB Server page's DB Server list.
   • Upgrade: Executing DB version upgrade
   • Running: The upgrade is complete.

Manage operation system

Update operating system of created DB Server to the latest version.
The operating system update applies to the entire DB Service and is performed collectively on all servers within the service. During the OS update, you can also perform a major version upgrade to the latest version of DB.
Server access is not available while the update is in progress, and all DB data will be initialized.

Updating only the operating system

Updates only the operating system of DB.
For HA products, the update is applied to both the master and standby-Master Servers at the same time.

1. To proceed, click [OS management], review the popup window, and then click [Next].
   
2. After reviewing the precautions for the operating system update, click the checkbox.
3. After reviewing all items, click [Yes].
   
4. You can monitor the update progress through the DB Server status.
   

Updating the operating system and DB version simultaneously

Upgrades both the operating system and DB to the latest version.
For HA products, the update is applied to both the master and standby-Master Servers at the same time.

1. Click [OS management], review the popup window, and then click [Check DB version].
   

2. Check the [DB version upgrade] checkbox and select the Config Group that corresponds to the latest DB version.
   

3. After reviewing the precautions for the operating system update, click the checkbox.

4. Once you've confirmed all items, click [Yes].
   

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

Change high availability settings

Change the selected DB Server in Cloud DB for Cache to stand alone or high availability configuration.

To change configuration:

1. In the DB Server list, click [Change high availability settings].
   
2. When the popup window appears, check the note and click [OK].
   • Stand Alone → High availability configuration: The checkbox is displayed and can be selected.
   • High availability configuration → Stand Alone: The checkbox is not displayed.
     
3. When the setting is applied, the status of the DB Server changes to configuring, once completed, it switches to running.