Planning Shared Administrative Resources; Ensuring Successful Name Resolution For Groupwise Resource Groups - Novell GROUPWISE 8 - INTEROPERABILITY Manual

If a resource group's current owner node fails, the resource group fails over to the next node in the
possible owners list. You should customize the owners list for each GroupWise resource group
based on the fan-out-failover principle.
When a node fails, its resource groups should not all fail over together to the same node in the
cluster. Instead, the resource groups should be distributed across multiple nodes throughout the
cluster. This prevents any one node from shouldering the entire processing load typically carried by
another node. In addition, some GroupWise resource groups should never have the potential of
failing over to the same node. For example, a post office and POA that service a large number of
very active GroupWise client users should never fail over to a node where another very large post
office and heavily loaded POA reside. If they did, users on both post offices would notice a decrease
in responsiveness of the GroupWise client.
IMPORTANT: If you are planning more than one Internet Agent or WebAccess Agent in the
cluster, you must ensure that they can never fail over to the same node at the same time. You cannot
customize the Windows service names for the Internet Agent or the WebAccess Agent. Therefore,
only one of each can run on a server. The Windows service names for POAs and MTAs include the
name of the post office or domain that they service, so this limitation does not apply to POAs and
MTAs.
SYSTEM CLUSTERING WORKSHEET
Under Item 4: Resource Group for Domain, specify the network name and other required information
for the domain resource group. Mark whether you will place the post office in the same resource
group with the domain.
If you want the post office in a different resource group from where the domain is located, under Item
5: Resource Group for Post Office, specify the network name and other required information for the
post office resource group.

33.6 Planning Shared Administrative Resources

Depending on your administrative needs, you might or might not want to set up shared
administrative resources. For example, you might want to have a shared disk where you install the
®
GroupWise snap-ins to ConsoleOne instead of installing them on multiple administrator
workstations. You might also have a shared disk where you create the GroupWise software
distribution directory. These shared disks could be configured to fail over as part of your clustered
environment.
SYSTEM CLUSTERING WORKSHEET
Under Item 3: Resources for GroupWise Administration, list any shared disks you want to use for
GroupWise administration purposes.
33.7 Ensuring Successful Name Resolution for
GroupWise Resource Groups
When you establish GroupWise resource groups, you establish network names for the locations of
domains and post offices. The network names remain constant no matter which node in the cluster
the domain or post office is currently active on. Because you are using virtual network names, not
physical locations, you must ensure that short name resolution is always successful. For example, in
Planning GroupWise in a Microsoft Cluster 281