1.8 Using Clustering

Reference these sections if you are installing GroupWise Disaster Recovery in a GroupWise cluster.

1.8.1 Installing GroupWise Disaster Recovery in a GroupWise Cluster

GroupWise Disaster Recovery can be implemented where GroupWise is in a cluster.

When GroupWise is implemented in a cluster there are a few extra steps needed to configure GroupWise Disaster Recovery to operate successfully.

In this example there are three servers:

  • GroupWise Disaster Recovery Server

  • GroupWise Cluster Node 1 (NODE1)

  • GroupWise Cluster Node 2 (NODE2)

1.8.2 Installation Collector/Server Model

These sections describe how to install in a GroupWise cluster.

On the GroupWise Disaster Recovery Server

To install GroupWise Disaster Recovery on the GroupWise Disaster Recovery server:

  1. Create a Post Office Profile for the Post Office on the GroupWise Cluster.

  2. If upgrading a standard server model profile to a Collector/Server model profile:

    In GroupWise Disaster Recovery Web Administration, choose the profile and go to the Configure tab for the profile.

  3. Select the Post Office and POA Settings panel.

  4. Find the line Note: Disk Space Required for Collector.

  5. Check that there is sufficient space for the collector and data on each node. Note: This calculation does not take Document Management Libraries into account. If you wish to add DMS, multiple the size of the GWDMS directory structure by 2.

  6. Set Allow Paired Collector to Enabled.

On GroupWise Cluster Node 1 (NODE1)

To install the GroupWise Disaster Recovery Collector Software on NODE1:

  1. Browse to the GroupWise Disaster Recovery Server and select the appropriate collector software from the Tools drop-down menu and select go, or copy the software from the GroupWise Disaster Recovery server found in the directory:

    /opt/beginfinite/reload/setup/collector/gwdr_collector.rpm

  2. Run the following command from the terminal:

    rpm -ivh gwdr_collector.rpm

  3. To exchange SSH keys with the GroupWise Disaster Recovery Server, run the following command from the terminal:

    ssh-copy-id -i /root/.ssh/id_rsa.pub <address of the GroupWise Disaster Recovery Server>

    This is to setup the SSH connection so NODE1 can rsync with GroupWise Disaster Recovery without being prompted for a password. This must be successful before proceeding.

  4. Create a GroupWise Disaster Recovery Collector Profile:

    1. Run the following command from the terminal:

      reload

    2. Choose Create Profile.

    3. Select Create: Create Profiles.

    4. Select Post Office: Create a New GroupWise Post Office Profile.

    5. Give the profile a name. The profile name should not exceed eight characters. Use letters and numbers only, no spaces or other characters. For example: “po”. Be aware, that a profile cannot be renamed, once it has been created. Choose the name wisely. Perhaps you will want to name the profile so that the name is the same as the GroupWise post office or domain that the profile represents, but does not have to match. Once complete, click Next.

    6. Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Domain Collector. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Once complete, click Next.

    7. Enter the path or browse to the local destination directory to store the backup data. For example: /reload. This path can be a location on the Linux server, or an NFS mount to another Linux/Unix server, or to a SAN. The path should always be available; GroupWise Disaster Recovery is not configured to mount paths in order to access stored data. Also, the path should be to a location that has a lot of disk space available. Once complete, click Next.

    8. Confirm the path to the local destination directory.

    9. Choose the server type: "Collector (A Local Post Office/Domain Paired to a GroupWise Disaster Recovery Server)". Select the Next button.

    10. Enter the TCP/IP Address or DNS hostname for the GroupWise Disaster Recovery server this collector will be paired with. Select the Next button.

    11. A terminal session will appear to prompt you to accept an SSH key and enter the password for the GroupWise Disaster Recovery server.

    12. Enter the SSH port used by the GroupWise Disaster Recovery server (default port: 22)

    13. Enter the destination path the data will be stored in on the GroupWise Disaster Recovery server. This is the destination directory you entered when creating the Paired Server on the GroupWise Disaster Recovery server.

    14. Source Path to the GroupWise files: Enter the source path to the local destination directory entered earlier on the GroupWise server. For example: /groupwise/po

    15. Confirm the path to the local source directory

    16. A summary of the profile settings will appear. Select the OK button.

    17. Test and Initialization:

      If the profile is correct, select the Test button.

      If the profile is not correct, select the Skip button.

    18. The profile creation wizard tests and initializes the newly created profile and prepares it to accept a pairing request from a Paired Collector and initializes the newly created profile and prepares it to accept a pairing request from a Paired Collector.

  5. Browse to the GroupWise Disaster Recovery Web Administration page on NODE1. For example, http://NODE1:5555.

  6. Choose the profile being configured.

  7. Select the Configure tab and open the GroupWise Disaster Recovery Collector Settings panel.

  8. Set This Collector is on a Cluster Node to Enabled.

  9. To run a backup job, select the Backups tab, open the Reload Job Control panel, and click Start a Standard Backup Job [SmartPurge Disabled].

    Allow the backup to complete normally.

On GroupWise Cluster Node 2 (NODE2)

Profile settings are not shared across the cluster automatically, this needs to be done manually when setting up or when settings are changed.

  1. Install the GroupWise Disaster Recovery Collector Software on NODE1:

    1. Browse to the GroupWise Disaster Recovery Server and select the appropriate collector software from the Tools drop-down menu and select go, or copy the software from the GroupWise Disaster Recovery server found in this directory:

      /opt/beginfinite/reload/setup/collector/gwdr_collector.rpm

    2. Run the following command from the terminal:

      rpm -ivh gwdr_collector.rpm

  2. Exchange SSH keys with the GroupWise Disaster Recovery Server.

    Run the following command from the terminal:

    ssh-copy-id -i /root/.ssh/id_rsa.pub <address of the GroupWise Disaster Recovery Server>

    This is to set up the SSH connection so NODE1 can rsync with GroupWise Disaster Recovery without being prompted for a password. This must be successful before proceeding.

  3. Obtain the following files from NODE1 and copy them to the same directories on NODE2:

    • The contents of the /opt/beginfinite/reload/conf directory (including the ../conf/cron directory).

    • The license file /opt/beginfinite/reload/license/reload.pem

  4. Restart the GroupWise Disaster Recovery daemon on NODE2 with the following command: reloadd restart

  5. Browse to the GroupWise Disaster Recovery Web Administration page on NODE2. For example:

    http://NODE2:5555

  6. Select the Backups tabs, open the Reload Job Control panel, and click Start a Standard Backup Job [SmartPurge Disabled] to run a backup job.

    This backup should “fail”.

    In the Event Log the failure will look as follows:

    DATE: Fri_Dec_11 TIME: 14:57:25 PROFILE: COLLECT1 - STARTING JOB FOR PROFILE: COLLECT1

    DATE: Fri_Dec_11 TIME: 14:57:25 PROFILE: COLLECT1 - DISK SPACE IN USE AT JOB BEGINNING: 46%

    DATE: Fri_Dec_11 TIME: 14:57:25 PROFILE: COLLECT1 - JOB TYPE: COLLECTOR (INCREMENTAL) BACKUP

    DATE: Fri_Dec_11 TIME: 14:57:25 PROFILE: COLLECT1 - [GRE_DBS_AGENTS] Start Database Backup

    DATE: Fri_Dec_11 TIME: 14:57:34 PROFILE: COLLECT1 - [GRE_DBS_OFUSER] Start OFUSER Backup

    DATE: Fri_Dec_11 TIME: 14:57:38 PROFILE: COLLECT1 - [GRE_DBS] Terminating Processing, Post Office Volume for Profile Not Mounted.

    DATE: Fri_Dec_11 TIME: 14:57:38 PROFILE: COLLECT1 - [GRE_DBS] This must not be the active node for the Post Office

On NODE1 & NODE2

Only the GroupWise Disaster Recovery server requires Backup Age monitoring.

To disable Backup Age Monitoring:

  1. Browse to the GroupWise Disaster Recovery Web Administration page on each node.

  2. Navigate to the Collector Profile > Configure tab, and open the Preferences panel.

  3. Under Backup Age Monitoring, set Monitor How Old the Most Current Backup Is to Disabled.

1.8.3 Upgrading Collectors in a Cluster

Clusters are a bit of a challenge to work with as an inactive node does not do anything since it is inactive, therefore you will have to upgrade each node manually.

  1. Browse to the GroupWise Disaster Recovery Server and select the appropriate collector software from the Tools drop-down menu and select Go, or copy the software from the GroupWise Disaster Recovery server found in the directory:

    /opt/beginfinite/reload/setup/collector/gwdr_collector.rpm

  2. Place the file on each '''inactive''' node in: /opt/beginfinite/reload/upgrade

  3. Upgrade the GroupWise Disaster Recovery Collector software from the terminal by running the reloadu command.