Backup principles using SEP sesam in a Micro Focus OES environment

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2020. 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.


The Novell corporate brand has been acquired by Micro Focus. The Novell OES product name is now Micro Focus Open Enterprise Server; however, SEP sesam documentation update (such as names and screenshots) to reflect these changes is being done in a phased manner, therefore Micro Focus OES may still appear under the name Novell OES.

SEP sesam is a valuable tool for backing up and restoring Novell's server environments. Novell Storage Services (NSS) is fully supported for OES Linux and OES NetWare. In contrast to all other SEP sesam supported operating systems there is no native client to backup and restore a Novell OES NetWare server. To operate an OES NetWare server backup it requires an existing Novell OES2/11 Linux machine in the network environment. This OES Linux machine works as the Data Mover for the native OES NetWare servers.

Data Mover OES 2 / OES 11 / OES 15 / OES 18 Linux

SEP recommends using an OES 2 Linux or OES 11 or OES 15 or OES 18 system as Data Mover backing up OES NetWare:

  • Installing SLES 11 as Data Mover is only supported on OES 11 and OES 15, because Novell support SMS components on SLES11 only with OES 11 installed. For OES 18 only SLES 12 is supported by Microfocus.
  • SEP AG cannot guarantee that the Novell SMS components work properly on a Data Mover based on any other Linux systems.

The following systems can operate as the Data Mover:

  • SEP sesam server on a Novell OES2 Linux / OES 11 / OES 15 / OES 18 and an additionally installed Sesam-Novell-client (to find in the download area under /netware/OES-Linux). For OES 2018 the sesam Microfocus Module is already a part of the sesam SLES 12 Linux client.
  • Any other Novell OES2 Linux / OES 11 / OES 15 / OES 18 server with an installed SEP sesam client and an additionally installed SEP sesam-Novell-client
  • At own risk: any other Linux machine in the network with an installed SEP sesam client, an additionally installed SEP sesam-Novell-client and the Novell OES2/11 SMS components.

Sesam Backup Novell OES Principle.jpg

The DB Server (see the example in the figure above) works as Data Mover for the native OES NetWare servers File Server 1, File Server 2 and Mail Server. The data communication will be effected on the Novell's backup infrastructure (Storage Management Services or SMS). The SEP sesam module SBC_SMDR is a Novell "Storage Management Data Requester" (SMDR) allowing backups of Novell Open Enterprise Server on OES NetWare and OES Linux.

The Storage Management Services (SMS) architecture by Novell is a collection of services providing backup, restore, and data migration. The backup and restore is done by Target Service Agent (TSA) modules loaded on the Novell OES servers and are called by the Storage Management Data Requester (SMDR).

On every OES server has to load the SMS module and the necessary TSA's. Here are some existing TSA's:

Step by Step

Here is a basic description how to configure a backup of an OES NetWare resource. For example, we like to backup the NSS volume VOL1: on File Server 2.

  1. Define which OES2 Linux sesam client has to operate as Data Mover, install a sesam client and Sesam-Novell-client on it and start the SMDR service.
  2. Load the SMS module and the TSAFS module on the File Server 2.
  3. Register the Data Mover and the File Server 2 as client in the SEP sesam GUI.
  4. In the client properties on the page Netware Access enter the eDirectory information and the Data Mover.
  5. Define a new task for client File_Server_2 with data source "VOL1:" and the task type <Netware>.
  6. Start the backup task per schedule or by immediate start.

Where the data goes along

  1. The SEP sesam server starts the backup task for client File_Server_2...
  2. ...and ask the Data Mover (DB_Server) of that client over the SMDR service for the TSAFS source on the OES NetWare client (File Server 2).
  3. If the connection was established the data for the source VOL1: will be requested.
  4. After the data were parsed successfully the backup data go from the client File Server 2 to the Data Mover DB_Server over Novell's SMS.
  5. On the Data Mover the sesam client service takes the data over and send them via TCP to the SEP sesam server.
  6. The SEP sesam server stores the backup data on that mediapool you have configured for the job.

Detailed Installation Information

See the following document: Sesam README for Micro Focus OES Linux and OES Netware

Further Information

Advantages of using Novell SMS (Storage Management Services) architecture to backup Novell / OES data