Configuring the PowerHA SystemMirror GUI server to be highly available

You can configure PowerHA SystemMirror GUI server to be highly available either by using the Enable the GUI Server for High Availability wizard for the PowerHA SystemMirror GUI server or by using the PowerHA SystemMirror command line interface(CLI).

Configuring the PowerHA SystemMirror GUI server to be highly available by using the PowerHA SystemMirror GUI

In PowerHA SystemMirror Version 7.2.4, or later, you can use the GUI Server High Availability option that is available in the cluster view of the PowerHA SystemMirror GUI to enable or to disable the high availability of the PowerHA SystemMirror GUI server.

Before you enable the PowerHA SystemMirror GUI server for high availability, ensure that the server file set of the PowerHA SystemMirror GUI is installed on all nodes of the cluster. After you install the server file set, run the smuiinst.ksh command on all nodes of the cluster to complete the installation process. Because the PowerHA SystemMirror GUI server must run only on one node, stop the PowerHA SystemMirror GUI server on other agent nodes by running the following command:

stopsrc -cs phauiserver

For more information about installing the PowerHA SystemMirror GUI server file set, see Installing PowerHA SystemMirror GUI. The cluster must be in an online state and stable, or in an offline state.

When you set the GUI Server High Availability option to Enabled, the Enable the GUI Server for High Availability wizard for the PowerHA SystemMirror GUI server is displayed. You must specify the volume group that must be used for shared storage, the service IP address to access to the PowerHA SystemMirror GUI server, and network on which the service IP address must be configured to make the PowerHA SystemMirror GUI server highly available. The volume group that you specify must be created before you enable the PowerHA SystemMirror GUI server for high availability. You cannot assign the volume group that is created by using the PowerHA SystemMirror GUI because the volume group is already assigned to a resource group. You can create the volume group by using SMIT or by running the clmgr command. Create the volume group across all the cluster nodes and ensure that the volume group is not assigned to any resource group.

Configuring the PowerHA SystemMirror GUI server to be highly available by using the command line interface

In PowerHA SystemMirror Version 7.2.3, or later, you can run the /usr/es/sbin/cluster/ui/server/bin/server_high_availability.sh script to make the PowerHA SystemMirror GUI server highly available.

To make the PowerHA SystemMirror GUI server highly available, enter the following command:


server_high_availability.sh <Volume_Group> <Service_IP> <Network> [<Netmask>]

After you run the /usr/es/sbin/cluster/ui/server/bin/server_high_availability.sh script, the PowerHA SystemMirror GUI server functions similar to any other application that PowerHA SystemMirror monitors. For example, you can start or stop the PowerHA SystemMirror GUI server by using the clmgr command or by using the SMIT interface. The PowerHA SystemMirror GUI server can be moved to another cluster node, and if a failure occurs, the PowerHA SystemMirror GUI server can failover to another cluster node automatically.

The server_high_availability.sh script creates the following objects:

Resource group that is named pha_gui_server_rg
Service IP address
File system that is created in the /opt/pha_gui_fs directory
Application controller that is named pha_gui_server_app
Application monitor that is named pha_gui_server_mon

Note: Do not change names and the location of the objects the server_high_availability.sh script creates. If you want to remove objects that are created, run the server_high_availability.sh –-remove script.

When you run the server_high_availability.sh script, the following actions occur in your environment:

The server database is copied to the new shared file system.
The security files in the GUI server that runs the script is copied to the remote server node. This process overwrites any existing security files on the remote server node.