Installing Postgres Enterprise Manager in HA Patterns#
Before deploying High Availability PEM, please familiarize yourself with the high-level guidance in High Availability Patterns for PEM Deployment .
The following pages provide detailed instructions for some example of HA PEM architectures. They are not intended to be an exhaustive guide to all possible patterns.
In addition, the following guides to specific elements of HA PEM deployment are provided:
- HA PEM using the C1 architecture with EFM and a Virtual IP
- Initial package installation and Postgres configuration
- User and access configuration on the primary
- Configure PEM on the primary
- Copy PEM configuration to the standbys
- Set up the primary node for streaming replication
- Set up the standby nodes for streaming replication
- Configure SELinux
- Register agents and servers on the standbys
- Set up EFM to manage failover
- Correct the agent-server binding host on the primary
- HA PEM using the S1 architecture with EFM and a Virtual IP
- Deploying the PEM backend
- Initial package installation and Postgres configuration
- User and access configuration on the primary
- Configure PEM on the primary backend node
- Copy the configuration record to the standbys
- Set up the primary node for streaming replication
- Set up the standby nodes for streaming replication
- Register agents and servers on the standbys
- Set up EFM to manage failover
- Deploy the PEM Web Application
- Deploying the PEM backend
- Storing user settings in the backend, accessible to all web application instances
- HA PEM using the SM architecture with Patroni
- Setting up a Distributed Consensus Store with etcd
- Configuring EDB Repos
- Deploying the PEM backend
- Initial package installation and Postgres configuration
- Configure PEM on the primary backend node
- Copy the configuration record to the standbys
- Set up Patroni on the primary node
- Create Patroni users and generate a configuration file
- Edit the generated configuration file
- Set up the standby nodes
- Register agents and servers on the standbys
- Register the standbys as PEM backends
- Deploy the PEM Web Application