Source:Micro Focus GroupWise Configuration

From SEPsesam
Revision as of 11:01, 21 July 2017 by Sta (talk | contribs) (Added link to Hardware requirements.)
Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.

Copyright © SEP AG 1999-2024. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check Novell GroupWise archive.


Overview

This article describes prerequisites and configuration requirements for Novell GroupWise environment. Note that the procedures introduced in this article are only the required pre-configuration steps. For details on Novell GroupWise backup and restore configuration, see Novell GroupWise Backup and Novell GroupWise Restore. All required programs for GroupWise backup and restore are included in the SEP sesam Novell client package.

SEP sesam provides reliable data protection for GroupWise environments and supports the following GroupWise object types:

  • GroupWise domains: Primary (created on installation of Groupwise) and secondary domains are main administrative unit for GroupWise system that serves as a logical grouping of one or more post offices and is used for routing processes.
  • GroupWise post offices: A post office is a set of folders on a network file server. It serves as an administrative unit for a group of users and mailboxes. The post office folder stores user mailboxes, messages and information used to distribute the messages.
  • GroupWise libraries: A library is a collection of documents and document properties that are stored in database. A post office can own more libraries. Documents can be stored directly at the post office or in document storage areas outside the post office. Libraries with document storage areas inside the post office will be saved with the post office.

For more details about GroupWise system, see the relevant guide: Novell GroupWise 2012 Administration Guide, Novell GroupWise 2014 Administration Guide

Requirements

Make sure that the following conditions are met when configuring GroupWise with SEP sesam.

General requirements

  • GroupWise 2012/2014 system (all post office/domain/library objects on OES servers). Check the support matrix for the list of supported versions.
  • Verify that your network is set up correctly and that DNS name resolution is successful. Note that forward and reverse DNS resolution is required by SEP sesam (SEP sesam Server, data mover server, GroupWise server/cluster resource, cluster nodes). For details, see How to check DNS configuration.
  • Working SLP name resolution in the network (running slpd on the OES servers).
  • SEP sesam Server ≥ 4.2.2-40
  • Check Hardware requirements for SEP sesam Server or RDS.
  • Data mover server (OES11 or OES2 with installed and activated SMDR modules) with SEP sesam Novell client. For details, see Novell data mover.

GroupWise server requirements

  • The Target Service Agent for File Systems (tsafs) module must work in default Linux mode (not dual or Netware) and the option --EnableGW is required to activate the backup of GroupWise through tsafs. Note that the full path name of the tsafs configuration file on Open Enterprise Server Linux is /etc/opt/novell/sms/tsafs.conf.
  • The GroupWise configuration file gwha.conf must exists in the default folder /etc/opt/novell/groupwise/. If the file gwha.conf exists in another folder, copy and edit edit gwsep.conf file as described below.
  • The home switch in the startup files must have the syntax -- home /<path>/, as described in the Novell GroupWise documentation.

Requirements for GroupWise as standalone server

Groupwise Server (OES11 or OES2 with installed and activated SMDR modules and TSAFS) with SEP sesam Client.

Information sign.png Note
  • The SEP sesam Server and GroupWise server can be also the data mover server.
  • It is not recommended nor supported to have the SEP sesam Server, data mover server and GroupWise server running on a single machine.

Requirements for GroupWise as a Novell cluster resource

All cluster nodes for GroupWise resource (OES11 or OES2 with installed and activated SMDR modules and TSAFS ) must have SEP sesam Client installed.

Information sign.png Note
  • The SEP Sesam Server can be also the data mover server.
  • It is not recommended nor supported to use the cluster nodes as data mover server.

Installing SEP sesam client and Novell client packages

Download and install the following items:

  1. Use the current SEP sesam backup Client for the supported server platform (SLES10/11 x32/x64) from SuSE-Linux.
  2. Install the SEP sesam backup Client on the SEP sesam data mover and/or GroupWise Server/Cluster nodes
    rpm -Uvh <path to sesam client>/<client package>.
  3. Use the current SEP sesam Novell Client >= 4.2.x from OES-Linux.
  4. Install the SEP sesam Novell client on the SEP sesam Server or SEP sesam data mover or GroupWise Server
    rpm -Uvh <path to Sesam Novell client package>/<Novell client package>.

Configuring GroupWise server/cluster nodes

  1. Check if SMDRD is running and TSAFS is loaded correctly:
  2. rcnovell-smdrd status Checking for smdr daemon: running
  3. Check file /etc/opt/novell/sms/tsafs.conf for line:
  4. tsamode=linux
  5. Check file /etc/opt/novell/sms/smdrd.conf for line:
  6. autoload: tsafs --EnableGW or, if the tsamode in the tsafs.conf is not set to Linux: autoload: tsafs --EnableGW --tsamode=linux
  7. Check if TSAFS is loaded.
  8. /opt/novell/sms/bin/smsconfig -t loaded TSAs tsafs --EnableGW --tsamode=linux tsands
    Information sign.png Note
    If you set the Linux TSA Mode in the tsafs.conf and not in the smdrd.conf, only the --EnableGW switch is visible.
  9. A valid access from the SEP sesam data mover to the SEP sesam Client on the GroupWise server respectively the cluster nodes are required. Run the following command on the GroupWise Server respectively on each cluster node.
  10. /opt/sesam/bin/sesam/sm_setup/set_client <hostname of SEP sesam data mover>

Configuring a Novell GroupWise server or cluster as a SEP sesam Client

To protect your GroupWise environment, you must configure the Novell GroupWise server or cluster as a SEP sesam Client.

  1. From Main Selection -> Components -> Topology, select your location and click the New client button. The New client window opens.
  2. In the New client window, configure the following options:
    • Enter the Client name which is virtual NCP Server Name (as shown in ConsoleOne, resolvable via DNS).


  3. Click OK to add the new client.
Information sign.png Note
For GroupWise on non-NSS filesystem (POSIX) use root user for Novell credentials or give your LUM-enabled eDir user the required POSIX permissions.

Known issues

If you have problems with Novell GroupWise, check the Troubleshooting Guide.

See also

Novell GroupWise BackupNovell GroupWise Restore