Available in Classic
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 page
The basic description of using DB Server is as follows:

| Component | Description |
|---|---|
| ① Menu name | Shows the current menu name and number of DB Servers in operation. |
| ② Basic features | Create a DB Server, check details for Cloud DB for Cache, and refresh the DB Server page |
| ③ Post-creation features | Delete, monitor, and manage DB Server in operation |
| ④ DB Server list | Check the list of DB Servers in operation and their information. |
| ⑤ Search | Search the server you want by the service name from the DB Server list. |
View DB Server 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:
You can view the list only when there are 1 or more servers in operation. If you do not have any servers created and operating, no list appears on the DB Server interface.
- In the Classic environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB for Cache. - Click the DB Server menu.
- If the list of created DB Servers appears, then check the summary or click an DB Server to check the details.
- Service name: DB Server Services name
- Role: role of the DB Server (Master/Standby Master/Stand Alone)
- DB Server name: DB Server name
- DB Memory: available memory size on DB Server
- DNS name: name of the DNS being used by the DB Server
- Status: DB Server status
- Creating: Status in which the DB Server is created with the information you entered.

- Configuring: Status in which the DB Server is created and configured with the information you entered.

- Running: Status in which the creation and configuration of the DB server has been completed with the information entered by user, and access to the DB from the application servers is available

- Deleting: Status in which the created DB Server is being deleted with the information you entered.

- Creating: Status in which the DB Server is created with the information you entered.
- Created date: Date when the DB Server was created and the initial point when the server status entered the creating status.
- Running date: Date when the DB Server operation started and the initial point when the DB server status entered the "running" status.
- ACG: ACG name and ID used in the DB Server
: Click to move to Server > ACG.- [View rules] button: Click to view the detailed rules applied.
- Zone: Name of the Zone to which the DB Server belongs
- DB Version: DB version information
- License: Open source license information applied to the DB
- High availability: Whether to use the high availability feature with Y or N
- Access port: Name of the port 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): The configured backup file storage period and backup cycle, if the backup feature is enabled.
: Click to enable or disable the backup feature or set the file retention period and backup cycle.
- Monitoring: Click to move to Cloud DB for Cache > Monitoring
If you clear the backup, all existing backup files are deleted.
Create DB Server
To create a DB Service on NAVER Cloud Platform's console:
-
In the Classic environment of the NAVER Cloud Platform console, navigate to
> Services > Database > Cloud DB for Cache. -
Click the DB Server menu.
-
Click [Create DB Server].

-
When the service subscription page appears, take the following steps in order:
Click [Subscribe] in NAVER Cloud Platform portal's Services > Database > Cloud DB for Cache to go directly to the page in Step 4.
1. Server and DB settings
To enter settings to create a DB Server:
- When the server and DB settings page appears, check the version and license information of the DB to be created.
- DB Version: Information of the DB version that can be created on NAVER Cloud Platform
- License: Open-source license information of the DB that can be created on NAVER Cloud Platform.
- Set items related to Zone and DB Server, which are needed for the creation of the DB Server.
- Zone: Click to select the zone in which to create the server
- DB Server Type: Select the DB type to be created and available memory according to the server type.
- Set memory size for each node.
- Total available memory: Sum of all master nodes' memory sizes
- 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.
- Click (Cloud DB for Cache is only available at hourly rates.) for more information on the pricing plans.
- Set the rest of the items required for the creation of DB Server.
- DB Server name: Enter the name of the DB Server to create
- 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 Services 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.
- 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.
- DB Server name: Enter the name of the DB Server to create
- 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: Select by clicking 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: The backup is started every day within 15 minutes from the time specified by the user
- Backup settings: Set whether to use the backup, backup file retention period, and backup time.
- Click the [Next] button.
2. Final confirmation
- When the final confirmation page appears, check the configured server information, DB information, and backup information.
- Click [Previous] to edit the settings.
- Click [Create].
- Check the status of the DB created in the DB Server page's DB Server list.
- Creating: Status in which the DB is created with the information you entered.
- Configuring: Status in which the DB Server is created and configured with the information you entered.
- Running: Status in which the creation and configuration of the DB server has been completed with the information entered by user, and access to the DB from the application servers is available
To view the latest status from step 3, click [Refresh].
It may take up to 3 minutes as the system progresses through creating and configuring states before reaching the running status where actual usage becomes available.
Delete DB Server
You can delete an DB Server 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:
- From the Platform menu on NAVER Cloud Platform console, click and select Classic.
- Navigate to Services > Database > Cloud DB for Cache.
- Click the DB Server menu.
- Click the DB Server you want to delete, and then click [Delete DB Server].
- When the Delete DB Server popup window appears, enter the name of the DB Server to delete, and then click [Yes].
- Check the status of the DB deleted in the DB Server page's DB Server list.
- Deleting: status in which a DB is being deleted
The actual deletion from the list after going through the Deleting status may take a certain amount of time (minutes).
DB Service monitoring
NAVER Cloud Platform's Cloud DB for Cache provides a monitoring service through the dashboards on each server. This allows you to intuitively view servers in operation and data status, and efficiently manage them.
For more information on Monitoring, see Monitoring.
To go to the monitoring page of the DB Service that has been created and is in operation:
- From the Platform menu on NAVER Cloud Platform console, select and click Classic.
- Navigate to Services > Database > Cloud DB for Cache.
- Click the DB Server menu.
- Click the DB Service you want to monitor, and then click [Monitoring].
- Click and select the dashboard you want to monitor.

Manage DB Server
While operating a created DB Server, 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 Server with just a few clicks.
By default, managing a DB Server is available when the server status is running.
To manage the DB Server that has been created and is in operation:
- From the Platform menu on NAVER Cloud Platform console, select and click Classic.
- Navigate to Services > Database > Cloud DB for Cache.
- Click the DB Server menu.
- Click the DB Server you want to manage, and then click [Manage].
- Click and select the item you want to manage.
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.
The servers will restart when you upgrade server specifications. As access is unavailable during the restart, it is recommended to view the data after the restart is completed.
To change the specifications:
- When the Change specifications popup window appears, check the current server specifications.
- Click and select the server specifications you want to change to.

- Click [Yes].
- 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 configured with the information you entered.
- Running: Status in which the configuration of the DB server has been completed with the information entered by user, and access to the DB from the application servers is available.
Managing Config
You can make the config settings for the DB Server created. Settings added by the user are applied to the entire service. Deleting the added config resets the settings to the default. To make the config settings:
- When the Change DB config popup window appears, check the current config on the Config variable list
- Config Name: Name of config variable to set.
- Config Value: Variable value.
- Click to select the name of config variable to set, enter a value and click the [Add] button.
- Click the [Save] button.
Config variable list
The following are descriptions of config variables:
| Config Name (name of the config variable) | Description |
|---|---|
| hash-max-ziplist-entries | Criterion for the hash form to be saved as ziplist (number of fields) |
| hash-max-ziplist-value | Criterion for the hash form to be saved as ziplist (bytes) |
| maxclients | Maximum number of client users |
| maxmemory-policy | Memory policy when the DB memory 100% |
| zset-max-ziplist-entries | Criterion for the zset form to be saved as ziplist (number of fields) |
| zset-max-ziplist-value | Criterion for the zset form to be saved as ziplist (bytes) |
Variable Status
You can view the current settings of the config variables. To view the current settings of config variables:
- When the variables popup window appears, check the config values on the variables list
- Variables Name: Name of config variable to set.
- Value: Variable value.
Variable value list
The following are descriptions of the variable values:
| Variables name (name of config variable) | Description |
|---|---|
| hash-max-ziplist-entries | Criterion for the hash form to be saved as ziplist (number of fields) |
| hash-max-ziplist-value | Criterion for the hash form to be saved as ziplist (bytes) |
| list-max-ziplist-entries | Criterion for the list form to be saved as ziplist (number of fields) |
| list-max-ziplist-value | Criterion for the list form to be saved as ziplist (bytes) |
| maxclients | Maximum number of client users |
| maxmemory-policy | Memory policy when the DB memory 100% |
| slowlog-log-slower-than | Slow command logging time (microseconds) |
| slowlog-max-len | Slow command logging amount |
| tcp-keepalive | Client's check cycle |
| timeout | Client's waiting time |
| zset-max-ziplist-entries | Criterion for the zset form to be saved as ziplist (number of fields) |
| zset-max-ziplist-value | Criterion for the zset form to be saved as ziplist (bytes) |
| activerehashing | If this is set to yes, 1 millisecond is added for rehashing to the usual 1 per 100 milliseconds, thus making the rehashing period 2 per 100 milliseconds |
| always-show-logo | View the ASCII logo each time the Redis server starts |
| client-output-buffer-limit(normal) | Option for client output buffer limit. 〈class〉 〈hard limit〉 〈soft limit〉 〈soft seconds〉 |
| client-output-buffer-limit (Slave) | Option for client output buffer limit. 〈class〉 〈hard limit〉 〈soft limit〉 〈soft seconds〉 |
| client-output-buffer-limit(pubsub) | Option for client output buffer limit. 〈class〉 〈hard limit〉 〈soft limit〉 〈soft seconds〉 |
| cluster-require-full-coverage | Select whether to prohibit the use of clusters altogether or allow operation of all other nodes except the downed nodes when the master node goes down |
| daemonize | Decide whether to run the Redis server as a daemon |
| Database | Set the number of databases |
| hll-sparse-max-bytes | HyperLogLog sparse representation byte limit. If the limit is exceeded, the expression is converted to a denser one. |
| hz | Reference value for determining the cycle of background tasks such as disabling client connection and deleting an expired key |
| latency-monitor-threshold | Execution time of internal processing operations handled by the Latency Monitor. If it exceeds the setting (milliseconds), the computation is recorded. |
| lazyfree-lazy-eviction | Whether to use UNLINK for deleting a key as per the maxmemory policy |
| lazyfree-lazy-expire | Whether to use UNLINK when deleting expired keys |
| lazyfree-lazy-server-del | Whether to use UNLINK when an existing key must be deleted by SET or RENAME |
| maxmemory | Limit to the memory used by the Redis Server |
| maxmemory-samples | Number of samples to be used by algorithms needing samples (LRU, LFU, minimum TTL) in the maxmemory policy |
| port | Allow access to the Redis Server through the selected port |
| protected-mode | Limit access as per the bind or password setting when protection mode is enabled |
| rdbchecksum | Whether to record the checksum value at the end of the rdb file |
| rdbcompression | Use LZF compression for saving rdb files |
| repl-backlog-size | Replication backlog size |
| repl-disable-tcp-nodelay | If this is set to yes, nodelay becomes false, so data are collected and sent in large packets during Full Sync between the master and the replicated server |
| repl-diskless-sync | Select whether to use the disk or socket method for total data synchronization |
| repl-diskless-sync-delay | Standby time for transfer to enable a single processing of multiple replication requests when socket replication is selected for total data synchronization |
| repl-ping-slave-period | Interval at which a replica node sends ping to the master node. |
| repl-timeout | Recorded time of disconnection between the master and replica nodes |
| set-max-intset-entries | Criterion for storing a set as intset. |
| slave-lazy-flush | Whether to delete the existing data with FLUSHALL async when the replica node receives the entire data from the master |
| slave-priority | Value that determines the priority of replica nodes in becoming the master node when the master node goes down, and there are multiple replica nodes available |
| slave-read-only | Whether to enable the commands for entering, editing, and deleting data for the client's replica nodes |
| slave-server-stale-data | Method to respond to the client's request when the replica node is disconnected from the master node or replication is in progress |
| stop-writes-on-bgsave-error | Whether to allow the server to keep receiving the write command when the BGSAVE command has failed |
| tcp-backlog | Specify the number of client connections per second for the Redis server. |
Setting Backup
You can set the backup options for the DB Server created. To make backup settings:
If you clear the backup, all existing backup files are deleted.
For more information on Backup settings, see backup.
- When the Set backup popup window appears, make backup settings.
- Backup settings: whether to use the 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,
- Click [Yes].
DB Flush
You can delete all data on the DB Server created.
Even if all data has been deleted with DB Flush, you can restore the data with a backup file if you have one. However, note that restoration is made only up to the point of backup rather than to the point when DB Flush was executed.
- When the DB Flush popup window appears, enter the name of DB Server from which to delete data.

- Click [Yes].
- On the DB list on the DB Server page, check the status of DB with all its data deleted.
- Configuring: all data are being deleted on the DB Server