Creating a New Post Office in a Cluster

You can create a new post office in the same resource group where its domain is located or in a separate resource group. If the post office and its domain are in the same resource group, they fail over together. If they are in separate resource groups, they fail over separately.

To create a new post office in a Microsoft cluster:

1. If you selected Yes for Post Office in Same Resource Group as Domain? (under System Clustering Worksheet item 4), map a drive to the shared disk of the domain resource group.

   or

   Map a drive to the shared disk of the post office resource group (System Clustering Worksheet item 5).

2. Manually create the post office directory (System Clustering Worksheet item 8).

   This step is not required, but in a Microsoft cluster, Step 4 will be easier if the post office directory already exists.

3. In ConsoleOne, connect to the GroupWise domain where you want to create the new post office, as described in "Connecting to a Domain" in "Domains" in the GroupWise 6.5 Administration Guide.

4. Create the new post office, following the steps provided in "Creating the New Post Office" in "Post Offices" in the GroupWise 6.5 Administration Guide. Keep in mind the following cluster-specific details:

   • Use the Post Office Worksheet you filled out during Planning a New Clustered Post Office to fill in the fields on the Create GroupWise Post Office page.
   • In the Post Office Database Location field, be sure to browse through the shared disk you accessed in Step 1 to the post office directory you created in Step 2 above.
   • If you want to create a library at the post office (System Clustering Worksheet item 9), select Create Library.
   • The Configure Link option is selected by default. Select TCP/IP Link from Domain to New Post Office. Refer to the Agent Clustering Worksheet that you filled in during Planning Cluster-Unique Port Numbers for Agents in the Cluster for the resource group IP address and cluster-unique port numbers that you need to specify in order to configure the link.

5. In ConsoleOne, right-click the new Post Office object, then click Properties.

6. Click GroupWise > Post Office Settings, then in the Access Mode field, select Client/Server Only.

7. Right-click the new POA object, then click Properties.

   On the POA Agent Settings and Scheduled Events pages, you might want to specify unique times for the following POA activities to prevent multiple POAs from performing the same activities on the same node at the same time during a failover situation:

   • Start User Upkeep
   • Generate Address Book for Remote
   • Enable QuickFinder Indexing
   • Mailbox/Library Maintenance Event

   For more information about these repetitive POA activities, see "Performing Nightly User Upkeep", "Regulating Indexing", and "Scheduling Database Maintenance" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.

8. Make sure you are still connected to the domain that owns the new post office.

9. Rebuild the post office database for the new post office, following the steps provided in "Rebuilding Domain or Post Office Databases" in "Databases" in the GroupWise 6.5 Administration Guide. Be sure to browse to the database location (System Clustering Worksheet item 7) through the shared disk you accessed in Step 1 to the post office directory you created in Step 2 above.

   The database rebuild is necessary in order to transfer the POA configuration information and the post office link information into the post office database, because the POA for the new post office is not yet running.

10. If you want to create a library (System Clustering Worksheet item 9) for the new clustered post office, follow the steps in "Setting Up a Basic Library" or "Setting Up a Full-Service Library" in "Libraries and Documents" in the GroupWise 6.5 Administration Guide, after you have completely finished setting up the new clustered post office.

11. Continue with Installing and Configuring the MTA and the POA in a Cluster.