OpenText GroupWise Backup
Last updated
Last updated
DPX supports backups and restores of OpenText GroupWise in a non-clustered environment. When you install a client on an OpenText Open Enterprise Server (OES) machine that GroupWise runs on, the GroupWise disks will be viewable in DPX.
The following is an extract from a File Backup window of a node that is running GroupWise 2014. This depicts a minimal GroupWise environment containing one GroupWise domain and one GroupWise post office. Additional GroupWise components would appear as additional volumes on the File Backup window. Note that the display may be different for other versions of GroupWise.
DPX supports GroupWise through the Target Service Agents (TSAs) recommended by OpenText for each OpenText and GroupWise platform. For more information on recommended TSAs and their required switches and flags, see the GroupWise Administration Guide.
DPX supports GroupWise and OES as supported by OpenText. If you are using OpenText or Micro Focus software no longer supported by OpenText, our Technical Support assistance may be limited for functions dependent on that software. To address certain issues, the analyst may recommend you upgrade the relevant OpenText software.
For information about OpenText or GroupWise verification utilities, refer to your Micro Focus or GroupWise documentation.
To define backups and restores of GroupWise components, use the web or desktop interface just as you would for any simple backup or restore.
Domain (DOM)
DPX has the ability to back up the entire GroupWise domain structure. DPX can restore entire domains or individual files to their original location or to an alternate location.
Post Offices (PO)
DPX can back up entire post offices or individual files within a post office. DPX can restore entire post offices or individual files to their original location or to an alternate location.
Documentation Management Services (DMS)
DPX can perform backups at the library level or at the file level. DPX can restore entire libraries or individual files to their original location or to an alternate location.
Binary Large Object (BLB)
Binary large objects (blobs) are the database structures for storing message attachments and DMS documents. Binary large objects may be stored separately from the post office. DPX can perform backups of GroupWise binary large objects and can restore entire binary large objects to their original location or to an alternate location.
When restoring any files or components involving a GroupWise domain, including GroupWise post offices, you may need to bring down the MTAs, the POAs, the Micro Focus user interface, and Micro Focus Web Access. However, GroupWise DMS restores can occur while those agents are running.
To test basic backups on OES Linux, use the nbackup utility. To test the TSAFS connection on OES Linux, use the de utility. The de utility might not be included in a standard OpenText installation, but it can be acquired from OpenText.
The information in the remainder of this chapter assumes the reader has a strong grasp of OpenText GroupWise, including post offices, domains, libraries, and storage areas. A list of files needed for complete backup of these components can be found in the GroupWise Administration Guide available at http://www.Micro Focus.com/documentation. The reader is also assumed to have an understanding of GroupWise startup files.
Note. The discussions in the remainder of this chapter reflect GroupWise 7.0. They may be different in some details from other versions of GroupWise.
The following is a brief overview of GroupWise logical and physical layouts.
Each NDS tree in a network can have an associated GroupWise system. At a minimum, the GroupWise system has a primary domain and a post office. Like NDS, the logical framework of GroupWise is hierarchical, with GroupWise domains at the top level, post offices underneath, and libraries defined within the post offices. Further, storage areas can be created for libraries that store library documents in an area other than underneath the post office.
There is also a physical layout of a GroupWise system. GroupWise is flexible enough to allow each GroupWise system process to reside on a separate server. In most organizations, each post office has its dedicated server. Thus, a system with 3 domains, 6 post offices and 6 libraries (3 with separate storage areas) can involve 18 different servers. Additional servers may be used to house various gateway processes, but that is beyond the scope of DPX documentation (most gateways do not need to be restored, even in a disaster recovery scenario).
GroupWise services can be mixed and matched as well. For instance, on a server containing one domain and two post offices, one of the post offices may not be defined in that particular domain. However, Micro Focus strongly recommends that you run only one post office agent per server. It will be rare for more than one post office to run on a given server.
The following represents a typical GroupWise service scenario:
GWServer1
GWDom1 and GWDom2
GWServer2
GWPO1
GWServer3
GWPO2
GWServer4
GWPO3
GWServer5
GWPO4
GWServer6
Storage areas for GWPO4 Library2
Usually, gateways appear under their own domains (logically) and on one server (physically).
For GroupWise resources, there is an NDS/system name for a resource, and a corresponding top-level directory. On the windows, the GroupWise resource is shown as [resource_type]directory_name: or numeric_prefix[resource_type]:, depending on GroupWise versions.
DPX supports GroupWise through the Target Service Agents (TSAs) recommended by OpenText for each GroupWise platform. As a general rule, the following TSAs support the functionality described.
TSANDS, when running, allows the treename and Schema resources to be shown.
TSAFS, when running, allows the server volumes to be shown.
TSAFSGW, when running, allows GroupWise Domain and Post Office volumes to be shown. Note that TSAFSGW does not apply to GroupWise 2012 and later.
GroupWise 2014 and GroupWise 2012 SP3 have been qualified for DPX with OES 11 SP2 x64.
