From add1592531a67702bb4cb4e718ba141c449d5087 Mon Sep 17 00:00:00 2001 From: Rachel Elledge Date: Wed, 27 May 2026 17:15:59 -0500 Subject: [PATCH] DOC-1499 RS: Added note to upgrade Replica Of destination DB before the source DB --- .../rs/7.22/databases/import-export/replica-of/_index.md | 4 ++++ .../7.22/installing-upgrading/upgrading/upgrade-database.md | 2 ++ .../rs/7.4/databases/import-export/replica-of/_index.md | 4 ++++ .../rs/7.4/installing-upgrading/upgrading/upgrade-database.md | 2 ++ .../rs/7.8/databases/import-export/replica-of/_index.md | 4 ++++ .../rs/7.8/installing-upgrading/upgrading/upgrade-database.md | 2 ++ .../operate/rs/databases/import-export/replica-of/_index.md | 4 ++++ .../rs/installing-upgrading/upgrading/upgrade-database.md | 2 ++ 8 files changed, 24 insertions(+) diff --git a/content/operate/rs/7.22/databases/import-export/replica-of/_index.md b/content/operate/rs/7.22/databases/import-export/replica-of/_index.md index dadc85e8b7..1374cd9a31 100644 --- a/content/operate/rs/7.22/databases/import-export/replica-of/_index.md +++ b/content/operate/rs/7.22/databases/import-export/replica-of/_index.md @@ -211,6 +211,10 @@ make sure that you disable **Replica Of** before you direct clients to the desti This avoids a full sync that can overwrite your data. {{% /warning %}} +## Upgrade order + +When you [upgrade]({{< relref "/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database" >}}) a Replica Of database, upgrade the destination database before the source database to avoid possible replication failures. + ## Active-Passive replication backlog In addition to the [database replication backlog]({{< relref "/operate/rs/7.22/databases/durability-ha/replication#database-replication-backlog" >}}), active-passive databases maintain a replication backlog (per shard) to synchronize the database instances between clusters. diff --git a/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md index 1123a55a88..6d2e36a9ab 100644 --- a/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md +++ b/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md @@ -63,6 +63,8 @@ Before upgrading a database: 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. +- For [Replica Of databases]({{< relref "/operate/rs/7.22/databases/import-export/replica-of/" >}}), upgrade the destination database before the source database. + - Check client compatibility with the database version. 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]({{< relref "/operate/rs/7.22/references/compatibility/resp#client-prerequisites-for-redis-72-upgrade" >}}) for more details and examples. diff --git a/content/operate/rs/7.4/databases/import-export/replica-of/_index.md b/content/operate/rs/7.4/databases/import-export/replica-of/_index.md index 51a8d571aa..b7c77478e8 100644 --- a/content/operate/rs/7.4/databases/import-export/replica-of/_index.md +++ b/content/operate/rs/7.4/databases/import-export/replica-of/_index.md @@ -206,6 +206,10 @@ make sure that you disable **Replica Of** before you direct clients to the desti This avoids a full sync that can overwrite your data. {{% /warning %}} +## Upgrade order + +When you [upgrade]({{< relref "/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database" >}}) a Replica Of database, upgrade the destination database before the source database to avoid possible replication failures. + ## Active-Passive replication backlog In addition to the [database replication backlog]({{< relref "/operate/rs/7.4/databases/durability-ha/replication#database-replication-backlog" >}}), active-passive databases maintain a replication backlog (per shard) to synchronize the database instances between clusters. diff --git a/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md index 82b80eb6b0..e4432daaf5 100644 --- a/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md +++ b/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md @@ -60,6 +60,8 @@ Before upgrading a database: 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. +- For [Replica Of databases]({{< relref "/operate/rs/7.4/databases/import-export/replica-of/" >}}), upgrade the destination database before the source database. + - Check client compatibility with the database version. 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]({{< relref "/operate/rs/7.4/references/compatibility/resp#client-prerequisites-for-redis-72-upgrade" >}}) for more details and examples. diff --git a/content/operate/rs/7.8/databases/import-export/replica-of/_index.md b/content/operate/rs/7.8/databases/import-export/replica-of/_index.md index 8b3b26a9da..8a4ef334a8 100644 --- a/content/operate/rs/7.8/databases/import-export/replica-of/_index.md +++ b/content/operate/rs/7.8/databases/import-export/replica-of/_index.md @@ -206,6 +206,10 @@ make sure that you disable **Replica Of** before you direct clients to the desti This avoids a full sync that can overwrite your data. {{% /warning %}} +## Upgrade order + +When you [upgrade]({{< relref "/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database" >}}) a Replica Of database, upgrade the destination database before the source database to avoid possible replication failures. + ## Active-Passive replication backlog In addition to the [database replication backlog]({{< relref "/operate/rs/7.8/databases/durability-ha/replication#database-replication-backlog" >}}), active-passive databases maintain a replication backlog (per shard) to synchronize the database instances between clusters. diff --git a/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md index ad99ef6f08..cb7d611f5c 100644 --- a/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md +++ b/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md @@ -62,6 +62,8 @@ Before upgrading a database: 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. +- For [Replica Of databases]({{< relref "/operate/rs/7.8/databases/import-export/replica-of/" >}}), upgrade the destination database before the source database. + - Check client compatibility with the database version. 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]({{< relref "/operate/rs/7.8/references/compatibility/resp#client-prerequisites-for-redis-72-upgrade" >}}) for more details and examples. diff --git a/content/operate/rs/databases/import-export/replica-of/_index.md b/content/operate/rs/databases/import-export/replica-of/_index.md index 41d09e453a..2dd546a166 100644 --- a/content/operate/rs/databases/import-export/replica-of/_index.md +++ b/content/operate/rs/databases/import-export/replica-of/_index.md @@ -210,6 +210,10 @@ make sure that you disable **Replica Of** before you direct clients to the desti This avoids a full sync that can overwrite your data. {{% /warning %}} +## Upgrade order + +When you [upgrade]({{< relref "/operate/rs/installing-upgrading/upgrading/upgrade-database" >}}) a Replica Of database, upgrade the destination database before the source database to avoid possible replication failures. + ## Active-Passive replication backlog In addition to the [database replication backlog]({{< relref "/operate/rs/databases/durability-ha/replication#database-replication-backlog" >}}), active-passive databases maintain a replication backlog (per shard) to synchronize the database instances between clusters. diff --git a/content/operate/rs/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/installing-upgrading/upgrading/upgrade-database.md index b4dac5fe38..d5d9e8fc35 100644 --- a/content/operate/rs/installing-upgrading/upgrading/upgrade-database.md +++ b/content/operate/rs/installing-upgrading/upgrading/upgrade-database.md @@ -49,6 +49,8 @@ Before upgrading a database: 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. +- For [Replica Of databases]({{< relref "/operate/rs/databases/import-export/replica-of/" >}}), upgrade the destination database before the source database. + - Check client compatibility with the database version. 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]({{< relref "/operate/rs/references/compatibility/resp#client-prerequisites-for-redis-72-upgrade" >}}) for more details and examples.