Backup principles using SEP sesam in a Micro Focus OES environment

From SEPsesam
Other languages:

Copyright © SEP AG 1999-2023. 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 Beefalo/5.0.0 Jaglion. For previous documentation version(s), check Micro Focus archive.


Overview

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 your Micro Focus (previously Novell) 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 SEP sesam Client available to back up and restore a Micro Focus OES NetWare server. Such backups require Micro Focus OES Linux machine in the network environment, which acts as a data mover for the native OES NetWare servers.

This article explains only the SEP sesam backup principles in the Micro Focus environment. For details about installation and configuration, see SEP sesam README for Micro Focus OES Linux and OES NetWare.

Data mover prerequisites

  • SEP sesam Client/RDS/Server on Novell OES2 Linux or Micro Focus OES11, OES 2015, OES 2018 or OES 2023, and additionally installed SEP sesam Micro Focus Client.
    • Installing SLES 11 as data mover is only supported on OES11 and OES 2015, because Micro Focus supports SMS components on SLES 11 only with OES11 installed.
    • For OES 2018 only SLES 12 is supported by Micro Focus. SEP sesam Micro Focus OES module is already a part of the SLES 12 packages, no additional installation of sesam-novell-client package is required.
    • For OES 2023 only SLES 15 is supported by Micro Focus. SEP sesam Micro Focus OES module is already a part of the SLES 15 packages, no additional installation of sesam-novell-client package is required.
    • SEP AG cannot guarantee that the Micro Focus SMS components will work properly on a data mover based on any other Linux systems! Check the SEP sesam OS and Database Support Matrix for the list of supported Micro Focus OES versions.

Backup principle example

In the following example, the DB Server acts as data mover for the native OES NetWare servers File Server 1, File Server 2 and Mail Server. The data communication takes place via the Micro Focus backup infrastructure (Storage Management Services/SMS). The SEP sesam module SBC_SMDR is a Micro Focus Storage Management Data Requester (SMDR) allowing backups on Micro Focus OES NetWare and OES Linux.

The Micro Focus Storage Management Services (SMS) architecture 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 Micro Focus OES servers and called by the SMDR.

TSA examples:

Sesam Backup Novell OES Principle.jpg

Steps

This section shows how to configure a backup of an OES NetWare resource. In our example, the NSS volume VOL1: on the File Server 2 will be backed up.

  1. Determine which OES Linux SEP sesam Client will act as a data mover. Install a SEP sesam Client and Micro Focus OES NetWare module (sesam-novell-client package) on it and start the SMDR service. For details, see Starting SMDR.
  2. Load the SMS module and the TSAFS module on File Server 2.
  3. In the SEP sesam GUI, add the data mover (e.g., DB_Server) and the File Server 2 as SEP sesam Clients, then switch to the Micro Focus SMS tab to enter the eDirectory information and select the data mover. For details, see Configuring Clients.
  4. NetWare client access Beefalo V2.jpg
  5. Create a new backup task for the File Server 2 client. From Main Selection -> Tasks -> By Clients, select your File Server 2 client and click New Backup Task. The New Backup Task window opens.
  6. Enter a meaningful task name. Depending on what you are backing up, select NSS (file system) or eDirectory (Identity Vault) as a task type, and specify VOL1: as a backup source. For details, see Creating a Backup Task.
  7. If you want to start the newly created task immediately, right-click the name of the task and click Immediate Start. If you want to create a periodic backup, you have to create a schedule for your backup task: Click New Schedule under Main Selection -> Scheduling -> Schedules and set up a schedule. For more details, see Creating a Schedule.
  8. Once you have configured a schedule, you must create a new backup event for it. For general information on creating a backup event, see Creating a backup event.

Data backup workflow

The data is backed up as follows:

  1. The SEP sesam Server starts the backup task for the File Server 2 client and asks the data mover (DB_Server) of this client via the SMDR service for the TSAFS source on the OES NetWare client (File Server 2).
  2. When the connection is established, the data is requested for the VOL1: backup source.
  3. After the data is successfully parsed, the backup data is transferred from the client File Server 2 to the data mover DB Server using the Micro Focus SMS.
  4. On the data mover, SEP sesam Client service takes over the data and transfers it via TCP to the SEP sesam Server.
  5. The SEP sesam Server stores the data on the specified media pool.