> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/in-memory-db/how-tos/v2/update-in-memory-db-cluster.md).
# Update an In-Memory DB Cluster
After creation, you can modify the name, properties, configuration details, upgrade the cluster version, and the maintenance period of an In-Memory DB cluster.
To modify a cluster, follow these steps:
{% stepper %}
{% step %}
## Navigate to the cluster
1\. In the **DCD**, go to **Menu** > **Databases** > **In-Memory DB**.
A list of all In-Memory DB clusters is displayed.
2\. Click **Edit** in the **OPTIONS** column for the cluster you want to modify.
{% hint style="info" %}
**Note:** Alternatively, you can click the cluster name or select **View details** in the **OPTIONS** column to open the cluster details page, and then click **Edit**.
{% endhint %}
{% endstep %}
{% step %}
## Modify cluster properties
In the **Properties** section, you can update the following:
1\. **Cluster name:** Enter an updated name for the cluster. It must be between 2 and 63 characters long, must start and end with an alphanumeric character, and may contain the following special characters: hyphen (-), underscore (\_), and period (.).
2\. *(Optional)* **Description:** Update the human-readable description for the cluster.
{% hint style="info" %}
**Note:** **Location** is displayed for reference only and cannot be changed after the cluster is created.
{% endhint %}
{% endstep %}
{% step %}
## Update the cluster configuration
In the **Cluster configuration** section, you can update the following:
1\. **Version:** Select a version from the drop-down list. You can only upgrade to a version listed as available for your cluster's current version; downgrades are not supported.
2\. **Instances:** Enter the number of instances in the cluster. We recommend a minimum of three instances for production usage. Setting more than one instance enables replication. You can set a maximum of five instances within a cluster.
{% hint style="info" %}
**Note:** **Replication Type** and **CPU Type** are displayed for reference only. Replication Type reflects the number of instances configured (**No Replication** for a standalone instance, **Asynchronous** once more than one instance is set), and CPU Type is always **Dedicated Core**.
{% endhint %}
3\. **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.
{% hint style="info" %}
**Note:** Block storage is derived automatically from the configured RAM and persistence mode and cannot be set manually or downsized. Switching to a mode with higher storage requirements increases the allocated storage accordingly. For more information, see [Data Persistence](/cloud/databases/in-memory-db/overview/data-persistence.md).
{% endhint %}
4\. **Eviction Policy:** Select the key eviction strategy applied when the memory limit is reached, for example **noeviction**, which returns an error on write instead of removing data.
{% endstep %}
{% step %}
## Update snapshot storage
In the **Snapshot** section, you can update the following:
1\. **Location:** Select the Object Storage region where cluster snapshots are stored. 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. 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.
{% endstep %}
{% step %}
## Modify Observability settings
In the **Observability** section, you can update the following:
1\. **Enable logs:** Turn on to forward cluster logs to your logging endpoint.
2\. **Enable metrics:** Turn on to forward cluster metrics to your monitoring endpoint.
{% hint style="info" %}
**Note:** Both settings are turned off by default. Observability services must be activated for your contract before logs and metrics can be collected; if not activated, these settings are accepted but have no effect until the service is activated.
{% endhint %}
{% endstep %}
{% step %}
## Adjust instance resources
In the **Instance configuration** section, adjust the resources allocated per instance:
1\. **Number of CPUs (per instance):** Use the slider to set the number of dedicated CPU cores per instance.
2\. **RAM Size (per instance):** Use the slider to set the amount of RAM per instance. RAM cannot be downgraded, as storage size is derived from it.
{% hint style="info" %}
**Note:** The **Current availability** panel on the right shows the CPU and RAM already used against your contract's quota.
{% endhint %}
{% endstep %}
{% step %}
## Review network configuration
The **Network configuration** section displays the network settings configured during cluster creation.
{% hint style="info" %}
**Note:** These settings are read-only and cannot be changed after the cluster is created.
{% endhint %}
* **Virtual Data Center:** The datacenter to which the cluster is connected.
* **VDC LAN:** The LAN within the datacenter used for cluster connectivity.
* **Private IP address:** The private IP address and subnet used to connect to the cluster.
{% endstep %}
{% step %}
## Update the maintenance window
In the **Maintenance Period** section, you can update the following:
1\. **Day:** Select a day from the drop-down list, for example **Sunday**.
2\. **Start Time (UTC):** Enter a start time for the maintenance window.
{% hint style="info" %}
**Note:** The maintenance timeframe is your selected start time (UTC) plus 4 hours. If not specified, the timeframe for maintenance can be anytime Mon - Fri, 7 AM - 5 PM.
{% endhint %}
{% endstep %}
{% step %}
## Save the changes
Review the **Estimated costs** displayed at the bottom of the page, then click **Save** to apply your changes.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**Result:** Your In-Memory DB cluster is updated. Its **STATE** is set to **Updating** while the changes are being applied. Once complete, the cluster returns to **Available**.
{% endhint %}
## Next steps
* [View In-Memory DB Clusters](/cloud/databases/in-memory-db/how-tos/v2/view-in-memory-db-clusters.md): View the details and status of your updated cluster.
* [Delete an In-Memory DB Cluster](/cloud/databases/in-memory-db/how-tos/v2/delete-in-memory-db-cluster.md): Remove a cluster that is no longer needed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ionos.com/cloud/databases/in-memory-db/how-tos/v2/update-in-memory-db-cluster.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.