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

to run the package. Here the Sybase ASE binaries reside on the
local
storage. If any change is made to the configuration files, the
file
must be copied to all nodes. The user is responsible to ensure
the
systems remain synchronized.
Shared Configuration
This is the recommended configuration. Here, the configuration
and
database files are kept on shared disks (but the Sybase ASE
binaries
can be on the local storage). Since the configuration files and
data
files reside on a shared location, there is no additional work to
ensure
all nodes have the same configuration at any point in time.
Another
alternative setup is to put the Sybase ASE binaries too on the
shared
location along with the configuration and database files.
Sybase supports multiple ASE instances running on the same
node
simultaneously. This allows the system administrator the ability to
move
one instance from its own node while leaving another instance 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 etc. This means the configuration information for each
instance
must be identical for each node that will be configured to run
that
instance. Refer to the chapter "Building an HA Cluster
Configuration"
in the manual "Managing Serviceguard" located at "http://docs.hp.com/
en/ha.html" for information on volume group creation and logical
volume
management.
(NOTE: As previously stated, configuration can be stored on a
local
disk. If the choice is to do this, it is the user's responsibility
to
ensure the data is propagated to all the nodes, and is
consistently