Documentation Index

Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

DB Server

Prev Next

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 basics of using DB Server are as follows:

database-database-8-1_0003_vpc_ko

Component Description
① Menu name Current menu name and number of DB Servers in operation.
② Basic features Create a DB Server, view details of Cloud DB for Cache, download DB information Excel file, or refresh the DB Server interface.
③ 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 Service list

You can view information for each service in the list of DB services that have been created and are currently in operation. To view the information:

Note

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.

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for Cache.
  2. Click the DB Server menu.
  3. When the list of created DB services appears, check the summary or click a DB Service name to see details.
    database-database-8-1_06121_vpc
    • Service name: DB Server service name.
    • Memory: Available memory size on DB Server.
    • DB Server prefix: DB Server name.
    • Mode: Type of DB Server (cluster/simple).
    • Number of master nodes: Number of master nodes.
    • Status: DB Server status.
      • Creating: Status in which the DB Server is created with the information you entered.
        clouddbforredis-redisserver_05_vpc_ko
      • Configuring: Status in which the DB Server is created and configured with the information you entered.
        clouddbforredis-redisserver_06_vpc_ko
      • Running: Status in which the creation and configuration of the DB server has been completed with the information you entered, and access to the DB from the application server is available.
        clouddbforredis-redisserver_07_vpc_ko
      • Deleting: Status in which the DB Server created with the information you entered is being deleted.
        clouddbforredis-redisserver_08_vpc_ko
      • Upgrade: Upgrading to the specifications that you selected or upgrading to the DB version that you selected.
        clouddbforredis-redisserver_10_vpc_ko
    • Creation 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.
      • clouddbforredis-start_ico-01: 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 the DB Server.
    • VPC: Name of the VPC being used by the DB Server.
    • Subnet: Name of the subnet used by the DB Server.
    • License: Open source license information applied to the DB.
    • High availability: Whether to use the high availability feature with Y or N.
    • Port/access port: Name of the port used by the DB Server.
    • DB Config: Name of config group to which the DB Server belongs.
      • clouddbforpg_ico-02: 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.
      • clouddbforpg_ico-02: Click to enable or disable the backup feature or set the file retention period and backup cycle.
Caution

If you clear the backup, all existing backup files are deleted.

Create DB Service

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

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for Cache.
  2. Click the DB Server menu.
  3. Click [Create DB Server].
    database-database-8-1_03_vpc_ko
  4. When the service subscription interface appears, proceed with the following steps in order:
Note

Click [Subscribe] from the NAVER Cloud Platform portal's Services > Database > Cloud DB for Cache to go directly to the interface in Step 4.

1. Server and DB settings

To enter settings to create a DB Server:

  1. When the server and DB settings interface appears, click to select the mode for the DB to create.
    database-database-8-1_0004_vpc_ko

    • DB Cluster: DB that can distribute traffic through data sharding using Master and Slave methods.
    • 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 of DBMS that can be created on NAVER Cloud Platform.
    • Server generation: Information of the server generation that can be created on NAVER Cloud Platform.
    • 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.
  3. Configure the VPC, DB Server, and Config Group settings required to create a DB Server.

    • VPC: Select the VPC to be used for the creation of the server and DB.
      • [Refresh]: Click to refresh the list of the created VPC list.
      • [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 the VPC.
      • [Refresh]: Click to refresh the list of the 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 Cluster.
    • Replicas per shard: Click to select the number of slave nodes, namely replicas of the master nodes, to create if the DB mode is 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 DB type to be created and available memory according to the server type if the DB is in the Simple mode.
      • 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 the created Config Group list.
      • [Create Config Group]: Click if you haven't created any Config Group and need to create one.
  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 more information on the pricing plans, click (Cloud DB for Cache is only available at hourly rates.) .
  5. 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 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 2 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 are 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: 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 are 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.
  7. Click [Next].

Note

DB Cluster automatically distributes data on multiple DB nodes, and its advantages are as follows:

  • Traffic distribution: The servers divide and process the traffic being concentrated on specific data by processing data in multiple devices.
  • High availability: It provides high availability to the clients by bundling servers together and making them operate as a single system.
  • Backup server supplement: It minimizes the loss of data.

2. Final confirmation

  1. When the final confirmation interface appears, check the configured server information, DB information, and backup information.
    database-database-8-1_redis-server-setting_ko

    • Click [Previous] to edit the settings.
  2. Click [Create].

  3. Check the status of the DB created in the DB Server interface's DB 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 you entered, and access to the DB from the application server is available.
Caution

It may take up to 3 minutes as the system progresses through Creating and Configuring before reaching the Running status where actual usage becomes available.

Note

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

Delete 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, the backup files are also deleted. To delete a DB Service:

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

The actual deletion from the list after going through the Deleting status may take a certain amount of time (minutes).

Monitor DB Service

NAVER Cloud Platform's Cloud DB for DB provides a monitoring service through the dashboard on each server. This allows you to intuitively check the status of operating server and its data and effectively manage them.

Note

For more information on Monitoring, see Monitoring.

To go to the monitoring interface 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 Menu > Services > Database > Cloud DB for Cache.
  2. Click the DB Server menu.
  3. Click the DB Service you want to monitor, and click [Monitoring].
  4. Click and select the dashboard you want to monitor.
    database-database-8-1_06_ko

Manage DB Service

While operating the 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.

Note

By default, managing a DB Service is available when the server status is Running.

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 Menu > Services > Database > Cloud DB for Cache.
  2. Click the DB Server menu.
  3. Click the DB Service you want to manage, and click [Manage].
  4. Click and select the item you want to manage.
    database-database-8-1_07_vpc_ko

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.

Caution

The servers 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:

  1. When the Change specifications popup appears, check the current server specifications.
  2. Click and select the server specifications you want to change to.
    clouddbforredis-redisserver_07_ko
  3. Click [Yes].
  4. Check the status of a DB for which you changed specifications from the DB list in the DB Server interface.
    • 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 you entered, and access to the DB from the application server is available.

Config Group

You can create, edit, or delete Config Group. In Step 5 in Manage DB Service, you can click a Config Group to move to the Config Group interface. 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 interface appears for the DB Server selected, view the details.
    • Hostname: DB Server host name.
    • Memory: Available memory size on DB Server.
    • Status: DB Server status.
    • Role: DB Server role.
      • Stand-Alone: Stand-alone server that does not use the high availability feature.
      • Master: Main server with the high availability feature being used.
      • Standby-Master: Backup server with the high availability feature 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 the slot assigned to the DB Server.
    • Dns: Name of the DNS being used by the DB Server.
  2. For DB Cluster, you can add nodes. To add a node, click [Add node].
    database-database-8-1_08_vpc_ko
  3. When the Add Cluster node popup appears, enter the required information.
    clouddbforredis-redisserver_09_ko
    • 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].
Caution

When shards are added, a temporary disruption may occur, and it can take 3 hours or more for the process to be completed.

  1. Both Cluster and Simple types support server restart. If a restart is required, click [Restart server].
  2. When the Restart server popup appears, enter the hostname of the server to restart.
    database-database-8-1_restart_ko
  3. Click [OK].
Caution
  • Data loss may occur during a restart. For stand-alone servers, all data is deleted.
  • For Simple HA, the Master and Standby-Master restart simultaneously.
  1. Both Cluster and Simple types support data initialization. If data initialization is required, click [Flush All].
  2. When the Flush All popup appears, enter the hostname of the server whose data you want to initialize.
    database-database-8-1_flushall_ko
  3. Click [OK].

Set Backup

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

Caution

If you clear the backup, all existing backup files are deleted.

Note

For more information on Backup settings, see Backup.

  1. When the Set backup popup appears, configure backup settings.
    clouddbforredis-redisserver_10_ko
    • 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.
  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.

Caution
  • The interval between manual backup cycles cannot be less than 30 minutes.
  • Stand-alone server may be affected by master since backup is done from master.

To request a manual backup:

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

Change server name

You can change the name of created DB Severs.

Note

You can only change common Server Prefix within the same service.

To change the name of the server:
clouddbforredis-redisserver_name_vpc_ko

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

DB Version Upgrade

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

Caution
  • The DB is restarted during a version upgrade, which may cause a temporary disruption in DB access.
  • Due to the nature of DB, version upgrades can cause data loss.

To upgrade minor versions of DB Server:
clouddbforredis-redisserver_upgrade_vpc_ko

  1. When the DB version upgrade popup 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 interface's DB list.
    • Upgrade: Executing DB version upgrade.
    • Running: The upgrade is complete.

Manage operating 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 operating system 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 is initialized.

Caution
  • After the operating system update, all existing DB data is initialized. Make sure to check and back up any necessary DB data before proceeding with the operating system update.
  • After the operating system update, monitoring data and event history for the servers from before the update are no longer available in the console. If you need to back up the monitoring data and event history prior to the upgrade, refer to the widget data download feature in the Cloud Insight user guide and the export log feature in the Cloud Log Analytics user guide.
  • Custom notification settings configured for the DB Cluster are not transferred automatically. If you have any manually configured notification items, reconfigure them after the operating system update is complete.
  • Linked Server configurations are not transferred automatically. Reconfigure the DB Server after the latest version operating system update is complete.
  • After the operating system update, the Private IP address is changed. Cloud DB for Cache recommends connecting through private domain to prevent service disruption caused by IP changes. If you are using a private IP address, DB connection errors may occur after the operating system update.
  • Once the operating system update is complete, rolling back to the previous version is not supported.

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

Note
  • The update time may vary depending on the number of Servers.
  • StandAlone clusters are also supported for this update.
  1. Click [OS management], check the popup, and click [Next].
    clouddbforredis_os_upgrade_management_vpc_ko
  2. After reviewing the precautions for the operating system update, click the checkbox.
  3. After reviewing all items, click [Yes].
    clouddbforredis_os_upgrade_vpc_ko
  4. You can monitor the update progress through the DB Server status.
    clouddbforredis_update_status

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

Note
  • Only the latest version of DB is supported for the upgrade. You cannot select a specific version of DB.
  • You must create a Config Group for the latest version of DB in advance.
  • If you perform a DB version upgrade during the operating system update, backups created in previous DB versions may not be restored properly. If necessary, use the Export to Object Storage feature to back up your data in advance.
  1. Click [OS management], check the popup, and click [Check DB version].
    clouddbforredis_oswithversion_upgrade_vpc_ko

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

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

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

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

Update kernel version

Updates the DB kernel version.

  1. Click [OS management], check the popup, and click [Next].
    database-cache-kernelupdate1_ko
    • Outdated kernel versions appear in red.
  2. After reviewing the precautions for the kernel update, click the checkbox.
  3. Once you've confirmed all items, click [Yes].
    database-cache-kernelupdate2_ko

Change high availability settings

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

Caution
  • This feature is supported only in Simple mode and is not available in Cluster mode.
  • Changing to stand-alone or high availability configuration may affect billing.

To change configuration:

  1. In the DB Server list, click [Change high availability settings].
    clouddbserver_ha_1
  2. When the popup 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.
      clouddbserver_ha_2
  3. When the setting is applied, the status of the DB Server changes to Configuring; once completed, it switches to Running.