InfoScale™ 9.0 Cluster Server Agent for Sybase Installation and Configuration Guide - Solaris
- Introducing the Cluster Server for Sybase
- About the Cluster Server for Sybase
- Supported software for the VCS agent for Sybase
- How the agent makes Sybase highly available
- How the Sybase and SybaseBk agents support intelligent resource monitoring
- About the Sybase agent functions
- Monitoring options for the Sybase agent
- Action function for the VCS agent for Sybase
- Typical Sybase configuration in a VCS cluster
- Installing and configuring Sybase
- Installing, upgrading, and removing the agent for Sybase
- Configuring VCS service groups for Sybase
- About configuring service groups for Sybase
- Before configuring the service group for Sybase
- Configuring the service groups for Sybase
- Configuring the service group for Sybase from Cluster Manager (Java console)
- Configuring the service group for Sybase using the command line
- Encrypting passwords for Sybase
- About setting up detail monitoring for the agent for Sybase
- Enabling and disabling intelligent resource monitoring (IMF) for agents
- Administering the AMF kernel driver
- Administering VCS service groups for Sybase
- Appendix A. Resource type definitions for Sybase
- Appendix B. Sample configurations for Sybase
- About the sample configuration for the Sybase agent
- Resource dependency graph for the Sybase agent
- Sample configuration for agent for Sybase on Solaris systems
- Sample main.cf files for Sybase ASE CE configurations
- Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
- Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
- Sample main.cf for a primary CVM VVR site
- Sample main.cf for a secondary CVM VVR site
- Sample configuration for the Sybase agent in Solaris zones
Monitoring options for the Sybase agent
The VCS agent for Sybase provides two levels of application monitoring: basic and detail.
In the basic monitoring mode, the agent for Sybase monitors the Sybase dataserver processes to verify whether they are running.
For Sybase cluster edition, the agent uses qrmutil utility that Sybase provides to get the status of the Sybase instance. If the state returned by qrmutil utility is 'failure pending', the agent panics the node. When the Sybase agent detects that the configured Sybase server is not running on a system, based on the value of the OnlineRetryLimit attribute of the Sybase service group, the service group is restarted on the same system on which the group faulted.
For example:
# qrmutil --quorum_dev=/quorum/quorum.dat --monitor=ase1 Executing 'monitor' command for instance 'ase1' Instance 'ase1' has a failure pending. # echo $? 99
In this example instance 'ase1' has a failure pending state. The agent will panic the node running the instance 'ase1'. The node will automatically rejoin the cluster after reboot.
In the detail monitoring mode, the agent performs a transaction on a test table in the database to ensure that Sybase server is functioning properly. The test table should be created by the user, and the table is specified in the attribute Table for the Sybase agent. The agent uses this test table for internal purposes. Arctera recommends that you do not perform any other transaction on the test table.
For the Sybase ASE Enterprise edition, when the agent detects that the configured Sybase server is not running on a system, the Sybase service group is failed over to the next available system in the service group's SystemList. The configured Sybase servers are started on the new system, thus ensuring high availability for the Sybase server and data.
More Information