1.3 High availability terminology used in this book

 < Day Day Up > 

1.3 High availability terminology used in this book

It helps to share a common terminology for concepts used in this redbook. The high availability field often uses multiple terms for the same concept, but in this redbook, we adhere to conventions set by International Business Machines Corporation whenever possible.


This refers to a group of servers configured for high availability of one or more applications.


This refers to a single server in a cluster.


This refers to a node that initially runs an application when a cluster is started.


This refers to one or more nodes that are designated as the servers an application will be migrated to if the application's primary node fails.


This refers to the process of a node announcing its availability to the cluster.


This refers to the process of a backup node taking over an application from a failed primary node.


This refers to the process of a failed primary node that was repaired rejoining a cluster. Note that the primary node's application does not necessarily have to migrate back to the primary node. See fallback.


This refers to the process of migrating an application from a backup node to a primary node. Note that the primary node does not have to be the original primary node (for example, it can be a new node that joins the cluster).

For more terms commonly used when configuring high availability, refer to High Availability Cluster Multi-Processing for AIX Master Glossary, Version 5.1, SC23-4867.

 < Day Day Up > 

High Availability Scenarios with IBM Tivoli Workload Scheduler and IBM Tivoli Framework
High Availability Scenarios With IBM Tivoli Workload Scheduler And IBM Tivoli Framework
ISBN: 0738498874
EAN: 2147483647
Year: 2003
Pages: 92
Authors: IBM Redbooks

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net