Skip to content

Commit f4b25eb

Browse files
committed
Manually revert steps
1 parent 5949427 commit f4b25eb

File tree

1 file changed

+22
-7
lines changed

1 file changed

+22
-7
lines changed

content/operate/rc/databases/upgrade-version.md

Lines changed: 22 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,15 @@ All new Redis Cloud Essentials databases are on the latest available version of
2121
Redis Cloud Pro databases that are not on the latest available version of Redis can be upgraded to a later version at any time.
2222

2323
{{< note >}}
24-
Reverting to a previous Redis version is not supported on Redis Cloud.
24+
Please keep in mind the following before upgrading your database version:
2525

26-
Before upgrading your Redis version, we recommend that you [back up your data]({{< relref "/operate/rc/databases/back-up-data" >}}). If you need to revert back to a previous database version, you can either:
27-
- [Create a new database in the same subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) with your desired version and the same port number, and [import]({{< relref "/operate/rc/databases/import-data" >}}) the backup to the new database, OR
28-
- [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) with your desired version, and [migrate data]({{< relref "/operate/rc/databases/migrate-databases" >}}) and connections from the old database to the new one.
26+
- We recommend that you [back up your data]({{< relref "/operate/rc/databases/back-up-data" >}}) before upgrading to make it easier to [manually revert the upgrade](#manually-revert-upgrade) if needed.
2927

30-
Review the breaking changes for the new database version before updating:
31-
- [Redis 7.2]({{< relref "/operate/rc/changelog/2023/june-2023#redis-72-breaking-changes" >}})
32-
- [Redis 7.4]({{< relref "/operate/rc/changelog/july-2024#redis-74-breaking-changes" >}})
28+
- Review the breaking changes for the new database version before upgrading:
29+
- [Redis 7.2]({{< relref "/operate/rc/changelog/2023/june-2023#redis-72-breaking-changes" >}})
30+
- [Redis 7.4]({{< relref "/operate/rc/changelog/july-2024#redis-74-breaking-changes" >}})
31+
32+
- You must upgrade the target database in an [Active-Passive]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}) setup before you upgrade the source database to prevent compatibility issues.
3333
{{< /note >}}
3434

3535
### Upgrade Redis Cloud Pro database
@@ -60,7 +60,22 @@ The database will start upgrading to the selected version immediately. The upgra
6060

6161
You can continue to use the Redis Cloud console for other tasks during the upgrade.
6262

63+
### Manually revert upgrade
64+
65+
Automatically reverting to a previous Redis version is not supported on Redis Cloud.
66+
67+
If you [backed up your database]({{< relref "/operate/rc/databases/back-up-data" >}}) before you upgraded your version, you can:
6368

69+
1. [Delete your database]({{< relref "/operate/rc/databases/delete-database" >}}) without deleting your subscription.
70+
1. [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) in your subscription with the following settings:
71+
- **Port number**: Use the same port number as the old database.
72+
- **Version**: Select the original version of Redis.
73+
1. [Import the backup files]({{< relref "/operate/rc/databases/import-data" >}}) into the new database.
6474

75+
This allows you to connect to the database on the previous version without changing your connection details in your application.
6576

77+
If you did not back up your database before upgrading:
6678

79+
1. [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) in your subscription and select the original version of Redis.
80+
1. [Migrate data]({{< relref "/operate/rc/databases/migrate-databases" >}}) from the original database to the new database.
81+
1. Change connection details in your application from the old database to the new database.

0 commit comments

Comments
 (0)