diff --git a/product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx b/product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx deleted file mode 100644 index d63337f8b3a..00000000000 --- a/product_docs/docs/efm/4/03_installing_efm/13_initial_config.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "Initial configuration" ---- - - - -If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). - -After installing on each node of the cluster: - -1. Modify the [cluster properties file](04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. -2. Modify the [cluster members file](04_configuring_efm/03_cluster_members/#cluster_members) on each node. -3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. -4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](08_controlling_efm_service/#controlling-the-failover-manager-service). - - diff --git a/product_docs/docs/efm/4/03_installing_efm/09_efm4_rhel8_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx similarity index 56% rename from product_docs/docs/efm/4/03_installing_efm/09_efm4_rhel8_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx index bb653cd71fd..5374ce64157 100644 --- a/product_docs/docs/efm/4/03_installing_efm/09_efm4_rhel8_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/09_efm4_rhel8_ppcle.mdx @@ -1,11 +1,13 @@ --- -title: "RHEL 8 on IBM Power (ppc64le)" +title: "Installing Failover Manager on RHEL 8 IBM Power (ppc64le)" +navTitle: "RHEL 8 " --- -There are two steps to completing an installation: +There are three steps to completing an installation: - Setting up the repository - Installing the package +- Initial configuration For each step, you must be logged in as superuser. @@ -15,7 +17,7 @@ To log in as a superuser: sudo su - ``` -#### Setting up the Repository +## Setting up the repository 1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). @@ -55,10 +57,21 @@ sudo su - dnf -qy module disable postgresql ``` -#### Installing the Package +## Installing the package ```shell dnf -y install edb-efm ``` where `` is the version number of Failover Manager. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). + diff --git a/product_docs/docs/efm/4/03_installing_efm/10_efm4_rhel7_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx similarity index 64% rename from product_docs/docs/efm/4/03_installing_efm/10_efm4_rhel7_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx index 5ee3ee75545..19e3c681e3b 100644 --- a/product_docs/docs/efm/4/03_installing_efm/10_efm4_rhel7_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/10_efm4_rhel7_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 7 on IBM Power (ppc64le)" +title: "Installing Failover Manager on RHEL 7 IBM Power (ppc64le)" +navTitle: "RHEL 7" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). @@ -54,3 +55,13 @@ To request credentials that allow you to access an EnterpriseDB repository, see ```text yum -y install edb-efm42 ``` +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/11_efm4_sles15_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx similarity index 55% rename from product_docs/docs/efm/4/03_installing_efm/11_efm4_sles15_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx index 8cbc08eebe6..b47d1c114b5 100644 --- a/product_docs/docs/efm/4/03_installing_efm/11_efm4_sles15_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/11_efm4_sles15_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on IBM Power (ppc64le)" +title: "Installing Failover Manager on SLES 15 IBM Power (ppc64le)" +navTitle: "SLES 15" --- @@ -7,7 +8,7 @@ There are three steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) -- [Performing the initial configuration](12_initial_config) +- [Performing the initial configuration](#initial-configuration) For each step, you must be logged in as superuser. @@ -18,7 +19,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -43,7 +44,7 @@ SUSEConnect -p PackageHub/15.3/ppc64le zypper refresh ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-efmedb-efm<4x> @@ -51,3 +52,13 @@ zypper -n install edb-efmedb-efm<4x> Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/12_efm4_sles12_ppcle.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx similarity index 58% rename from product_docs/docs/efm/4/03_installing_efm/12_efm4_sles12_ppcle.mdx rename to product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx index 1fe443d8172..efa0caa80a0 100644 --- a/product_docs/docs/efm/4/03_installing_efm/12_efm4_sles12_ppcle.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/12_efm4_sles12_ppcle.mdx @@ -1,11 +1,13 @@ --- -title: "SLES 12 on IBM Power (ppc64le)" +title: "Installing Failover Manager on SLES 12 IBM Power (ppc64le)" +navTitle: "SLES 12" --- There are two steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) +- [Initial configuration](#initial-configuration) For each step, you must be logged in as superuser. @@ -51,3 +53,13 @@ zypper -n install edb-efm<4x> Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx new file mode 100644 index 00000000000..b87affd70fc --- /dev/null +++ b/product_docs/docs/efm/4/03_installing_efm/ibm_power_pcc64le/index.mdx @@ -0,0 +1,16 @@ +--- +title: "Installing Failover Manager on IBM Power (ppc64le)" +navTitle: "IBM Power (ppc64le)" +--- + + + + + +For operating system-specific install instructions, including accessing the repo, see: + + - [RHEL 8](09_efm4_rhel8_ppcle) + + - [RHEL 7](10_efm4_rhel7_ppcle) + - [SLES 15](11_efm4_sles15_ppcle) + - [SLES 12](12_efm4_sles12_ppcle) diff --git a/product_docs/docs/efm/4/03_installing_efm/index.mdx b/product_docs/docs/efm/4/03_installing_efm/index.mdx index a7083a78216..02260a9419b 100644 --- a/product_docs/docs/efm/4/03_installing_efm/index.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/index.mdx @@ -1,17 +1,25 @@ --- -title: "Installing Failover Manager" +title: "Installing Failover Manager on Linux" +navTitle: "Installing on Linux" redirects: - ../efm_user/03_installing_efm legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/4.0/installing_efm.html" - "/edb-docs/d/edb-postgres-failover-manager/user-guides/user-guide/4.1/installing_efm.html" +navigation: +- x86_amd64 +- ibm_power_pcc64le +- 13_initial_config +- 14_install_details --- +Native packages for Linux are available in the EDB repository. + For information about the platforms and versions supported by Failover Manager, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility#efm). !!! Note @@ -21,21 +29,20 @@ For information about the platforms and versions supported by Failover Manager, For platform-specific install instructions, including accessing the repo, see: - Linux x86-64 (amd64): - - [RHEL 8/OL 8](01_efm4_rhel_8_x86) + - [RHEL 8/OL 8](x86_amd64/01_efm4_rhel_8_x86) - - [Rocky Linux 8/AlmaLinux 8](02_efm4_other_linux8_x86) - - [RHEL 7/OL 7](03_efm4_rhel7_x86) - - [CentOS 7](04_efm4_centos7_x86) - - [SLES 15](05_efm4_sles15_x86) - - [SLES 12](06_efm4_sles12_x86) - - [Ubuntu 20.04/Debian 10](07_efm4_ubuntu20_deb10_x8) - - [Ubuntu 18.04/Debian 9](08_efm4_ubuntu18_deb9_x86) + - [Rocky Linux 8/AlmaLinux 8](x86_amd64/02_efm4_other_linux8_x86) + - [RHEL 7/OL 7](x86_amd64/03_efm4_rhel7_x86) + - [CentOS 7](x86_amd64/04_efm4_centos7_x86) + - [SLES 15](x86_amd64/05_efm4_sles15_x86) + - [SLES 12](x86_amd64/06_efm4_sles12_x86) + - [Ubuntu 20.04/Debian 10](x86_amd64/07_efm4_ubuntu20_deb10_x8) + - [Ubuntu 18.04/Debian 9](x86_amd64/08_efm4_ubuntu18_deb9_x86) - Linux on IBM Power (ppc64le): - - [RHEL 8](09_efm4_rhel8_ppcle) + - [RHEL 8](ibm_power_pcc64le/09_efm4_rhel8_ppcle) - - [RHEL 7](10_efm4_rhel7_ppcle) - - [SLES 15](11_efm4_sles15_ppcle) - - [SLES 12](12_efm4_sles12_ppcle) + - [RHEL 7](ibm_power_pcc64le/10_efm4_rhel7_ppcle) + - [SLES 15](ibm_power_pcc64le/11_efm4_sles15_ppcle) + - [SLES 12](ibm_power_pcc64le/12_efm4_sles12_ppcle) -After you complete the installation, see [Initial configuration](13_initial_config). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/01_efm4_rhel_8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx similarity index 68% rename from product_docs/docs/efm/4/03_installing_efm/01_efm4_rhel_8_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx index f4f3dc1127b..bbd7434491c 100644 --- a/product_docs/docs/efm/4/03_installing_efm/01_efm4_rhel_8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/01_efm4_rhel_8_x86.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 8/OL 8 on x86_64" +title: "Installing Failover Manager on RHEL 8/OL 8 x86" +navTitle: "RHEL 8/OL 8" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). @@ -47,4 +48,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co dnf -y install edb-efm42 ``` +## Initial configuration +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/02_efm4_other_linux8_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx similarity index 66% rename from product_docs/docs/efm/4/03_installing_efm/02_efm4_other_linux8_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx index 05966eb3b0f..c198cbaa6c2 100644 --- a/product_docs/docs/efm/4/03_installing_efm/02_efm4_other_linux8_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/02_efm4_other_linux8_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +title: "Installing Failover Manager on Rocky Linux 8/AlmaLinux 8 x86" +navTitle: "Rocky Linux 8/AlmaLinux 8" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). @@ -46,4 +47,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co dnf -y install edb-efm42 ``` +## Initial configuration +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/03_efm4_rhel7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx similarity index 67% rename from product_docs/docs/efm/4/03_installing_efm/03_efm4_rhel7_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx index bac5e349397..e0ec497e10c 100644 --- a/product_docs/docs/efm/4/03_installing_efm/03_efm4_rhel7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/03_efm4_rhel7_x86.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 7/OL 7 on x86_64" +title: "Installing Failover Manager on RHEL 7/OL 7 x86" +navTitle: "RHEL 7/OL 7" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). @@ -45,3 +46,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/04_efm4_centos7_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx similarity index 65% rename from product_docs/docs/efm/4/03_installing_efm/04_efm4_centos7_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx index 51f4798abd7..42d569f931a 100644 --- a/product_docs/docs/efm/4/03_installing_efm/04_efm4_centos7_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/04_efm4_centos7_x86.mdx @@ -1,5 +1,6 @@ --- -title: "CentOS 7 on x86_64" +title: "Installing Failover Manager on CentOS 7 x86" +navTitle: "CentOS 7" --- To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). @@ -39,3 +40,13 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/05_efm4_sles15_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx similarity index 55% rename from product_docs/docs/efm/4/03_installing_efm/05_efm4_sles15_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx index 0d279cc59eb..b0571570e73 100644 --- a/product_docs/docs/efm/4/03_installing_efm/05_efm4_sles15_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/05_efm4_sles15_x86.mdx @@ -1,12 +1,13 @@ --- -title: "SLES 15 on x86_64" +title: "Installing Failover Manager on SLES 15 x86" +navTitle: "SLES 15" --- There are three steps to completing an installation: - [Setting up the repository](#setting-up-the-repository) - [Installing the package](#installing-the-package) -- [Performing the initial configuration](12_initial_config) +- [Performing the initial configuration](#initial-configuration) For each step, you must be logged in as superuser. @@ -17,7 +18,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -42,7 +43,7 @@ SUSEConnect -p PackageHub/15.3/x86_64 zypper refresh ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-efm<4x> @@ -51,3 +52,13 @@ zypper -n install edb-efm<4x> Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/06_efm4_sles12_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx similarity index 68% rename from product_docs/docs/efm/4/03_installing_efm/06_efm4_sles12_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx index 3dc035cd446..c9fa3dbd81e 100644 --- a/product_docs/docs/efm/4/03_installing_efm/06_efm4_sles12_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/06_efm4_sles12_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on x86_64" +title: "Installing Failover Manager on SLES 12 x86" +navTitle: "SLES 12" --- To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the instructions to [access EDB software repositories](https://www.enterprisedb.com/repository-access-request). @@ -51,3 +52,13 @@ You can use the `zypper` package manager to install a Failover Manager agent on Where <4x> is the version of Failover Manager you are installing. +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/07_efm4_ubuntu20_deb10_x8.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx similarity index 56% rename from product_docs/docs/efm/4/03_installing_efm/07_efm4_ubuntu20_deb10_x8.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx index e8d3e25b0b6..dc06e9c646f 100644 --- a/product_docs/docs/efm/4/03_installing_efm/07_efm4_ubuntu20_deb10_x8.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/07_efm4_ubuntu20_deb10_x8.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 20.04/Debian 10 on x86_64" +title: "Installing Failover Manager on Ubuntu 20.04/Debian 10 x86" +navTitle: "Ubuntu 20.04/Debian 10" --- @@ -37,4 +38,13 @@ Use the EnterpriseDB APT repository to install Failover Manager. ```text apt-get -y install edb-efm42 ``` +## Initial configuration +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). diff --git a/product_docs/docs/efm/4/03_installing_efm/08_efm4_ubuntu18_deb9_x86.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx similarity index 54% rename from product_docs/docs/efm/4/03_installing_efm/08_efm4_ubuntu18_deb9_x86.mdx rename to product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx index 457aceb2a28..17e92960ce0 100644 --- a/product_docs/docs/efm/4/03_installing_efm/08_efm4_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/08_efm4_ubuntu18_deb9_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 18.04/Debian 9 on x86_64" +title: "Installing Failover Manager on Ubuntu 18.04/Debian 9 x86" +navTitle: "Ubuntu 18.04/Debian 9" --- To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the [EnterpriseDB website](https://www.enterprisedb.com/user/login). @@ -32,3 +33,13 @@ Use the EnterpriseDB APT repository to install Failover Manager. ```text apt-get -y install edb-efm42 ``` +## Initial configuration + +If you are using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/#controlling-the-failover-manager-service). \ No newline at end of file diff --git a/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx new file mode 100644 index 00000000000..1041a5811bd --- /dev/null +++ b/product_docs/docs/efm/4/03_installing_efm/x86_amd64/index.mdx @@ -0,0 +1,21 @@ +--- +title: "Installing Failover Manager on x86 (amd64)" +navTitle: "x86 (amd64)" +--- + + + + + +For operating system-specific install instructions, including accessing the repo, see: + + - [RHEL 8/OL 8](01_efm4_rhel_8_x86) + + - [Rocky Linux 8/AlmaLinux 8](02_efm4_other_linux8_x86) + - [RHEL 7/OL 7](03_efm4_rhel7_x86) + - [CentOS 7](04_efm4_centos7_x86) + - [SLES 15](05_efm4_sles15_x86) + - [SLES 12](06_efm4_sles12_x86) + - [Ubuntu 20.04/Debian 10](07_efm4_ubuntu20_deb10_x8) + - [Ubuntu 18.04/Debian 9](08_efm4_ubuntu18_deb9_x86) + diff --git a/product_docs/docs/efm/4/03_installing_efm/14_install_details.mdx b/product_docs/docs/efm/4/14_install_details.mdx similarity index 100% rename from product_docs/docs/efm/4/03_installing_efm/14_install_details.mdx rename to product_docs/docs/efm/4/14_install_details.mdx diff --git a/product_docs/docs/efm/4/index.mdx b/product_docs/docs/efm/4/index.mdx index 19de386b4f8..8191e637aac 100644 --- a/product_docs/docs/efm/4/index.mdx +++ b/product_docs/docs/efm/4/index.mdx @@ -12,6 +12,7 @@ navigation: - "#Installing" - 01_prerequisites - 03_installing_efm + - 14_install_details - 12_upgrading_existing_cluster - "#Configuring" - 14_configuring_streaming_replication diff --git a/product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx b/product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx deleted file mode 100644 index 48d46570678..00000000000 --- a/product_docs/docs/migration_toolkit/55/03_migration_methodology.mdx +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: "Migration methodology" - ---- - - - -You might consider migrating from one database to another for many reasons. Migration can allow you to take advantage of new or better technology. If your current database doesn't offer the right set of capabilities to allow you to scale the system, moving to a database that offers the functionality you need is the best move for your company. - -Migration can also be cost effective. Migrating systems with significant maintenance costs can save money spent on system upkeep. By consolidating the number of databases in use, you can also reduce in-house administrative costs. By using fewer database platforms (or possibly taking advantage of database compatibility), you can do more with your IT budget. - -Using more than one database platform can offer you a graceful migration path if a vendor raises their pricing or changes their company directive. EnterpriseDB has, for years, helped companies migrate their existing database systems to Postgres. - - - -## The migration process - -The migration path to Postgres that we recommend includes the following main steps: - -1. Start the migration process by determining the database objects and data to include in the migration. Form a migration team that includes someone with solid knowledge of the architecture and implementation of the source system. - -2. Identify potential migration problems. If it is an Oracle-to-EDB Postgres Advanced Server migration, consult the [EnterpriseDB Postgres Advanced Server documentation](/epas/latest/) for complete details about the compatibility features supported in EDB Postgres Advanced Server. Consider using the EnterpriseDB migration assessment service to help with this review. - -3. Prepare the migration environment. Obtain and install the needed software, and establish connectivity between the servers. - -4. If the migration involves a large body of data, consider migrating the schema definition before moving the data. Verify the results of the DDL migration and resolve any problems reported in the migration summary. [Migration errors](09_mtk_errors/#mtk_errors) includes information about resolving migration problems. - -5. Migrate the data. For small data sets, use Migration Toolkit. If it's an Oracle migration into EDB Postgres Advanced Server, and the data set is large or if you notice slow data transfer, take advantage of one of the other data movement methods available: - - - Use the EDB Postgres Advanced Server database link feature compatible with Oracle databases. - - If your data has BLOB or CLOB data, use the dblink_ora style database links instead of the Oracle style database links. - - Both of these methods use the Oracle Call Interface (OCI) to connect to Oracle. After connecting, use an SQL statement to select the data from the 'linked' Oracle database and insert the data into the EDB Postgres Advanced Server database. - -6. Confirm the results of the data migration, and resolve any problems reported in the migration summary. - -7. Convert applications to work with the newly migrated Postgres database. Applications that use open standard connectivity such as JDBC or ODBC normally require changes only to the database connection strings and selection of the EnterpriseDB driver. See [Connecting an application to Postgres](#connecting_application_postgres) for more information. - -8. Test the system performance, and tune the new server. If you're migrating into an EDB Postgres Advanced Server database, take advantage of EDB Postgres Advanced Server's performance tuning utilities: - - - Use Dynatune to dynamically adjust database configuration resources. - - Use Optimizer Hints to direct the query path. - - Use the `ANALYZE` command to retrieve database statistics. - - See [EDB Postgres Advanced Server](../../epas/latest) and [Database Compatibility for Oracle Developers](../../epas/latest/epas_compat_tools_guide/) for information about the performance tuning tools available with EDB Postgres Advanced Server. - - - -## Connecting an application to Postgres - -To convert a client application to use a Postgres database, you must modify the connection properties to specify the new target database. In the case of a Java application, change the JDBC driver name (`Class.forName`) and JDBC URL. - -A Java application running on Oracle might have the following connection properties: - -```text -Class.forName("oracle.jdbc.driver.OracleDriver"); -Connection con = -DriverManager.getConnection -("jdbc:oracle:thin:@localhost:1521:xe", - "user", - "password") -``` - -Modify the connection string to connect to a Postgres server: - -```text -Class.forName("com.edb.Driver") -Connection con = DriverManager.getConnection -("jdbc:edb://localhost:5444/edb", - "user", - "password"); -``` - -Converting an ODBC application to connect to an instance of Postgres is a two-step process. - -1. To connect an ODBC application, use an ODBC data source administrator to create a data source that defines the connection properties for the new target database. - - Most Linux and Windows systems include graphical tools that allow you to create and edit ODBC data sources. After installing ODBC, check the **Administrative Tools** menu for a link to the ODBC Data Source Administrator. Select **Add** to start the Create New Data Source wizard. Then, complete the dialogs to define the new target data source. - -2. Change the application to use the new data source. - - The application contains a call to `SQLConnect` or `SQLDriverConnect`. Edit the invocation to change the data source name. In the following example, the data source is named `OracleDSN`: - - ```text - result = SQLConnect(conHandle, // Connection handle - (returned) - "OracleDSN", SQL_NTS, // Data source name - username, SQL_NTS, // User name - password, SQL_NTS); // Password - ``` - -To connect to an instance of Postgres defined in a data source named `PostgresDSN`, change the data source name: - -```text -result = SQLConnect(conHandle, // Connection handle (returned) - "PostgresDSN", SQL_NTS, // Data source name - username, SQL_NTS, // User name - password, SQL_NTS); // Password -``` - -After establishing a connection between the application and the server, test the application to find any compatibility problems between the application and the migrated schema. In most cases, a simple change resolves any incompatibility that the application encounters. When a feature is not supported, use a workaround or third-party tool to provide the functionality required by the application. See [Migration errors](09_mtk_errors/#mtk_errors), for information about some common problems and their workarounds. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx index f74858050ff..a5f39c3e1c4 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx @@ -8,11 +8,10 @@ legacyRedirects: - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_sles.html" - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_centos_or_rhel.html" navigation: - - mtk_rel_notes - - 02_supported_operating_systems_and_database_versions - - 03_migration_methodology - - 04_functionality_overview - - 05_installing_mtk + - install_on_linux + - install_on_mac + - install_on_windows + - 13_upgrading_rpm_install --- @@ -21,15 +20,15 @@ Before installing Migration Toolkit, you must install Java (version 1.8.0 or lat You can install Migration Toolkit on: -- [Linux x86-64 (amd64) and IBM Power (ppc64le)](install_on_linux_using_edb_repo) +- [Linux x86-64 (amd64)](install_on_linux/x86_amd64) and [IBM Power (ppc64le)](install_on_linux/ibm_power_ppc64le) - [Windows x86-64](install_on_windows) - [Mac OS X](install_on_mac) -## Installing Source-Specific Drivers +## Installing source-specific drivers -Before invoking Migration Toolkit, you must download and install a freely available source-specific driver. To download a driver, or for a link to a vendor download site, see the [Third Party JDBC Drivers](https://www.enterprisedb.com/software-downloads-postgres#third-party-jdbc-drivers) on the Downloads page. +Before invoking Migration Toolkit, you must download and install a freely available source-specific driver. To download a driver, or for a link to a vendor download site, see [Third Party JDBC Drivers](https://www.enterprisedb.com/software-downloads-postgres#third-party-jdbc-drivers) on the Downloads page. After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx similarity index 91% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx index adab91ce0df..5deef52379e 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/09_mtk55_rhel8_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/09_mtk55_rhel8_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 8 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on RHEL 8 IBM Power (ppc64le)" +navTitle: "RHEL 8" --- There are two steps to completing an installation: @@ -15,7 +16,7 @@ To log in as a superuser: sudo su - ``` -## Setting up the Repository +## Setting up the repository 1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). @@ -55,9 +56,8 @@ sudo su - dnf -qy module disable postgresql ``` -## Installing the Package +## Installing the package ```shell dnf -y install edb-migrationtoolkit ``` - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx similarity index 94% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx index 6ca7ac63eff..0759e040d20 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/10_mtk55_rhel7_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/10_mtk55_rhel7_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 7 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on RHEL 7 IBM Power (ppc64le)" +navTitle: "RHEL 7" --- @@ -31,7 +32,7 @@ Before installing Migration toolkit: The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the EDB repository configuration file, assume superuser privileges and invoke the following command: @@ -68,7 +69,7 @@ The following steps provide detailed information about accessing the EnterpriseD --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-* -server-rpms" ``` -## Installing the Package +## Installing the package To install Migration Toolkit, run the following command. ```text diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx similarity index 90% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx index 3b00332523c..40012bec8b1 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/11_mtk55_sles15_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on SLES 15 IBM Power (ppc64le)" +navTitle: "SLES 15 " --- @@ -18,7 +19,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -43,7 +44,7 @@ SUSEConnect -p PackageHub/15.3/ppc64le zypper refresh ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-migrationtoolkit diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx similarity index 91% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx index 1a28617bb17..18c008ea2be 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/12_mtk55_sles12_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on IBM Power (ppc64le)" +title: "Installing Migration Toolkit on SLES 12 IBM Power (ppc64le)" +navTitle: "SLES 12 " --- @@ -18,7 +19,7 @@ sudo su - Before setting up the repository, you need to register with EDB. To receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). -## Setting up the Repository +## Setting up the repository Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps. @@ -47,7 +48,7 @@ zypper refresh zypper -n install java-1_8_0-openjdk ``` -## Installing the Package +## Installing the package ```shell zypper -n install edb-migrationtoolkit diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/index.mdx new file mode 100644 index 00000000000..cbc6623544c --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/index.mdx @@ -0,0 +1,17 @@ +--- +title: "Installing Migration Toolkit on IBM Power (ppc64le)" +navTitle: "IBM Power (ppc64le)" +--- + +For operating system-specific install instructions, see: + + + - [RHEL 8](09_mtk55_rhel8_ppcle) + + - [RHEL 7](10_mtk55_rhel7_ppcle) + - [SLES 15](11_mtk55_sles15_ppcle) + - [SLES 12](12_mtk55_sles12_ppcle) + +After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing source-specific drivers](../../#installing_drivers) for more information. + + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/index.mdx new file mode 100644 index 00000000000..6145e785acf --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/index.mdx @@ -0,0 +1,34 @@ +--- +title: "Installing on Linux" +navTitle: "Linux" +navigation: +- x86_amd64 +- ibm_power_ppc64le +--- + + +To install Migration Toolkit, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). + +For platform-specific install instructions, see: + +- Linux x86-64 (amd64): + - [RHEL 8/OL 8](x86_amd64/01_mtk55_rhel8_x86) + + - [Rocky Linux 8/AlmaLinux 8](x86_amd64/02_mtk55_other_linux8_x86) + - [RHEL 7/OL 7](x86_amd64/03_mtk55_rhel7_x86) + - [CentOS 7](x86_amd64/04_mtk55_centos7_x86) + - [SLES 15](x86_amd64/05_mtk55_sles15_x86) + - [SLES 12](x86_amd64/06_mtk55_sles12_x86) + - [Ubuntu 20.04/Debian 10](x86_amd64/07_mtk55_ubuntu20_deb10_x86) + - [Ubuntu 18.04/Debian 9](x86_amd64/08_mtk55_ubuntu18_deb9_x86) + +- Linux on IBM Power (ppc64le): + - [RHEL 8](ibm_power_ppc64le/09_mtk55_rhel8_ppcle) + + - [RHEL 7](ibm_power_ppc64le/10_mtk55_rhel7_ppcle) + - [SLES 15](ibm_power_ppc64le/11_mtk55_sles15_ppcle) + - [SLES 12](ibm_power_ppc64le/12_mtk55_sles12_ppcle) + +After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing source-specific drivers](../#installing_drivers) for more information. + + diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/01_mtk55_rhel8_x86.mdx similarity index 95% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/01_mtk55_rhel8_x86.mdx index f0511868666..ceb8bb20498 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/01_mtk55_rhel8_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/01_mtk55_rhel8_x86.mdx @@ -1,11 +1,12 @@ --- -title: "RHEL 8/OL 8 on x86_64" +title: "Installing Migration Toolkit on RHEL 8/OL 8 x86" +navTitle: "RHEL 8/OL 8" --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command @@ -56,7 +57,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/02_mtk55_other_linux8_x86.mdx similarity index 95% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/02_mtk55_other_linux8_x86.mdx index 0338dc2f0fe..e1db7cd2d2f 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/02_mtk55_other_linux8_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/02_mtk55_other_linux8_x86.mdx @@ -1,11 +1,12 @@ --- -title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +title: "Installing Migration Toolkit on Rocky Linux 8/AlmaLinux 8 x86" +navTitle: "Rocky Linux 8/AlmaLinux 8" --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command @@ -56,7 +57,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/03_mtk55_rhel7_x86.mdx similarity index 95% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/03_mtk55_rhel7_x86.mdx index e0a0046df40..9a9c04e3b3b 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/03_mtk55_rhel7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/03_mtk55_rhel7_x86.mdx @@ -1,11 +1,12 @@ --- -title: "RHEL 7/OL 7 on x86_64" +title: "Installing Migration Toolkit on RHEL 7/OL 7 x86" +navTitle: "RHEL 7/OL 7 " --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text @@ -46,7 +47,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/04_mtk55_centos7_x86.mdx similarity index 95% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/04_mtk55_centos7_x86.mdx index 72c0ba3e43a..0dce19a5033 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/04_mtk55_centos7_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/04_mtk55_centos7_x86.mdx @@ -1,11 +1,12 @@ --- -title: "CentOS 7 on x86_64" +title: "Installing Migration Toolkit on CentOS 7 x86" +navTitle: "CentOS 7" --- You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. -## Creating a Repository Configuration File +## Creating a repository configuration file 1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text @@ -46,7 +47,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. After installing Migration Toolkit, you must configure the installation. Perform the following steps before invoking Migration Toolkit. -## Using Migration Toolkit with IDENT Authentication +## Using Migration Toolkit with IDENT authentication By default, the `pg_hba.conf` file for the RPM installer enforces `IDENT` authentication for remote clients. Before invoking Migration Toolkit, you must either modify the `pg_hba.conf` file, changing the authentication method to a form other than `IDENT` (and restarting the server), or perform the following steps to ensure that an `IDENT` server is accessible: diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx similarity index 95% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx index 8767d6da935..705ca7532b9 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/05_mtk55_sles15_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/05_mtk55_sles15_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on x86_64" +title: "Installing Migration Toolkit on SLES 15 x86" +navTitle: "SLES 15" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx similarity index 96% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx index cbfaff50df8..431eb100c3f 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/06_mtk55_sles12_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/06_mtk55_sles12_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on x86_64" +title: "Installing Migration Toolkit on SLES 12 x86" +navTitle: "SLES 12" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx similarity index 92% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx index fdf830574d5..f6093923a18 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/07_mtk55_ubuntu20_deb10_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/07_mtk55_ubuntu20_deb10_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 20.04/Debian 10 on x86_64" +title: "Installing Migration Toolkit on Ubuntu 20.04/Debian 10 x86" +navTitle: "Ubuntu 20.04/Debian 10" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx similarity index 92% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx rename to product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx index 89c2082f05b..ec2fa554a5a 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/08_mtk55_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/08_mtk55_ubuntu18_deb9_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 18.04/Debian 9 on x86_64" +title: "Installing Migration Toolkit on Ubuntu 18.04/Debian 9 x86" +navTitle: "Ubuntu 18.04/Debian 9" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/index.mdx new file mode 100644 index 00000000000..46020334941 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/x86_amd64/index.mdx @@ -0,0 +1,18 @@ +--- +title: "Installing Migration Toolkit on Linux x86 (amd64)" +navTitle: "Intel x86 (amd64)" +--- + +For operating system-specific install instructions, see: + + - [RHEL 8/OL 8](01_mtk55_rhel8_x86) + + - [Rocky Linux 8/AlmaLinux 8](02_mtk55_other_linux8_x86) + - [RHEL 7/OL 7](03_mtk55_rhel7_x86) + - [CentOS 7](04_mtk55_centos7_x86) + - [SLES 15](05_mtk55_sles15_x86) + - [SLES 12](06_mtk55_sles12_x86) + - [Ubuntu 20.04/Debian 10](07_mtk55_ubuntu20_deb10_x86) + - [Ubuntu 18.04/Debian 9](08_mtk55_ubuntu18_deb9_x86) + +After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing source-specific drivers](../../#installing_drivers) for more information. \ No newline at end of file diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx deleted file mode 100644 index 7e0ffdf1305..00000000000 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/index.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: "Installing on Linux using the EDB Repository" ---- - - -To install Migration Toolkit, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). - -For platform-specific install instructions, see: - -- Linux x86-64 (amd64): - - [RHEL 8/OL 8](01_mtk55_rhel8_x86) - - - [Rocky Linux 8/AlmaLinux 8](02_mtk55_other_linux8_x86) - - [RHEL 7/OL 7](03_mtk55_rhel7_x86) - - [CentOS 7](04_mtk55_centos7_x86) - - [SLES 15](05_mtk55_sles15_x86) - - [SLES 12](06_mtk55_sles12_x86) - - [Ubuntu 20.04/Debian 10](07_mtk55_ubuntu20_deb10_x86) - - [Ubuntu 18.04/Debian 9](08_mtk55_ubuntu18_deb9_x86) - -- Linux on IBM Power (ppc64le): - - [RHEL 8](09_mtk55_rhel8_ppcle) - - - [RHEL 7](10_mtk55_rhel7_ppcle) - - [SLES 15](11_mtk55_sles15_ppcle) - - [SLES 12](12_mtk55_sles12_ppcle) - -After installing Migration Toolkit, you must install the appropriate source-specific drivers before performing a migration. See [Installing Source-Specific Drivers](../#installing_drivers) for more information. - - diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx index 414f9507f7b..b4854b1e00d 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_mac.mdx @@ -1,5 +1,6 @@ --- title: "Installing on Mac OS X" +navTitle: "Mac OS X" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx index 715ccbb189f..7b44f1f29de 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_windows.mdx @@ -1,5 +1,6 @@ --- title: "Installing on Windows" +navTitle: "Windows" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/13_upgrading_rpm_install.mdx b/product_docs/docs/migration_toolkit/55/13_upgrading_rpm_install.mdx similarity index 93% rename from product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/13_upgrading_rpm_install.mdx rename to product_docs/docs/migration_toolkit/55/13_upgrading_rpm_install.mdx index 376519e4f44..aaefeca7f34 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux_using_edb_repo/13_upgrading_rpm_install.mdx +++ b/product_docs/docs/migration_toolkit/55/13_upgrading_rpm_install.mdx @@ -1,5 +1,5 @@ --- -title: Upgrading an RPM Installation +title: Upgrading an RPM installation --- If you have an existing RPM installation, 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: diff --git a/product_docs/docs/migration_toolkit/55/index.mdx b/product_docs/docs/migration_toolkit/55/index.mdx index 1952af45ab9..a683cc5e966 100644 --- a/product_docs/docs/migration_toolkit/55/index.mdx +++ b/product_docs/docs/migration_toolkit/55/index.mdx @@ -8,6 +8,7 @@ navigation: - 03_migration_methodology - 04_functionality_overview - 05_installing_mtk + - 13_upgrading_rpm_install ---