|
|
There are several pre-requisites that need to be met prior to configuring the Transaction Manager with the NoOP policy:
In order for other cluster members to be able to perform transaction recovery, the cluster members must have access to the transaction logs of the failed server. If the cluster members are on different physical systems, then the file system must be accessible from each system.
Another important consideration regarding the file system are the file locking semantics. When a cluster member becomes unavailable, then the peer cluster member that is elected to perform recovery must be able to exclusively lock the transaction log to ensure data integrity. See 6.7.2, Hot-failover of Transaction Manager using shared file system for more information about shared file systems and the requirements for TM.
This software provides continuity to business applications. The software typically provides functionality such as IP takeover, monitoring of applications, starting and stopping applications, heartbeating and various other availability functions. There are many clustering software vendors with products such as IBM HACMP, Tivoli System Automation (TSA), Sun Cluster and VERITAS Cluster Server.
