Reload for GroupWise Configuration

From GWAVA Technologies Training
Jump to: navigation, search

Contents

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 Maintenance Purge

This is optional but without it, you will only get a snapshot and not a complete backup. 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 | Environment | Cleanup | Maintenance
  • Enable "Do not purge items until they are backed up"

Configure Profiles

There are two models for creating profiles:

  • Paired Collector
  • Server Only

Paired Collector/Server Model [1]

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

You first set up a receiving server profile (marked with a <~>) on the Reload server then a sending collector profile (marked with a ~) on the GroupWise server.

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 Only 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 On Linux GroupWise Systems

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

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

/reload/

The name of the profile will be used to create sub-directories for each profile.

You will need to know the directories on the GroupWise server for the live data. For example: 

/groupwise/domain
/groupwise/po1

Domain Profile: Collector/Server Model

On the Reload Server, create the Server:

  • Create a directory for the backup data. For example: /reload
  • Start the Reload Administration Console by typing on the command line: 
reload
  • Select "Create (Create Profile)"
  • Select "Domain (Create a New GroupWise Domain Profile)"
  • 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: Domain 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Primary Domain. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Select the Next button.
  • 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. Do not use a NAS as it doesn't allow the right kind of access. The path should always be available; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Choose the server type: "Paired (A Profile on This Server that has a Paired Collector)". Select the Next button.
  • 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.

Testing and initializing a profile does not backup the post office or domain in any way.

Once a profile is tested and initialized successfully, the profile is available to be configured further. The default configuration of a profile is sufficient for making quickly accessible backups with Reload. Further configuration of the profile should be done in Reload Web Administration.

To be able to backup the data, a collector needs to be created on the GroupWise server.

On the GroupWise Server, create the Collector:

On the GroupWise server, the collector will need to be downloaded, installed and configured to connect to the Reload server.

If this is an existing Reload installation with an existing Server model connection for the profile:

  • On the Reload server, browse to the Reload Web Administration Console. Reload_Server_IP_or_Hostname:5555
  • Select the profile
  • Click on the Configure tab
  • Open the Domain and MTA Settings section
  • Enable "Allow Paired Collector"
  • On the GroupWise server, in the Domain directory a new directory (/collect) will be created and the file "reload_collector.rpm" will be created.
  • Open a terminal window, go to where the file is and run: 
rpm -i reload_collector.rpm

If this is a new installation with no preexisting connection:

  • On the GroupWise server, browse to the Reload Web Administration Console. Reload_Server_IP_or_Hostname:5555
  • From the Tool dropdown menu select Domain Collector
  • Click on 2. Installing the Reload Collector Software to open the section
  • Click on reload_collector.rpm to download
  • Open a terminal window, go to where the file is and run: 
rpm -i reload_collector.rpm

Once the collector is installed, start the Reload Administration Console by typing on the command line: 

reload
  • Select "Create (Create Profile)"
  • Select "Domain (Create a New GroupWise Domain Profile)"
  • 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: domain. 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • 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. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Choose the server type: "Collector (A Local Post Office/Domain Paired to a Reload Server)". Select the Next button.
  • Enter the TCP/IP Address or DNS hostname for the Reload server this collector will be paired with. Select the Next button.
  • A terminal session will appear to prompt you to accept an SSH key and enter the password for the Reload server.
  • Enter the SSH port used by the Reload server (default port: 22)
  • Enter the destination path the data will be stored in on the Reload server. This is the destination directory you entered when creating the Paired Server on the Reload server.
  • Enter the source path to the local destination directory entered earlier on the GroupWise server. For example: /groupwise/domain
  • Confirm the path to the local source directory
  • A summary of the profile settings will appear. Select the OK button.
  • Test and Initialization:
    • If the profile is correct, select the Test button.
    • If the profile is not correct, select the Skip button.
  • 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.

Domain Profile: Server Only Model

On the GroupWise server, create an NFS mount by starting YaST2 and installing NFS Server. Each domain and post office must receive their own mount points.

    • Set NFS Server to start
    • Open the port in the firewall, if applicable.
    • Add Directory
      • Browse to the domain directory. For example /groupwise/domain
      • Set options to: rw,no_root_squash,sync

On the Reload server, create a data directory and a profile

  • Create a directory for the backup data. For example: /reload
  • Start the Reload Administration Console by typing on the command line: 
reload
  • Select "Create (Create Profile)"
  • Select "Domain (Create a New GroupWise Domain Profile)"
  • 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: Domain 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Primary Domain. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Select the Server Platform: "Linux (NFS/Linux Server or Linux Cluster Resource)"
  • Select Linux Server Type: "Standard (Standard NFS/Linux Server)"
  • Select NFS/Linux Server Address Type: "1 (TCP/IP Address)"
  • Enter the NFS/Linux Server IP Address
  • Enter the NFS Export Path on the GroupWise server from above. For example: /groupwise/domain
  • A warning page appears that asks if the IP Address and Export path are correct.
  • A Profile Summary page appears
  • The Test and Initialize page allows you to finalize the profile by selecting Test.
    • If the configuration is incorrect, select Skip and makes your changes.
  • Browse to the Reload Web Administration Console and run a backup job.

Post Office Profile: Collector/Server Model

On the Reload Server, create the Server:

  • Create a directory for the backup data. For example: /reload
  • Start the Reload Administration Console by typing on the command line: 
reload
  • Select "Create (Create Profile)"
  • Select "Post Office (Create a New GroupWise Post Office Profile)"
  • 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: Post Office. 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Primary Post Office. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Choose the server type: "Paired (A Profile on This Server that has a Paired Collector)". Select the Next button.
  • 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.

Testing and initializing a profile does not backup the post office or domain in any way.

Once a profile is tested and initialized successfully, the profile is available to be configured further. The default configuration of a profile is sufficient for making quickly accessible backups with Reload. Further configuration of the profile should be done in Reload Web Administration.

To be able to backup the data, a collector needs to be created on the GroupWise server.

On the GroupWise Server, create the Collector:

On the GroupWise server, the collector will need to be downloaded, installed and configured to connect to the Reload server.

If this is an existing Reload installation with an existing Server model connection for the profile:

  • On the Reload server, browse to the Reload Web Administration Console. Reload_Server_IP_or_Hostname:5555
  • Select the profile
  • Click on the Configure tab
  • Open the Post Office and POA Settings section
  • Enable "Allow Paired Collector"
  • On the GroupWise server, in the Domain directory a new directory (/collect) will be created and the file "reload_collector.rpm" will be created.
  • Open a terminal window, go to where the file is and run: 
rpm -i reload_collector.rpm

If this is a new installation with no preexisting connection:

  • On the GroupWise server, browse to the Reload Web Administration Console. Reload_Server_IP_or_Hostname:5555
  • From the Tool dropdown menu select Domain Collector
  • Click on 2. Installing the Reload Collector Software to open the section
  • Click on reload_collector.rpm to download
  • Open a terminal window, go to where the file is and run: 
rpm -i reload_collector.rpm

Once the collector is installed, start the Reload Administration Console by typing on the command line: 

reload
  • Select "Create (Create Profile)"
  • Select "Post Office (Create a New GroupWise Post Office Profile)"
  • 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • 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. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Choose the server type: "Collector (A Local Post Office/Domain Paired to a Reload Server)". Select the Next button.
  • Enter the TCP/IP Address or DNS hostname for the Reload server this collector will be paired with. Select the Next button.
  • A terminal session will appear to prompt you to accept an SSH key and enter the password for the Reload server.
  • Enter the SSH port used by the Reload server (default port: 22)
  • Enter the destination path the data will be stored in on the Reload server. This is the destination directory you entered when creating the Paired Server on the Reload server.
  • Enter the source path to the local destination directory entered earlier on the GroupWise server. For example: /groupwise/po
  • Confirm the path to the local source directory
  • A summary of the profile settings will appear. Select the OK button.
  • Test and Initialization:
    • If the profile is correct, select the Test button.
    • If the profile is not correct, select the Skip button.
  • 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.

Post Office Profile: Server Only Model

On the GroupWise server, create an NFS mount by starting YaST2 and installing NFS Server. Each domain and post office must receive their own mount points.

    • Set NFS Server to start
    • Open the port in the firewall, if applicable.
    • Add Directory
      • Browse to the Post Office directory. For example /groupwise/po
      • Set options to: rw,no_root_squash,sync

On the Reload server, create a data directory and a profile

  • Create a directory for the backup data. For example: /reload
  • Start the Reload Administration Console by typing on the command line: 
reload
  • Select "Create (Create Profile)"
  • Select "Domain (Create a New GroupWise Post Office Profile)"
  • 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: Post Office. 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Primary Post Office. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Select the Server Platform: "Linux (NFS/Linux Server or Linux Cluster Resource)"
  • Select Linux Server Type: "Standard (Standard NFS/Linux Server)"
  • Select NFS/Linux Server Address Type: "1 (TCP/IP Address)"
  • Enter the NFS/Linux Server IP Address
  • Enter the NFS Export Path on the GroupWise server from above. For example: /groupwise/po
  • A warning page appears that asks if the IP Address and Export path are correct.
  • A Profile Summary page appears
  • The Test and Initialize page allows you to finalize the profile by selecting Test.
    • If the configuration is incorrect, select Skip and makes your changes.
  • Browse to the Reload Web Administration Console and run a backup job.

Implimenting a Reload Collector in a Cluster

Implementing a Reload Collector in a Cluster http://support.gwava.com/kb/?View=entry&EntryID=2675

Upgrading Collectors in a Cluster http://support.gwava.com/kb/?View=entry&EntryID=2742

Switching from Server model to Collector Model

If you have been running Reload using the server model and the GroupWise Domain and/or Post Office is on Linux, then you can easily switch to the collector model.

If switching the Domain profile:

  • Browse to the Reload Web Administration console
  • Select the Domain Profile
  • Select the Configure tab and open "Domain and MTA Settings"
  • Enable "Allow Paired Collector" and press save
  • Click on "Setup Paired Collector". This will create the directory /collect in the domain directory on the Groupwise server and copy the file "reload_collector.rpm" to it.
  • Connect to the GroupWise server and run 
rpm -ivh reload_collector.rpm
  • Setup up the collector by running 
reload
  • See Domain Profile: Collector/Server Model to complete the setup process
  • Start a backup job on the collector and the profile on the Reload will change to a Collector/Server with a <~> after the name

If switching the Post Office profile:

  • Browse to the Reload Web Administration console
  • Select the Post Office Profile
  • Select the Configure tab and open "Post Office and POA Settings"
  • Enable "Allow Paired Collector" and press save
  • Click on "Setup Paired Collector". This will create the directory /collect in the post office directory on the Groupwise server and copy the file "reload_collector.rpm" to it.
  • Connect to the GroupWise server and run 
rpm -ivh reload_collector.rpm
  • Setup up the collector by running 
reload
  • See Post Office Profile: Collector/Server Model to complete the setup process
  • Start a backup job on the collector and the profile on the Reload will change to a Collector/Server with a <~> after the name

Troubleshooting Collector Connectivity Issues

That are occasionally issues with the Collector connecting properly to the Reload server during profile testing and an error like this appears: 

The authenticity of host '<ip address>' can't be established. ECDSA key fingerprint is <numeric value> [MD5]
Are you sure you want to continue connecting (yes/no)?

On the server with the Reload Collector:

  • Go to the directory: 
/root/.ssh
  • Delete all files in the directory
  • In the terminal, enter the command 
ssh-keygen -t rsa
  • Take the default values or enter your own, if desired
  • Exchange the ssh keys with the Reload server by entering the command: 
ssh-copy-id -i /root/.ssh/id_rsa.pub <address of Paired Reload Server>
For example, ssh-copy-id -i /root/.ssh/id_rsa.pub 10.1.1.123
  • Return to the Reload Console and retest the Profile

Creating Profiles On Windows GroupWise Systems

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

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

/reload/

The name of the profile will be used to create sub-directories for each profile.

On the Windows GroupWise server:

  • Install the Server Role File and Storage Services | Server for NFS, restart required.

Create the share point

  • In File Explorer browse to the GroupWise folder
  • Right-click the folder to be shared and select Properties
  • Select the NFS Sharing tab and click Manage NFS Sharing
  • Enable Share this folder
  • Select Permissions
  • Set Type of Access to Read-Write and click OK
  • Click OK
  • Click Close

On the Reload server:

  • Create a mount point. For example, /mnt/domain
  • Mount the NFS point from the Windows server 
mount -t nfs <address of GW Windows server>:/<shared folder> <local mount point>
For example: mount -t nfs 10.1.1.123:/po /mnt/po

Domain Profile: Server Only Model

On the Reload server, create a data directory and a profile

  • Create a directory for the backup data. For example: /reload
  • Start the Reload Administration Console by typing on the command line: 
reload
  • Select "Create (Create Profile)"
  • Select "Domain (Create a New GroupWise Domain Profile)"
  • 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: Domain 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Primary Domain. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Select the Server Platform: "Linux (NFS/Linux Server or Linux Cluster Resource)" (Yes, we know its Windows but NFS is the important part)
  • Select Linux Server Type: "Standard (Standard NFS/Linux Server)"
  • Select NFS/Linux Server Address Type: "1 (TCP/IP Address)"
  • Enter the NFS/Linux Server IP Address
  • Enter the NFS Export Path on the GroupWise server from above. For example: /groupwise/domain
  • A warning page appears that asks if the IP Address and Export path are correct.
  • A Profile Summary page appears
  • The Test and Initialize page allows you to finalize the profile by selecting Test.
    • If the configuration is incorrect, select Skip and makes your changes.
  • Browse to the Reload Web Administration Console and run a backup job.

Post Office Profile: Server Only Model

On the GroupWise server, create an NFS mount by starting YaST2 and installing NFS Server. Each domain and post office must receive their own mount points.

    • Set NFS Server to start
    • Open the port in the firewall, if applicable.
    • Add Directory
      • Browse to the Post Office directory. For example /groupwise/po
      • Set options to: rw,no_root_squash,sync

On the Reload server, create a data directory and a profile

  • Create a directory for the backup data. For example: /reload
  • Start the Reload Administration Console by typing on the command line: 
reload
  • Select "Create (Create Profile)"
  • Select "Domain (Create a New GroupWise Post Office Profile)"
  • 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: Post Office. 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 its name is the same as the GroupWise post office or domain that the profile represents. Select the Next button.
  • Give the Profile a Description. The profile description should not exceed 60 characters and should not have comma(,), nor dollar sign($) characters. For example: Primary Post Office. The description of the profile will be added to the Agent Log when backup jobs are run for the profile. Select the Next button.
  • 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; Reload 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. Select the Next button.
  • Confirm the path to the local destination directory
  • Select the Server Platform: "Linux (NFS/Linux Server or Linux Cluster Resource)" (Yes, we know its Windows but NFS is the important part)
  • Select Linux Server Type: "Standard (Standard NFS/Linux Server)"
  • Select NFS/Linux Server Address Type: "1 (TCP/IP Address)"
  • Enter the NFS/Linux Server IP Address
  • Enter the NFS Export Path on the GroupWise server from above. For example: /groupwise/po
  • A warning page appears that asks if the IP Address and Export path are correct.
  • A Profile Summary page appears
  • The Test and Initialize page allows you to finalize the profile by selecting Test.
    • If the configuration is incorrect, select Skip and makes your changes.
  • Browse to the Reload Web Administration Console and run a backup job.

Configure Restore Area

Once a backup has been created the link to the Restore Area can be made.

On Reload Server:

  • Enable NFS Server:
  • Open YaST2 and select Network Services | NFS Server
  • Start the server
  • Select Add Directory button
  • Browse to the post office backup directory. For example: /reload/po
  • Set options: rw,no_root_squash,sync

On a Linux GroupWise Server:

  • Create a mount point
    • Open a terminal window
    • Create a local directory for the mount point. Generally, this is placed in the /mnt directory. For example: md /mnt/backup
  • Enable NFS Client
    • Open YaST2 and select Network Services | NFS Client
    • Set the NFS Server Hostname to the Reload server IP address or hostname
    • Set the Remote Directory to the backup directory on the Reload server. For example: /reload/po
    • Set the Mount Point to the one created on the GroupWise server

On a Windows GroupWise Server

http://support.gwava.com/kb/?View=entry&EntryID=2182 Samba is wonky chmod 777 helps but only temporarily because non-permanent mount

Prerequisite: Install Samba Server on the Reload server

On the Reload server:

Using the "Nautilus File Browser":

  • Browse to the parent directory of the profiles. For example, /reload, with /reload/po under it
  • Right-click on the parent directory of your profiles and select "Properties"
  • Select the Share tab
  • Enable "Share this folder" and give it a share name

In GroupWise Administration

  • Create Post Office Restore Area, this will need to be done for each Post Office:
    • Browse to GroupWise Administration
    • Open System | Restore Area Management
    • Select New
    • Enter a Name and Description
      • If using Linux, Set the Path and Linux Path to the mount point adding /connect/restore. For example: /mnt/backup/connect/restore.
      • If using Windows, Set the Path and Linux Path to the Samba share adding \connect\restore \\<Reload Server Address>\<Post Office Directory>\connect\restore. For example, \\10.1.1.123\po1\connect\restore
    • Under the Membership tab
      • Click Add
      • Select Post Offices
      • Add Post Office

To check if this worked:

  • On the Reload server, load a backup for the profile:
    • From the Reload Web Console, select a Post Office profile
    • Select the Backups tab
    • From the Actions of Existing Backups, select "Turn On Access to the Most Current Backup"
  • On a workstation with a GroupWise client:
    • Move a few items that exist in the backup to the Trash
    • Select File | Open Backup. This view will show the items in the Reload backup, and 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 call to the helpdesk. This won't help if they deleted something a week ago but it does reduce calls to the helpdesk.

  • Prerequisites
    • Profile created
    • Backup stored
    • Restore Area setup

Configure Auto Reload

  • Browse to the Reload Server Web Administration Console
  • Select the Profile for the Post Office
  • Under the Configure tab, under the section "User Access to Backups", enable "[ Auto-Reload ] Load the Most Recent Backup:"

Configure Tape Backups

Reload can create TAR files for long term backup storage.

Under each profile, you can configure Tape Backups, under the Configure tab.

  • Prerequisites:
    • Create a directory for the tape backup TAR files.

Configure Tape Backups

  • Browse to the Reload Web Console
  • Select the Profile
  • Select the Configure tab
  • Open the Tape Backup section
  • Set Create Tape Archive Files to Enabled, and save.
  • Set the Tape Archive File Storage Path, and save.

By default, the schedule is Saturday at 2:00AM

Configure Notifications

Reload will send notifications about Daily Status, Errors, Warnings, Job Completion and Audit events.

Configure Reports & Notifications

  • Browse to the Reload Web Administration Console
  • Select the Configure tab
  • Open the "Reports & Notifications" section
  • Configure each section:
    • Enable each type of notification you wish to receive
    • Enable each section with a Notification TO Recipient

To see if this worked, press the Send button for each section and check your mailbox.

Tip: You can change the From address for each section. You may want to consider using different From addresses and filtering the status messages to go to a folder while errors and warnings go to your inbox to make managing your inbox easier.

Troubleshooting Notifications

If you are unable to receive messages from Reload you can check the Agent log for errors. Reload uses postfix to send mail. Searching for postfix in the log may help you find out what is happening.

A common issue is that the Reload server cannot find the SMTP relay host. You can set this manually.

  • Browse to the Reload Web Administration Console
  • Select the Configure tab
  • Open the "Reload Mailer Preferences, Help & Troubleshooting" section
  • Set the "SMTP Relay Host" to your mail server, and save.
  • Send another test message.

Configure Number of Backups to Keep

By default, Reload keeps 14 days of backups. You can increase or decrease the amount as needed.

This setting is found in the Reload Web Administration under the Profile configuration | <select desired profile> | Configure | Backup Job Settings | Number of Backups To Keep.

Retrieved from "https://traininggwava.microfocus.net/index.php?title=Reload_for_GroupWise_Configuration&oldid=314247"
Personal tools
Namespaces

Variants
Actions
Home
Exchange
GroupWise
JAVA
Linux
MTK
Retain
GW Monitoring and Reporting (Redline)
GW Disaster Recovery (Reload)
GW Forensics (Reveal)
GWAVA
Secure Messaging Gateway
GW Mailbox Management (Vertigo)
Windows
Other
User Experience
Toolbox
Languages
Toolbox