Perform the following steps on the primary server:
- On the Edit menu, select Server, then Create Resource Hierarchy.
The Create Resource Wizard dialog will appear.
- Select PostgreSQL Database from the drop-down list and click Next.
- You will be prompted for the following information. When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is helpful should you encounter any error requiring you to correct the previously entered information. You may click Cancel at any time to cancel the entire creation process.
| Switchback Type | Choose either intelligent or automatic. This determines how the PostgreSQL resource will be switched back to the primary server after it comes in-service (active) on the backup server following a failover. Intelligent switchback requires administrative intervention to switch the resource back to the primary server, while automatic switchback occurs as soon as the primary server is back on line and re-establishes LifeKeeper communication paths. Note: The switchback strategy must match that of the dependent resources to be used by the PostgreSQL resource. |
| PostgreSQL Executable Location | This field is used to specify the directory path containing the PostgreSQL executables. The valid characters allowed for the pathname are letters, digits and the following special characters: – _ . / |
| PostgreSQL Client Executable Location | This field is used to specify the directory path containing the PostgreSQL executable psql. The valid characters allowed for the pathname are letters, digits and the following special characters: – _ . / |
| PostgreSQL Administration Executable Location | This field is used to specify the directory path containing the PostgreSQL executable pg_ctl. The valid characters allowed for the pathname are letters, digits and the following special characters: – _ . / |
| PostgreSQL Data Directory | This field is used to specify the location of the PostgreSQL data directory (datadir) that will be placed under LifeKeeper protection. The specified directory must exist and reside on a shared file system. The valid characters allowed for the pathname are letters, digits and the following special characters: – _ . / |
| PostgreSQL Port | This field is used to specify the TCP/IP port number on which the postmaster daemon is listening for connections from client applications. |
| PostgreSQL Socket Path | This field is used to specify the full path to the Unix-domain socket on which the postmaster daemon is listening for connections from client applications. The valid characters allowed for the pathname are letters, digits and the following special characters: – _ . / |
| PostgreSQL Database Administrator User | This field is used to specify a PostgreSQL Database Administrator User name for the specified database instance with connection and administrator privileges for the instance. |
| PostgreSQL Logfile | This field is used to specify the log file path used by the -l option of pg_ctl to start and stop PostgreSQL. |
| PostgreSQL Database Tag | This is a unique tag name for the new PostgreSQL database resource on the primary server. The default tag name consists of the word pgsql followed by the port number for the database instance. You may type in another unique tag name. The valid characters allowed for the tag are letters, digits and the following special characters: – _ . / |
- Click Create. The Create Resource Wizard will then create your PostgreSQL resource hierarchy. LifeKeeper will validate the data entered. If LifeKeeper detects a problem, an error message will appear in the information box.
- You should see a message indicating that you have successfully created a PostgreSQL resource hierarchy, and you must extend that hierarchy to another server in your cluster to achieve failover protection. Click Next.
- Click Continue. LifeKeeper will then launch the Pre-extend Wizard. Refer to Step 2 in the topic Extending a PostgreSQL Resource Hierarchy for details on how to extend your resource hierarchy to another server.
Post your comment on this topic.