DB Server

Available in VPC

In DB Server, you can create or delete Cloud MongoDB Server, as well as check the list of MongoDB Server in operation. In addition, you can also change the specifications of the MongoDB Server in operation or manage admin (user) accounts.

DB Server interface

The basic description of using DB Server is as follows:

Checking MongoDB Server list

You can check the information of each server from the list of MongoDB Servers that have been created and are in operation. To view the information:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.

2. Click the DB Server menu.

3. If the list of created MongoDB Servers appears, check the summary information or click a MongoDB Server to check the details.
   

   • DB Service name: A group of MongoDB clusters under the MongoDB Service name.
   • Cluster role: Roles of the MongoDB cluster.
   • DB Server name: Name of the MongoDB Server.
   • DB role/role: Roles of the MongoDB Server.
   • DB Server type: Type of the MongoDB Server and its available memory.
   • Monitoring: Go to the monitoring screen.
   • DB Status: Directs to the view DB Server details page.
   • DB access port: Port number being used by the MongoDB Server.
   • Private domain: Information of the private domain.
   • Public domain: Information of public domain.
   • Data storage: Size of the data storage in use (available capacity).
   • Data storage type: Type of data storage in use.
   • Data storage capacity: Available capacity and used capacity of the data storage in use.
   • Status: Status of the MongoDB Server.
     • Creating: Status in which the MongoDB Server is being created with the information entered by the user.
     • Configuring: Status in which the MongoDB Server is being configured with the information entered by the user.
     • Running: Status in which the creation and configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application server is available.
     • Deleting: Status in which the MongoDB Server created is being deleted with the information entered by the user.
     • Stopping: Status in which the MongoDB Server created is being stopped with the information entered by the user.
     • Restarting: Status in which the MongoDB Server created is being restarted with the information entered by the user.
     • Failover pending: Status in which the system is waiting for user-initiated failover of the primary member during operations such as an OS upgrade.
   • Created date: Date when the MongoDB Server was created, the initial point when the server entered "creating" status.
   • Running date: Date when the MongoDB Server started running, the initial point when the server entered "running" status.
   • ACG: ACG name and ID used in the MongoDB Server.
     • : Click to move to Server > ACG.
     • [View rules]: Click to view the detailed rules applied.
   • DB engine version: Information of the MongoDB version installed on the server
   • Cluster type: Type of the MongoDB cluster
   • Replica set (shard) name: Name of the replica set (shard).
   • VPC: VPC name used in the MongoDB Server
   • Subnet: Name of the subnet being used by the MongoDB Server.
   • 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.

Creating MongoDB Server

To create a MongoDB Server in the NAVER Cloud Platform console:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.

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. Set cluster
   • 2. Set server
   • 3. Set DB
   • 4. Final confirmation

1. Set cluster

To set the information for the MongoDB cluster to be installed:

1. When the set cluster page appears, check the type of DBMS you want to install to the server from DBMS type.
   

2. Select the server generation.

3. Select the MongoDB version you want to install.

4. Select the type of the MongoDB cluster.

   • Stand Alone: Supports configuration for test and development environment.
   • Single replica set: A mongod process group that maintains the same data set and provides high availability
   • Sharding: A configuration that distributes the storage of data in multiple replica sets
   • The settings can't be changed after you create the MongoDB Server.

5. Set the rest of the items required when you create the MongoDB.

   • DB Server Name: Enter the name of the MongoDB Server.
     • Enter between 3 and 15 characters using English letters, numbers, and hyphens (-).
     • Duplicate names are not allowed.
     • Random text will be added to avoid duplicate host names.
   • DB Service name: Enter the group name of the MongoDB Server.
     • Enter between 3 and 15 characters using Korean letters, English letters, numbers, and hyphens (-).
     • Duplicate names are not allowed.
   • VPC: Select the VPC to use to create the server and MongoDB.
     • [Refresh]: Click to view the latest version of the 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 VPC.
     • [Refresh]: Click to view the latest version of the VPC list.
     • [Create Subnet]: Click to create a new subnet
   • Data storage type: Select or check the type of storage
     • Server generation G2: Select from available storage types (SSD, HDD) for storing DB data (cannot be changed after creation)
     • Unit(s)
       G3: Fix as SSD
   • Data storage capacity: Check the storage capacity for saving DB data.
     • 10 GB is allocated upon initial creation of the MongoDB Server.
     • The capacity is automatically added in 10 GB units and charged as data increases.
     • Supports up to 2,000 GB.

6. Check the applicable pricing plan information when using Cloud DB for MongoDB.

   • 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, click Pricing information.

7. Check the MongoDB version and license information.

8. Specify the ACG settings for the MongoDB Server access.

   • Access Control Group (ACG) is created automatically.
   • The detailed settings for the ACG are available from Server > ACG in the console.

9. Click [Next].

2. Set server

To set the information for MongoDB Server to be installed:

1. When the set server page appears, set items required to create the MongoDB Server.

   • If you've selected stand-alone for the cluster type, then set the following items:
     
     • Stand-alone server spec: Select the specifications for the stand-alone server.
     • Port: Enter the port number of the standalone server between 10,000 - 65,535.
       • Default: 17017.
       • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities
   • If you've selected single replica set for the cluster type, then set the following items:
     
     • Number of members per replica set (primary & secondary): Select the number of member servers in each shard (3 to 7 including the arbiter server)
     • Member server spec: Select the specifications for the Member Server.
     • Number of arbiters per replica set: Select the number of arbiter server per shard (0-1 unit).
       • In clusters consisting of primary - secondary - arbiter, when there is a replication delay or failure in one secondary member, a request set as read concern: majority or write concern: { w: majority } will not respond (difficult to see the effect of server duplexing)
       • In clusters with primary - secondary - arbiter configuration, it is recommended to set read concern: local, write concern: { w: 1, j: True }
       • Avoid configuring primary - secondary - arbiter in the production environment
     • Arbiter server spec: Select the specifications for arbiter server.
     • port: Enter the port number of each server between 10000–65535.
       • Default: 17017.
       • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities
   • If you've selected sharding for the cluster type, then set the following items:
     
     • Number of members per replica set (primary & secondary): Select the number of member servers in each shard (3 to 7 including the arbiter server)
     • Member server spec: Select the specifications for the Member Server.
     • Number of arbiters per replica set: Select the number of arbiter server per shard (0-1 unit).
       • In clusters consisting of primary - secondary - arbiter, when there is a replication delay or failure in one secondary member, a request set as read concern: majority or write concern: { w: majority } will not respond (difficult to see the effect of server duplexing)
       • In clusters with primary - secondary - arbiter configuration, it is recommended to set read concern: local, write concern: { w: 1, j: True }
       • Avoid configuring primary - secondary - arbiter in the production environment
     • Arbiter server spec: Select the specifications for arbiter server.
     • Number of shards: Select the number of shards
       • 2 or 3 can be selected upon initial installation.
       • Up to 5 shards can be added in the management page after installation
       • If you need more than 5 Shards, make an inquiry to customer support
     • Number of Mongos (Router) Servers: Select the number of mongos servers (2-5 units).
     • Mongos Server Spec: Select the specifications for the Mongos Servers.
     • Number of config servers: Check the number of config servers (3 fixed units).
     • Config server spec: Select the specifications for the config Servers.
     • port: Enter the port number of each server between 10000–65535.
       • Default: 17017.
       • The default MongoDB port number of "27017" is not recommended due to security vulnerabilities

2. Click [Next].

3. Set DB

To set the information for the MongoDB to be installed:

1. When the Set DB page appears, set items required to create the MongoDB Server.
   

   • USER_ID: Enter the account ID of the MongoDB Server admin

     • Enter between 4 and 16 characters using English letters and numbers.
     • The first character must be an English letter.
     • You cannot use predefined reserved words.

   • USER password: Enter the account password of the MongoDB Server admin

     • Enter 8 to 20 characters using at least 1 English letter, number, and special character.
     • You cannot use special characters ` & + \ " ' / or spaces

   • DB Config settings: View the optimized basic settings provided by NAVER.

   • DB Data Compress: Select the data compression algorithm provided by MongoDB

     • Using the default value is recommended

   • Collect DB log: View the provision of log collection and viewer features for error logs and slow query logs.

     • Cloud Log Analytics integrations.
2. Set whether to use backup for the server.
   • Backup file retention period: Click and select the period to store the backup file in a separate backup storage.
     • For point-in-time recovery, the backup file is stored for the maximum set retention period + 24 hours.
   • Backup time: Select the backup execution time
     • The backup is performed once a day at the specified time using mongodump provided by MongoDB
     • The backup is started every day within 15 minutes from the time specified by the user
     • If you select this, additional fees will be incurred depending on the storage capacity used.
3. Click [Next].
4. When the Request subscription to Cloud Log Analytics appears, view the content, and click [OK].
   • If you need to subscribe to Cloud Log Analytics, click [Subscribe to Cloud Log Analytics].
   • For more information about Cloud Log Analytics, see Cloud Log Analytics user guide.

4. Final confirmation

1. When the final confirmation page appears, check the configured cluster information and server information.
   
   • Click [Previous] to edit the settings.
2. Click [Create].
3. Check the status of the MongoDB created in the DB Server page's MongoDB Server list.
   • Creating: Status in which the MongoDB Server is being created with the information entered by the user
   • Configuring: Status in which the MongoDB Server is being created and configured with the information entered by the user
   • Running: Status in which the creation and configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

Restart MongoDB Server

You can easily and conveniently restart MongoDB Server. You can't access servers while they're being restarted. To restart:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MongoDB.
2. Click the DB Server menu.
3. Click the MongoDB Server you want to restart, and then click [Restart].
4. When the Restart DB Server popup window appears, check the name of the DB Server to restart, and then click [Yes].
5. Check the status of the MongoDB Server from the MongoDB Server list in the DB Server page.
   • Stopping: Status in which the MongoDB Server is being stopped
   • Restarting: Status in which the MongoDB Server is being restarted

Deleting MongoDB Server

You can delete a MongoDB Server that has been created and is in operation. If you're using the replica set or sharding type clusters, then all of the clusters are deleted together. 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 Menu > Services > Database > Cloud DB for MongoDB.
2. Click the DB Server menu.
3. Click the MongoDB Server you want to delete and click [Delete DB Server].
4. When the Delete DB Server popup window appears, enter the name of the DB Server to delete, and then click [Yes].
5. Check the status of the MongoDB Server from the MongoDB Server list in the DB Server page.
   • Deleting: Status in which the MongoDB Server is being deleted

Monitoring MongoDB Server

NAVER Cloud Platform's Cloud DB for MongoDB 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 MongoDB Server 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 MongoDB.
2. Click the DB Server menu.
3. Click the MongoDB Server you want to monitor, and then click [Monitoring].
4. Click and select the dashboard you want to monitor.
   

MongoDB Server management

While operating the created MongoDB Server, you may need to change the options of the server or DB configured upon creation. Cloud DB for MongoDB supports changes or upgrades of a certain number of specifications simply through a few clicks, even for MongoDB Server that have already been created.

To manage a MongoDB Server 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 MongoDB.
2. Click the MongoDB Server menu.
3. Click the MongoDB Server you want to manage, and then click [Manage DB].
4. Click and select the item you want to manage.
   
   • Manage DB user
   • Manage admin user
   • Change secondary
   • Add shards
   • Change mongos
   • Change config server
   • Change DB specifications
   • Manage public domain
   • Primary DB Failover
   • MongoDB Engine Upgrade
   • Create DB access string

Manage DB user

Cloud DB for MongoDB provides a user management feature that enables you to conveniently add, edit, and delete user accounts that use the server. You can add up to 10 user accounts at each time of creation, change, or deletion.

To add, edit, and delete user accounts:

1. When the Manage DB user popup window appears, perform the required tasks for the user account.
   
   • Add user account: Select Create, enter the information for USER_ID, database, DB permissions, and password, and then click [Add DB user]
   • Delete user account: Select Change/delete, and then click [Delete] in the same row as the user account to be deleted
   • Edit user account information: Select Change/delete in the same row as the user account to be modified, and then click [Edit] to edit, and click [Save]
2. Click [Yes].
3. Check the status of a MongoDB for which you've set users from the MongoDB list in the DB Server page.
   • Configuring: Status in which the MongoDB Server is being configured with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

Manage admin user

When creating a MongoDB Server, the ID and password for the server admin account are created by default. However, while operating the server, you may need to reset the password of the admin account.

To change the admin account password, enter the new password in the Admin user management popup window, and then click [Yes].

Change secondary

You can change the Member server configuration of the replica set (shard), including the config server.

To change a secondary server:

1. When the Change secondary (arbiter) popup window appears, check the number of current secondary (arbiter) servers.
2. Click and select the quantity you want to change to.
   
3. Click [OK].
4. Check the status of MongoDB for which you changed the secondary from the MongoDB list in the DB Server page.
   • Creating: Status in which the MongoDB is being created with the information entered by the user
   • Configuring: Status in which the MongoDB Server is being configured with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

Add shards

You can add up to 5 Shards within the MongoDB Service.

To add shards:

1. When the Add shards popup window appears, check the current number of Shards.
2. Click and select the number of shards you want to change to.
   
3. Click [Yes].
4. Check the status of a MongoDB that added shards from the MongoDB Server list in the DB Server page.
   • Creating: Status in which the MongoDB is being created with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

Change Mongos

You can change the number of Mongos in the MongoDB Service. The number of Mongos can be configured from a minimum of 2 to a maximum of 5.

To change the number of Mongos:

1. When the Change number of Mongos popup window appears, check the current number of mongos servers.
2. Click and select the number of mongos servers you want to change to.
   
3. Click [OK].
4. Check the status of a MongoDB for which you changed mongos count from the MongoDB list in the DB Server page.
   • Creating: Status in which the MongoDB is being created with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

Change config server

You can change the number of config server for the MongoDB Service. The number of config server can be from a minimum of 3 to a maximum of 7.

To change the number of config server:

1. When the Change number of config server popup window appears, view the number of config server.
2. Click and select the quantity you want to change to.
   
3. Click [OK].
4. Check the status of a MongoDB for which you changed the number of config servers from the MongoDB list in the DB Server page.
   • Creating: Status in which the MongoDB is being created with the information entered by the user
   • Configuring: Status in which the MongoDB Server is being configured with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

Change DB specifications

You can change the server specifications for the MongoDB Server you’ve created. Additional fees are incurred when applying specifications upgrades.

To change the specifications:

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

Manage public domain

You can allocate or remove public domains required for external access to MongoDB Server.

1. When the Manage public domain or Remove public domain popup window appears, check the name of the DB Server you'll allocate a public domain to or remove a domain from.
   
2. Click [Yes].
3. Check the status of a MongoDB for which you allocated or removed a public domain from the MongoDB list in the DB Server page.
   • Configuring: Status in which the MongoDB Server is being configured with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available
4. The editing of the host file is required for replica sets.
   See Create DB access string.

Primary DB Failover

If the primary MongoDB Server fails, then the user can directly use the failover feature to stepdown the primary server. During the process of the primary being elected again, the primary may not exist for several seconds or longer, which may have an effect on service.

To stepdown the primary server:

1. When the Primary DB failover popup window appears, check the selected server and the shard number.
   
2. Click [Yes].
3. Check the MongoDB's DB role from the MongoDB list in the DB Server page.
   • Configuring: Status in which the MongoDB Server is being configured with the information entered by the user
   • Running: Status in which the configuration of the MongoDB Server has been completed with the information entered by the user, and access to MongoDB from the application servers is available

MongoDB Engine Upgrade

You can upgrade the MongoDB version. The version upgrade is applied to the entire DB Service.
When the version is updated, a temporary disruption may occur due to a failover, and you will be notified by SMS and email.
In the case of that there is a sharding cluster, the upgrade proceeds one by one in the order of config -> shard -> mongos.
All replica sets (config and shard in replica set cluster and sharding cluster) are upgraded in the order of secondary/arbiter -> primary.
During the upgrade, the target server access is not available, and when upgrading the primary server, it is switched to secondary to keep service access to a minimum.

1. Click DB management > version upgrade.
2. Select the version to upgrade and click [Yes].
   
3. If a major version upgrade is required, you can select a higher major version by checking [Major version upgrade].

Create DB access string

You can create a sample of a string required for external access to MongoDB Servers.

To create an access string:

1. When the Create DB access string popup window appears, check the created string.
2. Edit the client's host file to access a replica set through a public domain.
   • You can access it using the access string after adding the viewed information to the hosts file.
   • If the replica set is not using a public domain, you cannot view host file information.
     
3. Click [OK].

Manage operation system

Update the operating system of the DB Server to the latest version provided by NAVER Cloud Platform.
The operating system update is applied to the entire DB Service and proceeds one server at a time in the following order: secondary -> arbiter -> primary -> Mongos. To update the primary DB Server, you need to use the [Failover and OS upgrade] button. For more information, see the guide below.

Updating the operating system of the secondary server

Secondary and arbiter servers are updated one at a time, and access to the servers is blocked while the update is in progress.
In the case of replica sets, all secondary and arbiter servers are updated, and in the case of sharding, all secondary and arbiter servers in the shard and config server are updated.

1. To update the server's operating system version, click OS management, review the popup window, and then click [Next].

• Operating System Update
  
• Kernel Update
  

2. After reviewing the precautions for the operating system update, click the checkbox.
3. Once you’ve confirmed all items, click [Upgrade].

• Operating System Update
  
• Kernel Update
  

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

Updating the operating system of the primary server

After performing a failover, update the OS of the secondary (prior primary) server.
In the case of replica sets, 1 primary server is updated, and in the case of sharding, all primary servers and Mongos servers in the shard and config server are updated.

1. To update the operating system version of the primary and Mongos server, select the primary server and click [Failover and OS upgrade].
   

2. After reviewing the precautions for updating the primary server’s OS, click [Upgrade].
   

3. You can monitor the update progress through the DB Server status.