How to Respond to Installation Script Prompts
The High Availability Option installation script prompts you to complete the following steps:
1. Install Ingres High Availability Option package files.
The Ingres High Availability Option consists of an Ingres resource type and runtime scripts, which are installed as part of the High Availability option package files install. The High Availability option package files must be accessible from every node that Ingres can fail over. The package files must be installed either on a cluster file system or on all nodes in the cluster where the Ingres DBMS Server can fail over.
The install.sh script installs the High Availability Option package files by default in local directory /opt/Ingres/IngresSCAgent. If you choose to install these files on a local file system, you should execute this install step on every failover node before continuing to the next step in the install process.
The resource file Ingres.ingres_server is copied to the standard resource type directory /usr/cluster/lib/rgm/rtreg.
Note: When installing the HA option files on a local file system, the actual path should be identical on each node.
2. Install Ingres.ingres_server resource type.
This step registers the Ingres resource type (Ingres.ingres_server). Resource type registration is required only once on the cluster.
Multiple Ingres failover installations can be installed in separate failover groups, but they will all share the same Ingres resource type.
3. Configure Ingres installation.
This step modifies the Ingres installation configuration options to create a logical hostname and then renames the configuration options in config.dat.
This steps ensures that Ingres has the same logical hostname and reads the same logical configuration options when run on any failover node.
4. Create resource group containing an Ingres installation.
This step creates an Ingres resource group and a resource in the group that corresponds to the Ingres installation.
The install script generates a default group name, but you can override this during installation. By default, this group will contain all cluster nodes as potential masters.
The install script generates a default resource name for the Ingres installation, but you can override this resource name during installation.
5. Add the cluster logical hostname to the Ingres resource group.
This step creates a logical hostname resource and adds it to the Ingres resource group. A logical hostname allows a floating IP address to be defined that moves from one node to another, along with the Ingres installation, during failover. This ensures that one IP address and DNS entry can be used to reference the Ingres installation regardless of the node it is running on.
This step prompts for a logical hostname, which can be entered as a DNS hostname or as a static IP address.
Last modified date: 01/30/2023