INSTALLING AND UPGRADING

• Installing Postgres Enterprise Manager server
  • Linux x86-64 (amd64)
    • Red Hat Enterprise Linux (RHEL) and derivatives
    • SUSE Linux Enterprise (SLES)
    • Debian and derivatives
  • Linux Installing Postgres Enterprise Manager server on Linux IBM Power (ppc64le)
    • Red Hat Enterprise Linux (RHEL) and derivatives
    • SUSE Linux Enterprise (SLES)
  • Linux Installing Postgres Enterprise Manager server on Linux AArch64 (ARM64)
    • Red Hat Enterprise Linux (RHEL) and derivatives
    • Debian and derivatives
  • Windows
    • Dependencies of the PEM Server and Agent on Linux
      • OpenSSL
      • Libcurl
      • SNMP++
      • Boost libraries
    • Installing Postgres Enterprise Manager server on Linux x86 (amd64)
      • Red Hat Enterprise Linux (RHEL) and derivatives
      • SUSE Linux Enterprise (SLES)
      • Debian and derivatives
    • Installing Postgres Enterprise Manager server on Linux AArch64 (ARM64)
      • Red Hat Enterprise Linux (RHEL) and derivatives
      • Debian and derivatives
    • Installing Postgres Enterprise Manager server on Linux IBM Power (ppc64le)
      • Red Hat Enterprise Linux (RHEL)
      • SUSE Linux Enterprise (SLES)
    • Installing Postgres Enterprise Manager server on Windows
      • Installing the PEM server and PEM-HTTPD on the same host
      • Installing the PEM server and PEM-HTTPD on separate hosts
      • Installing the PEM server on an existing Postgres servers
    • Creating an EDB repository on an isolated network
    • Configuring the PEM server on Linux
      • Configuring the PEM Server
      • Post-configuration steps when web server and PEM backend database are installed separately
      • Accessing the PEM application
    • Installing Postgres Enterprise Manager in HA Patterns
      • HA PEM using the C1 architecture with EFM and a Virtual IP
      • HA PEM using the S1 architecture with EFM and a Virtual IP
      • Storing user settings in the backend, accessible to all web application instances
      • HA PEM using the SM architecture with Patroni
      • Generating SSL files for HA PEM backend hosts
• Installing Postgres Enterprise Manager agent
  • Linux x86-64 (amd64)
    • Red Hat Enterprise Linux (RHEL) and derivatives
    • SUSE Linux Enterprise (SLES)
    • Debian and derivatives
  • Linux Installing Postgres Enterprise Manager server on Linux IBM Power (ppc64le)
    • Red Hat Enterprise Linux (RHEL) and derivatives
    • SUSE Linux Enterprise (SLES)
  • Linux Installing Postgres Enterprise Manager server on Linux AArch64 (ARM64)
    • Red Hat Enterprise Linux (RHEL) and derivatives
    • Debian and derivatives
  • Windows
    • Installing Postgres Enterprise Manager agent on Linux x86 (amd64)
      • Red Hat Enterprise Linux (RHEL) and derivatives
      • SUSE Linux Enterprise (SLES)
      • Debian and derivatives
    • Installing Postgres Enterprise Manager agent on Linux AArch64 (ARM64)
      • Red Hat Enterprise Linux (RHEL) and derivatives
      • Debian and derivatives
    • Installing Postgres Enterprise Manager agent on Linux IBM Power (ppc64le)
      • Red Hat Enterprise Linux (RHEL)
      • SUSE Linux Enterprise (SLES)
    • Installing Postgres Enterprise Manager agent on Windows
      • Invoking the agent installer from the command ine
• Configuring user authentication in PEM
  • Configuring the PEM server to use two-factor authentication
    • Mail server configuration
  • Configuring the PEM server to use Kerberos authentication
    • 1. Install Kerberos, the PEM server, and the PEM backend database
    • 2. Add principals on Kerberos server
    • 3. Extract key tables from Kerberos server
    • 4. Configure the PEM backend database server
    • 5. Obtain and view the initial ticket
    • 6. Configure the PEM server
    • 7. Browser settings
  • Configuring the PEM server to use Windows Active Directory domain services for Kerberos authentication (SSPI)
    • 1. Install Active Directory, the PEM server, and the PEM backend database server
    • 2. Create users in Active Directory to map with service principals
    • 3. Extract key tables from Active Directory
    • 4. Configure the PEM backend database server
    • 5. Obtain and view the initial ticket
    • 6. Configure the PEM server
• Connection pooling using PgBouncer
  • Preparing the PEM database server
    • Prerequisites
    • Creating users and roles for PgBouncer-PEM connections
    • Updating the configuration files to allow PgBouncer-PEM connections
    • Creating the SSL key and certificate for PgBouncer-PEM authentication
  • Configuring PgBouncer
    • Prerequisites
      • EDB PgBouncer and PgBouncer installation considerations
    • Configuring PgBouncer
  • Configuring the PEM agent
    • Prerequisites
    • Configuring a new PEM agent
    • Configuring an existing PEM agent
• Upgrade and migration
  • Upgrading a PEM installation
    • Upgrading a PEM installation on a Linux host
      • Upgrading a PEM server installation
      • Configuring the PEM server
      • Upgrading a PEM agent installation
    • Upgrading a PEM installation on a Windows host
      • Upgrading a PEM agent on a Windows host
      • Upgrading the PEM server on a Windows host
    • Upgrading an HA PEM installation
      • Upgrade the primary
      • Upgrade the replicas
      • Upgrade the primary backend
      • Upgrade the replica backends
      • Upgrade the web applications
  • PEM upgrade best practices and remediation
    • How PEM upgrades preserve permissions
      • Check your cluster before upgrading
    • Dos and don’ts
      • Before the upgrade
      • During the upgrade
      • After the upgrade
    • Pre-upgrade preparation
      • Step 1 — Stop PEM services
      • Step 2 — Transfer ownership (only if changing ownership)
      • Step 3 — Register default privileges for the upgrade role
      • Step 4 — Revoke orphaned defaults from the old role (optional, only if you changed ownership)
      • Step 5 — Schema USAGE safety net
      • Step 6 — Re-run the verification query and upgrade
    • Post-upgrade verification
    • Remediation for already-affected clusters
    • Example: upgrade with an ownership change
  • Upgrading the PEM backend Postgres database
  • Adding entries for PEM Agens and admins to connect to PEM server
  • Adding entries (localhost) for PEM Agens and admins to connect to PEM server
  • Upgrading SQL Profiler
  • Upgrading the PEM web server
    • Upgrading the web server on Linux
      • RHEL / Rocky Linux / AlmaLinux / Oracle Linux
      • Debian / Ubuntu
      • SLES
      • Versioning in RHEL and RHEL derivatives
    • Upgrading PEM-HTTPD on Windows
  • Moving the PEM server
    • If the PEM agent resides on Linux
    • If the PEM agent resides on Windows
• Splitting an existing PEM server
  • Install PEM on the new host
  • Copy all data from your existing PEM instance
  • Update the pg_hba.conf file on the new PEM instance
  • Configure SSL on the new server and reconfigure PEM agents
    • Approach 2 – Use different server certificates but the same CA
    • Approach 3 – Replace all server and agent certificates
    • Approach 4 – Use only certificates from an external CA
  • Disable disconnected agents on each PEM instance
  • Validate your PEM instances
• Uninstalling
  • Uninstalling Postgres Enterprise Manager components on Linux
    • Uninstalling PEM components from RHEL or Rocky Linux or AlmaLinux hosts
    • Uninstalling PEM components from Debian or Ubuntu hosts
    • Uninstalling PEM components from SLES hosts
  • Uninstalling Postgres Enterprise Manager components on Windows
• Troubleshooting
  • Known installation and configuration issues
    • Conflict with existing mod_wsgi
    • Errors from JIT
    • Crash due to bug in RHEL Python 3.9 standard library
    • Blocking TRACK/TRACE Methods in Apache HTTPD
  • Reconfiguring the PEM server
  • PEM web application not loading
  • Error connecting to PostgreSQL server
  • PEM web server connectivity check
  • SQL Error - column “ssl” of relation “server” does not exist
  • SSL Error - Incomplete sslutils upgrade
  • Nginx SSL_read() failure errors