From 8fc0ef063907c545cc3df0afe6dcb06a1edc5d04 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 10 Feb 2023 09:25:12 -0500 Subject: [PATCH 1/6] EPRS: clarifying upgrade instructions --- .../upgrading_replication_server/index.mdx | 16 ++++++---------- .../upgrading_linux.mdx | 9 +++++---- .../upgrading_with_xdb_rpm_package.mdx | 5 +++-- 3 files changed, 14 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx index 73172ee46ed..e9da31fefe9 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx @@ -10,23 +10,19 @@ 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 on the same host machine that is currently running Replication Server 6.2.x and that you will then manage the existing replication systems using Replication Server 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. -A direct upgrade is supported only from Replication Server versions 6.2.x. +A direct upgrade is supported only from Replication Server versions 7.x. -After upgrading to version 6.2, you can then upgrade to 7. +If you are using a version of Replication Server earlier than 6.2.x on Linux, first upgrade to 6.2.x, and then upgrade to version 7.x. See: +- [Upgrading to xDB Replication Server 6.2](/eprs/6.2/10_appendix/02_upgrading_to_xdb6_2) +- [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) -If you are using a version of Replication Server older than 6.2.x, first upgrade to 6.2.x, and then upgrade to version 7. For more details on upgrading Replication Server, see: - [Updating the publication and subscription server](updating_sub_and_pub_ports) -- [Upgrading a Linux installation](upgrading_linux) +- [Upgrading from a Replication Server 7.x installation on Linux](upgrading_linux) - [Upgrading with the graphical user interface installer](upgrading_with_gui_installer) -- [Upgrading from a Replication Server RPM package installation](upgrading_with_xdb_rpm_package) -
-upgrading_with_gui_installer upgrading_with_xdb_rpm_package updating_sub_and_pub_ports - -
diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx index c3f8db5cf2e..c7a8096b979 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx @@ -1,16 +1,17 @@ --- -title: "Upgrading a Linux installation" +title: "Upgrading from a Replication Server 7.x installation on Linux" +navTitle: Upgrading from 7.x redirects: - /eprs/latest/03_installation/03a_updating_linux_installation/ - /eprs/latest/installing/upgrading/ --- -If you have an existing Replication Server installed on Linux, you can use yum to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: +If you have an existing Replication Server 7.x installation on Linux, you can use yum to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: `yum upgrade edb-repo` `yum` will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages: -`yum upgrade ppas-xdb*` +`yum upgrade edb-xdb*` -See [Upgrading from a Replication Server RPM Package Installation](upgrading_with_xdb_rpm_package) for details. +If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details. diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx index 3314d1e1a36..ef0d1a47e7e 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx @@ -1,5 +1,6 @@ --- -title: "Upgrading from a RPM package installation" +title: "Upgrading from a Replication Server 6.2 installation on Linux" +navTitle: Upgrading from 6.2 redirects: - /eprs/latest/10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/ - /eprs/latest/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/ @@ -36,7 +37,7 @@ If you're using Replication Server 6.2.x that was installed using the Replicatio 1. As the root account, invoke the yum update command to begin the upgrade from Replication Server 6.2.x to Replication Server 7 as shown by the following: - `yum update edb-xdb*` + `yum update ppas-xdb*` Be sure to include the asterisk character (\*) to update all Replication Server components. From e01d975ade04726cad4932522a4266dd65d343a1 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 10 Feb 2023 14:48:27 -0500 Subject: [PATCH 2/6] EFM: fixed typo reported by GitHub issue 3640 --- .../4/04_configuring_efm/06_configuring_for_eager_failover.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index 5d55cccb262..d2e88e2c0a8 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -21,7 +21,7 @@ You can set up Eager Failover by performing the following steps. The example us If you don't set this property before starting Failover Manager, shutting down a Failover Manager agent shuts down the database without failover. -- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid thihs scenario, you can disable the command using the `enable.stop.cluster` property. +- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid this scenario, you can disable the command using the `enable.stop.cluster` property. ```ini enable.stop.cluster=false From fd97a9d2c5b8027b47b13407c641e346b1dfe303 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 10 Feb 2023 14:49:42 -0500 Subject: [PATCH 3/6] Revert "EFM: fixed typo reported by GitHub issue 3640" This reverts commit e01d975ade04726cad4932522a4266dd65d343a1. --- .../4/04_configuring_efm/06_configuring_for_eager_failover.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index d2e88e2c0a8..5d55cccb262 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -21,7 +21,7 @@ You can set up Eager Failover by performing the following steps. The example us If you don't set this property before starting Failover Manager, shutting down a Failover Manager agent shuts down the database without failover. -- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid this scenario, you can disable the command using the `enable.stop.cluster` property. +- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid thihs scenario, you can disable the command using the `enable.stop.cluster` property. ```ini enable.stop.cluster=false From 3e595dfeedd03983520ae08d0fc66c0c0b341305 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 10 Feb 2023 14:50:26 -0500 Subject: [PATCH 4/6] Revert "Revert "EFM: fixed typo reported by GitHub issue 3640"" This reverts commit fd97a9d2c5b8027b47b13407c641e346b1dfe303. --- .../4/04_configuring_efm/06_configuring_for_eager_failover.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index 5d55cccb262..d2e88e2c0a8 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -21,7 +21,7 @@ You can set up Eager Failover by performing the following steps. The example us If you don't set this property before starting Failover Manager, shutting down a Failover Manager agent shuts down the database without failover. -- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid thihs scenario, you can disable the command using the `enable.stop.cluster` property. +- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid this scenario, you can disable the command using the `enable.stop.cluster` property. ```ini enable.stop.cluster=false From a6d2d749a21fcb5ac7d28f93d156b7d1e7bb9350 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 10 Feb 2023 14:53:30 -0500 Subject: [PATCH 5/6] Revert "EFM: fixed typo reported by GitHub issue 3640" This reverts commit e01d975ade04726cad4932522a4266dd65d343a1. --- .../4/04_configuring_efm/06_configuring_for_eager_failover.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx index d2e88e2c0a8..5d55cccb262 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/06_configuring_for_eager_failover.mdx @@ -21,7 +21,7 @@ You can set up Eager Failover by performing the following steps. The example us If you don't set this property before starting Failover Manager, shutting down a Failover Manager agent shuts down the database without failover. -- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid this scenario, you can disable the command using the `enable.stop.cluster` property. +- With Eager Failover enabled, using the `efm stop-cluster` command stops all of the Failover Manager agents and shuts down the primary database. Since the agents aren't running, there's no failover. To avoid thihs scenario, you can disable the command using the `enable.stop.cluster` property. ```ini enable.stop.cluster=false From ff44cef9cae4a65f295e2d479f4d1fffcdcb59b6 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 13 Feb 2023 07:24:05 -0500 Subject: [PATCH 6/6] removed statement about direct upgrades only from 7.x --- .../eprs/7/installing/upgrading_replication_server/index.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx index e9da31fefe9..8947285badc 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx @@ -12,8 +12,6 @@ You can install Replication Server 7 when you have existing single-master or mul 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. -A direct upgrade is supported only from Replication Server versions 7.x. - If you are using a version of Replication Server earlier than 6.2.x on Linux, first upgrade to 6.2.x, and then upgrade to version 7.x. See: - [Upgrading to xDB Replication Server 6.2](/eprs/6.2/10_appendix/02_upgrading_to_xdb6_2) - [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package)