To set up the load script:

1. In ConsoleOne, browse to and select the Cluster object.

   If necessary, click View > Console View to display its contents.

2. Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the default volume resource load script for the GroupWise volume.

3. Make the following changes to the default load script:

   • Remove the trustmig command. It is not necessary to migrate trustees for a GroupWise volume. Removing this line helps the load script to execute faster.

   • On NetWare 5.1, if you selected SLP as a short name resolution method, add the cvsbind add command for the GroupWise volume to the load script.

     cvsbind add cluster_volume_SERVER IP_address
     

   • If you selected vol:\system on GroupWise volume as the agent installation location (Agent Clustering Worksheet item 1), add a search add command to add the new vol:\system directory to the server search path.

     search add volume:\system
     

   • If you selected sys:\system on each node as the installation location (Agent Clustering Worksheet item 1) but you are storing the agent startup files on the GroupWise volume, add that location to the server search path.

   • If you marked No under Load Agents in Protected Memory? (Agent Clustering Worksheet item 8), add the following abend recovery options:

     set auto restart after abend = 2
     set auto restart after abend delay time = 0
     set auto restart down timeout = 60
     set developer option = off
     

     These settings provide the best possible handling of GroupWise databases in the event that an abend should occur within the cluster when the agents are not running in protected memory.

   • Transfer the agent load commands from the grpwise.ncf file into the load script. Use Ctrl+C to copy and Ctrl+V to paste text into the load script page. Then delete or rename the grpwise.ncf file to avoid future confusion.

     load volume:\system\agent.nlm @startup_file
     

   • If you marked Yes under Load Agents in Protected Memory? (Agent Clustering Worksheet item 8), add the address space parameter to the agent load commands to specify the protected address space for each agent. Add a protection restart command for each address space name.

     load address space=addr_space_name
                             volume:\system\agent.nlm @startup_file
     protection restart name
     

   The result would look similar to the following example:

   

   NOTE:The set commands are needed in the load script only when the agents are not running in protected memory. The address space parameters are needed in the load commands only when the agents are running in protected memory.

4. Click Apply to save the load script.

5. If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

6. Continue with Modifying the Volume Resource Unload Script for the Agents.

To set up the unload script:

1. In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Unload to display the default volume resource unload script.

2. Make the following changes to the default unload script:

   • If you marked Yes under Load Agents in Protected Memory? (Agent Clustering Worksheet item 8), add an unload address space command for each address space. Add an unload kill address space command to ensure that the address space is completely cleaned up.

     unload address space=addr_space_name
     unload kill address space=addr_space_name
     

     If your system seems to be trying to kill the address space before the GroupWise agents have been completely unloaded, resulting in the agents hanging in the unloading state, load the delay.nlm program and set a delay of several seconds before issuing the unload kill address space command to allow the GroupWise agents adequate time to unload completely. The length of the delay varies from system to system; ten seconds is a good starting place.

     unload address space=addr_space_name
     load delay.nlm
     delay 10
     unload kill address space=addr_space_name
     

   • If you marked No under Load Agents in Protected Memory? (Agent Clustering Worksheet item 8), create an unload command parallel to each load command that you placed in the load script.

     unload agent.nlm
     

   • On NetWare 5.1, if you selected SLP as a short name resolution method, add the cvsbind del command for the GroupWise volume to the unload script.

     cvsbind del cluster_volume_SERVER IP_address
     

   • Remove the trustmig command just like you did in the load script.

   The result would look similar to the following example:

   

3. Click Apply to save the unload script.

4. If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

5. Continue with Setting the Failover Path and Policies for the Agents.

To modify the failover path and policies for a GroupWise volume resource:

1. In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Nodes to display the default failover path for the GroupWise volume resource.

   

2. Arrange the nodes in the cluster into the desired failover path for the domain or post office volume (under Agent Clustering Worksheet items 3 or 6).

3. Click Apply to save the failover path.

4. Click Policies to display the default start, failover, and failback policies.

   

   The default policy settings are often appropriate. By default, a volume resource:

   • Fails over automatically if the node it is running on fails

   • Starts automatically on the next node in its failover path

   • Continues running at its failover location, even after its most preferred node is again available

   If you are considering changing these defaults, see the section about failover and failback modes in the cluster documentation for your version of NetWare, as listed in Section 1.0, Introduction to GroupWise 7 and Novell Cluster Services on NetWare.

5. Click OK when you are finished editing the GroupWise volume resource properties.

6. Skip to Section 3.6, Testing Your Clustered GroupWise System.

To create a new startup file without installing the agent software:

1. Make a copy of an existing startup file and name it after the domain or post office that will be serviced by the agent.

2. Edit the setting of the /home startup switch to point to the location of the new domain directory or post office directory. Be careful to maintain the syntax of the original line.

3. Scroll down through the startup file looking for other active (not commented out) startup switches, then modify them as needed for the new agent.

   For example, you might find that the /httpport switch is active and needs to be changed to a cluster-unique port number for the new agent.

4. Save the new startup file.

5. Continue with Modifying Existing Load and Unload Scripts.

To modify existing load and unload scripts:

1. In ConsoleOne, browse to and select the Cluster object.

   If necessary, click View > Console View to display its contents.

2. Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the volume resource load script for the GroupWise volume.

3. Following the pattern of the existing load commands, add load commands for the new instances of the agents you are setting up. Use Ctrl+C to copy and Ctrl+V to paste lines in the load script page.

   The results would be similar to the following example:

   

4. Click Apply to save the modified load script.

5. Click Unload

6. Add corresponding unload commands for the new instances of the agents.

   

7. Click Apply to save the modified unload script.

   You might want to review other properties of the Volume Resource object, such as the failover path on the Nodes page and the failover/failback/migration procedures on the Policies page, in light of the fact that an additional domain and/or post office now resides on the GroupWise volume.

8. Change other Volume Resource properties as needed.

9. Click OK to save the modified properties.

10. In the Cluster State View, take the GroupWise volume offline and then bring it online again to test the new startup files and the modified load and unload scripts. If you need assistance with these tasks, see Section 3.6, Testing Your Clustered GroupWise System.