Create an In-Memory DB Cluster
Using this guide, you can create an In-Memory DB cluster in the DCD using the new v2 infrastructure.
Define cluster properties
In the Properties section, specify the following:
1. Cluster name: Enter a name for the cluster.
2. Location: Select the region where the cluster is deployed, for example Germany / Berlin (de/txl). In v2, each cluster is bound to a region-specific API endpoint, and the location you select determines which endpoint manages the cluster. This cannot be changed after the cluster is created.
3. (Optional) Description: Enter a human-readable description for the cluster.

Configure the cluster
In the Cluster configuration section, enter the following details:
1. Version: Select the In-Memory DB version for the cluster, for example 9.0.
2. Instances: Enter the number of instances in the cluster. A value of 1 creates a standalone instance; values 2–5 create a replicated setup with one primary and n-1 passive secondaries. You can create a maximum of five instances within a cluster.
3. Replication Type: Displayed as Asynchronous. The primary instance does not wait for a secondary to confirm the data has been written, so the cluster can lose some committed transactions to ensure availability.
4. CPU Type: Displayed as Dedicated Core.
5. Persistence: Select one of the following modes for how data is persisted to disk:
In-Memory: Data is in-memory only and will not be persisted. Suitable for applications that primarily use In-Memory DB as a temporary data store.
AOF (Append Only File): Every write operation is logged for full durability.
RDB (Redis Database File): Periodic point-in-time snapshots of the in-memory state.
RDB and AOF: Both mechanisms are active for maximum data safety.
6. Eviction Policy: Select the key eviction strategy applied when the memory limit is reached, for example allkeys-lru, which evicts the least recently used keys across all keys.

Configure snapshot storage
In the Snapshot section, specify the following:
1. Location: Select the Object Storage region where cluster snapshots are stored, for example eu-central-4. For added data safety, choose a location different from the cluster's own region.
2. Retention days: Enter the number of days snapshots are retained before being automatically deleted. The default is 7 days; you can set a value between 1 and 365.
3. Snapshot Hours: Select one or more hours of the day (UTC) at which snapshots are taken. At least one hour must be specified.

(Optional) Restore from a snapshot
To initialize the new cluster with data from an existing snapshot, go to the Restore configuration section and select Restore cluster from snapshot, then specify the following:
1. Source snapshot: Select the snapshot to restore from. Only snapshots from clusters within the same region are eligible.
2. Recovery target datetime: Select a date and time within the displayed recovery window. The cluster is restored from the most recent snapshot taken at or before that time. If left empty, the cluster is restored from the latest available snapshot.

Configure instances
In the Instance configuration section, specify the following:
1. Number of CPUs (per instance): Select the number of dedicated CPU cores using the slider.
2. RAM Size (per instance): Select the amount of RAM using the slider. RAM cannot be downgraded after the cluster is created, since storage size is derived from it.
The Current availability panel on the right shows the CPU and RAM already used against your contract's quota.

Configure the network
In the Network configuration section, provide the following information to connect your cluster with the datacenter:
1. Virtual Data Center: Select a datacenter from the available list.
2. VDC LAN: Select a LAN for your datacenter.
3. Private IP address: Enter the private IP address in CIDR notation. For more information, see Private IP Address Ranges.


Next steps
View In-Memory DB Clusters: View the details and status of your newly created cluster.
Delete an In-Memory DB Cluster: Remove a cluster that is no longer needed.
Last updated
Was this helpful?



