Additional Setup Tasks for Extended Configurations

If your configuration uses a shared storage device or you are using SIOS DataKeeper, you may choose a configuration that will be extended to a third (or more) server(s).

1. If it has not already been done, configure two systems following the steps given in Installation and Configuration – Adding PostgreSQL to an Existing LifeKeeper Configuration.

2. Use the Disk Management utility to configure your disk resources and define the shared or replicated volumes that you want to use. If you are using shared storage assign the same drive letter to the shared volume as assigned on the primary server. For replicated storage be sure the volume size is adequate.

3. Install the PostgreSQL Server software EXACTLY as you did on the primary server (program files in the same directory on the local disk and data files in the same location on the protected volume) using the following guidelines:

   1. Using the —extract-only argument to the PostgreSQL installer is not recommend as it does not configure all of the information required by the PostgreSQL Recovery Kit.

   2. By default the installation of the PostgreSQL software creates a single database cluster (a database cluster is a collection of databases that is managed by a single instance of a running PostgreSQL database server). During installation the Data Directory prompt determines where the database cluster will be created. Select any location as the data directory will be removed in a later step. If replicated storage is being used it can be the volume created above in step 2. If shared storage is being used do not use the volume located above to prevent overwriting the current PostgreSQL database cluster.

   3. The database service created during install does not configure the postmaster process to start with the port argument (-p port) which is required by the LifeKeeper for Windows PostgreSQL Server Recovery Kit to properly manage the instance. The Windows service (e.g. postgresql-x64-9.6 with PostgreSQL v9.6) created for the default database cluster will need to be updated to include this option if it will be protected by the LifeKeeper for Windows. See Configuring the Postmaster Port Argument for more information. While updating the Postmaster Port Argument you will also need to update the data directory path (-D argument value) to match the install location on the primary server.

4. Follow the steps outlined in Configure for Unattended Connections if the pgpass.conf will be used for authentication (if setting up a trust relationship via the pg_hba.conf file this step can be skipped as that will have already been done as part of the configuration on the primary server).

5. The default database cluster instance created during installation is not required and can be removed.

   1. Stop the database cluster instance created during installation.

   2. Open Explorer and migrate to the location of the data directory entered during installation of the PostgreSQL software.

   3. Delete the PostgreSQL database cluster directory.

   4. Delete the PostgreSQL service that was created during installation. You can use the Windows “sc delete <servicename>” command to do this.

6. If no comm paths exist to the new LifeKeeper cluster node, use the LifeKeeper GUI on the Primary Server to create comm paths between the primary and the new LifeKeeper cluster node and to create comm paths between the backup server and the new LifeKeeper cluster node.

7. Extend the PostgreSQL hierarchy to the new LifeKeeper cluster node. See Creating the PostgreSQL Hierarchy for more information. Test the new PostgreSQL Server hierarchy by performing a manual switchover to the new LifeKeeper cluster node.