> ## Documentation Index
> Fetch the complete documentation index at: https://formbricks.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 6.2: Valkey 9 upgrade

> Upgrade the bundled Redis-compatible service while preserving data and a recovery point.

**Applies to:** the upgrade to 6.2, for deployments with the bundled Valkey (8.1.9, or the legacy
one-click 8.1.1 pin, → 9.1.2). Part of the
[6.2 upgrade guide](https://formbricks.com/docs/self-hosting/upgrade/versions/6.2.md). Managed Redis/Valkey services follow their provider's procedure.

## Before

* Schedule a brief service interruption and stop writers using the [standard upgrade procedure](https://formbricks.com/docs/self-hosting/advanced/upgrade.md).
* Back up the Valkey volume and record its current image and configuration. Keep the existing volume.
* Use the image/digest from your **selected release's** Compose file or Helm values. Both `linux/amd64`
  and `linux/arm64` are supported; do not substitute a platform-specific digest.

## During

> [tab] Docker Compose
>
> [Download the selected release](https://formbricks.com/docs/self-hosting/upgrade/configuration.md#download-the-selected-release).
> Copy only its `redis` image reference into your working Compose file, preserving local settings and mounts.
>
> ```bash theme={null}
> docker compose config --quiet &&
>   docker compose pull redis &&
>   docker compose up -d --no-deps --force-recreate redis
> ```
>
> One-click updates replace only the legacy amd64-only 8.1.1 pin, with 9.1.2. They keep the 8.1.9 pin from 6.1
> and custom pins, so a one-click install stays on 8.1.9 until you copy the `redis` image reference into
> `formbricks/docker-compose.yml` as above.
> The Compose backup still uses the historical `.before-valkey-8.1.9` suffix.

> [tab] Kubernetes
>
> Copy `redis.image.digest` from the selected chart's defaults into your tracked values if you previously
> pinned it. Apply it during the [Kubernetes upgrade](https://formbricks.com/docs/self-hosting/upgrade/kubernetes.md), retaining the PVC.
> Explicit old overrides otherwise keep the old image.

## After

Check Redis/Valkey connectivity, pending jobs and rate limiting before reopening traffic.
Do not delete the volume or run `FLUSHDB`.

## Recovery

Stop writers before recovery. Older Valkey versions may not read persistence files rewritten by version 9.
Restore the pre-upgrade data backup with its matching image and configuration; reconcile pending work
before restarting consumers.

Source: [Valkey image upgrade](https://github.com/formbricks/formbricks/pull/9743).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.