Installing the Manager software in a Multi-Manager configuration

This topic describes how to install the BMC Database Automation Manager software in a mesh on several servers. BMC Database Automation uses the Slony-I enterprise-level replication system to provide the mesh for the Multi-Manager configuration. For more information on Slony-I, see http://www.slony.info/.

Before you begin

Ensure that the following prerequisites are met:

  • You have satisfied the OS requirements for Multi-Manager environments.
  • You must have root user privileges to perform this installation.
  • Slony-I must be compiled at your site (supported versions are 1.2 and 2.1). The following tools are required to compile Slony-I:
    • GNU make version 3.76 and up
    • An ISO/ANSI C compiler, such as GCC
    • PostgreSQL source version 7.3.3 and up

For additional information on system requirements for Slony-I, see http://www.slony.info/documentation/1.2/requirements.html

To install the Manager software in a Multi-Manager configuration

Perform the following steps on every manager that will be in the mesh:

  1. Install the Manager software on the servers that will comprise the mesh using the steps in Installing-the-Manager-software-in-a-Standalone-configuration.
  2. To ensure that the changes made in this procedure are saved, make sure the dmanager, mtd and postgresql services are running.
  3. Download the Slony source file:
  4. To unpack, compile, and install Slony, type the following commands and press <Enter>:
    1. tar xvjf <downloaded file from previous step>
    2. cd <extracted directory>
    3. ./configure --with-pgconfigdir=`which pg_config` --with-perltools=/var/lib/pgsql/data/slony
    4. make
    5. make install

      Note

      The Slony-I build requires the pg_config tool to run correctly. This tool is installed with the postgres-devel RPM. For example, the full name of the postgresql-devel tools RPM for Red Hat Enterprise Linux version 6 is postgresql-devel-8.4.4-2.el6.x86_64. If you find that the pg_config tool is missing, you must download and install the postgres-devel RPM. See http://www.postgresql.org/ for download information for the RPM.

  5. Copy the Slony initialization script into the /etc/init.d directory:
    cp /app/clarity/manager_scripts/bin/slony.init /etc/init.d/slony

  6. Grant remote login privileges to the Multi-Manager postgres users for all managers in the mesh:

    Note

    The following changes should be added in addition to the BDA default entries (for example, tcrimi) that are already present in the postgres configuration files.

    1. If the manager is to be used as a Content  manager:
      1. Open the /var/lib/pgsql/data/pg_hba.conf file in a text editor.

      2. Add the the following lines at the beginning of the file:local   GridApp     megamesh_config                      trust

        host    GridApp     megamesh_config     127.0.0.1/32     trust
        host    GridApp     megamesh_config     ::1/128          trust
      3. Add the following lines under the lines in Step aii (two-line entries for each Satellite manager in the mesh):
        host all megamesh <satellite1 IP> 255.255.255.255 password
        host all megamesh_config <satellite1 IP> 255.255.255.255 password         
      4. Save the /var/lib/pgsql/data/pg_hba.conf file.
      5. Open the /var/lib/pgsql/data/postgresql.conf file in a text editor.
      6. Add the following line at the beginning of the file:
        listen_addresses = '*'
      7. Save the /var/lib/pgsql/data/postgresql.conf file.
      8. Restart the postgresql service:
        service postgresql restart
    2. If the manager is to be used as a Satellite manager:
      1. Open the /var/lib/pgsql/data/pg_hba.conf file in a text editor.

      2. Add the the following lines at the beginning of the file:local   GridApp     megamesh_config                      trust

        host    GridApp     megamesh_config     127.0.0.1/32     trust
        host    GridApp     megamesh_config     ::1/128          trust
      3. Add the following lines immediately under the lines in Step bii:
        host all megamesh <content manager IP> 255.255.255.255 password
         host all megamesh_config <content manager IP> 255.255.255.255 password
      4. Add the following lines immediately under the lines in Step biii (satellite IP is the IP address of the server in Step 6b (in other words, the server itself)):
        host all megamesh <satellite IP> 255.255.255.255 password
        host all megamesh_config <satellite IP> 255.255.255.255 password
      5. Save the /var/lib/pgsql/data/pg_hba.conf file.
      6. Open the /var/lib/pgsql/data/postgresql.conf file in a text editor.
      7. Add the following line at the beginning of the file:
        listen_addresses = '*'
      8. Save the /var/lib/pgsql/data/postgresql.conf file.
      9. Restart the postgresql service:
        service postgresql restart

Where to go next

Configuring-a-Multi-Manager-mesh

Related topic

Archiving-restoring-jobs-and-creating-backup-files

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*