Chapter 10: Active-Passive Configuration for Sun Cluster 3.0 and 3.1

Adaptive Server Enterprise version 15.0 does not support Sun Cluster version 2.2. If you currently have these clusters configured, you have to upgrade the respective cluster versions to configure Adaptive Server 15.0 for High Availability on Sun Solaris.

An active-passive configuration includes two nodes and a single Adaptive Server. The node that hosts the Adaptive Server under normal conditions is the primary node; the node that can potentially host the Adaptive Server is called the secondary node.

When the Adaptive Server or any of the resources it depends on, such as a disk or the node itself, crashes, the Adaptive Server, along with all required resources, is relocated and restarted on the secondary node. This movement from the primary node to the secondary node is called failover.

After failover, the node hosting Adaptive Server is considered the primary node until the System Administrator performs a planned failback, or until the Adaptive Server on the new primary node fails, causing another fail over.

After failover, all existing client connections are lost. The clients must reestablish their connections and resubmit any uncommitted transactions as soon as the Adaptive Server is started on the secondary node. The client connection failover can be performed automatically by using high availability connections and self-referencing the hafailover entry in the interfaces file. See “Configuring the interfaces file on the client side” for information.