This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Overview

1: Server Types
2: Monitoring metrics

Service Overview

CacheStore(DBaaS) is a service that provides the in-memory data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that automates the installation of Redis OSS and valkey through a web-based console and performs management functions for operation.

CacheStore (DBaaS) provides a Sentinel architecture consisting of a Master server that performs read/write operations and read‑only Replica servers that replicate the Master data. Sentinel checks the status of DB servers with the engine installed, and when a failure occurs on the Master server, it automatically fails over the Replica servers to the Master server. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, enabling data recovery based on the backup point.

Provided Features

CacheStore(DBaaS) provides the following features.

Auto Provisioning(Auto Provisioning): It is possible to install and configure the Database (DB) via the UI, and a redundant configuration can be set up with a Sentinel-based Single Master server and Replica servers (1 or 2).
Operation Control Feature: Provides a function to control the status of running servers. * In addition to start and stop, you can restart if there is a DB issue or to apply configuration changes. * When configured for high availability (HA), you can switch the Active-Standby servers via a switch-over.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be set by the user, and additional fees apply based on backup size. * It also provides a recovery function for backed‑up data, so when the user performs a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user.
Parameter Management: Performance improvement and security-related DB configuration parameters can be modified.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, and DB performance monitoring information can be viewed through the Cloud Monitoring service.
Minor version upgrade: To apply some feature improvements and security patches, you can perform a Minor version upgrade within the same Major version.

Component

CacheStore (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it according to 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.

Since the EOS and EoTS dates may change according to the supplier’s policy, 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	2029-06 (planned)	2029-12-01
valkey Sentinel	8.1.4	TBD	TBD

Table. CacheStore (DBaaS) provided engine versions

information

The next version of CacehStore is scheduled to be offered after July 2026. The actual service delivery schedule is subject to change.

Redis OSS Sentienl 7.2.14
Valkey Sentienl 8.1.7

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

Standard redis1v2m4

Category	example	Detailed description
Server type	Standard	Provided server type Standard: commonly used standard specifications (vCPU, Memory) configuration
Server specifications	redis1	Provided server specifications redis1: Standard specifications (vCPU, Memory) commonly used
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. CacheStore (DBaaS) server type components

Preceding 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 and prepare in advance.

Service Category	service	Detailed description
Networking	VPC	A service that provides an isolated virtual network in a cloud environment

Table. CacheStore (DBaaS) Preceding Service

1 - Server Types

CacheStore(DBaaS) server type

CacheStore(DBaaS) offers server types composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating a CacheStore (DBaaS), Redis is installed according to the server type selected for the intended use.

The server types supported by CacheStore(DBaaS) are as follows.

Standard redis1v2m4

Category	example	Detailed description
Server type	Standard	Provided server type classification Standard: Configured with the commonly used standard specifications (vCPU, Memory)
Server specifications	redis1	Provided server type classification and generation redis: means standard specifications, and 1 indicates the generation
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. CacheStore (DBaaS) server type format

redis1 server type

The redis1 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	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

Table. CacheStore (DBaaS) server type specifications - redis1 server type

css1 server type

The css1 server type of CacheStore (DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	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 specifications - css1 server type

2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
  Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
  - You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.

Offering	Region	Cloud Monitoring console URL
Enterprise	kr-west1	https://console.kr-west1.e.samsungsdscloud.com/console/monitoring
Enterprise	kr-east1	https://console.kr-east1.e.samsungsdscloud.com/console/monitoring
Samsung	kr-west1	https://console.kr-west1.s.samsungsdscloud.com/console/monitoring
Samsung	kr-east1	https://console.kr-east1.s.samsungsdscloud.com/console/monitoring
Sovereign	kr-south1	https://console.kr-south1.g.samsungsdscloud.com/console/monitoring
Sovereign	kr-south2	https://console.kr-south2.g.samsungscloud.com/console/monitoring
Sovereign	kr-south3	https://console.kr-south3.g.samsungscloud.com/console/monitoring

Table. Cloud Monitoring console URL by region

Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
  - After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch 개요.

CacheStore(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics for CacheStore (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

For CacheStore (DBaaS) server monitoring metrics, refer to the Virtual Server Monitoring Metrics guide.

Performance items	Detailed description	unit
Active Defragmentation Keys [Hits]	Number of keys after defragmentation	cnt
Active Defragmentation Keys [Miss]	Number of keys skipped in the active defragmentation removal process	cnt
Active Defragmentationd [Hits]	Number of value reallocations performed by the active defragmentation removal process	cnt
Active Defragmentations [Miss]	Count of value reallocations interrupted by the active defragmentation removal 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 bytes allocated by CacheStore (DBaaS)	bytes
AOF Buffer Size	AOF buffer size	bytes
AOF File Size [Current]	AOF current file size	bytes
AOF File Size [Lastest Startup]	AOF file size on recent start or rewrite	bytes
AOF Rewrite Buffer Size	AOF rewrite buffer size	bytes
AOF Rewrite Current Time	If applicable, the time of the ongoing AOF rewrite operation	sec
AOF Rewrite Last Time	Final AOF rewrite time	sec
Calls	Number of calls that reached command execution (not rejected)	cnt
Changes [Last Saved]	Number of changes after the final 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 pending on 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 final RBD save operation	bytes
Copy On Write Allocated Size [RDB]	COW allocation size during the final RBD 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 on the CacheStore (DBaaS) server	%
CPU Usage [User Process]	User CPU usage used 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 caused by the maxmemory limit	cnt
Fsyncs [Delayed]	Delayed fsync counter	cnt
Fsyncs [Pending]	Number of pending fsync operations in the background I/O queue	cnt
Full Resyncs	Number of full resynchronizations with the slave	cnt
Keys [Expired]	Total number of key expiration events	cnt
Keys [Keyspace]	Number of keys in the key space	cnt
Lastest Fork Duration Time	Recent fork (fork) operation time	usec
Lookup Keys [Hit]	Number of successful key lookups in the 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 elapsed since the final interaction with the master	sec
Master Last Interaction Time Ago [Sync]	Time elapsed since the final 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	Remaining bytes before synchronization completes	bytes
Memory Fragmentation Rate	Ratio of used_memory_rss to used_memory	%
Memory Fragmentation Rate [Allocator]	Fragmentation ratio	%
Memory Fragmentation Used	Bytes between used_memory_rss and used_memory	bytes
Memory Fragmentation Used [Allocator]	resident byte	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 byte	bytes
Network In Bytes [Total]	Total network input (bytes)	bytes
Network Out Bytes [Total]	Total network output (bytes)	bytes
Network Read Rate	Network read speed (KB/sec)	cnt
Network Write Rate	Network write speed (KB/sec)	cnt
Partial Resync Requests [Accepted]	Number of accepted partial resynchronization requests	cnt
Partial Resync Requests [Denied]	Number of rejected 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 count of pub/sub channels with client subscriptions	cnt
Pub/Sub Patterns	Global count of publish/subscribe patterns with client subscriptions	cnt
RDB Saved Duration Time [Current]	If applicable, the time of the ongoing RDB save operation	sec
RDB Saved Duration Time [Last]	Final RDB save operation time	sec
Received Connections [Total]	Total number of received connections	cnt
Rejected Connections [Total]	Total number of rejected connections	cnt
Replication Backlog Actove Count	Replication backlog activation flag	cnt
Replication Backlog Master Offset	Master offset of the replication backlog buffer	cnt
Replication Backlog Size	Data size of the replication backlog buffer	bytes
Replication Backlog Size [Total]	Total size of the replication backlog buffer	bytes
Slave Priority	Server priority as a fault remediation target	cnt
Slave Replication Offset	Replication offset of the slave server	pid
Slow Operations	Number of slow tasks	cnt
Sockets [MIGRATE]	Number of sockets opened for migration	cnt
Tracked Keys [Expiry]	Number of keys tracked for expiration (applicable only to writable slaves)	cnt
Instance Status [PID]	redis-server process PID	pid
Sentinel Status [PID]	sentinel process PID	pid

Table. CacheStore (DBaaS) Monitoring Metrics