> 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/mariadb/how-tos/v2/update-mariadb-cluster.md).
# Update a MariaDB Cluster
Learn how to update a MariaDB v2 cluster's version, instances, backup retention, resources, network, and maintenance window on IONOS Cloud
After creation, you can update the name, properties, configuration details, upgrade the cluster version, and the maintenance period of a MariaDB cluster.
To update a cluster, follow these steps:
{% stepper %}
{% step %}
## Navigate to the cluster
1\. In the **DCD**, go to **Menu** > **Databases** > **MariaDB**.
A list of all MariaDB clusters is displayed.
2\. Click **Edit** in the **OPTIONS** column for the cluster you want to update.
{% hint style="info" %}
**Note:** Alternatively, click the cluster name or select **Details** in the **OPTIONS** column to open the cluster details page, and then click **Edit**.
{% endhint %}
{% endstep %}
{% step %}
## Update 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\. **Location:** Displays the region where the cluster is deployed. This cannot be changed after the cluster is created.
3\. *(Optional)* **Description:** Enter or update the human-readable description for the cluster.
{% endstep %}
{% step %}
## Update the cluster configuration
In the **Cluster configuration** section, you can update the following:
1\. **Version:** Select a MariaDB version from the drop-down list. You can only upgrade to a higher version; downgrades are not supported.
2\. **Instances:** Enter the number of instances for the cluster. A value of **1** creates a single-instance cluster. Values **2–5** create a replicated cluster with one primary and n-1 secondary instances.
3\. **Backup:** Select the Object Storage region where cluster backups are stored, for example **eu-central-3**.
4\. **Retention days:** Enter the number of days backups are retained before being automatically deleted. You can set a value between **1** and **365**.
{% endstep %}
{% step %}
## Update 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:** Observability services must be activated for your contract before logs and metrics can be collected. If not activated, selecting these settings is accepted but has no effect.
{% endhint %}
{% endstep %}
{% step %}
## Adjust instance resources
In the **Resources** 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, in GB, per instance.
3\. **Storage Size (per instance):** Use the slider to set the storage, in GB, per instance. Storage size can only be increased after the cluster is created; it cannot be reduced.
{% endstep %}
{% step %}
## Review the Data Center connection
The **Data Center connection** section displays the network settings configured during cluster creation:
* **Network configuration:** The datacenter to which the cluster is connected.
* **VDC LAN:** The LAN within the datacenter used for cluster connectivity.
* **IP/Subnet:** The private IP address assigned to the cluster's primary instance.
{% hint style="info" %}
**Note:** Make sure the selected private IP address is not already in use within the DCD. The following IP address ranges cannot be used with MariaDB services:
* `10.208.0.0/12`
* `10.233.0.0/18`
* `192.168.230.0/24`
* `10.233.64.0/18`
{% endhint %}
{% endstep %}
{% step %}
## Update the maintenance window
In the **Maintenance period** section, you can update the following:
1\. **Day:** Select a day of the week from the drop-down list.
2\. **Start Time (UTC):** Enter or select 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 %}
## Update the database user
In the **User Creation** section, you can update the following:
1\. **Username:** Enter a username to provide access to the MariaDB cluster. It must be between 2 and 16 characters long and may only contain alphanumeric characters and underscores (\_). Some usernames are reserved for platform use (for example, `mariadb`, `admin`, `standby`) and are not allowed.
2\. **Password:** Enter a password for the respective user.
3\. **Database:** Enter a name for the database.
{% hint style="warning" %}
**Warning:** If the user already exists in the restored backup, its credentials will be overwritten.
{% 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 MariaDB 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 MariaDB Clusters](/cloud/databases/mariadb/how-tos/v2/view-mariadb-clusters.md): View the details and status of your updated cluster.
* [Restore a MariaDB Cluster](/cloud/databases/mariadb/how-tos/v2/restore-mariadb-cluster.md): Restore a cluster from an existing backup.
---
# 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/mariadb/how-tos/v2/update-mariadb-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.