Reload for GroupWise Configuration

Configure Reload for GroupWise

Set the GroupWise version in Reload Administration

Go to Reload Administration by running:

reload

Then go to System | GroupWise | Version and select the appropriate version of GroupWise.

Should that fail the GroupWise software can be added manually:

• Determine what, if any, GroupWise software is already loaded. Get a list of installed GroupWise software by running:

rpm -qa | grep groupwise

• This will return a list of GroupWise components already installed or just return to the command line if nothing is installed. For example, novell-groupwise-dbcopy and novell-groupwise-agents
• Uninstall existing software by running:

rpm -e <software>

For GroupWise 8 and 2012:

rpm -e novell-groupwise-dbcopy 
rpm -e novell-groupwise-agents

For GroupWise 2014:

rpm -e novell-groupwise-server

• Install the GroupWise software:

For GroupWise 8 and 2012, DBCopy and the agent software must be installed from the GroupWise installation software package. DBCopy is found in the "admin" directory and the agent software is found in the "agents" directory. For example, GroupWise 2012:

rpm -ivh novell-groupwise-agents-12.0.2-108211.i586
rpm -ivh novell-groupwise-dbcopy-12.0.2-108211.i586

For GroupWise 2014 and 2014R2, install the server software found in the "server" directory.

./install_server.sh

NOTE: Once the GroupWise software is installed, Reload and Blueprint for Reload can immediately use the version of software that you install. The version of GroupWise will eventually be reported correctly in the Reload Web Administration and Reload Console menu. It can take up to an hour because Reload only checks the version of the GroupWise software that is installed every hour.

Configure Retention Services

Enable Retention Services on GroupWise

To prevent items from being deleted from GroupWise before they are backed up, it is recommended to enable Message Retention Services across the Domain.

• Go into GroupWise Administration | Domain | <specific system> | Client Options | Integrations | Retention and enable "Enable Message Retention Service"

• Go into GroupWise Administration | Domain | <specific system> | Client Options | Environment | Cleanup and disable "Do not purge items until they are backed up"

Configure Profiles

There are two models for creating profiles:

• Collector
• Server

Collector Model

The Collector model creates a software agent called a collector that handles transferring the data to Reload.

It is faster than the Server model and can send the data to up to three different Reload server, but requires copying the entire domain or post office to another directory before sending the data so it has a snapshot of the data.

Server Model

The Server model requires an NFS connection from the GroupWise server to the Reload server. This is slower than the rsync connection that the collector uses, but does not require any extra disk space on the GroupWise server.

Creating Profiles

There are two kinds of profiles: Domain and Post Office.

Domain Profile: Collector Model

You will need to create a directory on the Reload server for the data. For example

/reload/domain/

Configure Restore Area

Once a backup has been created the link to the Restore Area can be made. On Reload Server:

• Enable NFS Server
• Export Profile directory

On GroupWise Server:

• Enable NFS Client
• Mount Reload Profile NFS mount
• Create PO Restore Area

To check if this worked:

• On the Reload server, load a backup for the profile
• On a workstation with a GroupWise client, select File | Open Backup. This will show the items not on the production GW server for the user.

Configure Auto-Reload

You can set up Reload to always have the latest backup available so users can just use the Restore area without having to make a support call. This won't help if they deleted something a week ago but it will reduce calls to the helpdesk.

Configure Tape Backups

Reload can create TAR files for long term backup storage.