Extending a PostgreSQL Resource Hierarchy

This operation can be started from the Edit menu or initiated automatically upon completing the Create Resource Hierarchy option, in which case you should refer to Step 2 below.

1. On the Edit menu, select Resource, then Extend Resource Hierarchy. The Pre-Extend Wizard appears. If you are unfamiliar with the Extend operation, click Next. If you are familiar with the LifeKeeper Extend Resource Hierarchy defaults and want to bypass the prompts for input/confirmation, click Accept Defaults.

2. The Pre-Extend Wizard will prompt you to enter the following information.

   Note: The first two fields appear only if you initiated the Extend from the Edit menu.

   Field	Tips
   Template Server	Select the server where your PostgreSQL resource is currently in service.
   Tag to Extend	Select the PostgreSQL resource you wish to extend.
   Target Server	Enter or select the server you are extending to.
   Switchback Type	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. You can choose either intelligent or automatic. The switchback type can be changed later, if desired, from the General tab of the Resource Properties dialog box. Note: Remember that the switchback strategy must match that of the dependent resources to be used by the PostgreSQL resource.
   Template Priority*	Select or enter a Template Priority. This is the priority for the PostgreSQL hierarchy on the server where it is currently in service. Any unused priority value from 1 to 999 is valid, where a lower number means a higher priority (1=highest). The extend process will reject any priority for this hierarchy that is already in use by another system. The default value is recommended. Note: This selection will appear only for the initial extend of the hierarchy.
   Target Priority	This is the priority for the new extended PostgreSQL hierarchy relative to equivalent hierarchies on other servers. Any unused priority value from 1 to 999 is valid indicating a server’s priority in the cascading failover sequence for the resource. Note that LifeKeeper assigns the number “1” to the server on which the hierarchy is created by default. The priorities need not be consecutive, but no two servers can have the same priority for a given resource.

3. After receiving the message that the pre-extend checks were successful, click Next.

4. Depending upon the hierarchy being extended, LifeKeeper will display a series of information boxes showing the Resource Tags to be extended, some of which cannot be edited.

5. The Extend Wizard will prompt you to enter the following information.

   Field	Tips
   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 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: – _ . /

6. After receiving the message “Hierarchy extend operations completed”, click Next Server to extend the hierarchy to another server, or click Finish if there are no other extend operations to perform.

7. After receiving the message “Hierarchy Verification Finished”, click Done.