Archive:Sesam README for Micro Focus OES Linux and OES Netware

From SEPsesam
Jump to: navigation, search

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

SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.


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.

The SEP sesam Novell client is a Novell Storage Management Data Requester (SMDR) which allows backups of Open Enterprise Server (formerly Novell® Open Enterprise Server) (OES) on NetWare or Linux.

The backup architecture of Novell Netware systems consists of Storage Management Services (SMS) which 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 Server and a second component, called Storage Management Data Requester (SMDR).

To find out more about the backup principles of SEP sesam in a Novell OES environment, please read Backup Principles of SEP in a Novell OES environment.

System Requirements

SEP sesam Server

  • SEP sesam Server with version 3.4 or higher.

OES Linux Client

Operating System

  • Open Enterprise Server 1 Linux SP1
  • Open Enterprise Server 2 Linux
  • Open Enterprise Server 11 Linux
  • Open Enterprise Server 15 Linux
  • Open Enterprise Server 2018 Linux

Sesam modules

  • SEP sesam backup client for SLES 9/10/11/12 x64 or i586
  • for OES 2018 the sesam Microfocus (Novell) module is included in the sesam Linux Client for SLES 12 (no additional installation required)

SMS Architecture

In order to use Novell SMS architecture the package novell-sms-1.1.4-12.i586.rpm (or newer) must be installed ( SMDR YAST pattern from OES section).

OES Netware Client

There is no native SEP sesam Client for OES Netware. To save it an OES Linux has to be used as Data Mover.

See also: Backup principles using SEP sesam in a Micro Focus OES environment

Data Mover OES 2 / OES 11 / OES15 / OES18 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/Micro Focus support SMS components on SLES11 only with OES 11 or OES 15 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.

Configuration of TSA

Configuration of the TSAs on the OES client

Start of SMDRD daemon

Usually the SMS is started in Run Level 3 and 5. To manually start or stop use

 /etc/init.d/novell-smdrd start/stop

For OES 2018 (SLES 12 based)

systemctl start/stop novell-smdrd.service

Starting the TSAs

For allocation and configuration of the TSA Services the program /opt/novell/sms/bin/smsconfig is used.

For instance the TSAFS can be loaded with

smsconfig -l tsafs

and unloaded with

smsconfig -u tsafs

TSAs required for the task types:

  • File System: tsafs
  • GroupWise System: tsafsgw - up to Groupwise 8, since Groupwise 2012 tsafsgw isn't supported by Novell
  • Novell eDirectory: tsands - not available on OES1 - (see section Backup of OES Novell Directory on Linux)
  • Novell iFolder: tsaif - not available on NetWare servers

The file /etc/opt/novell/sms/smdrd.conf allows a permanent configuration.

Example entries in smdrd.conf:

autoload: tsafs --EnableGW
autoload: tsafsgw --home /media/nss/GRPWISE/gw --home /media/nss/GRPWISE/gwpo

Another possibility:

autoload: tsafs --tsamode=linux --cluster

GroupWise TSAFSGW (up to GroupWise 8)

For backup Groupwise 2012/2014 please see the "SEP sesam Extension for Novell Groupwise_2012/2014"


 smsconfig -l tsafs --EnableGW

a file system backup will save GroupWise files in a consistent state.

To activate GroupWise object level backup

 smsconfig -l tsafsgw --home {gw_path} --home {gwpo_path}

is necessary.

Example for GroupWise TSA

/opt/novell/sms/bin/smsconfig -u tsafsgw
/opt/novell/sms/bin/smsconfig -l tsafsgw --home /media/nss/GRPWISE/gw --home /media/nss/GRPWISE/gwpo

The TSAFSGW has implemented the parameter --cluster, but it isn't capable. In this case use the tsafs instead:

/opt/novell/sms/bin/smsconfig -l tsafs --EnableGW --cluster

More information regarding NetWare clusters are deposited here: Backup of Clusters

NSS Volume Backup

The TSAFS for OES Linux supports NSS partitions. By default these partitions are treated like regular Linux file systems and the specific data is also backed up. In the case of a 'mixed Cluster', meaning a cluster containing both OES Linux and OES Netware server, it is recommended to choose the Netware Emulation Mode for TSAFS on OES Linux for the configuration of the NSS Volumes to avoid conflicts with the path name. In all other cases, use the Linux TSA mode.
Backup of such a NSS partition is implemented in such a way that it is automatically continued on the available cluster server in case of a server crash.

Set the TSA mode with:

  • to Linux, the default value:
 smsconfig -l tsafs --tsaMode=linux
  • to Netware:
 smsconfig -l tsafs --tsaMode=netware
  • to Dual to use Linux and Netware File System:
 smsconfig -l tsafs --tsaMode=dual

Installation and Update of SEP sesam Client

Please use a recent SEP sesam Client from

To install or update:

 rpm -Uvh sesam-novell-client-3.4.1-79.SuSE.i586.rpm

OES Netware Client


A Linux system is required to back up OES Netware via SMS. SMS must be installed as described under "2.2.2 SMS Architecture". If SEP sesam Server runs on OES Linux this system may be used to back up OES Netware. Otherwise an adequate SEP sesam Client on OES Linux must be used.

SMS Architecture

The SMS components are part of the OES Netware standard installation.

Start of the SMDR

By default, the SMS services SMDR, TSAFS/TSA500, and TSANDS are loaded by the autoexec.ncf script. You can also load them by using the SMSStart.ncf script provided by the SMS installation. To load SMS services manually, use the server console to execute SMSStart.ncf or load required NLM software manually, for instance



    > load TSANDS.NLM

Start of TSA Services

Only the required TSA services e.g. TSAFS.NLM must be loaded.

For Netware version 6.5 the following services are necessary:

  • File System Backup: TSAFS.NLM
  • GroupWise System: TSAFSGW.NLM
  • Novell eDirectory: TSANDS.NLM

HINT Restart TSAs: Use scripts to allow automatic load of required TSAs.

HINT GroupWise Backup: With the current TSAFS version a file system backup supports GroupWise with


But this does not allow backing up specific GroupWise resources. It only takes care that GroupWise files are backed up consistently.

HINT TSA versions: Novell recommends explicitly the use of the recent TSA versions! E.g. under with keyword: TSA

Backups of open Files

To backup open files CopyOnWrite has to be activated on NetWare.

This is an excerpt from the Novell documentation:

Open Files Backup
TSAFS.NLM supports backup of open files on Novell Storage Services (NSS) volumes if the CopyOnWrite feature is enabled.

To enable CopyOnWrite on a single NSS volume, do the following:

1. At the server console, enter
    nss /FileCopyOnWrite=volume_name
2. Dismount and remount the volume.
   1. To dismount the volume, enter
      dismount volume_name
   2. To remount the volume, enter
      mount volume_name

To enable the feature on all NSS volumes, enter
nss /FileCopyOnWrite=all


The further configuration is continued using the SEP sesam GUI

  • Add the new Novell OES Netware/Linux server. Here 'Netware' respectively 'UNIX' has to be selected as platform and 'Linux' respectively 'OES-Linux' as operating system in case of 'UNIX'.
  • In the properties of the client in the tab 'Novell SMS' (if OS=Linux) respectively 'NetWare Access' (OS=NetWare) a Netware backup user and his password must be entered. This password is used by the SBC_SMDR to login at the Novell server. It is stored encrypted in the SEP sesam database. Insert the hostname of the machine in the field 'Datamover', which has installed the Sesam Backup Client and additionaly the SEP sesam-Novell-client.
  • Task types. There are three types available for backup tasks. Please note that the required TSA Services must be activated on the OES server. The backup tasks are used to select the TSA services.

The source is made up of 3 components:

The SMDR server
usually the server name, and
the Target Service Agent
e.g. again a server name or a special identifier and
the Target Service
a source identifier.

For NDS eDirectory and GroupWise the Target Services can also be indicated in the source. The '@' sign is used as delimiter. If the Target service is not explicitly indicated, the first target service is used by default. The indication is therefore only necessary in case of more than one Target Service.


 TS.GroupWise System@2[SEP]SEPDMUG:

In the Client options, set the Netware Username (for eDirectory and OES-Netware you have to work with the full qualified Username like '' starting with a ".") and Password, as well as the Data-Mover (the system which the SEP sesam-novell-client is installed on), see this screenshot for an example:

Nss backup client.jpg

The following types are available:


The type 'Netware' is used for the backup of the file system data. In case of a Netware file system, the source consists of the volume and if necessary of the directory.

Netware server Full Backup of the Netware server
SYS: Full File Backup of SYS Volume
SYS:SYSTEM/ Backup of the subdirectory SYSTEM on the SYS Volume

In case of a Linux file system the required source is in UNIX Notation e.g. /usr. In case of a Netware client '{client}.NetWare File System' is used as target service agent, and in case of a Linux client '{client}.Linux File System' is used.

This screenshot shows a Backup task for OES or Netware a Client running in TSA Mode "Netware":

Nss backup netware.jpg

This screenshot shows a Backup task for a OES System with TSA Mode "Linux":

Nss backup linux.jpg


TSANDS is only available for OES Netware and (since OES2) on OES Linux. A Linux system with SMS architecture is required to back up NDS. The type 'eDirectory' is used to back up the Novell NDS eDirectory on OES Netware and OES Linux. As source the NDS identifier, e.g. 'NDS1' is sufficient. Use 'Full Directory Backup' as source to store the whole eDirectory.

In case you cannot browse the eDIR tree, change the Username in the clients properties to a full qualified Username starting with a "." like ''

OES1 Linux Novell Directory


Since SEP Sesam Novell client 4.2.x the backup of eDirectory on OES1 is no longer supported

Novell iFolder

To backup the Novell iFolder load the TSAIF. As Novell user you must use the "root" user for this backup job.

One possible backup source for iFolder is

In this case /admin.78317a6c-1927-4f30-b28c-30b5d89c7fdc is the root-directory of the iFolder.

It's possible to restore files/folders with the restore wizard.


The restore of iFolder data is only possible to the original source. An alternate restore target is not supported.

GroupWise up to V 2014

For backup Groupwise 2012/2014 please see the "SEP sesam Extension for Novell Groupwise_2012/2014" And SEP video channel

For backups of GroupWise systems the GroupWise resource must be indicated as source. For a backup of the entire system

GroupWise Mail Server

is used.

In case of a restore, paths or resources may be used. Resources may be used together with paths, e.g. "1[DOM]:/restoreDOM". If a resource is given then the data will be restored under the directory which is referenced by the resource.

To restore deleted Mailbox Items you have to set up a Restore Area, see


Browsing through the file system, especially for the sources of task types 'eDirectory' and 'GroupWise', is available since GUI Version V3.0 Build 2 R 1.242. Therefore in older versions the source has to be indicated manually. Sources for 'eDirectory' on OES Linux must be retrieved manually.

On a Linux client with SMS architecture the sbc_smdr module is used to determine the loaded TSA Modules and the possible sources.

For the calls you have to use the switch -D (display) together with successive Netware sources.

To determine available SMDRs the backup call

sbc_smdr -b -s -S localhost -v 3 

may be used.

The brackets around the resources must be removed to use as backup task source.

SBC_SMDR Options

The SEP sesam Backup module sbc_smdr allows several switches to control the backup or restore behavior.

The special options are shown in sbc_smdr usage output.

2013-02-27 14:05:20: sbc-3036: Info:     # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 4.0R6 Build: 1.1126 20130215 17:24:41 Linux i586 buildfix #
2013-02-27 14:05:20: sbc-3036: Info:     # $Id: sbc_smdr.c,v 1.236 2013/02/15 16:21:08 sesam Exp $ #
2013-02-27 14:05:20: sbc-3500: Info:     Use relocdeli='==::==' from '-o' option
2013-02-27 14:05:20: sbc-3000: Info:                                                              
sbc -b|r|D|h     [-a <DB_options>][-C <control_host>] [-d <device>]         
                 [-f <list_source>] [-F <data_format>] [-i <saveset_info>]  
                 [-j <job_name>] [-l <level>] [-L <control_target>]         
                 [-n <segment_number>] [-o {options}]                       
                 [-B <buffer_size[k]>                                       
                 [-N "<SMDR>:<TSA>:<TS>:<User>:<Pass>:0|1"                  
                 [-O <STOR/RETR_direct>] [-P <PID>] [-R <restore_target>]   
                 [-s <saveset_spec>] [-S <storage_node>] [-t <tape_spec>]   
                 [-T <since_time>] [-x <exclude_regexp>] [-X <exclude_list>]
                 [-v <level>]                                               
# backup  #   [<backup_source1>[ <backup_source2> <backup_sourceN>]] |      
# restore #   [<restore_source1>[ <restore_source2> <restore_sourceN>]] |   
# Display #   [<backup_source1>]                                            
# help    #                                                                 
{options}: comma separated list of                                          
 only for backup:    uncompress            # expand compressed data         
                                           ### open modes:                  
                     OPEN_READ_DENY_WRITE  #  deny write                    
                     USE_LOCK_MODE_IF_DW_FAILS # lock if deny write failed  
                     NO_LOCK_NO_PROTECTION # no lock and not protection     
                     OPEN_READ_ONLY        # dirty read                     
                                           ### TSA specific open modes:     
                     PRESERVE_ACCESS_TIME  # allow HSM solutions            
 only for restore:   rename, overwrite     # rename/overwrite if file exists
                     plain, tree           # restore plain/tree in target dir
                     next                  # start from subsequent tape     
                     skip_data             # process only ACL (Trustees)    
                     noacl                 # process without ACL (Trustees) 
                     INCLUDE_MIGRATED_DATA # restore migrated streams       
Hints for -N:                                                               
 example:      -N "filesrv:filesrv.Netware File System:filesrv:admin:mypass:0"
 encrypted password is enclosed in {}, eg. {02ef7807afb34c}

The meanings of the special open mode and TSA specific open modes are described in Novell SMS documentation. (See - Section "Target Services Generic Open Mode Values")


The backup option '-o uncompress' expands compressed data during backup.

The following information is extracted from SMS Administration Guide.



Backing up Compressed files

When you perform a backup, you need to decide whether to keep compressed files in the same state or back them up in a decompressed state. Listed below are few guidelines to make this decision:

  • Backups are faster if files are in compressed form. If volume compression is turned on and you back up compressed files in a decompressed state, restore speed is degraded when existing files are overwritten.
  • Compression is not supported in some environments (such as a NetWare® 3.11 server or Novell® Storage ServicesTM 2.0). If you intend to restore a file that is currently compressed to an environment that does not support compression, back it up in a decompressed state.
  • You might run out of disk space if you restore decompressed files to a volume, because the compression does not begin immediately.


File System (NSS) and Applications


  • Backup and file compression operation should not be run simultaneously. For example, if the default time for both scheduled backup and restore sessions, and compression is midnight, set one of these defaults to different time. If you want to perform a delayed backup that includes files flagged for compression, schedule the delayed backup after the compression time to allow time for the compression to be completed.
  • Different types of files have different impacts on the backup performance. For example, backups are faster if compressed files are backed up in the same state. If volume compression is turned on and you back up compressed files in a decompressed state, restore speed is degraded when the existing files are overwritten. Compression is not supported in some environments (such as a NetWare® 3.11 server or Novell® Storage ServicesTM 2.0 volumes or ReiserFS). If you intend to restore a file that is currently compressed to an environment that does not support compression, back it up in a decompressed state.


7.3 Common Backup and Restore Issues
Backup is slow
  • Possible Cause: Compressed files are being backed up in a decompressed format.
    Action: See “Backing Up Compressed files” on page 25.
  • Possible Cause: Migrated files are being backed up by demigrating the data.
    Action: See “Backing Up Migrated Files” on page 26.
  • Possible Cause: Background file compression and backup are running at the same time.
    Action: Schedule background file compression before or after backup is scheduled. Based on how compressed files are backed up (see “Backing Up Compressed files” on page 25) the order of scheduling can be decided.
Restore is slow
  • Possible Cause: File compression and restore are running at the same time.
    Action: Schedule restore and background compression of files at different times.
  • Possible Cause: Compressed files are being overwritten with decompressed files.
    Action: Back up compressed files as compressed in the future, if the restore is going to be to a compressed file system. See “Backing Up Compressed files” on page 25.
Unable to restore compressed files
  • Possible Cause: Compression is not supported in some environments such as Novell Storage Services 2.0 or ReiserFS on OES Linux.
    Action: Restore the file to a volume that supports compression.
  • Possible Cause: The file system that the data is restored to does not have the compression feature enabled.
    Action: Enable the compression feature on the file system that data is being restored to.
Out of disk space


  • Possible Cause: You might run out of disk space if you restore decompressed files to a volume, because the compression does not begin immediately.
    Action: Compress the files before the restore.

Backup of NSS volumes with trustees by Unix Extended Attributes (Xattr)

From SEP sesam version 4.0 and higher and Novell OES 2 / OES 11 / OES 15 / OES 18 Linux a backup of NSS file trustees by using of the Linux Extended Attributes is possible. For that the NSS volumes have to be configured that Novell NSS the trustees stored in the Linux EA.

Further information you can get in the Novell Documentation - Extended Attributes (XAttr) Commands (Linux)

You can set the saving of the trustees in the EA by using the Novell program nsscon:

 NSS /ListXattrNWMetadata
 NSS /CtimeIsMetadataModTime

These settings take effect temporarily. To set them permanently you have to adopt the file nssstart.cfg:


The file nssstart.cfg is located in the directory /etc/opt/novell/nss on an OES2 / OES11. When the Extended Attributes are requested from a file or directory in addition to the existing EA namespaces, so far, the information of the namespace netware will be displayed.


oes2k1:/media/nss/VOL1/home/hg/Downloads # getfattr -m- -d Christmas_Binary.gif
# file: Christmas_Binary.gif
user.test="This works"

Then you can create a Linux file backup task (e.g. NSS volume DATA):

 Task type: Path-Backup
 Source     : /media/nss/DATA

and the file trustees will be backed up too.

  • The trustee metadata will be displayed in binary format, as opposed to the regular Extended Attributes.
  • The Linux cp command has changed for OES2. In OES1 the extended attributes are also copied when you use the cp command as the root user to copy files. However, in OES 2, in order to copy the extended attributes, you must use the --preserve=all option.
  • During a restore the trustees will only be recovered if the restore target is a NSS volume. Is the target a regular point in the regular Linux file system (e.g. /tmp) only the EA will be restored which the user can create in the Linux file system, NO trustees.

Backup of DFS junctions

The TSA based backup doesn't follow junctions. Instead the junction file will be saved. Create a separate backup task for the source volume/path of the junction.

Backup of Clusters

To backup clusters the service smdr.novell must be registered in SLP (Service Locator Protocol).

In the following a way to retrieve the cause for problems is shown for OES Linux Clusters. The description is similar for Netware Cluster - beside the commands must be adopted for Netware or a Linux Shell emulation must be used.

This example will show how to configure and adjust the nodes to use the clustermode. The example uses the two nodes lnode1 ( respectively lnode2 ( and the resource DATENPOOL_SERVER (

Check via netstat:

#> netstat -apn | grep 40193
tcp        0      0*               LISTEN     7539/smdrd
#> netstat -apn | grep 40193
tcp        0      0*               LISTEN     7539/smdrd

In this case the cluster resource is neither bonded to lnode1 nor lnode2.

For a Cluster Backup smdrd must be bound to Cluster IP. Therefore a SLP registration for service smdr.novell is necessary.

Check with:

#> slptool findsrvs smdr.novell

The cluster nodes are registered but not the resource DATENPOOL_SERVER.

When using more than one IP address, the SLP has to recognize the correct IP. Check /etc/opt/novell/sms/smdrd.conf

Entry for IP of Cluster must be present (using lnode2):


Post SLP registration for IP of Cluster:

#> slptool register service:smdr.novell://

Check with

#> slptool findsrvs smdr.novell

Now the resource DATENPOOL_SERVER is registered correctly and is shown as CLUSTER_DATENPOOL_SERVER with SLP, which is the name to use in SEP sesam.

As from now CLUSTER_DATENPOOL_SERVER can be added as SEP sesam Client. To continue an active backup after a clusterswitch (failover/failback) it's required to use a datamover, which has nothing to do with the cluster.

One possible output when browsing the resource CLUSTER_DATENPOOL_SERVER:

Cluster Browse en.jpg

The source Full Pool backs up all volumes from a 'NetWare Cluster File System'.

Restore an OES Netware backup onto an OES Linux system


To restore a task type OES Netware onto a OES Linux system a SEP sesam Server version or higher is necessary!

By default, after the selection of the restore task on page "Start" in the restore wizard only hosts with the same operating system platform are offered. That means only OES Netware hosts will appear in the field "Target Node". To make it possible to restore this host backup to an OES Linux host you have to activate this with a SEP sesam database entry.

Before you execute the database command, you should set the SEP sesam profile. Now you can execute the sm_db command.

Up to SEP sesam version 3.6:
sm_db "update task_types set flags='os_indep', protection='A' where backup_type='NetWare'"
SEP sesam version 4.0 or higher:
sm_db "update task_types set flags='os_indep', protection='A' where backup_type='NSS File System'"

After that you can select also OES Linux systems as "Target Node" in the restore wizard (see the example in the figure below, there is the OES Linux host "oesnix1").

Selection of platform independent hosts in the field "Target Node"

Novell Teaming / VIBE

SEP support the backup for Novell Teaming / VIBE. This product can be installed as a stand-alone solution for Teaming / VIBE users or it can be integrated into a complete backup, recovery and disaster recovery solution using any of SEP's Novell certified backup products. Discover how to do a Teaming / VIBE backup here:

SEP sesam Teaming Backup part 1

SEP sesam Teaming Backup part 2


See Troubleshooting for Netware

Further Reference

The configuration of the Novell Storage Management Services is described in Storage Management Services Administration Guide.

The specific TSAs are described in these documents: