HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

HP recommends this configuration. Here, the configuration and database files are stored on shared
disks (but the Sybase ASE binaries can be on the local storage). The configuration files and data
files reside on a shared location, therefore, there is no additional work to ensure that all nodes
have the same configuration at any point in time. Another alternative setup is to place the Sybase
ASE binaries on the shared location along with the configuration and database files.
Sybase supports multiple ASE instances running on the same node simultaneously. With this feature
the system administrator can move one instance from its own node while another instance is up.
Each node can potentially run several instances. Each Sybase ASE Package corresponds to a
separate Sybase ASE instance with its own ASE_SERVER instance name, unique volume groups,
logical volume, and file system for storing ASE binaries, configuration files, data files, system
databases, log files, and so on. This means the configuration information for each instance must
be identical for each node that is configured to run that instance. See Building an HA Cluster
Configuration in the Serviceguard user manual available at:http://www.hp.com/go/
hpux-serviceguard-docs-> HP Serviceguard for information on volume group creation and logical
volume management.
NOTE: If configuration data is stored on a local disk, ensure the data is propagated to all the
nodes, and is consistently maintained across the nodes. A disadvantage of storing the configuration
on local disks is that this might make the configuration for a database instance inconsistent if
changes are made to the configuration in one node. This configuration data is not distributed to
all nodes that can run that database instance.
HP recommends that the master database and other ASE system database files - like master.dat
, sysprocs.datand sybsysdb.dat be on shared disk.
You must get the appropriate license for Sybase for this type of setup. For a license that is server
specific, each node requires a license to be generated with the corresponding MAC of that node.
For a local configuration, the license for each node can be separately put on the corresponding
node under the $SYBASE/$SYBASE_SYSAM2/licenses directory. For a shared configuration,
ensure that both nodes can access the corresponding license in the same path.
However, in case of a local configuration, note that the Sybase ASE instance specific files must
be identical on all nodes; and in a shared configuration, all files must be on shared storage and
be accessible from any one node at any given time.
Setting up the Application
NOTE: To set up the application, Sybase ASE must be installed in /home/Sybase on all package
nodes in the cluster, and shared storage must be configured.
To set up the application:
1. Make sure all database instances in the cluster have unique names (as identified by the
user-defined variable 'ASE_SERVER' in the package configuration file). This can be done at
the time of configuring the ASE server processes, with entries made in the <ASE_SERVER.cfg>
file while configuring with the default configuration tool, or in the
$SYBASE/$SYBASE_ASE/init/sample_resource_files/srvbuild.adaptive_server.rs and similarly
for the other servers.
NOTE: The dataserver and the monitor server, both need to be installed on the same disk
as monitor server is dependent on the dataserver for its working.
2. Make sure that the 'sybase' user has the same user id and group id on all nodes in the cluster.
Create the user or group with the following commands and verify the uid/gid by editing the
/etc/passwd file:
# groupadd sybase
# useradd -g sybase -d <installpath> -p <Passwd> sybase
Setting up the Application 65