cluster resource: A shared partition, secondary IP address, application, service, Web server, etc.,
that can function successfully anywhere in the cluster. Cluster resources include the GroupWise
agents and the Messenger agents.
failover: The process of moving cluster resources from a failed node to a functional node so that
availability to users is uninterrupted. For example, if the node where the POA is running goes down,
the POA and its post office fail over to a secondary node so that users can continue to use
GroupWise. When setting up cluster resources, you must consider what components need to fail
over together in order to continue functioning.
fan-out-failover: The configuration where cluster resources from a single failed node fail over to
several different nodes in order to distribute the load from the failed node across multiple nodes. For
example, if a node runs a cluster resource consisting of a domain and its MTA, another cluster
resource consisting of a post office and its POA, and a third cluster resource for the Internet Agent,
each cluster resource could be configured to fail over separately to different secondary nodes.
failback: The process of returning cluster resources to their preferred node after the situation
causing the failover has been resolved. For example, if a POA and its post office fail over to a
secondary node, that cluster resource can be configured to fail back to its preferred node when the
problem is resolved.
migration: The process of manually moving a cluster resource from its preferred node to a
secondary node for the purpose of performing maintenance on the preferred node, temporarily
lightening the load on the preferred node, etc.
126 GroupWise 8 Interoperability Guide
Need help?
Do you have a question about the GROUPWISE 8 - INTEROPERABILITY and is the answer not in the manual?
Questions and answers