From 7da104cd292f008cd1374d0951701912f181c132 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 17 Aug 2023 12:03:02 +0530 Subject: [PATCH 01/14] EPAS 15 - Log file fix as per DB-2428 Removed Log rotation file and Sudo configuration file and updated Logs and Lock files as per [DB-2428](https://enterprisedb.atlassian.net/browse/DB-2428) --- .../linux_install_details/component_locations.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx index 2619fc2125c..f675e154572 100644 --- a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx @@ -22,10 +22,8 @@ The RPM installers place EDB Postgres Advanced Server components in the director | Documentation | `/usr/edb/as15/share/doc` | | Contrib | `/usr/edb/as15/share/contrib` | | Data | `/var/lib/edb/as15/data` | -| Logs | `/var/log/as15` | -| Lock files | `/var/lock/as15` | -| Log rotation file | `/etc/logrotate.d/as15` | -| Sudo configuration file | `/etc/sudoers.d/as15` | +| Logs | `/var/log/edb/as15` | +| Lock files | `/var/lock/edb/as15` | | Binary to access VIP without sudo | `/usr/edb/as15/bin/secure` | | Backup area | `/var/lib/edb/as15/backups` | | Templates | `/usr/edb/as15/share` | From ef38a8614863f29c2ef54aa8aa5961c4f8a7c635 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 17 Aug 2023 13:33:22 +0530 Subject: [PATCH 02/14] removed and update components as per feedback from Tushar --- .../installing/linux_install_details/component_locations.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx index f675e154572..bcdd65f4541 100644 --- a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx @@ -18,13 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as15/bin` | | Libraries | `/usr/edb/as15/lib` | -| Cluster configuration files | `/etc/edb/as15` | +| Cluster configuration files | `/var/lib/edb/as15` | | Documentation | `/usr/edb/as15/share/doc` | | Contrib | `/usr/edb/as15/share/contrib` | | Data | `/var/lib/edb/as15/data` | | Logs | `/var/log/edb/as15` | | Lock files | `/var/lock/edb/as15` | -| Binary to access VIP without sudo | `/usr/edb/as15/bin/secure` | | Backup area | `/var/lib/edb/as15/backups` | | Templates | `/usr/edb/as15/share` | | Procedural Languages | `/usr/edb/as15/lib or /usr/edb/as15/lib64` | From ddbc60fd927e6badcf8e25ecdc115a4a31ca1308 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 21 Aug 2023 11:59:10 +0530 Subject: [PATCH 03/14] Updated v14 to v11 with same edits --- .../linux_install_details/component_locations.mdx | 9 +++------ .../linux_install_details/component_locations.mdx | 9 +++------ .../linux_install_details/component_locations.mdx | 9 +++------ .../linux_install_details/component_locations.mdx | 9 +++------ 4 files changed, 12 insertions(+), 24 deletions(-) diff --git a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx index ab97cfda841..7a657f60ef5 100644 --- a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx @@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as11/bin` | | Libraries | `/usr/edb/as11/lib` | -| Cluster configuration files | `/etc/edb/as11` | +| Cluster configuration files | `/var/lib/edb/as11` | | Documentation | `/usr/edb/as11/share/doc` | | Contrib | `/usr/edb/as11/share/contrib` | | Data | `/var/lib/edb/as11/data` | -| Logs | `/var/log/as11` | -| Lock files | `/var/lock/as11` | -| Log rotation file | `/etc/logrotate.d/as11` | -| Sudo configuration file | `/etc/sudoers.d/as11` | -| Binary to access VIP without sudo | `/usr/edb/as11/bin/secure` | +| Logs | `/var/log/edb/as11` | +| Lock files | `/var/lock/edb/as11` | | Backup area | `/var/lib/edb/as11/backups` | | Templates | `/usr/edb/as11/share` | | Procedural Languages | `/usr/edb/as11/lib or /usr/edb/as11/lib64` | diff --git a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx index 7f5a8778d12..83777c8ccc9 100644 --- a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx @@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as12/bin` | | Libraries | `/usr/edb/as12/lib` | -| Cluster configuration files | `/etc/edb/as12` | +| Cluster configuration files | `/var/lib/edb/as12` | | Documentation | `/usr/edb/as12/share/doc` | | Contrib | `/usr/edb/as12/share/contrib` | | Data | `/var/lib/edb/as12/data` | -| Logs | `/var/log/as12` | -| Lock files | `/var/lock/as12` | -| Log rotation file | `/etc/logrotate.d/as12` | -| Sudo configuration file | `/etc/sudoers.d/as12` | -| Binary to access VIP without sudo | `/usr/edb/as12/bin/secure` | +| Logs | `/var/log/edb/as12` | +| Lock files | `/var/lock/edb/as12` | | Backup area | `/var/lib/edb/as12/backups` | | Templates | `/usr/edb/as12/share` | | Procedural Languages | `/usr/edb/as12/lib or /usr/edb/as12/lib64` | diff --git a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx index 9f1b374a8eb..1954eaade0c 100644 --- a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx @@ -17,15 +17,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as13/bin` | | Libraries | `/usr/edb/as13/lib` | -| Cluster configuration files | `/etc/edb/as13` | +| Cluster configuration files | `/var/lib/edb/as13` | | Documentation | `/usr/edb/as13/share/doc` | | Contrib | `/usr/edb/as13/share/contrib` | | Data | `/var/lib/edb/as13/data` | -| Logs | `/var/log/as13` | -| Lock files | `/var/lock/as13` | -| Log rotation file | `/etc/logrotate.d/as13` | -| Sudo configuration file | `/etc/sudoers.d/as13` | -| Binary to access VIP without sudo | `/usr/edb/as13/bin/secure` | +| Logs | `/var/log/edb/as13` | +| Lock files | `/var/lock/edb/as13` | | Backup area | `/var/lib/edb/as13/backups` | | Templates | `/usr/edb/as13/share` | | Procedural Languages | `/usr/edb/as13/lib or /usr/edb/as13/lib64` | diff --git a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx index 7010acb2381..7d84735bec9 100644 --- a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx +++ b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx @@ -17,15 +17,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director | --------------------------------- | ------------------------------------------ | | Executables | `/usr/edb/as14/bin` | | Libraries | `/usr/edb/as14/lib` | -| Cluster configuration files | `/etc/edb/as14` | +| Cluster configuration files | `/var/lib/edb/as14` | | Documentation | `/usr/edb/as14/share/doc` | | Contrib | `/usr/edb/as14/share/contrib` | | Data | `/var/lib/edb/as14/data` | -| Logs | `/var/log/as14` | -| Lock files | `/var/lock/as14` | -| Log rotation file | `/etc/logrotate.d/as14` | -| Sudo configuration file | `/etc/sudoers.d/as14` | -| Binary to access VIP without sudo | `/usr/edb/as14/bin/secure` | +| Logs | `/var/log/edb/as14` | +| Lock files | `/var/lock/edb/as14` | | Backup area | `/var/lib/edb/as14/backups` | | Templates | `/usr/edb/as14/share` | | Procedural Languages | `/usr/edb/as14/lib or /usr/edb/as14/lib64` | From 836845aedb01b1a0ecaa35bab1031d07edd2cf0b Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 24 Aug 2023 17:53:36 -0700 Subject: [PATCH 04/14] Update index.mdx removed Extreme HA nomenclature - (link may still need to be updated if path changes) --- product_docs/docs/pgd/5/quickstart/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index e7d45925288..9101908990a 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,7 +20,7 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. !!! Note Fully managed BigAnimal - If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as the Extreme High Availability option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal Extreme High Availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview). + If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal Distributed High Availability clusters](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview). PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: From 63a60c7013e4ff394e3a1956dcdd480a6b3d13eb Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Thu, 24 Aug 2023 18:13:29 -0700 Subject: [PATCH 05/14] Update deployments.mdx updated deployment info --- product_docs/docs/pgd/5/deployments.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index f57916d3e1b..743593a332a 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,9 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account where it's operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. The addition of extreme-high-availability support through EDB Postgres Distributed (PGD) allows single-region Always On Gold clusters. These clusters are two PGD groups in different availability zones in a single cloud region, with a witness node in a third availability zone. See [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) in the [BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. -Coming soon: - -- EDB Postgres Distributed for Kubernetes will be a Kubernetes operator designed, developed, and supported by EDB. It will cover the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server and additional supported platforms including IBM Power and OpenShift. +- EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From 56d335b118bf7a1ff278bc01e2adc5ff08f67883 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 05:24:40 -0400 Subject: [PATCH 06/14] fixed link to BA docs --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 743593a332a..365f7b6ff22 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From e2854896eeeeb40e39c10bd1ed5933e0ea7a8185 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 08:54:26 -0400 Subject: [PATCH 07/14] Replication Server: adding driver step to upgrade instructions --- .../eprs/7/installing/upgrading_replication_server/index.mdx | 3 ++- .../upgrading_replication_server/upgrading_linux.mdx | 3 +++ .../upgrading_with_gui_installer.mdx | 2 ++ .../upgrading_with_xdb_rpm_package.mdx | 2 ++ 4 files changed, 9 insertions(+), 1 deletion(-) 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 35567da06db..48eb227facf 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 @@ -15,11 +15,12 @@ It is assumed that you are installing Replication Server 7.x on the same host ma 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 from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) - For more details on upgrading Replication Server, see: - [Updating the publication and subscription server](updating_sub_and_pub_ports) - [Upgrading from a Replication Server 7.x installation on Linux](upgrading_linux) - [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](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + 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 9649957e183..988eaf4f128 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 @@ -15,3 +15,6 @@ If you have an existing Replication Server 7.x installation on Linux, you can us `yum upgrade edb-xdb*` 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. + +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx index 6ea33561b9a..d15969f4d99 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx @@ -47,6 +47,8 @@ You can upgrade to Replication Server 7 using the graphical user interface insta If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console 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). The existing replication systems appear in the replication tree of the Replication Server Console. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink (for Linux) to it or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + You are now ready to use Replication Server 7 to create new replication systems and manage existing ones. !!! Note 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 ef0d1a47e7e..97c6a720728 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 @@ -183,4 +183,6 @@ If you're using Replication Server 6.2.x that was installed using the Replicatio If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console 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)). The existing replication systems appear in the replication tree of the Replication Server console. +After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information. + You are now ready to use Replication Server 7 to create new replication systems and manage existing ones. From f8e108c2f53001fd6623615aa2f2b5acaecc67e5 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 10:20:06 -0400 Subject: [PATCH 08/14] BigAnimal: a few more name change misses --- product_docs/docs/biganimal/release/overview/updates.mdx | 2 +- .../using_cluster/03_modifying_your_cluster/index.mdx | 6 +++--- .../biganimal/release/using_cluster/managing_replicas.mdx | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index 8ade89424af..04deef53917 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -8,7 +8,7 @@ EDB reserves the right to upgrade customers to the latest minor version without In some cases, these updates might terminate existing network connections to your clusters. If that happens, the outage is typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. -If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an extreme-high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). +If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). ## Connectivity issues after an automatic upgrade diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx index 22468f65f91..c70eceb791b 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx @@ -25,14 +25,14 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre | Settings | Tab | Notes | | ---------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to an extreme-high-availability cluster or vice versa. | + | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to an distributed high-availability cluster or vice versa. | | Number of replicas (for a high-availability cluster) | **Cluster Info** | — | | Cluster name and password | **Cluster Settings** | — | | Instance type | **Cluster Settings** | Changing the instance type can incur higher cloud infrastructure charges. | | Volume type | **Cluster Settings** | You can't switch between the io2 and io2 Block Express volume types in an AWS cluster. | | Volume properties | **Cluster Settings** | It can take up to six hours to tune IOPS or resize the disks of your cluster because AWS requires a cooldown period after volume modifications, as explained in [Limitations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html). The volume properties are disabled and can't be modified while this is in progress. | | Networking type (public or private) | **Cluster Settings** | If you're using Azure and previously set up a private link and want to change to a public network, you must remove the private link resources before making the change. | - | Nodes (for an extreme-high-availability cluster) | **Data Groups** | — | + | Nodes (for an distributed high-availability cluster) | **Data Groups** | — | | Database configuration parameters | **DB Configuration** | If you're using faraway replicas, only a small subset of parameters are editable. These parameters need to be modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica) for details. | | Retention period for backups | **Additional Settings** | — | | Custom maintenance window | **Additional Settings** | Set or modify a maintenance window in which maintenance upgrades occur for the cluster. See [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). | @@ -48,7 +48,7 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre ## Modify a data group -You can modify the data groups in your extreme-high-availability cluster by editing the configuration settings. +You can modify the data groups in your distributed high-availability cluster by editing the configuration settings. 1. Sign in to the [BigAnimal portal](https://portal.biganimal.com). diff --git a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx index 55073ed6224..07a6eff2185 100644 --- a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx @@ -97,7 +97,7 @@ You can promote a faraway replica to a full-fledged cluster, which makes it capa 1. The cluster settings are populated with values inherited from the source cluster. You can edit the cluster settings while creating your cluster. !!! NoteNotes - - You can promote a faraway replica to a single node or high-availability cluster but not to an extreme-high-availability cluster. + - You can promote a faraway replica to a single node or high-availability cluster but not to an distributed high-availability cluster. - While promoting a replica to a cluster, you can't modify the **Provider** and **Region** fields and the **Database Type** section or enable read-only workloads. 1. Select **Promote Replica**. From 6748fb249e43e92afdb9e93b0cb11c6e13e536a6 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 25 Aug 2023 10:49:28 -0400 Subject: [PATCH 09/14] update to terminology used in BA docs --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 365f7b6ff22..8bd88c5b120 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or an EDB hosted account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed, high availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From 036c2b210836982e89250e4e48805cb852b76538 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 11:14:28 -0400 Subject: [PATCH 10/14] Homepage: What's new - epas reorg --- src/pages/index.js | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/pages/index.js b/src/pages/index.js index 9ae45ffbb86..8358dcdc884 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -99,18 +99,18 @@ const Page = () => ( className="homepage-headling-link" to="/pgd/latest/reference/" > - EDB Postgres Distributed's ready reference + Find the EPAS content you're looking for

- Use the new reference section in EDB Postgres Distributed to - quickly look up views, catalogs, functions, and variables. - It's a new view of the documentation designed to centralize - essential information and speed up your development. + Whether you are an application programmer trying to debug your + programs or a DBA configuring your database, the new structure + of the EDB Postgres Advanced Server documentation makes + finding relevant content a snap.

From 82b42548c1eeec1df086b4a7c6d391fe24c202ea Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Fri, 25 Aug 2023 11:22:47 -0400 Subject: [PATCH 11/14] fixed link (keeping preview until GA) --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 8bd88c5b120..ea5c28523f4 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From 56945e6d8f5aa889c072bcf2819e8e61aca2921c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 11:36:36 -0400 Subject: [PATCH 12/14] fixed articles --- product_docs/docs/biganimal/release/overview/updates.mdx | 2 +- .../release/using_cluster/03_modifying_your_cluster/index.mdx | 4 ++-- .../biganimal/release/using_cluster/managing_replicas.mdx | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index 04deef53917..f232efe1632 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -8,7 +8,7 @@ EDB reserves the right to upgrade customers to the latest minor version without In some cases, these updates might terminate existing network connections to your clusters. If that happens, the outage is typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. -If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). +If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of a distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). ## Connectivity issues after an automatic upgrade diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx index c70eceb791b..69f3e3dfed0 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx @@ -25,14 +25,14 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre | Settings | Tab | Notes | | ---------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to an distributed high-availability cluster or vice versa. | + | Cluster type | **Cluster Info** | You can't switch from a single-node cluster or a high-availability cluster to a distributed high-availability cluster or vice versa. | | Number of replicas (for a high-availability cluster) | **Cluster Info** | — | | Cluster name and password | **Cluster Settings** | — | | Instance type | **Cluster Settings** | Changing the instance type can incur higher cloud infrastructure charges. | | Volume type | **Cluster Settings** | You can't switch between the io2 and io2 Block Express volume types in an AWS cluster. | | Volume properties | **Cluster Settings** | It can take up to six hours to tune IOPS or resize the disks of your cluster because AWS requires a cooldown period after volume modifications, as explained in [Limitations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html). The volume properties are disabled and can't be modified while this is in progress. | | Networking type (public or private) | **Cluster Settings** | If you're using Azure and previously set up a private link and want to change to a public network, you must remove the private link resources before making the change. | - | Nodes (for an distributed high-availability cluster) | **Data Groups** | — | + | Nodes (for a distributed high-availability cluster) | **Data Groups** | — | | Database configuration parameters | **DB Configuration** | If you're using faraway replicas, only a small subset of parameters are editable. These parameters need to be modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica) for details. | | Retention period for backups | **Additional Settings** | — | | Custom maintenance window | **Additional Settings** | Set or modify a maintenance window in which maintenance upgrades occur for the cluster. See [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). | diff --git a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx index 07a6eff2185..2f0727e496a 100644 --- a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx @@ -97,7 +97,7 @@ You can promote a faraway replica to a full-fledged cluster, which makes it capa 1. The cluster settings are populated with values inherited from the source cluster. You can edit the cluster settings while creating your cluster. !!! NoteNotes - - You can promote a faraway replica to a single node or high-availability cluster but not to an distributed high-availability cluster. + - You can promote a faraway replica to a single node or high-availability cluster but not to a distributed high-availability cluster. - While promoting a replica to a cluster, you can't modify the **Provider** and **Region** fields and the **Database Type** section or enable read-only workloads. 1. Select **Promote Replica**. From 915f86a4bbf3864cce2a9f4dd7da571a291e7fa2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 12:32:25 -0400 Subject: [PATCH 13/14] updated links --- src/pages/index.js | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/src/pages/index.js b/src/pages/index.js index 8358dcdc884..89f663535ac 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -95,10 +95,7 @@ const Page = () => (

- + Find the EPAS content you're looking for

@@ -114,7 +111,7 @@ const Page = () => (

- + Find out more →

From e5c26577be39898868423562bdf17b3a13572746 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 25 Aug 2023 15:12:54 -0400 Subject: [PATCH 14/14] PGD: fixing link and tweaking language --- product_docs/docs/pgd/5/quickstart/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index 9101908990a..7bd143a9660 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,7 +20,7 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. !!! Note Fully managed BigAnimal - If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal Distributed High Availability clusters](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview). + If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview). PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: