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 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 where the engine is installed and automatically fails over the Replica servers to become the Master server if a failure occurs on the Master server. Additionally, it provides an automatic backup feature at user‑specified times to prepare for issues with the DB server or data, allowing data recovery based on the backup point.
Provided Features
CacheStore(DBaaS) provides the following features.
- Auto Provisioning: It is possible to install and configure the Database (DB) via UI, and a redundant configuration with a Sentinel-based Single Master server and Replica server(s) (1 or 2) is possible.
- 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 based on backup size. It also provides a recovery function for backed-up data; 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: It is possible to modify DB configuration parameters related to performance improvement and security.
- 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.
- Minor version upgrade: Minor version upgrades can be performed within the same Major version to apply some feature improvements and security patches.
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 according to the scale of the service they want 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 6 months before the EoTS date.
Since the dates for EOS and EoTS may vary according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
- Redis: https://redis.io/docs/latest/operate/oss_and_stack/install/version-mgmt/
- Valkey: https://valkey.io/topics/releases/
| Image | Provided Version | EoS Date | EoTS Date |
|---|---|---|---|
| Redis OSS Sentinel | 7.2.11 | 2029-06 (planned) | 2029-12-31 |
| 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 Types.
Standard redis1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server Type | Standard | Provided Server Type
|
| Server Specifications | redis1 | Provided Server Specifications
|
| Server Specifications | v2 | Number of vCores
|
| Server Specifications | m4 | Memory Capacity
|
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 detailed information and prepare in advance.
| Service Category | Service | Detailed Description |
|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment |
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
Users can create CacheStore(DBaaS) by entering required information and selecting detailed options through the Samsung Cloud Platform Console.
Creating CacheStore(DBaaS)
You can create and use CacheStore(DBaaS) service through the Samsung Cloud Platform Console.
Before creating a service, configure the VPC Subnet type as General.
- If the Subnet type is Local, the Database service cannot be created.
To create CacheStore(DBaaS), follow these steps:
- Click the All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the Create CacheStore(DBaaS) button. It moves to the Create CacheStore(DBaaS) page.
- On the Create CacheStore(DBaaS) page, enter the information required for service creation and select detailed options.
- Select the required information in the Image and Version Selection area.
Classification RequiredDetailed Description Image Version Required Provides version list of CacheStore(DBaaS) Table. CacheStore(DBaaS) Image and Version Selection Items - Enter or select the required information in the Service Information Entry area.
Classification RequiredDetailed Description Server Name Prefix Required Server name where Redis/Valkey will be installed - Start with lowercase English letters, enter 3 to 13 characters using lowercase letters, numbers, and special characters (
-)
- Actual server name is created with a postfix like 001, 002 based on the server name
Cluster Name Required Cluster name where Redis/Valkey is installed - Enter 3 to 20 characters using English
- 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 server types provided by CacheStore(DBaaS), see CacheStore(DBaaS) Server Type
Service Type > Planned Compute Required Resource status with Planned Compute set - In Use: Number of resources with Planned Compute set that are in use
- Settings: Number of resources with Planned Compute set
- Coverage Preview: Amount applied by resource-based Planned Compute
- Create Planned Compute Service: Move to Planned Compute service application page
- For more information, see Apply for Planned Compute
Service Type > Block Storage Required Block Storage setting used by DB according to purpose - Basic OS: Area where DB engine is installed
- DATA: Storage area for table data and archive files, etc.
- Select storage type then enter capacity. (For more information by Block Storage type, see Creating Block Storage)
- SSD: High-performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key
- Set Storage type is applied equally to additional storage
- Enter capacity in multiples of 8 within the range of 16 to 5,120
- Select storage type then enter capacity. (For more information by Block Storage type, see Creating Block Storage)
High Availability Optional High Availability (HA) configuration - If using HA configuration, provided as Master-Replica configuration with 1 or 2 replicas
- Sentinel Port Number: Port number used when connecting to Sentinel
- Port for Master-Replica communication, enter within the range of 1200 to 65535
- Replica Count: Number of replicas to configure
- If selecting 1, configured as Master-Replica-Sentinel
- If selecting 2, configured as Master-Replica-Replica, and Sentinel is automatically installed on the server where Redis is installed
- Sentinel server type is set to minimum specification
Network Required Network where CacheStore(DBaaS) is installed - Select and connect to pre-created VPC and Subnet
- Only automatic IP generation is possible
Network > Common Settings Required Network settings where servers created in the service are installed - Select if you want to apply the same settings to all installed servers
- Select pre-created VPC and Subnet
- Only automatic IP generation is possible
Network > Per Server Settings Required Network settings where servers created in the service are installed - Select if you want to apply different settings for each installed server
- Select pre-created VPC and Subnet, IP, Public NAT
- Enter IP for each server
- Public NAT function is only available when VPC is connected to Internet Gateway. If you check Use, you can select from IPs reserved in Public IP of VPC product. For more information, see Creating Public IP
IP Access Control Optional Service access policy setting - Since access policy is set for the IP entered on the page, you don’t need to set Security Group policy separately
- Enter in IP format (example:
192.168.10.1) or CIDR format (example: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 Optional CacheStore(DBaaS) maintenance period - If selecting Use, set day of week, start time, and duration
- It is recommended to set the maintenance period for stable DB management. Patch work is performed at the set time and service interruption occurs
- If set to not used, Samsung SDS is not responsible for problems caused by not applying patches.
Table. CacheStore(DBaaS) Service Configuration Items - Start with lowercase English letters, enter 3 to 13 characters using lowercase letters, numbers, and special characters (
- Enter or select the required information in the Database Configuration Required Information Entry area.
Classification RequiredDetailed Description Backup Optional Backup usage - If selecting Use, set backup file retention period and backup start time
- Separate fees are charged for backup files depending on capacity
- File retention period can be set from 7 days to 35 days
- The minutes when backup is performed are set randomly, and backup end time cannot be set
Redis/Valkey Port Number Required Port number required for Redis/Valkey connection - Enter port within the range of 1200 to 65535
Redis/Valkey Password Required Password required for Redis/Valkey connection - Enter 8 to 30 characters including English letters, numbers, and special characters (excluding
$"’)
Redis/Valkey Password Confirmation Required Re-enter password identically Parameter Required Parameters to use for Redis/Valkey - Click the View button to check detailed information of parameters
- After creation is complete, parameter modification is possible, and DB restart is required after modification
Time Zone Required Time zone where Database will be used Table. CacheStore(DBaaS) Database Configuration Items - Enter or select the required information in the Additional Information Entry area.
Classification RequiredDetailed Description Tags Optional Add tags - Can add up to 50 per resource
- Click the Add Tag button then enter or select Key, Value values
Table. CacheStore(DBaaS) Additional Information Entry Items
- Select the required information in the Image and Version Selection area.
- In the Summary panel, review the detailed information and estimated charges, and click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
Checking CacheStore(DBaaS) Detailed Information
CacheStore(DBaaS) service allows you to check and modify the entire resource list and detailed information. The CacheStore(DBaaS) Details page consists of Detailed Information, Tags, Operation History tabs.
To check the detailed information of CacheStore(DBaaS) service, follow these steps:
- Click the 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 to check detailed information. It moves to the CacheStore(DBaaS) Details page.
- At the top of the CacheStore(DBaaS) Details page, status information and additional function information are displayed.
Classification Detailed Description Cluster Status Cluster status where Redis is installed - Creating: Cluster is being created
- Editing: Cluster is changing to Operation execution state
- Error: State where error occurred while cluster is performing operation
- If it occurs continuously, contact administrator
- Failed: State where cluster failed during creation process
- Restarting: State where cluster is being restarted
- Running: State where cluster is operating normally
- Starting: State where cluster is starting
- Stopped: State where cluster is stopped
- Stopping: State where cluster is in stop state
- Synchronizing: State where cluster is synchronizing
- Terminating: State where cluster is being deleted
- Unknown: State where cluster status is unknown
- If it occurs continuously, contact administrator
Cluster Control Buttons to change cluster status - Start: Start stopped cluster
- Stop: Stop running cluster
- Restart: Restart running cluster
- Switch-Over: Switch Replica cluster to Master
More Additional Functions Cluster-related management buttons - Sync Service Status: Check real-time Redis/Valkey service status
- Backup History: If backup is set, check backup normal execution status and history
- Database Recovery: Recover DB based on specific point in time
- Parameter Management: Check and modify Redis/Valkey configuration parameters
- Rename-Command: Change name of Redis/Valkey Command
Service Termination Button to terminate service Table. CacheStore(DBaaS) Status Information and Additional Functions
- At the top of the CacheStore(DBaaS) Details page, status information and additional function information are displayed.
Detailed Information
On the CacheStore(DBaaS) List page, you can check the detailed information of the selected resource and modify information if necessary.
| Classification | Detailed Description |
|---|---|
| Server Information | Server information configured in the 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 | User who created the service |
| Creation Date | Date and time when the service was created |
| Modifier | User who modified the service information |
| Modification Date | Date and time when the service information was modified |
| Image Version | Installed Redis/Valkey image and version information
|
| Cluster Name | Cluster name where Redis/Valkey servers are configured |
| Planned Compute | Resource status with Planned Compute set
|
| 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 communication |
| VIP | Virtual IP information
|
| Network | Network information where CacheStore(DBaaS) is installed (VPC, Subnet) |
| IP Access Control | Service access policy setting
|
| Master & Replica | Master, Replica server type, Basic OS, Additional Disk information
|
| Sentinel | Sentinel server type, Basic OS information
|
Tags
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
|
Operation History
You can check the operation history of the selected resource on the CacheStore(DBaaS) List page.
| Classification | Detailed Description |
|---|---|
| Operation History List | Resource change history
|
Managing CacheStore(DBaaS) Resources
If you need to change existing configuration options of created CacheStore(DBaaS) resources or perform recovery, command changes, etc., you can perform operations on the CacheStore(DBaaS) Details page.
Controlling Operation
If changes occur in running CacheStore(DBaaS) resources, you can start, stop, or restart. Also, if configured with HA, you can switch Master-Replica servers through Switch-over.
To control CacheStore(DBaaS) operation, follow these steps:
- Click the 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 to control operation. It moves to the CacheStore(DBaaS) Details page.
- Check CacheStore status and complete changes through the control buttons below.
- Start: CacheStore service installed server and CacheStore service will run (Running).
- Stop: CacheStore service installed server and CacheStore service can stop (Stopped).
- Restart: Can restart only CacheStore service.
- Switch Over: Can switch Master server and Replica server.
Syncing Service Status
You can sync the real-time service status of CacheStore(DBaaS).
To check CacheStore(DBaaS) service status, follow these steps:
- Click the 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 to check service status. It moves to the CacheStore(DBaaS) Details page.
- Click the Sync Service Status button. While retrieving, the cluster changes to Synchronizing status.
- When retrieval 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 the 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 to change server type. It moves to the CacheStore(DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of detailed information. The Edit Server Type popup window opens.
- In the Edit Server Type popup window, select the server type and click the OK button.
Terminating CacheStore(DBaaS)
You can reduce operating costs by terminating unused CacheStore(DBaaS). However, if you terminate the service, the running service may stop immediately, so you should proceed with termination after fully considering the impact caused by service interruption.
To terminate CacheStore(DBaaS), follow these steps:
- Click the 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, select the resource to terminate and click the Terminate Service button.
- When termination is complete, check if the resource is terminated on the CacheStore(DBaaS) List page.
2.1 - Managing CacheStore Service
Users can manage CacheStore(DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
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).
- 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 to view and modify parameters. It moves to the CacheStore(DBaaS) Details page.
- Click the More button and 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).
- 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 to view and modify parameters. It moves to the CacheStore(DBaaS) Details page.
- Click the More button and 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 needed, click the Edit button and enter modification contents in the user-defined value area of the parameter to be modified.
- When input is complete, click the Complete button.
Changing Command Name
Provides Redis OSS/Valkey Command viewing and Command name modification features. 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).
- 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 to modify Command name. It moves to the CacheStore(DBaaS) Details page.
- Click the More button and 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 needed, click the Edit button and enter modification contents in the user-defined value area of the Command to be modified.
- When input is complete, click the Complete button.
Upgrading Minor Version
Provides version upgrade feature for some function improvements and security patches. Only minor version upgrade function within the same Major version is supported.
To upgrade Minor Version, follow these steps:
- Click the 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 to upgrade version. It moves to the CacheStore(DBaaS) Details page.
- Click the Edit icon of the Image Version item. The Version Upgrade popup window opens.
- Select the upgrade version in the Version Upgrade popup window and click the OK button.
- Click the OK button in the Version Upgrade Notification popup window.
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 for 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.
- Click the Database Recovery button. It moves to the Database Recovery page.
- 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.
- Click the Public IP Reservation button. It moves to the Public IP Reservation page.
- 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 Use NAT and select the Public IP reserved in 1-4. Creating a Public IP.
- 2-1. Creating Server Keypair Connect the Keypair created from 2-1. Creating Server 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 Server 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. Creating Server Keypair.
- 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. Connecting to Bastion host.
3. Creating a Database
It describes the process of creating a Database service.
3-1. Creating CacheStore (DBaaS) Service
- Click the All services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the Create CacheStore(DBaaS) button. It moves to the Create CacheStore(DBaaS) page.
- Create CacheStore(DBaaS) page where you 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.
- Select the Security Group resource created in 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. Creating an Internet Gateway. 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 connection 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. Creating CacheStore(DBaaS) Service 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)
- Provides stable service continuity through the minor version upgrade feature.
- CacheStore(DBaaS) feature added
- New image added for CacheStore(DBaaS)
- Support for open source Valkey image developed by forking Redis OSS
- 2nd Generation Server Type added
- Added 2nd generation (db2) server type based on Intel 4th generation (Sapphire Rapids) Processor. For more information, see CacheStore(DBaaS) Server Type
- Backup notification feature provided
- Provides notification feature for backup success and failure. For more information, see Creating Notification Policy
- Added HDD, HDD_KMS types to Block Storage type
- New image added for CacheStore(DBaaS)
- Samsung Cloud Platform common feature changes
- Reflected common CX changes such as Account, IAM and Service Home, Tags, etc.
- Changed the service name to CacheStore(DBaaS).
- Added volume encrypted storage selection option to Block Storage type.
- Added Role Switch (Active ↔ Standby) function for Active DB and Standby DB configured in redundancy.
- Integrated with Cloud Monitoring Service to enable DB instance performance and log monitoring.
- Planned Compute policy setting is available according to the server type selected by the customer.
- Released Redis(DBaaS) service that allows easy creation and management of Redis OSS in a web environment.

