Launch Cluster Explorer from one of the nodes.
Note that these Veritas Cluster Server instructions assume you are using the graphical user interface to configure Messaging Server as an HA service.
To launch Cluster Explorer, run the following command:
# /opt/VRTSvcs/bin/hagui |
The VRTScscm package must be installed in order to use the GUI.
Add s1ms_dg disk group resource of type DiskGroup and enable it.
Add s1ms_mt mount resource of type Mount.
Create a link between s1ms_mt and s1ms_dg. Enable the resource s1ms_mt.
The figure depicts the dependency tree:
Run the Java Enterprise System installer, selecting Administration Server and Messaging Server.
During Administration Server configuration, be sure to specify the logical host name when asked to provide a hostname.
Run the Messaging Server Initial Runtime Configuration from the primary node (for example, Node_A) to install Messaging Server.
Install the Veritas Cluster Server agent package, SUNWmsgvc, (located in the Messaging Server Product subdirectory on the Java Enterprise System CD) by using the pkgadd(1M) command.
Messaging Server and the Veritas agent are now installed on Node_A.
Switch to the backup node (for example, Node_B).
Run the Java Enterprise System installer to install Messaging Server on the backup node (Node_B).
After installing Messaging Server, you can use the useconfig utility to obviate the need for creating an additional initial runtime configuration on the backup node (Node_B). The useconfig utility allows you to share a single configuration between multiple nodes in an HA environment. This utility is not meant to upgrade or update an existing configuration. See Using the useconfig Utility.
The Veritas agent is now installed on Node_B.
From the Cluster Explorer, Select Import Types... from the File menu which will display a file selection box.
Import the MsgSrvTypes.cf type from the /etc/VRTSvcs/conf/config directory. Import this type file. Note that you need to be on a cluster node to find this file.
Now create a resource of type MsgSrv (for example, Mail). This resource requires the logical host name property to be set.
The Mail resource depends on s1ms_mt and webip. Create links between the resources as shown in the following dependency tree:
Switch over to Node_A and check if the High Availability configuration is working.
Change the group attribute OnlineRetryLimit from 3 to 0, otherwise the failed-over service might restart on the same node.