Adding a PostgreSQL Cluster Instance

You can add master or standby cluster instances.

When you add an instance, the following backup sets are automatically created, each with a default database group:

• DumpBasedBackupSet

• FSBasedBackupSet

Prerequisites

You must install PostgreSQL iDA on each of the cluster nodes that need to be added to the cluster instance.

Procedure

1. From the Command Center navigation pane, go to Protect > Databases.

   The database Overview page appears.

2. From the Add instance list, select Database server.

   The Configure Database Instance page appears.

3. Select PostgreSQL Cluster, and then click Next.

   The Add Instance page appears.

4. Select an existing backup plan or add a new backup plan.

5. Click Next.

   The Configure PostgreSQL Cluster Instance Name page appears.

6. In the Instance name box, enter the name of the database instance.

7. From the Cluster type list, select the type of cluster you are creating the instance for. The following clusters are supported:

   • Patroni HA

   • EDB Failover Manager

   • Repmgr for Postgres

   • Native replication

   • AlloyDb Omni (For Allow Omni cluster type, see Create an instance for AlloyDB Omni cluster.)

   Note

   Select Native replication when no third party is available to manage the replication or failover.

   The Configure PostgreSQL Cluster Instance Nodes page appears.

8. Click add to add the PostgreSQL cluster nodes.

   The Add PostgreSQL cluster node dialog box appears.

9. From the Server name list, select the client which is part of the cluster.

10. In the Connection details section, enter the following details:

    1. From the Credential list, select a saved credential or add a new credential. To add a new credential, do the following:

       Steps to add a credential

       1. Click + icon.

          The Add Credential dialog box appears.

       2. From Account type list, select a database account.

       3. From the Database type list, select a database.

       4. From the Credential Vault list, select a credential vault to store credentials for different types of accounts.

       5. In the Credential name box, enter a name for the credential.

       6. Under the Azure AD/AWS IAM Authentication section, enter the following details:

          1. In the Username box, enter the user name to access the Azure Database for PostgreSQL application.

          2. In the Password box, enter the password to access the Azure Database for PostgreSQL application.

          Note

          If you move the Azure AD/AWS IAM Authentication toggle to right, you only need to enter the user name detail.

       7. The SSL certificate toggle key is unselected by default. By moving the this toggle key to right, you can perform the following actions:

          1. In the SSL CA file field, provide the SSL CA file path on the proxy computer.

          2. In the SSL Cert file field, provide the SSL certificate file path on the proxy computer.

          3. In the **SSL Key file&& field, provide the SSL key file path on the proxy computer.

       8. In the Description box, enter the details of the credential.

       9. Click Save.

    2. In the Maintenance DB box, enter the name of a system database that is used as maintenance DB.

    3. In the Port box, enter or select the port to open the communication between PostgreSQL Server and the clients.

11. In the PostgreSQL paths section, enter the following details:

    1. In the Binary Directory box, enter the path to the PostgreSQL application. For example: /usr/pgsql-16/bin. Alternatively, click Browse to locate the path.

    2. In the Library Directory box, enter the path to the library directory for the instance. For example: /usr/pgsql-16/lib. Alternatively, click Browse to locate the path.

    3. In the Archive Log Directory box, enter the path of the directory where you want to store the archive log files. For example, /opt/wal. Make sure that this path does not point to pg_log and pg_xlog directories.

    4. In the Cluster binary path box, enter the path of the third party cluster type bin directory. Alternatively, click Browse to locate the path.

    5. In the Cluster Config File, enter the path of the cluster configuration file. Alternatively, click Browse to locate the path. For example:

       • For patroni HA: /etc/patroni/patroni.yaml

       • For Repmgr: /etc/repmgr/repmgr.conf

       • For EFM: /etc/edb/efm-4.4/efm.properties

    Note

    • If Native Replication is selected as cluster type, the Cluster binary path and Cluster Config File options are not available.

    • You can add up to 10 nodes.

12. Click Save.

13. Click Next.

14. Review the summary and click Finish.

Results

A cluster client with the same name as instance is created.