Novell GROUPWISE 7 - INTEROPERABILITY GUIDE, Manual

Page: 64 / 485

64 GroupWise 7 Interoperability Guide
n
ov
do
cx (e
n)
11
Ju
ly 20
08
2 Select a page refresh rate, then click Begin Refresh so that the page automatically refreshes at
the selected rate.
3
Click a cluster resource to bring it online, take it offline, or migrate it to another node.
To take the currently running volume resource offline, click Offline . To migrate the volume
resource, select a node from the drop-down list, then click Migrate .
4 On the Cluster Resource page, click Event Log to view a list of cluster events.
The event log can help you resolve problems with cluster functioning.
3.7.3 Knowing What to Expect in MTA and POA Failover
Situations
In a failover situation, the agents might need to perform some database repair as they start on the
new node. The time required depends on the size of the databases involved.
Typically, the POA returns to full functionality faster than the MTA. This benefits GroupWise client
users, who can reconnect to their mailboxes very quickly and probably do not notice if messages to
users in other post offices are not delivered immediately. The only time a user would need to restart
the GroupWise client would be if he or she was actually in the process of sending a message when
the POA went down. Notify can continue running even if the connection to the POA becomes
unavailable and then it reconnects automatically when the POA is again available.
The MTA typically takes some time reestablishing the links to its post offices, other domains, and
gateways, but this situation usually resolves itself in a few minutes without administrator
intervention. If it does not, you can manually restart the MTA to speed up the process.
In comparison to failover, migration typically takes longer because the agents methodically
terminate their threads and close their databases as part of their normal shutdown procedure.
However, as a result, no database repair is required when the agents start up again in their new
location.
Continue with What’s Next .
3.8 What’s Next
Now that you have at least one GroupWise domain and post office up and running in a clustering
environment, you are ready to proceed with the rest of your GroupWise system setup by:
Š Adding users to post offices. See “ Users ” in the GroupWise 7 Administration Guide .
Š
Setting up the GroupWise client software and helping users to get started using it. See “ Client ”
in the GroupWise 7 Administration Guide . Also see the GroupWise 7 Windows Client User
Guide .
Š
Connecting your clustered GroupWise system to the Internet. See Chapter 4, “Implementing
the Internet Agent in a NetWare Cluster,” on page 69 .