Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX README: Release B.06.00

For more information on creating, importing, or managing the VG and
file
system, please refer to the chapter entitled "Building an HA
Cluster"
in the "Managing Serviceguard" manual for explicit instructions.
d. The ASE system files, data table-spaces and files must
be
located in the file system /SYBASE0 during the initial creation
of
database. Refer to your Sybase ASE documentation for information
on
setting up these files.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Multiple Instance Configuration
If multiple instances will be 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, you would
create a
second volume group (e.g., /dev/vg0_SYBASE_TEST1), logical volume
and
file system with mount point (/SYBASE_TEST1) for the second
instance.
All configuration information for SYBASE_TEST1 will reside
in
/SYBASE_TEST1/dbs. Similar to SYBASE0, symbolic links need to be
created
for all subdirectories (other than /SYBASE_TEST1/dbs/), to
link
/SYBASE_TEST1 to $SYBASE for that instance.
This configuration makes it possible to run several Sybase ASE
instances
on one node, facilitating failover/failback of Sybase ASE
packages
between nodes in the cluster.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Set up additional database logical volumes.
It is possible to have the database reside on the same VG/LVOL
as
$Sybase ASE_HOME/dbs, but more commonly, the database will
probably
reside on several volume groups and logical volumes, all of which need
to
be shared among the nodes that are able to run the Sybase ASE
instance.