This is the multi-page printable view of this section. Click here to print.
CacheStore(DBaaS)
1 - Overview
Service Overview
CacheStore(DBaaS) is a service that provides the in‑memory based data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that can automate the installation of Redis OSS and Valkey through a web‑based console and perform management functions for operation.
CacheStore (DBaaS) provides a Sentinel method consisting of a Master server that performs read/write operations and read-only Replica servers that replicate Master data. Sentinel checks the status of DB servers where the engine is installed, and if a failure occurs on the Master server, it automatically failovers the Replica servers to become the Master server. Additionally, to prepare for issues with the DB server or data, it offers a function that automatically backs up at a user-specified time, supporting data recovery based on the backup point.
Provided Features
CacheStore(DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and a redundant configuration is possible with a Sentinel-based Single Master server and Replica server (1 or 2).
- Operation Control Function: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), you can switch Active-Standby servers via Switch-over.
- Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage agency can be set by the user, and additional fees are incurred depending on the backup volume. It also provides a recovery function for backed-up data, so when the user performs a recovery, a separate DB is created and the recovery proceeds to the point in time selected by the user.
- Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
- Service status query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
Components
CacheStore (DBaaS) provides pre‑validated engine versions and various server types according to the open‑source support policy. Users can select and use them based on the scale of the service they wish to configure.
Engine Version
The engine versions supported by CacheStore(DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.
| Image | Provided Version | EoS Date | EoTS Date |
|---|---|---|---|
| Redis OSS Sentinel | 7.2.11 | TBD | TBD |
| valkey Sentinel | 8.1.4 | TBD | TBD |
Server Type
The server types supported by CacheStore (DBaaS) are as follows.
For detailed information about the server types provided by CacheStore(DBaaS), see CacheStore(DBaaS) server type.
Standard redis1v2m4
Category
Example
Detailed description
Server Type
Standard
Provided Server Type- Standard: Standard specifications (vCPU, Memory) configuration commonly used
Server specifications
redis1
Provided server specifications- redis1: Standard specifications (vCPU, Memory) configuration commonly used
Server Specification
v2
Number of vCores- v2: 2 virtual cores
Server specifications
m4
Memory capacity- m4: 4GB Memory
Table. CacheStore(DBaaS) Server Type Components
# Preliminary Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service for details and prepare in advance.<br>
Service Category
Service
Detailed Description
Networking
VPC
A service that provides an independent virtual network in a cloud environment
Table. CacheStore(DBaaS) Preliminary Service
1.1 - Server Type
CacheStore(DBaaS) server type
CacheStore(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating CacheStore(DBaaS), Redis is installed according to the selected server type suitable for the purpose of use.
The server types supported by CacheStore(DBaaS) are as follows.
Standard redis1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Provided server type distinction
|
| Server Specification | redis1 | Provided server type distinction and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specification | m4 | Memory capacity
|
redis1 server type
The redis1 server type of CacheStore(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 256 GB of memory Up to 12.5 Gbps of networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | redis1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | redis1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | redis1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | redis1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | redis1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | redis1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | redis1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | redis1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | redis1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | redis1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | redis1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | redis1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | redis1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | redis1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | redis1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | redis1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | redis1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
css1 server type
The css1 server type of CacheStore(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 256 GB of memory Up to 12.5 Gbps of networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | css1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | css1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | css1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | css1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | css1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | css1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | css1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | css1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | css1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | css1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | css1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | css1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | css1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | css1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | css1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | css1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | css1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
| Table. CacheStore(DBaaS) server type specification - css1 server type |
1.2 - Monitoring Metrics
CacheStore(DBaaS) Monitoring Metrics
The following table shows the performance monitoring metrics of CacheStore(DBaaS) that can be checked through Cloud Monitoring. For detailed instructions on using Cloud Monitoring, refer to the Cloud Monitoring guide.
For server monitoring metrics of CacheStore(DBaaS), refer to the Virtual Server Monitoring Metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Defragmentation Keys [Hits] | Number of keys defragmented | cnt |
| Active Defragmentation Keys [Miss] | Number of keys skipped in the active defragmentation process | cnt |
| Active Defragmentationd [Hits] | Number of value reassignments performed by the active defragmentation process | cnt |
| Active Defragmentations [Miss] | Number of value reassignments started and aborted by the active defragmentation process | cnt |
| Allocated Bytes [OS] | Number of bytes allocated by CacheStore(DBaaS) and recognized by the operating system (resident set size) | bytes |
| Allocated Bytes [Redis] | Total number of bytes allocated by CacheStore(DBaaS) | bytes |
| AOF Buffer Size | AOF buffer size | bytes |
| AOF File Size [Current] | Current AOF file size | bytes |
| AOF File Size [Lastest Startup] | AOF file size at the latest startup or rewrite | bytes |
| AOF Rewrite Buffer Size | AOF rewrite buffer size | bytes |
| AOF Rewrite Current Time | Time of the ongoing AOF rewrite operation, if any | sec |
| AOF Rewrite Last Time | Time of the last AOF rewrite operation | sec |
| Calls | Number of calls that reached command execution (not rejected) | cnt |
| Changes [Last Saved] | Number of changes since the last dump | cnt |
| Client Output Buffer [MAX] | Longest output list among current client connections | cnt |
| Clients [Sentinel] | Number of client connections (Sentinel) | cnt |
| Connected Slaves | Number of connected slaves | cnt |
| Connections [Blocked] | Number of clients waiting for blocking calls (BLPOP, BRPOP, BRPOPLPUSH) | cnt |
| Connections [Current] | Number of client connections (excluding slave connections) | cnt |
| Copy On Write Allocated Size [AOF] | COW allocation size during the last RDB save operation | bytes |
| Copy On Write Allocated Size [RDB] | COW allocation size during the last RDB save operation | bytes |
| CPU Time [Average] | Average CPU time used per command execution | cnt |
| CPU Time [Total] | Total CPU time used by these commands | usec |
| CPU Usage [System Process] | System CPU usage by background processes | % |
| CPU Usage [System] | System CPU usage by the CacheStore(DBaaS) server | % |
| CPU Usage [User Process] | User CPU usage by background processes | % |
| CPU Usage [User] | System CPU usage by background processes | % |
| Dataset Used | Dataset size | bytes |
| Disk Used | Datadir usage | MB |
| Evicted Keys | Number of evicted keys due to maxmemory limit | cnt |
| Fsyncs [Delayed] | Delayed fsync counter | cnt |
| Fsyncs [Pending] | Number of fsync operations pending in the background I/O queue | cnt |
| Full Resyncs | Number of full resynchronizations with slaves | cnt |
| Keys [Expired] | Total number of key expiration events | cnt |
| Keys [Keyspace] | Number of keys in the keyspace | cnt |
| Lastest Fork Duration Time | Time of the latest fork (fork) operation | usec |
| Lookup Keys [Hit] | Number of successful key lookups in the main dictionary | cnt |
| Lookup Keys [Miss] | Number of failed key lookups in the main dictionary | cnt |
| Lua Engine Memory Used | Memory used by the Lua engine | bytes |
| Master Last Interaction Time Ago | Time since the last interaction with the master | sec |
| Master Last Interaction Time Ago [Sync] | Time since the last interaction with the master | sec |
| Master Offset | Current replication offset of the server | pid |
| Master Second Offset | Offset until the replication ID is accepted | pid |
| Master Sync Left Bytes | Number of bytes left to synchronize | bytes |
| Memory Fragmentation Rate | Ratio of used_memory_rss to used_memory | % |
| Memory Fragmentation Rate [Allocator] | Fragmentation ratio | % |
| Memory Fragmentation Used | Difference between used_memory_rss and used_memory in bytes | bytes |
| Memory Fragmentation Used [Allocator] | Resident bytes | bytes |
| Memory Max Value | Memory limit | bytes |
| Memory Resident [Allocator] | Resident memory | bytes |
| Memory RSS Rate [Allocator] | Resident ratio | % |
| Memory Used [Active] | Active memory | bytes |
| Memory Used [Allocated] | Allocated memory | bytes |
| Memory Used [Resident] | Resident bytes | bytes |
| Network In Bytes [Total] | Total network input (bytes) | bytes |
| Network Out Bytes [Total] | Total network output (bytes) | bytes |
| Network Read Rate | Network read rate per second (KB/sec) | cnt |
| Network Write Rate | Network write rate per second (KB/sec) | cnt |
| Partial Resync Requests [Accepted] | Number of accepted partial resynchronization requests | cnt |
| Partial Resync Requests [Denied] | Number of denied partial resynchronization requests | cnt |
| Peak Memory Consumed | Maximum memory used by CacheStore(DBaaS) | bytes |
| Processed Commands | Number of commands processed per second | cnt |
| Processed Commands [Total] | Total number of processed commands | cnt |
| Pub/Sub Channels | Global number of pub/sub channels with client subscriptions | cnt |
| Pub/Sub Patterns | Global number of pub/sub patterns with client subscriptions | cnt |
| RDB Saved Duration Time [Current] | Time of the ongoing RDB save operation, if any | sec |
| RDB Saved Duration Time [Last] | Time of the last RDB save operation | sec |
| Received Connections [Total] | Total number of received connections | cnt |
| Rejected Connections [Total] | Total number of rejected connections | cnt |
| Replication Backlog Actove Count | Flag indicating whether replication backlog is active | cnt |
| Replication Backlog Master Offset | Master offset of the replication backlog buffer | cnt |
| Replication Backlog Size | Size of data in the replication backlog buffer | bytes |
| Replication Backlog Size [Total] | Total size of the replication backlog buffer | bytes |
| Slave Priority | Priority of the server as a failover target | cnt |
| Slave Replication Offset | Replication offset of the slave server | pid |
| Slow Operations | Number of slow operations | cnt |
| Sockets [MIGRATE] | Number of sockets open for migration | cnt |
| Tracked Keys [Expiry] | Number of keys tracked for expiration (only for writable slaves) | cnt |
| Instance Status [PID] | PID of the redis-server process | pid |
| Sentinel Status [PID] | PID of the sentinel process | pid |
2 - How-to guides
The user can enter the necessary information of CacheStore(DBaaS) through the Samsung Cloud Platform Console and create the service by selecting detailed options.
Creating CacheStore(DBaaS)
You can create and use the CacheStore(DBaaS) service in the Samsung Cloud Platform Console.
Please configure the Subnet type of VPC to General before creating the service.
- If the Subnet type is Local, the creation of the corresponding Database service is not allowed.
To create a CacheStore(DBaaS), follow these steps.
Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
On the Service Home page, click the CacheStore(DBaaS) creation button. It moves to the CacheStore(DBaaS) creation page.
CacheStore(DBaaS) creation page, enter the information required for service creation and select detailed options.
Image and Version Selection area, please select the necessary information.
Classification NecessityDetailed Description Image Version Required Provides a list of CacheStore (DBaaS) versions Fig. CacheStore(DBaaS) image and version selection itemsEnter Service Information Enter or select the required information in the area.
Classification NecessityDetailed Description Server Name Prefix Required Server name where Redis/Valkey will be installed - Starts with lowercase English letters, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (
-)
- A postfix such as 001, 002 is attached based on the server name to create the actual server name
Cluster Name Required Name of the cluster where Redis/Valkey is installed - Enter in English, 3-20 characters
- Cluster is a unit that bundles multiple servers
Service Type > Server Type Required Server type where Redis/Valkey will be installed - Standard: Standard specification commonly used
- For more information on the server types provided by CacheStore(DBaaS), refer to CacheStore(DBaaS) Server Type
Service Type > Planned Compute Required Current status of resources with Planned Compute set - In Use: Number of resources with Planned Compute set that are currently in use
- Settings: Number of resources with Planned Compute set
- Coverage Preview: Amount applied by Planned Compute for each resource
- Create Planned Compute Service: Move to the Planned Compute service application page
- For more information, refer to Apply for Planned Compute
Service Type > Block Storage Required Block Storage settings used by DB according to purpose - Basic OS: Area where DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Please select the storage type and enter the capacity. (For more information on each Block Storage type, see Creating Block Storage)
- SSD: High-performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption key
- The set Storage type will be applied equally to additional storage
- Capacity should be entered in multiples of 8 within the range of 16 to 5,120
- Please select the storage type and enter the capacity. (For more information on each Block Storage type, see Creating Block Storage)
High Availability Optional Whether to configure High Availability (HA) - Using High Availability (HA) configuration provides Master-Replica configuration, and Replica can be configured with 1 or 2
- Sentinel Port Number: Port number used when connecting to Sentinel
- Port for Master-Replica communication, enter within the range of 1,024 to 65,535
- Number of Replicas: Number of Replicas to be configured
- If 1 is selected, it is configured as Master-Replica-Sentinel
- If 2 is selected, it is configured as Master-Replica-Replica, and Sentinel is automatically installed on the server where Redis is installed
- The server type of Sentinel is set to the minimum specification
Network Required The network where CacheStore(DBaaS) is installed - Select and connect the pre-created VPC and Subnet
- IP can only be generated automatically
Network > Common Settings Required Network settings for servers created by the service - Select if you want to apply the same settings to all servers being installed
- Select pre-created VPC and Subnet
- IP can only be generated automatically
Network > Server-specific settings Required Network settings for servers created by the service - Select to apply different settings for each server being installed
- Select pre-created VPC and Subnet, IP, Public NAT
- Enter the IP for each server
- The Public NAT function is only available if the VPC is connected to the Internet Gateway. If Use is checked, you can select from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
IP Access Control Select Set service access policy - Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32), and click the Add button
- To delete the entered IP, click the x button next to the entered IP
Maintenance period Selection CacheStore(DBaaS) maintenance period - Use is selected to set the day of the week, start time, and duration
- It is recommended to set the maintenance period for stable DB management, and patch work is performed at the set time, resulting in service interruption
- If not used, Samsung SDS is not responsible for any problems that occur due to non-application of patches
Fig. CacheStore(DBaaS) Service Configuration Items- Starts with lowercase English letters, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (
Database Configuration Required Information Input area, please enter or select the required information.
Classification NecessityDetailed Description Backup Selection Whether to use backup - Use is selected to set the backup file storage period and backup start time
- Backup files are charged separately according to capacity
- The file storage period can be set from 7 to 35 days
- The minute (minutes) when the backup is performed is set randomly, and the backup end time cannot be set
Redis/Valkey Port number mandatory Port number required for Redis/Valkey connection - Port must be entered within the range of 1,024 ~ 65,535
Redis/Valkey password mandatory Password required when connecting to Redis/Valkey - Enter 8-30 characters, including English, numbers, and special characters (excluding
$"‘)
Redis/Valkey password confirmation required Re-enter the password identically Parameter Required Redis/Valkey parameters to use - Query button can be clicked to check detailed information of parameters
- Parameters can be modified after creation is completed, and DB restart is required after modification
Time Zone Required Time zone where the Database will be used Fig. CacheStore(DBaaS) Database Configuration ItemsEnter Additional Information Enter or select the required information in the area.
Classification MandatoryDetailed Description Tag Selection Add Tag - Up to 50 can be added per resource
- Click the Add Tag button and enter or select Key, Value
Table. Additional information input items for CacheStore(DBaaS)
In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
- Once creation is complete, check the created resource on the Resource List page.
Check CacheStore(DBaaS) detailed information
The CacheStore(DBaaS) service allows you to view and modify the entire resource list and detailed information. The CacheStore(DBaaS) details page consists of detailed information, tags, and operation history tabs.
To check the detailed information of the CacheStore(DBaaS) service, follow the next procedure.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- Service Home page, click the CacheStore(DBaaS) menu. Move to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to check the detailed information. Move to the CacheStore(DBaaS) details page.
- CacheStore(DBaaS) details page top shows status information and additional features.
| Division | Detailed Description |
|---|---|
| Cluster Status | Redis cluster status installed
|
| Cluster Control | Buttons that can change the cluster status
|
| Additional features more | Cluster-related management buttons
|
| Service Cancellation | A button to cancel the service |
Detailed Information
On the CacheStore(DBaaS) list page, you can check the detailed information of the selected resource and modify the information if necessary.
| Classification | Detailed Description |
|---|---|
| Server Information | Server information configured in the corresponding cluster
|
| Service | Service Name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource Name
|
| Resource ID | Unique resource ID in the service |
| Creator | The user who created the service |
| Creation Time | Time when the service was created |
| Modifier | Service information modified user |
| Modified Time | Time when service information was modified |
| Image/Version | Installed Redis/Valkey Image and Version Information |
| Cluster Name | Redis/Valkey server cluster name |
| Planned Compute | Planned Compute settings for current resources
|
| Maintenance period | DB patch work period setting status
|
| Backup | Backup setting status
|
| Redis/Valkey Port number | Port number required for Redis/Valkey connection |
| Time Zone | Redis/Valkey Time Zone |
| Sentinel Port number | Port number for Master and Replica to communicate |
| VIP | Virtual IP information
|
| Network | Network information (VPC, Subnet) where CacheStore (DBaaS) is installed |
| IP Access Control | Service Access Policy Setting
|
| Master & Replica | Master, Replica server type, default OS, additional Disk information
|
| Sentinel | Sentinel server type, basic OS information
|
Tag
On the CacheStore(DBaaS) list page, you can check the tag information of the selected resource, and add, change, or delete it.
| Classification | Detailed Description |
|---|---|
| Tag List | Tag list
|
Work History
CacheStore(DBaaS) list page where you can check the operation history of the selected resource.
| Division | Detailed Description |
|---|---|
| Work History List | Resource Change History
|
CacheStore(DBaaS) resource management
If you need to change or restore the existing setting options of the generated CacheStore(DBaaS) resource, or change the command, you can perform the task from the CacheStore(DBaaS) details page.
Operating Control
If changes occur in the running CacheStore (DBaaS) resource, you can start, stop, and restart it. Also, if HA is configured, you can switch the Master-Replica server through Switch-over.
To control the operation of CacheStore(DBaaS), follow the next procedure.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to control the operation. Move to the CacheStore(DBaaS) details page.
- Check the CacheStore status and complete the change through the control button below.
- Start: The CacheStore service is installed on the server and the CacheStore service is running.
- Stop: CacheStore service can stop the server where CacheStore service is installed.
- Restart: Only the CacheStore service can be restarted.
- Switch Over: You can switch between the Master server and the Replica server.
Synchronizing Service Status
You can synchronize the real-time service status of CacheStore(DBaaS).
To check the service status of CacheStore(DBaaS), follow the next procedure.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to query the service status. Move to the CacheStore(DBaaS) details page.
- Click the 서비스 상태 동기화 button. During the query, the cluster changes to Synchronizing status.
- When the query is complete, the status is updated in the server information item, and the cluster changes to Running status.
Changing Server Type
You can change the configured server type.
To change the server type, follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- On the CacheStore(DBaaS) list page, click the resource you want to change the server type for. It moves to the CacheStore(DBaaS) details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window opens.
- In the Server Type Modification popup window, select the server type and click the OK button.
Cancel CacheStore(DBaaS)
You can cancel unused CacheStore (DBaaS) to reduce operating costs. However, when canceling the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.
To cancel CacheStore(DBaaS), follow the procedure below.
- All Services > Database > CacheStore(DBaaS) menu is clicked. It moves to the Service Home page of CacheStore(DBaaS).
- Service Home page, click the CacheStore(DBaaS) menu. Move to the CacheStore(DBaaS) list page.
- On the CacheStore(DBaaS) list page, select the resource to be canceled and click the Service Cancellation button.
- Once the cancellation is complete, please check if the resource has been cancelled on the CacheStore(DBaaS) list page.
2.1 - Managing CacheStore Service
Users can manage CacheStore (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
It provides a feature to easily view and modify database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps:
- Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
- Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
- Click the resource you want to view and modify parameters on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
Modifying Parameters
To modify configuration parameters, follow these steps:
- Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
- Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
- Click the resource you want to view and modify parameters on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the parameter to be modified.
- When the input is complete, click the Save button.
Renaming Commands
It provides a function to view and modify Redis OSS/Valkey Command names. To view and modify Command names, follow these steps:
- Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
- Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
- Click the resource you want to modify the Command name on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
- Click the More button and then click the Rename-Command button. It moves to the Rename-Command page.
- Click the View button on the Rename-Command page. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the Command to be modified.
- When the input is complete, click the Complete button.
2.2 - CacheStore Backup and Recovery
The user can set up backups of CacheStore(DBaaS) through the Samsung Cloud Platform Console and recover with the backed-up files.
CacheStore(DBaaS) backup
CacheStore(DBaaS) provides a data backup function based on its own backup command. It also provides an optimized backup environment for data protection and management through backup history check and backup file deletion functions.
Setting up backup
The method of setting up a backup for CacheStore(DBaaS) is described in CacheStore(DBaaS) creation guide, please refer to it.
To modify the backup settings of the generated resource, follow these steps.
If backup is set, backup will be performed at the specified time after the set time, and additional fees will be incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the stored backup data will be deleted and can no longer be used.
- All Services > Database > CacheStore(DBaaS) menu, click. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to set the backup. It moves to the CacheStore(DBaaS) detail page.
- Click the Edit icon of the backup item. The Backup Settings popup window opens.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
- If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.
Check Backup History
To check the backup history, follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to check the backup history. It moves to the CacheStore(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Deleting Backup Files
To delete the backup history, follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to check the backup history. It moves to the CacheStore(DBaaS) detail page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the file you want to delete and click the Delete button.
CachStore(DBaaS) recovery
In the event of a failure or data loss, where recovery from a backup file is necessary, the recovery function allows recovery based on a specific point in time.
To recover CacheStore(DBaaS), follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource you want to restore. It moves to the CacheStore(DBaaS) details page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- After entering information in the Database recovery configuration area, click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | User sets the point in time to recover
|
| Server name prefix | Required | Server name of the recovery DB
|
| Cluster Name | Required | Cluster name of the recovery DB
|
| Service Type > Server Type | Required | Server type where the recovery DB will be installed
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Block Storage setting used by recovery DB
|
| Redis/Valkey Port number | required | Redis/Valkey Port number set in the original DB |
| IP Access Control | Select | Set service access policy
|
| Maintenance period | Select | CacheStore(DBaaS) DB maintenance period
|
| Tag | Selection | Add Tag
|
2.3 - CacheStore(DBaaS) server connection
Scenario Overview
CacheStore(DBaaS) connection scenario is a scenario where Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To connect to CacheStore (DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, allowing access through a DB connection client.
Scenario Components
You can configure the scenario using the following services.
| Service Group | Service | Detailed Description | |
|---|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that allows users to subdivide the network according to purpose,size in VPC | |
| Networking | VPC > Public IP | A service that reserves public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | CacheStore(DBaaS) | A service that easily creates and manages CacheStore in a web environment | |
| Compute | Virtual Server | Cloud computing optimized virtual server | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- The default policy of Security Group is Deny All, so only allowed IPs should be registered.
- In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources to external threats.
- By specifying the necessary IP and Port to set the policy, you can enhance security.
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This describes the process of configuring the network environment for connecting to the Bastion Host and Database services.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information required for service creation.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource on the VPC list page.
1-2. Creating a Subnet
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet Creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
- Once creation is complete, check the created resource on the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. Move to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select Use in the Firewall usage item.
- In the Summary panel, review the detailed information and the estimated charge amount, and then click the Complete button.
- Once the creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Public IP menu. It moves to the Public IP list page.
- Public IP Reservation 버튼을 클릭하세요. Public IP Reservation 페이지로 이동합니다.
- Public IP Reservation page, please enter the required information necessary for service reservation.
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource on the Public IP list page.
1-5. Creating a Security Group
- Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Create Security Group button. Move to the Create Security Group page.
- Security Group Creation page, please enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion host
This describes the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating a Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Keypair menu. It moves to the Keypair list page.
- Create Keypair button will be clicked. It moves to the Create Keypair page.
- Keypair creation page where you enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key download is only available for the first time, and re-issuance is not provided.
- Please make sure to store the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server creation button. Move to the Virtual Server creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- Image is Windows, please select.
- Please select the pre-created VPC and Subnet.
- Click NAT and select the Public IP reserved in 1-4. Public IP 생성하기.
- 2-1. Creating Server Keypair Connect the Keypair created from 2-1. 서버 Keypair 생성하기.
- In the Summary panel, review the detailed information and estimated billing amount, and click the Complete button.
- Once the creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Server Keypair creation.
- After attaching, click the Password confirmation button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to connect to the Bastion host later in 5-1. Connect to Bastion host.
3. Creating a Database
It describes the process of creating a Database service.
3-1. Creating CacheStore (DBaaS) Service
- All services > Database > CacheStore(DBaaS) menu is clicked. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) creation button. It moves to the CacheStore(DBaaS) creation page.
- CacheStore(DBaaS) creation page, please enter the required information needed for service creation.
- Select and connect to the pre-created VPC and Subnet.
- Enter database-related creation information on the essential information input screen.
- Add the Bastion host IP to the IP access control item.
- Database Port is 2866 by default, but users can also specify it.
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource on the CacheStore(DBaaS) list page.
4. Setting Rules
This describes the process of setting rules for users to access the Bastion host and for the Bastion host to access the Database.
4-1. Security Group Add Security Rules
- Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from 1-5. Creating a Security Group. It moves to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab, click the Add Rule button. It moves to the Add Rule popup window.
- In the Add Rule popup window, enter the following rules and click the OK button
| Direction | Remote | Target Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion connection PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Internet Gateway creation. It moves to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab, click the Add Rule button. Move to the Add Rule popup window.
- In the Add Rule popup window, enter the following rules and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion connection PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
5. Connecting to the Database
This explains the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using Another Redis Desktop Manager. There are various database client programs and CLI utilities, so you can also install and use the tools that are suitable for the user.
5-1. Connecting to the Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- When the remote desktop connection is successful, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Check Bastion host access ID and PW and click the Confirm button.
5-2. Install DB connection client program (Another Redis Desktop Manager) on the Bastion host
- Download another Redis Desktop Manager program.
- Another Redis Desktop Manager program download path: https://github.com/qishibo/AnotherRedisDesktopManager/releases
- Connect the hard drive of the user PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources items in the Local Resources tab of the remote desktop connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Download the file, copy it to the Bastion Host, and upload it, then click on the pgAdmin installation file to install it.
5-3. Using DB connection client program(Another Redis Desktop Manager) to connect to Database
- Run Another Redis Desktop Manager and click New Connection. The New Connection popup window will appear.
- New Connection popup window, enter the Database server information created in 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
Required Input Element Items Input Value Host Database Server IP Port Database Port Password Database password Connection Name Custom (ex. Service Name) DB Connection Client Program Input Items - After connecting, you can perform basic information checks on Redis, data management, and CRUD operations on keys.
3 - API Reference
4 - CLI Reference
5 - Release Note
CacheStore(DBaaS)
- CacheStore(DBaaS) feature added
- CacheStore(DBaaS) New Image Added
- Redis OSS was forked and developed as an open-source, Valkey image support
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see CacheStore(DBaaS) server type
- Backup Alert Feature provided
- Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
- Block Storage type added HDD, HDD_KMS type
- Samsung Cloud Platform common feature changes
- Account, IAM and Service Home, tags, etc. reflected common CX changes.
- The service name is changed to CacheStore(DBaaS).
- Block Storage type has an option to select encrypted storage for volumes added.
- The Role Switch (Active ↔ Standby) function has been added to the Active DB and Standby DB composed of duplication.
- The cloud monitoring service is linked, so DB instance performance and log monitoring are possible.
- Depending on the server type selected by the customer, Planned Compute policy setting is possible.
- A Redis(DBaaS) service that can easily create and manage Redis OSS in a web environment has been released.

