Skip to content

Commit

Permalink
Merge pull request #4855 from EnterpriseDB/docs/edits_to_eprs_pr4802
Browse files Browse the repository at this point in the history
edits to upgrade topic
  • Loading branch information
nidhibhammar authored Sep 27, 2023
2 parents 7865738 + 157a85b commit 6837c3b
Showing 1 changed file with 3 additions and 5 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,12 @@ redirects:

You can install Replication Server 7 when you have existing single-master or multi-master replication systems that are running under Replication Server version 7.

It is assumed that you are installing Replication Server 7.x on the same host machine that is currently running the earlier version of Replication Server you are upgrading from and that you will then manage the existing replication systems using Replication Server 7.x.
It's assumed that you're installing Replication Server 7.x on the same host machine that's currently running the earlier version of Replication Server you're upgrading from and that you plan to then manage the existing replication systems using Replication Server 7.x.

If you are using a version of Replication Server earlier than 6.2.15, first upgrade to 6.2.15 or a later 6.2.x point version before upgrading to 7.x.
If you're using a version of Replication Server earlier than 6.2.15, first upgrade to 6.2.15 or a later 6.2.x point version before upgrading to 7.x.

!!!note
Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments; however, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. There is no downgrade path from version 7.x to version 6.2.x so it is essential to test the upgrade first before applying it to the production environment.
Version 7.x provides a non-breaking upgrade path for existing 6.2.x based cluster deployments. However, we strongly recommended that you verify the upgrade in a staging or nonproduction environment before applying the upgrade in a production environment. There's no downgrade path from version 7.x to version 6.2.x, so it's essential to test the upgrade first before applying it to the production environment.



Expand All @@ -27,5 +27,3 @@ For more details on upgrading Replication Server, see:
- [Upgrading with the graphical user interface installer](upgrading_with_gui_installer)

After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it (for Linux) or rename the driver (for Windows). See [Installing a JDBC driver](../installing_jdbc_driver/) for more information.


0 comments on commit 6837c3b

Please sign in to comment.