Use the information in this section to prepare Sun Cluster nodes for Sun Cluster HA for Sybase installation.
You can install the Sybase binaries either on a physical host's local disks or on the shared multihost disks (logical host). Use Table 6-1, which shows the advantages and disadvantages of each install location, to determine the install location that best fits your needs.
Table 6-1 Sybase Install Locations Comparison
If you install the Sybase server on the multihost disk, you must install the Sybase clients in /var/opt/sybase on all nodes. If you install the Sybase servers on local disks, you are not required to install Sybase clients.
On each node that can master the logical host running Sun Cluster HA for Sybase, modify the /etc/nsswitch.conf file so that "group" lookups are directed to files first. For example:
... group: files nisplus ... |
Sun Cluster HA for Sybase uses the su sybase command when starting and stopping the database server.
Adding these settings will ensure that the su sybase command does not refer to NIS/NIS+ when the network information name service is not available due to a failure of the public network on the cluster node.
If you are using Solstice DiskSuite, you can configure Sun Cluster HA for Sybase to use UFS logging or raw mirrored metadevices. See Appendix B, Configuring Solstice DiskSuite, for details about setting up metadevices.
If you are using Sun StorEdge Volume Manager, you can configure Sun Cluster HA for Sybase to use VxFS logging or raw devices. Refer to your Sun StorEdge Volume Manager documentation for more information.