Backup principles using SEP sesam in a Novell OES environment

From SEPsesam

Jump to: navigation, search

Introduction

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 a OES NetWare server backup it requires an existing Novell OES2 Linux machine in the network environment. These OES2 Linux machine works as the Data Mover for the native OES NetWare servers.


ATTENTION using Data Mover

SEP recommends to use a OES2 Linux system as Data Mover backing up OES NetWare:

  • If installing SLES 11 as Data Mover, a significant amount of effort will be required from the installation engineer. However, this solution is currently not supported by SEP, because Novell doesn't support SMS components on SLES11.
  • Data Mover based on any other Linux systems SEP AG can not guarantee that the Novell SMS components working properly on it.


The following systems can operate as the Data Mover:

  • SEP sesam server on a Novell OES2 Linux and an additionally installed Sesam-Novell-client (to find in the download area under /netware/OES-Linux)
  • Any other Novell OES2 Linux server with an installed Sesam client and an additionally installed Sesam-Novell-client
  • At own risk: any other Linux machine in the network with an installed Sesam client, an additionally installed Sesam-Novell-client and the Novell OES2 SMS components.


image: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 neccesary TSA's. Here are some existing TSA's:

  • TSAFS for backing up Netware 6.5 server directories and files and their additional informations (e.g. NSS volumes)
  • TSANDS for backing up the servers eDirectory informations
  • TSAFSGW for a object oriented backup of the GroupWise data
  • TSA500 for Netware 5.x servers
  • TSAIF iFolder information

Step by Step

Here is a basic description how to configure a backup of a OES NetWare ressource. 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 backup 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 Informations

See the following document: http://wiki.sepsoftware.com/wiki/index.php/Sesam_README_for_Novell_OES_Linux_%26_OES_Netware

Retrieved from "http://wiki.sepsoftware.com/wiki/index.php/Backup_principles_using_SEP_sesam_in_a_Novell_OES_environment"
Personal tools