> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/databases/mariadb/mariadb-upgrade.md).

# MariaDB - Upgrade

## **PaaS upgrade workflow** <a href="#redisupgradeinplace-redispaasupgrade" id="redisupgradeinplace-redispaasupgrade"></a>

### Request <a href="#mariadbupgradeinplace-request" id="mariadbupgradeinplace-request"></a>

The update of a mariaDB PaaS is the responsibility of **cegedim.cloud** and can be requested via a request ticket submitted from ITCare, specifying a time slot for the operation.

Please specify if the operation is to be carried out outside of business hours in order to plan an RFC.

It is recommended that you upgrade your non-production environments first in order to estimate the downtime generated by the operation and to test your applications using the new engine version.

### Process <a href="#mariadbupgradeinplace-process" id="mariadbupgradeinplace-process"></a>

The upgrade of a mariaDB deployment (single-instance or Galera Cluster) takes place in two fully automated steps:

* Update the Operating system first if required
  * Multiple updates depending on the scenario: Debian 10 → Debian 11 -> Debian 12
* Update of the mariaDB engine in the target version

Depending on the source and target versions of mariaDB, it may be necessary to first migrate the operating system to a version supported by **cegedim.cloud**

```mermaid
graph TD
    start["MariaDB X<br/>Debian X"] --> debian["Upgrade Debian<br/>(once, twice or not required)"]
    debian --> mariadb["Upgrade MariaDB"]
    mariadb --> done["MariaDB Y<br/>Debian Y"]

    debian -.->|Handled by cegedim.cloud| mariadb

    style start fill:#e8e8e8,stroke:#000,stroke-width:2px,color:#000
    style debian fill:#ffe0b2,stroke:#e8820c,stroke-width:2px,color:#000
    style mariadb fill:#c8e6c9,stroke:#2ca02c,stroke-width:2px,color:#000
    style done fill:#e8e8e8,stroke:#000,stroke-width:2px,color:#000
```

### Impacts

* The duration of an update is variable depending on:
  * The configured cpu and ram resources
  * The amount of data whose headers must be modified by the mariaDB engine.
  * The amount of data to be reindexed following the change of C library, after an OS update (Debian).
* The backup mode:
  * Point-in-time Recovery (PITR) from Rubrik Software.

### Time references <a href="#mariadbupgradeinplace-timereferences" id="mariadbupgradeinplace-timereferences"></a>

As an average guideline, durations for each steps of an upgrade in place of a 10 GB database (standalone):

* Debian upgrade: 10 minutes on average
* mariaDB updated: 5 minutes on average

As an average guideline, durations for each steps of an upgrade in place of a 10 GB database (Cluster Galera):

* Debian upgrade: 10 minutes on average
* mariaDB updated: 5 minutes on average

## **OS / mariaDB support matrix** <a href="#mariadbupgradeinplace-os-mariadbsupportmatrixmatrice" id="mariadbupgradeinplace-os-mariadbsupportmatrixmatrice"></a>

Linux distributions supported by **cegedim.cloud** depending on the mariaDB version:

<table><thead><tr><th width="258">Versions de MariaDB</th><th>Distribution Linux supportée</th></tr></thead><tbody><tr><td>mariaDB 10.6</td><td>Debian 11</td></tr><tr><td>mariaDB 10.11</td><td>Debian 12</td></tr><tr><td>mariaDB 11.4</td><td>Debian 12</td></tr></tbody></table>

## **Supported mariaDB update paths** <a href="#mariadbupgradeinplace-supportedmariadbupdatepaths" id="mariadbupgradeinplace-supportedmariadbupdatepaths"></a>

If the operating system is updated, it may require a complete reindexing (also handled by **cegedim.cloud**) due to changes in the C library when the operating system is updated.

Depending on the amount of data, this operation may take some time.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.cegedim.cloud/databases/mariadb/mariadb-upgrade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.