Installing Failover Manager

To request credentials that allow you to access an EnterpriseDB repository, visit the EDB website at:

Installing Failover Manager on a RedHat, CentOS, or OEL Host

After receiving your credentials, you must create the EnterpriseDB repository configuration file on each node of the cluster, and then modify the file to enable access. The following steps provide detailed information about accessing the EnterpriseDB repository; the steps must be performed on each node of the cluster:

To create the repository configuration file, assume superuser privileges, and invoke the following command:

  • On RHEL or CentOS 7:

    yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm

  • On RHEL or CentOS 8:

    dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm

The repository configuration file is named edb.repo. The file resides in /etc/yum.repos.d.

After creating the edb.repo file, use your choice of editor to ensure that the value of the enabled parameter is 1, and replace the username and password placeholders in the baseurl specification with the name and password of a registered EnterpriseDB user.

[edb]
name=EnterpriseDB RPMs $releasever - $basearch
baseurl=https://<username>:<password>@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY

After saving your changes to the configuration file, you can use the following command to install Failover Manager:

  • On RHEL or CentOS 7:

    yum install edb-efm310

  • On RHEL or CentOS 8:

    dnf install edb-efm310

When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter y, and press Return to continue.

During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve.

|variable_prod_name| must be installed by root. During the installation process, the installer will also create a user named efm that has sufficient privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres.

If you are using |variable_prod_name| to monitor a cluster owned by a user other than enterprisedb or postgres, see Extending Failover Manager Permissions .

After installing |variable_prod_name| on each node of the cluster, you must:

  1. Modify the cluster properties file on each node.

  2. Modify the cluster members file 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 |variable_prod_name| agent on each node of the cluster. For more information about controlling the |variable_prod_name| service, see Section 5.

Installation Locations

|variable_prod_name| components are installed in the following locations:

Component

Location

Executables

/usr/edb/efm-3.10/bin

Libraries

/usr/edb/efm-3.10/lib

Cluster configuration files

/etc/edb/efm-3.10

Logs

/var/log/efm-3.10

Lock files

/var/lock/efm-3.10

Log rotation file

/etc/logrotate.d/efm-3.10

sudo configuration file

/etc/sudoers.d/efm-310

Binary to access VIP without sudo

/usr/edb/efm-3.10/bin/secure

Installing Failover Manager on a Debian or Ubuntu Host

To install |variable_prod_name|, you must also have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, visit the EnterpriseDB website at:

https://www.enterprisedb.com/repository-access-request

Follow the links in the EDB |variable_prod_name| table to request credentials.

The following steps will walk you through using the EnterpriseDB apt repository to install |variable_prod_name|. When using the commands, replace the username and password with the credentials provided by EnterpriseDB.

  1. Assume superuser privileges:

    sudo su -

  2. Configure the EnterpriseDB apt repository:

sh -c 'echo “deb https://<username>:<password>@apt.enterprisedb.com/$(lsb_release - cs)-edb/ $(lsb_release -cs) main” > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list'

  1. Add support to your system for secure APT repositories:

    apt-get install apt-transport-https

  2. Add the EDB signing key:

wget -q -O - https://<username>:<password>
@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add -

  1. Update the repository meta data:

    apt-get update

  2. Install |variable_prod_name|:

    apt-get install edb-efm310

Installing Failover Manager on a SLES Host

To install |variable_prod_name|, you must also have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, visit the EnterpriseDB website at:

You can use the zypper package manager to install a |variable_prod_name| agent on an SLES 12 host. zypper will attempt to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EnterpriseDB.

You must assume superuser privileges and stop any firewalls before installing |variable_prod_name|. Then, use the following commands to add EnterpriseDB repositories to your system:

zypper addrepo http://zypp.enterprisedb.com/suse/epas96-sles.repo
zypper addrepo http://zypp.enterprisedb.com/suse/epas-sles-tools.repo
zypper addrepo http://zypp.enterprisedb.com/suse/epas-sles-dependencies.repo

The commands create the repository configuration files in the /etc/zypp/repos.d directory. Then, use the following command to refresh the metadata on your SLES host to include the EnterpriseDB repository:

zypper refresh

When prompted, provide credentials for the repository, and specify a to always trust the provided key, and update the metadata to include the EnterpriseDB repository.

You must also add SUSEConnect and the SUSE Package Hub extension to the SLES host, and register the host with SUSE, allowing access to SUSE repositories. Use the commands:

zypper install SUSEConnect
SUSEConnect -r *registration_number* -e *user_id*
SUSEConnect -p PackageHub/12/x86_64
SUSEConnect -p sle-sdk/12/x86_64

Then, you can use the zypper utility to install a |variable_prod_name| agent:

zypper install edb-efm310

For detailed information about registering a SUSE host, visit: