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.
- From the Edit menu, select Resource then Extend Resource Hierarchy. The Pre-Extend Wizard appears. If you are unfamiliar with the Extend operation, click Next.
- The Pre-Extend Wizard will prompt you to enter the following information. Note: These first two fields appear only if you initiated the Extend from the Edit menu.
Select a server where a resource hierarchy to be extended is currently defined and in service.
|Resource Hierarchy to Extend
|Select the resource hierarchy to extend.
|Select a server to be the backup server for the resource hierarchy.
- After receiving the message that the pre-extend checks were successful, click Next.
- The Extend Wizard will prompt you to enter the following information. Note: The first two fields appear only if a Windows Service for the PostgreSQL does not exist on the backup server (the service name entered on the primary server during create is used for checking on the backup server).
|PostgreSQL Service Logon Account
|Enter the user account to be used for the logon credentials for the PostgreSQL Windows Service on the backup server. This account must have privileges to start and stop the PostgreSQL instance being protected.
|PostgreSQL Service Logon Password
|Enter the user password to be used for the logon credentials for the new PostgreSQL Windows Service..
|PostgreSQL Executable Location
|Select the location of the PostgreSQL executables (directory where pg_ctl.exe and psql.exe reside). If multiple versions of PostgreSQL are installed on the system, then the path selected must match the PostgreSQL version used to create the protected database cluster. Example: If intidb from version 10 was used to create the database cluster, then the path selected for pg_ctl.exe and psql.exe must be the version 10 path.
|Enter a number between 1 and 999 to specify the template server’s priority in the cascading failover sequence for this resource. A lower number means a higher priority. LifeKeeper for Windows assigns the number “1” to the server on which the hierarchy was created. No two servers can have the same priority for a given resource.
- Click Extend.