Cluster Server 8.0 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
How the agent makes Sybase highly available
The Cluster Server agent for Sybase continuously monitors the Sybase database and SybaseBk processes to verify whether they function properly.
The agent for Sybase can perform different levels of monitoring and different actions which you can configure.
Primary or Basic monitoring: In the basic monitoring mode, the agent monitors the configured Sybase server process, and fails over or restarts the group during an application failure.
Detail monitoring: In the optional detail monitoring mode, the agent detects application failure if it cannot perform a transaction in the test table in the Sybase database server.
Intelligent monitoring framework (IMF): The Sybase agent is IMF-aware and uses asynchronous monitoring framework (AMF) kernel driver for resource state change notifications.
See How the Sybase and SybaseBk agents support intelligent resource monitoring .
For Sybase cluster edition, the agent uses the Sybase-provided utility, qrmutil, to know if the status of the instance is up or down. If qrmutil reports the status as failure pending, the agent reboots the node and the instance is automatically started again.
When the Sybase agent detects that the configured Sybase server is not running on a system, based on the value of OnlineRetryLimit attribute of the Sybase server group, the service group is restarted on the same system on which the group faulted.
For 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.