Novell GROUPWISE 7 - INTEROPERABILITY GUIDE, Руководство пользователя

Страница: 287 / 485

Planning GroupWise in a Heartbeat Cluster 287
n
ov
do
cx (e
n)
11
Ju
ly 20
08
Š
Domains and their MTAs are less noticeable to users when they are unavailable (unless users in
different post offices happen to be actively engaged in an e-mail discussion when the MTA
goes down). On the other hand, domains and their MTAs are critical to GroupWise
administrators, although administrators might be more tolerant of a down server than end users
are. Critical domains in your system would be the primary domain and, if you have one, a hub
or routing domain. These domains should be in the cluster, even if other domains are not.
Š The Internet Agent might or might not require high availability in your GroupWise system,
depending on the importance of immediate messaging across the Internet and the use of POP or
IMAP clients by GroupWise users.
Š The WebAccess Agent might or might not require high availability in your GroupWise system,
depending on the importance of mailbox access from a Web browser.
There is no right or wrong way to implement GroupWise in a cluster. It all depends on the specific
needs of your particular GroupWise system and its users.
30.1.3 Planning Cluster Resources and Resource Groups
In a GroupWise Heartbeat cluster, the required cluster resources for each resource group are an
EVMS container, a file system, a secondary IP address, and one or more GroupWise agents. All of
these types of resources, as members of a cluster resource group, fail over from one node to another
while providing uninterrupted service to GroupWise users. So, for example, the resource group for a
GroupWise domain would include the EVMS container and file system where the domain directory
will be located and the secondary IP address that will be used by the MTA that services the domain.
The domain directory and secondary IP address must be available before the MTA can start.
Typically, Heartbeat resources and groups are named with the object type first, followed by an
underscore (_), followed by a unique name. For example, if you are creating a new GroupWise
system and you want to put the primary domain in the same cluster resource group as the initial post
office, you could name the resource group
group_gwprimary
. You could name the domain
resource
resource_gwmta
and the post office resource
resource_gwpoa
. In this example,
the domain and the post office would fail over together.
You might want the domain and post office together in the same cluster resource group or in
different cluster resource groups. If you want the domain and the post office to fail over separately,
you need two separate cluster resource groups. For the domain, you could create a resource group
named
group_domain1
and a resource named
resource_mta1
. For the post office, you could
create a resource group named
group_post1
and a resource named
resource_poa1
.
30.1.4 Planning Secondary IP Addresses
Each cluster resource group needs a unique secondary IP address in the cluster. The secondary IP
address remains constant regardless of which node the cluster resource group is running on. It is
independent of all physical IP addresses in your network.
HEARTBEAT CLUSTERING WORKSHEET
Under Item 6: Cluster Resource Groups for GroupWise Components , list the cluster resource groups that
you want to create for GroupWise components. Initially, you plan one or two resource groups for the
primary domain and initial post office. Later, you plan additional resource groups for additional
GroupWise components. A GroupWise resource needs a resource name and the name of the domain or
post office equivalent to its eDirectory
TM object name.