{
  "id": "upgrade-database",
  "title": "Upgrade a Redis Enterprise Software database",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database/",
  "summary": "Upgrade a Redis Enterprise Software database.",
  "content": "\n## Default Redis database versions {#default-db-versions}\n\nWhen you upgrade an existing database, it uses the latest bundled Redis version unless you specify a different version with the `redis_version` option in the [REST API]() or [`rladmin upgrade db`]().\n\nRedis Enterprise Software v6.x includes two Redis database versions: 6.0 and 6.2.\nAs of version 7.2, Redis Enterprise Software includes three Redis database versions.\n\nTo view available Redis database versions:\n\n- In the Cluster Manager UI, see **Redis database versions** on the **Cluster \u003e Configuration** screen.\n\n- Send a [`GET /nodes` REST API request]() and see `supported_database_versions` in the response.\n\nThe default Redis database version differs between Redis Enterprise releases as follows:\n\n\u003ca name=\"db-versions-table\"\u003e\u003c/a\u003e\n| Redis\u003cbr /\u003eSoftware | Bundled Redis\u003cbr /\u003eDB versions | Default DB version\u003cbr /\u003e(upgraded/new databases) |\n|-------|----------|-----|\n| 7.8.x | 6.2, 7.2, 7.4 | 7.4 |\n| 7.4.x | 6.0, 6.2, 7.2 | 7.2 |\n| 7.2.4 | 6.0, 6.2, 7.2 | 7.2 |\n| 6.4.2 | 6.0, 6.2 | 6.2 |\n| 6.2.x | 6.0, 6.2 | 6.0 |\n\n\nThe upgrade policy is only relevant for Redis Enterprise Software versions 6.2.4 through 6.2.18. For more information about upgrade policies, see the [6.2 version of this document](https://docs.redis.com/6.2/rs/installing-upgrading/upgrading/#redis-upgrade-policy).\n\n## Upgrade prerequisites\n\nBefore upgrading a database:\n\n- Review the relevant [release notes](https://redis.io/docs/latest/operate/rs/release-notes/) for any preparation instructions.\n\n- Verify that both the [current database version and the target database version are supported](#db-versions-table) by the cluster's Redis Enterprise Software version.\n\n    To determine the current database version:\n\n    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select  **About**.\n\n    - _(Optional)_ Use the [`rladmin status extra all`]() command to display configuration details:\n\n        ```sh\n        rladmin status extra all\n        ```\n    \n        When the database compatibility version is outdated, \u003cnobr\u003e`OLD REDIS VERSION`\u003c/nobr\u003e appears in the command output.\n\n- Verify the cluster is fully upgraded and operational.\n\n    Use the Cluster Manager UI to display the **Configuration** tab for the cluster. The tab displays the cluster version information and the Redis database compatibility version.\n\n- Check client compatibility with the database version.\n\n    If you run Redis Stack commands with Go-Redis versions 9 and later or Lettuce versions 6 and later, set the client’s protocol version to RESP2 before upgrading your database to Redis version 7.2 to prevent potential application issues due to RESP3 breaking changes. See [Client prerequisites for Redis 7.2 upgrade]() for more details and examples.\n\n- To avoid data loss during the upgrade, [back up your data]().  \n\n    You can [export the data]() to an external location, [enable replication](), or [enable persistence]().\n\n    When choosing how to back up data, keep the following in mind:\n\n    - To reduce downtime when replication is enabled, a failover is performed before restarting the primary (master) database.\n\n    - When persistence is enabled without replication, the database is unavailable during restart because the data is restored from the persistence file. AOF persistence restoration is slower than snapshot restoration.\n\n## Upgrade database\n\nTo upgrade a database:\n\n1.  _(Optional)_  Back up the database to minimize the risk of data loss.\n\n1.  Use [`rladmin`]() to upgrade the database. During the upgrade process, the database will restart without losing any data. Use the `preserve_roles` option to keep the database's current state, including primary shard placement, and prevent the cluster from becoming unbalanced.\n\n    - To upgrade a database and its modules:\n\n        ``` shell\n        rladmin upgrade db \u003cdatabase name | database ID\u003e preserve_roles\n        ```\n\n        Example of a successful upgrade:\n\n        ``` shell\n        rladmin\u003e upgrade db demo\n        Monitoring d194c4a3-631c-4726-b799-331b399fc85c\n        active - SMUpgradeBDB init\n        active - SMUpgradeBDB wait_for_version\n        active - SMUpgradeBDB configure_shards\n        completed - SMUpgradeBDB\n        Done\n        ```\n\n    - To upgrade the database to a version other than the default version, use the `redis_version` parameter:\n\n        ```sh\n        rladmin upgrade db \u003cdatabase name | database ID\u003e redis_version \u003cversion\u003e preserve_roles\n        ```\n\n1. Check the Redis database compatibility version for the database to confirm the upgrade.  \n\n    To do so:\n\n    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select  **About**.\n\n    - Use [`rladmin status databases extra all`]() to display a list of the databases in your cluster and their current Redis database compatibility version:\n\n        ```sh\n        rladmin status databases extra all\n        ```\n\n    Verify that the Redis version is set to the expected value.\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00"
}