> 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/valkey/valkey-from-redis.md).

# Valkey - Upgrade Redis to Valkey

## **Migration process from Redis to Valkey** <a href="#valkeyfromredis-valkeypaasupgrade" id="valkeyfromredis-valkeypaasupgrade"></a>

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

Updating a Redis PaaS to a Valkey PaaS is the responsibility of **cegedim.cloud** and can be requested via a ticket submitted from ITCare.

Please specify a time slot when you are available for the operation and whether it should be carried out outside of business hours.

We recommend updating your non-production environments first so that you can estimate the downtime generated by the operation and test your applications on the Valkey PaaS. Please note that in Sentinel topology, the migration process is carried out via a rolling upgrade, meaning that a master node will always be present, minimizing or even eliminating service interruption.

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

Updating a Redis deployment (single instance or high availability cluster) to a Valkey deployment is a two-step, fully automated process:

* Update the operating system beforehand
  * Several updates depending on the scenario: Debian Redis → Debian Valkey
* Installation and configuration of Valkey

<figure><picture><source srcset="/files/ZxID3MTnYt2lLZvkdKMX" media="(prefers-color-scheme: dark)"><img src="/files/cQ3L34iUFxmn6YQAw03Y" alt="" width="563"></picture><figcaption></figcaption></figure>

{% hint style="info" %}
Depending on the source and target versions of Valkey, it may be necessary to first migrate the operating system to a version supported by cegedim.cloud (for more information, see the OS/Valkey support matrix below).
{% endhint %}

### Impacts

The duration of an update varies depending on:

* The topology
  * Standalone topology: Valkey will be installed.
  * Sentinel topology: Valkey and Sentinel will be installed on each node.
* The number of operating system updates required.

### Reference times

* Debian operating system update: 10 minutes on average
* Valkey installation and configuration: 5 minutes on average
* Installation, configuration of Sentinel, and replication: variable depending on the volume of data.

## OS/Redis/Valkey support matrix

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

| Redis / Valkey versions | Debian version                              |
| ----------------------- | ------------------------------------------- |
| Redis 6.2.x             | 10                                          |
| Redis 6.2.x             | 12 (deployments created after May 31, 2024) |
| Redis 7.2.x             | 12                                          |
| Valkey 8.1.x            | 12                                          |

{% hint style="info" %}
The operating system update is only required if PaaS Redis 6.2 was provisioned before May 31, 2024. After this date, PaaS Redis was updated to be deployed on Debian 12.
{% endhint %}


---

# 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://academy.cegedim.cloud/databases/valkey/valkey-from-redis.md?ask=<question>&goal=<endgoal>
```

`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.
