Knowing What To Expect In Mta And Poa Failover Situations; What's Next - Novell GROUPWISE 8 - INTEROPERABILITY Manual

Recording Cluster-Specific Information for a Software Distribution Directory
To permanently record important cluster-specific information about a software distribution directory
located on a GroupWise partition:
1 In ConsoleOne, click Tools > System Operations > Software Directory Management.
2 Select the software distribution directory, then click Edit.
3 In the description field, record the secondary IP address of the GroupWise partition where the
software distribution directory resides.
4 Click OK, then click Close to save the software distribution directory description.
5 Continue with Knowing What to Expect in MTA and POA Failover
14.6.2 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 needs to restart the
GroupWise client is 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.

14.7 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
Setting up the GroupWise client software and helping users to get started using it. See "Client"
in the GroupWise 8 Administration
Guide.
Connecting your clustered GroupWise system to the Internet. See
the Internet Agent in a Linux Cluster," on page
Providing access to users' GroupWise mailboxes from their Web browsers. See
"Implementing WebAccess in a Linux Cluster," on page
GroupWise 8 Administration
Guide. Also see the GroupWise 8 Windows Client User
161.
181.
Setting Up a Domain and a Post Office in a Linux Cluster 157
Situations.
Guide.
Chapter 15, "Implementing
Chapter 16,