After you have completed the necessary setup tasks outlined in the SIOS Protection Suite for Windows Installation Guide, use the steps listed below to create the PostgreSQL Server hierarchy to protect your database cluster.
If you have an existing PosgreSQL database cluster installed, you may need to close any client applications (local or remote) that are accessing the PostgreSQL database cluster prior to completing this procedure. Closing all client connections is required if any of the following conditions exist:
- From the LifeKeeper GUI menu, select Edit then Server. From the menu, select Create Resource Hierarchy.
- The Create Protected Application dialog box will display. Select the Primary and Backup servers from the pull-down list. Select Next to continue.
- The dialog box will appear with a drop down list box displaying all recognized recovery kits installed within the cluster. Select PostgreSQL Server and click Next.
- You will be prompted to enter 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 an error requiring you to correct previously entered information. You may click Cancel at any time to cancel the entire creation process.
|PostgreSQL Service Name||
Enter the Windows Service Name for this instance.
If the name entered is an existing PostgreSQL service, then the PostgreSQL Recovery Kit will use the service information to pull information for the resource creation.
If the name entered is not an existing PostgreSQL service, then the create process will require additional inputs in order to create a Windows Service using the entered name.
Note: If a Windows Service is created during the PostgreSQL resource create, then a delete of the PostgreSQL resource will remove the PostgreSQL service. If the PostgreSQL service already exists at create time, then a delete of PostgreSQL resource will not remove the service.
|PostgreSQL Executable Location||Select the location of the PostgreSQL executables (directory where pg_ctl.exe and psql.exe reside).|
|PostgreSQL Data Directory||Enter the path to the data directory for the PostgreSQL database cluster to be protected. If the PostgreSQL Service name entered exists, then it will default to the data directory defined for that service.|
|PostgreSQL Port||Select the port to be used for the PostgreSQL database cluster. This field is used to specify the TCP/IP port number on which the postmaster daemon is listening for connections from client applications. The default choice is obtained from the running PostgreSQL Server.|
|Enter Database Administrator User||Enter the name of the PostgreSQL database cluster administrative user. This user must have connection and administrative privileges.|
|PostgreSQL Database Tag||
Enter a unique tag name, or you can accept the default tag name offered by SPS.
Note: The tag name must consist of printable ASCII characters.
|The following fields only appear if the PostgreSQL Service Name entered does not already exist as a Windows service.|
|PostgreSQL Service Logon Account||Enter the user account to be used for the logon credentials for the new PostgreSQL Windows Service. This account must have privileges to start and stop the PostgreSQL server instance being protected. This user account must also have full control file permissions for all files in the PostgreSQL Data Directory.|
|PostgreSQL Service Logon Password||
Enter the user password to be used for the logon credentials for the new PostgreSQL Windows Service.
Note: If built-in system accounts (e.g. “Local System” or “Network Service”) are used, enter any non-blank value into this field (blank is not allowed). For built-in accounts, the password is ignored.
- After you click Create, the Wizard will create your PostgreSQL resource. SIOS Protection Suite will validate the data entered. If SIOS Protection Suite detects a problem, an error message will appear in the information box.
- Another information box will appear indicating that you have successfully created a PostgreSQL resource hierarchy, and you must Extend that hierarchy to another server in your cluster in order to achieve failover protection. Click Next.
- After you click Next, SIOS Protection Suite will launch the Pre-Extend Wizard.