---
title: "Cloud DB for Cache prerequisites"
slug: "clouddbforcache-spec"
updated: 2026-09-17T09:25:07Z
published: 2026-09-17T09:25:07Z
canonical: "guide.ncloud-docs.com/clouddbforcache-spec"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud DB for Cache prerequisites

Available in Classic and VPC

View supported environments, server specifications, service limits, etc., for best usage of Cloud DB for Cache.

## Cloud environment specifications

Cloud environment specifications supported by Cloud DB for Cache are described as follows:

| Item | Specifications |
| --- | --- |
| Region (zone) | Korea, U.S., Singapore, and Japan |
| Classic | Supported |
| VPC | Supported |
| Languages | Korean, English, and Japanese |

              Note

              

For more information on the VPC environment, see [Service introduction](https://www.ncloud.com/product/networking/vpc) on NAVER Cloud Platform portal, and for more information on whether the VPC environments are supported for each service, see [Ncloud user environment guide](/docs/en/environment-environment-1-1).

## Server specifications

For NAVER Cloud Platform's Cloud DB for Cache, you can flexibly select from various types of server type and use them according to your service size. For server specifications supported by Cloud DB for Cache, see **[Services > Database > Cloud DB for Cache](https://www.ncloud.com/product/database/cloudDbCache)** in the portal.

              Caution

              

Up to 10 High Memory servers can be created per user account, and up to 20 servers can be created per account regardless of the type. If you need to create more, contact customer support.

### Service limits when changing server specifications

While the type of DB Server that has been created and is in operation can't be changed, the size of available memory can always be changed using the **Change specifications** feature of the **DB Server** menu in the console. For information on how to upgrade, see [DB Server (VPC)](/docs/en/database-database-8-1), [DB Server (Classic)](/docs/en/clouddbforcache-cacheserver-classic) depending on the user environment. However, a few service limits exist when changing the server specifications. You need to fully understand these restrictions before changing the server specifications. The service limits are as follows:

- They can only be changed within the same type.
- They can only be changed to a larger cache memory size type (higher specifications) due to the in-memory characteristics
- If configured with more than 2 servers as Active and Standby (using high availability), change all to the same specifications.
- The server restarts upon completion of the change. Therefore, the service may possibly be affected.

The data continuity is guaranteed as the data in memory is saved to a disk when the server specifications are changed. However, once the server specifications change is complete, we recommend checking the data status using the `dbsize` command.

## Server redundancy configuration

Cloud DB for Cache supports the high availability (HA) feature. Automatic failover to a standby server if an active server fails and normal service is not possible. As the redundancy is configured with the DNS method, no additional application change is required. When creating DB Server in NAVER Cloud Platform console, you can choose whether to use high availability (HA) or not, and the server configuration depends on whether to use it. The following describes the server configuration by availability:

| Enable high availability | Number of created servers (units) | Composition |
| --- | --- | --- |
| O | 2 | Active Master, Standby Master |
| X | 1 | Standalone |

              Caution

              

Failover can take up to 3 minutes.

## DB command service limits

Some DB commands are not available for operating Cloud DB for Cache efficiently. The following commands are not available:

- `BGREWIRTEAOF`
- `BGSAVE`
- `SAVE`
- `SLAVEOF`
- `FLUSHALL`
- `FLUSHDB`
- `CONFIG`
- `KEYS`
- `MIGRATE`
- `SHUTDOWN`

              Caution

              

APIs are supported to compensate for the role of the unavailable DB commands. For how to use APIs of Cloud DB for Cache, see [Cloud DB for DB (VPC) API guides](https://api.ncloud-docs.com/docs/en/database-vcache).

## Pricing information

Cloud DB for Cache uses a pay-as-you-go pricing plan. For detailed description of Cloud DB for Cache's pricing standard, see **Portal > Services > Database > Cloud DB for Cache**.

- [**Portal > Services > Database > Cloud DB for Cache**](https://www.ncloud.com/product/database/cloudDbCache)