Recording Heartbeat Cluster Information; Planning Groupwise Cluster Organization - Novell GROUPWISE 7 - INTEROPERABILITY GUIDE Manual

Section 30.1.2, "Planning GroupWise Cluster Organization," on page 286
Section 30.1.3, "Planning Cluster Resources and Resource Groups," on page 287
Section 30.1.4, "Planning Secondary IP Addresses," on page 287

30.1.1 Recording Heartbeat Cluster Information

Now that you have installed Heartbeat on Linux, you need to record key information about the
cluster. In a Heartbeat cluster, most items that you add to the cluster are referred to as cluster
resources.
HEARTBEAT CLUSTERING WORKSHEET
Under Item 1: HA Management Client
to the GUI HA Management Client for administering your Heartbeat cluster.
Under Item 2: Nodes in the
Identify each node by its DNS hostname and the IP address that it is physically configured with.
Under Item 3: EVMS Container
for GroupWise domains and post offices. An EVMS container resource needs a resource name and the
name of an EMVS storage container.
Under Item 4: File System
information about the file system on that partition. List the device name (for example,/dev/evms/
gwsystem/gwvol1), mount directory (for example, /mnt/gwsystem), and file system type (for
example, reiserfs or ext3) for the file system. In addition to the device, the directory, and the file
system type, a file system resource also needs a resource name.
NOTE: The reiserfs file system type is recommended for storing GroupWise data because it
most efficiently handles the large numbers of small files that are stored in domains and post offices.

30.1.2 Planning GroupWise Cluster Organization

The number of nodes that are available in the cluster and the amount of shared storage in your SAN
strongly influence where you can place GroupWise domains, post offices, and agents. You have
several alternatives:
Your whole GroupWise system can run in a single cluster.
Parts of your GroupWise system can run in one cluster while other parts of it run in one or more
other clusters.
Parts of your GroupWise system can run in a cluster while other parts run outside of the cluster,
on non-clustered servers.
If you do not have the system resources to run all of your GroupWise system in a cluster, you must
decide which parts have the most urgent need for the high availability provided by clustering. Here
are some suggestions:
Post offices and their POAs must be available in order for users to access their GroupWise
mailboxes. Therefore, post offices and their POAs are excellent candidates for the high
availability provided by clustering.
286 GroupWise 7 Interoperability Guide
Password, record the password you want to use to provide access
Cluster, list the nodes that you want to use for your GroupWise system.
Resources, list the EVMS shared storage partitions that you want to use
Resources, for each EVMS shared storage partition, provide the necessary