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

3. Create a volume group, logical volume, and file system to hold the necessary configuration
information and symbolic links to the Sybase ASE executables. This file system is defined as
SYBASE in the package configuration file and master control script. The volume group and
file system must be uniquely named within the cluster, therefore, use the name of the database
instance (ASE_SERVER) in the names:
Considering that the name of the ASE instance is 'SYBASE0', create the following:
A volume group: /dev/vg0_SYBASE0
A logical volume: /dev/vg0_SYBASE0/lvol1
A file system: /dev/vg0_SYBASE0/lvol1 mounted at /SYBASE0
After the volume group, logical volume, and file system is created on one node, it must be
imported to the other nodes that will run this database. Create the directory /SYBASE0 on all
nodes so that /dev/vg0_SYBASE0/lvol1 can be mounted on that node, if you want to run
the package on the node.
For more information on creating, importing, or managing the VG and file system, see the
Building an HA Cluster in the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs—>HP Serviceguard .
4. The ASE system files, data tablespaces, and files must be located in the file system /SYBASE0
during the initial creation of database. For more information, see Sybase ASE documentation
for information on setting up these files.
Multiple Instance Configuration
If multiple instances are run in the same cluster, repeat the preceding steps for each instance. For
example, if a second instance (SYBASE_TEST1) is to be included in the configuration, create a
second volume group (for example, /dev/vg0_SYBASE_TEST1), logical volume, and file system
with mount point (/SYBASE_TEST1) for the second instance. All configuration information for
SYBASE_TEST1 resides in /SYBASE_TEST1/dbs. Similar to SYBASE0, symbolic links must be
created for all subdirectories (other than /SYBASE_TEST1/dbs/), to link /SYBASE_TEST1 to
$SYBASE for that instance.
With this configuration, you can run several Sybase ASE instances on one node, which facilitates
failover/failback of Sybase ASE packages between nodes in the cluster.
Set up additional database logical volumes.
The database can reside on the same VG/LVOL as $Sybase ASE_HOME/dbs, but more commonly,
the database resides on several volume groups and logical volumes, all of which must be shared
among the nodes that are able to run the Sybase ASE instance. Use naming convention for the
VGs that include the instance name (${ASE_SERVER}) to associate a VG with a unique instance.
For Example:
Use with Asynchronous disk access and file systems:
/dev/vg01_SYBASE0/lvol1 #Logical volume Sybase ASE data
/dev/vg02_SYBASE0/lvol1 #Logical volume Sybase ASE data
/dev/vg02_SYBASE0/lvol2 #Logical volume Sybase ASE data
See the Sybase ASE documentation to determine which format is more appropriate for the setup
environment that user prefers.
File system for Sybase ASE data files:
/SYBASE0 - mount point for /dev/vg03_SYBASE0/lvol1
All data belonging to the database must reside on shared logical volumes (file system), space
needs to be allocated and shared for the following:
• Sybase ASE system data tables
• Sybase ASE indexes
66 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX