Do not install PSQL on the cluster shared storage where the PSQL data resides.
|
|||||||||||
Note: Because of the dependencies, bring the PSQL resources online in the following order: first the PSQL Transactional Engine then the PSQL Relational Engine (and stop them in reverse order).
|
|||||||||||
|
|||||||||||
You configure the database engine with PSQL Control Center (PCC) to add certain configuration settings to the registry. Configure the engine on the current active node in your cluster, then move the cluster group, making the configuration changes to each of the nodes in your cluster.
In PCC, set the following engine properties for Directories. When PCC prompts you to restart the services, select No.
|
Install PSQL Server on each cluster node and choose identical options for each installations. Do not install PSQL on the cluster shared storage, where the PSQL database(s) resides.
|
|||||
Create (or at least identify) a location on shared storage where you want the database to reside. The location is your choice. Ensure that user psql has read, write, and execute authority for the location.
|
|||||
On each cluster node, log in as user psql then create a directory that will be mounted to the shared storage. (User psql has no password and can only be accessed through the root account with the su command.) The name of the directory is your choice.
|
|||||
Configure the Heartbeat server on each of the nodes that will control the PSQL database engine. Configure the following:
|
|||||
Linux Heartbeat provides a default user named hacluster for logging in to the Heartbeat Management Client. Assign a password to user hacluster on each of the nodes from which you want to run Heartbeat Management Client.
|
|||||
Log in as root and start the Heartbeat Management Client on one of the cluster nodes. Log in as user hacluster and add a new group. For ID, specify a name for the PSQL group. Set Ordered and Collocated to true.
|
|||||
In the Heartbeat Management Client, add a new native item. For Belong to group, select the group you added for PSQL. For Type, select IPaddr.
On the resource you just added, specify the IP address of the cluster for the IP Value. Use the IP address assigned to the cluster (not the node) when Linux Heartbeat was installed and configured.
Add another new native item. For Belong to group, select the group you added for PSQL.
For Type, select Filesystem and delete the parameter fstype, which is not required. Add a new parameter and select “device” for Name. For Value, specify the device name of the shared storage, a colon, and the share mount location.
Add another new parameter and select “directory” for Name. For Value, specify the directory to use with the NFS mount.
Add another new native item. For Belong to group, select the group you added for PSQL. For Type, click “psql” with a Description of “PSQL OCF Resource Agent.” No additional parameters are required for the parameter.
|
|||||
Now that you have added the Filesystem resource, the mount exists between the cluster server and the shared storage. On one of the cluster nodes, log in as user psql. Under the shared storage mount, create a directory named “log” and another named “etc.”
|
|||||
Place all cluster nodes into standby mode except for the one from which you will run PCC. As user psql, start PCC on the one active node or from a client that can access the active node.
Access the properties for the server you just added. If prompted to log in, log in as user admin. Leave the password blank. Access the Directories Properties. For Transaction Log Directory, specify the directory that you created for the “log” location. For DBNames Configuration Location, specify the directory that you created for the “etc” location. See Create the Subdirectories on the Mounted Shared Storage.
|
|||||
From the operating system on one of the cluster nodes, log on as user psql and create the directory under the file system share where you want the database to reside. (If you create the directory as user root, ensure that user psql has read, write, and execute authority on the directory.)
As user psql, start PCC on the one active node or from a client that can access the active node. Create a new database for the server you added in Configure the Cluster Server in PCC. For Location, specify the directory you created where you want the database to reside. Specify the other database options as desired.
|
|||||
1
|
Right-click Actian PSQL Relational Engine and select Bring this resource offline.
|
2
|
Right-click Actian PSQL Transactional Engine and select Bring this resource offline.
|
3
|
Right-click Actian PSQL Transactional Engine and select Bring this resource online.
|
4
|
Right-click Actian PSQL Relational Engine and select Bring this resource online.
|