Merge pull request #3514 from EnterpriseDB/release/2023-01-06

Release: 2023-01-06

product_docs/docs/biganimal/release/pricing_and_billing/index.mdx

@@ -45,7 +45,7 @@ The table shows a breakdown of management costs for Microsoft Azure.
 | Azure blob storage             | BigAnimal uses blob storage to store metadata about your account.                                                                                     |
 | Key vault                      | BigAnimal uses key vault to securely store credentials for managing your infrastructure.                                                              |
 
-At list price, estimated overall monthly management costs are $400–$700 for a single cluster. Check with your Microsoft Azure account manager for specifics that apply to your account. 
+At list price, estimated overall monthly management costs are $400–$700 for a single region. Check with your Microsoft Azure account manager for specifics that apply to your account. 
 
 To get a better sense of your Microsoft Azure costs, check out the Microsoft Azure pricing [calculator](https://azure.microsoft.com/en-us/pricing/calculator/) and reach out to [BigAnimal Support](../overview/support). 
 
@@ -60,7 +60,7 @@ The table shows a breakdown of management costs for AWS.
 | Simple Storage Service (S3)             | BigAnimal uses S3 to store metadata about your account.                                                                                     |
 | Key Management Service                      | BigAnimal uses the key management service to securely store credentials for managing your infrastructure.                                                              |
 
-At list price, estimated overall monthly management costs are $400–$600 for a single cluster. Check with your AWS account manager for specifics that apply to your account.
+At list price, estimated overall monthly management costs are $400–$600 for a single region. Check with your AWS account manager for specifics that apply to your account.
 
 To get a better sense of your AWS costs, check out the AWS pricing [calculator](https://calculator.aws/#/) and reach out to [BigAnimal Support](../overview/support).  
 

product_docs/docs/eprs/6.2/03_installation/01_installing_with_stackbuilder.mdx

@@ -43,7 +43,7 @@ Follow the directions for your host operating system to install Java runtime.
 **Step 5 (For Advanced Server):** Expand the EnterpriseDB Tools node and check the box for Replication Server. Click the Next button.
 
 !!! Note
-    Though the following ../images show Replication Server v6.0, use the same process for Replication Server v6.2.
+    Though the following images show Replication Server v6.0, use the same process for Replication Server v6.2.
 
 ![StackBuilder Plus applications](../images/image29.png)
 

product_docs/docs/eprs/6.2/03_installation/02_installing_from_cli.mdx

@@ -28,7 +28,7 @@ Follow the directions for your host operating system to install Java runtime.
 The following example shows how to start the xDB Replication Server installation in text mode.
 
 ```text
-$ ./xdbreplicationserver-6.1.0-alpha-1-linux-x64.run --mode text
+$ ./xdbreplicationserver-6.2.0-alpha-1-linux-x64.run --mode text
 Language Selection
 
 Please select the installation language
@@ -47,7 +47,7 @@ The following example shows how to start the installation in unattended mode wit
 ```text
 $ su root
 Password:
-$ ./xdbreplicationserver-6.1.0-alpha-1-linux-x64.run --optionfile /home/user/xdb_config
+$ ./xdbreplicationserver-6.2.0-alpha-1-linux-x64.run --optionfile /home/user/xdb_config
 ```
 
 The following is the content of the options file, `xdb_config`.

product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx

@@ -116,7 +116,7 @@ For example, to access xDB Replication Server version 6.2, enable the following
 
 ```text
 [enterprisedb-xdb60]
-name=EnterpriseDB XDB 6.0 $releasever - $basearch
+name=EnterpriseDB XDB 6.2 $releasever - $basearch
 baseurl=http://<username>:<password>@yum.enterprisedb.com/xdb60/redhat/rhel-$releasever-$basearch
 enabled=0
 gpgcheck=1

product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/02_print_version.mdx

@@ -14,7 +14,7 @@ Examples
 
 ```text
 $ java -jar edb-repcli.jar -version
-Version: 6.1.0-alpha
+Version: 6.2.0-alpha
 
                       .
 ```

product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/03_print_xdb_server_version.mdx

@@ -20,7 +20,7 @@ Examples
 
 ```text
 $ java -jar edb-repcli.jar -repversion -repsvrfile ~/pubsvrfile.prop
-6.1.0-alpha
+6.2.0-alpha
 
                       .
 ```

product_docs/docs/eprs/7/installing/index.mdx

@@ -10,7 +10,7 @@ navigation:
 - windows
 - installing_jdbc_driver
 - installation_details
-- upgrading
+- upgrading_replication_server
 - uninstalling
 ---
 

product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx

@@ -0,0 +1,32 @@
+---
+title: "Upgrading Replication Server"
+navTitle: Upgrading
+redirects:
+- /eprs/latest/10_appendix/02_upgrading_to_xdb6_2/
+- /eprs/latest/10_appendix/01_upgrading_to_xdb6_2/
+---
+
+<div id="upgrading_to_xdb6_2" class="registered_link"></div>
+
+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.
+
+A direct upgrade is supported only from Replication Server versions 6.2.x.
+
+After upgrading to version 6.2, you can then upgrade to 7.
+
+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 with the graphical user interface installer](upgrading_with_gui_installer)
+- [Upgrading from a Replication Server RPM package installation](upgrading_with_xdb_rpm_package)
+
+<div class="toctree" maxdepth="3">
+
+upgrading_with_gui_installer upgrading_with_xdb_rpm_package updating_sub_and_pub_ports
+
+</div>

product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx → product_docs/docs/eprs/7/installing/upgrading_replication_server/updating_sub_and_pub_ports.mdx

@@ -1,21 +1,22 @@
 ---
 title: "Updating the publication and subscription server ports"
 redirects:
-- /docs/eprs/latest/10_appendix/02_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports
+- /eprs/latest/10_appendix/02_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports/
+- /eprs/latest/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports/
 ---
 
 <div id="updating_sub_and_pub_ports" class="registered_link"></div>
 
-The newly installed publication server and subscription server of Replication Server 7.0 are configured to use the default port numbers 9051 and 9052, respectively. These port numbers are set in the Replication Server startup configuration file as described [Replication Server configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file).
+The newly installed publication server and subscription server of Replication Server 7 are configured to use the default port numbers 9051 and 9052, respectively. These port numbers are set in the Replication Server startup configuration file as described [Replication Server configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file).
 
-If your Replication Server 6.2.x replication systems were running under port numbers other than 9051 and 9052, you must adjust some of your settings in Replication Server 7.0 to continue to use these existing replication systems.
+If your Replication Server 6.2.x replication systems were running under port numbers other than 9051 and 9052, you must adjust some of your settings in Replication Server 7 to continue to use these existing replication systems.
 
 !!! Note
     The following changes regarding port 9052 and the subscription server are needed only if you're running a single-master replication system. If you're using only a multi-master replication system, then only the changes involving port 9051 and the publication server are needed.
 
 You can use either of two methods can correct this:
 
 -   To continue to use the old port numbers (other than 9051 and 9052) that were in use for Replication Server 6.2.x, stop the publication and subscription servers. Change the settings of the `PUBPORT` and `SUBPORT` parameters in the Replication Server Startup Configuration file from `9051` and `9052` to the old port numbers used by Replication Server 6.2.x. Restart the publication and subscription servers. Register the publication server and the subscription server with the old Replication Server 6.2.x port numbers along with the admin user and password as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server).
--   To use the default port numbers 9051 and 9052 with the Replication Server 7.0 replication systems, you must replace the old port numbers with the default port numbers 9051 and 9052. Register the publication server and the subscription server with port numbers 9051 and 9052 along with the admin user and password as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). For single-master replication systems only, you then need to change the port numbers stored in the control schema from the old port numbers to 9051 and 9052. First, perform the procedure described in [Subscription server network location](../../07_common_operations/06_managing_publication/01_updating_publication_server/#sub_server_network_loc), and then perform the procedure described in [Updating a subscription](../../05_smr_operation/05_managing_subscription/03_updating_subscription/#updating_subscription).
+-   To use the default port numbers 9051 and 9052 with the Replication Server 7 replication systems, you must replace the old port numbers with the default port numbers 9051 and 9052. Register the publication server and the subscription server with port numbers 9051 and 9052 along with the admin user and password as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). For single-master replication systems only, you then need to change the port numbers stored in the control schema from the old port numbers to 9051 and 9052. First, perform the procedure described in [Subscription server network location](../../07_common_operations/06_managing_publication/01_updating_publication_server/#sub_server_network_loc), and then perform the procedure described in [Updating a subscription](../../05_smr_operation/05_managing_subscription/03_updating_subscription/#updating_subscription).
 
 After making the changes, select **Refresh** in the Replication Server console. The replication tree of the Replication Server console displays the complete set of nodes for the replication systems.

product_docs/docs/eprs/7/installing/upgrading.mdx → product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx

@@ -1,8 +1,8 @@
 ---
 title: "Upgrading a Linux installation"
-navTitle: "Upgrading"
 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:
@@ -13,4 +13,4 @@ If you have an existing Replication Server installed on Linux, you can use yum t
 
 `yum upgrade ppas-xdb*`
 
-See [Upgrading from a Replication Server RPM Package Installation](../10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/) for details.
+See [Upgrading from a Replication Server RPM Package Installation](upgrading_with_xdb_rpm_package) for details.