Sesam README for Novell OES Linux and OES Netware
From SEPsesam
(C)SEP AG
Copyright 1999-2011 by SEP AG. 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.
Description
The SEP sesam Novell client is a Novell Storage Management Data Requester (SMDR) which allows backups of 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
- OES Linux SP1
- SuSE Linux 9.1 or higher
- SuSE Enterprise Server 9
- RedHat Enterprise Server 4.0
- Debian 3.1 (Sarge)
SMS Architecture
In order to use Novell SMS architecture the package novell-sms-1.1.4-12.i586.rpm (or higher) must be installed.
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 Novell OES environment
| Data Mover OES2 Linux |
|
SEP recommends using an OES2 Linux system as Data Mover backing up OES NetWare:
|
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
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 backup types:
- File System: tsafs
- GroupWise System: tsafsgw
- 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 TSA
With
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 on OES Linux for the configuration of the NSS Volumes to avoid conflicts with the path name. 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 http://download.sep.de/netware/OES-Linux/
To install or update:
rpm -Uvh sesam-novell-client-3.4.1-79.SuSE.i586.rpm
OES Netware Client
| ATTENTION |
|
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 Linux this system may be used to back up OES Netware. Otherwise an adequate SEP sesam Client 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
> SMSSTART
or
> 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
TSAFS /EnableGW
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 http://support.novell.com/filefinder/ 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
Configuration
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 SEP sesam-Novell-client.
- Backup 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.
Example:
TS.GroupWise System@2[SEP]SEPDMUG:
In the Client options, set the Netware Username 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:
The following Backup types are available:
Netware
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":
This screenshot shows a Backup task for a OES System with TSA Mode "Linux":
eDirectory
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.
OES1 Linux Novell Directory
On OES1 Linux there is no TSANDS available. Instead the program 'ndsbackup' has to be used. The configuration is described in chapter "Backup of OES1 Novell Directory on Linux"
Novell iFolder
To backup the Novell iFolder load the TSAIF.
One possible backup source for iFolder is
/admin.78317a6c-1927-4f30-b28c-30b5d89c7fdc
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.
GroupWise
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 http://www.novell.com/documentation/gw65/index.html?page=/documentation/gw65/gw65_admin/data/abcggai.html
| Hint |
|
Browsing through the file system, especially for the sources of backup 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 test.save -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.
oes642fix:~ # /opt/sesam/bin/sesam/sbc_smdr
2009-08-02 12:33:47: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS,
VERSION: 2.0A4 Build: 1.433 20090804 13:34:23 Linux i686 postfix #
2009-08-02 12:33:47: sbc-3000: Info:
usage:
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}]
[-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)
The meanings of the special open mode and TSA specific open modes are described in Novell SMS documentation.
(See http://developer.novell.com/documentation//smscomp/index.html - Section "Target Services Generic Open Mode Values")
UNCOMPRESS
The backup option '-o uncompress' expands compressed data during backup.
The following information is extracted from http://www.novell.com/documentation/oes/pdfdoc/smsadmin/smsadmin.pdf:
Novell Open Enterprise Server STORAGE MANAGEMENT SERVICES 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 OES1 Novell Directory on Linux
On Novell OES1 Linux there is no TSANDS available for eDirectory. Therefore SEP sesam provides the special backup type "OES Novell Directory" on OES1 Linux. This backup type is using SEP's sbc_nds and Novell's ndsbackup to back up eDirectory. sbc_nds is generating an appropriate command line for backup level FULL/DIFF and INCR. ndsbackup needs User and Password. These values must be defined in the properties of the Backup Task as Backup Option and Restore Option with -a user={your user},pass={your password}
For instance:
-a user=cn=admin.o=novell,pass=novell
As with OES2 the TSANDS Daemon is available and is used for the Backup. Choose "eDirectory" as
Backup type.
Requirements
- SEP sesam-novell-client >= 3.0.1.15
Configuration
- Client configured with User and Password
- If not already existing, a Backup User with Password for eDirectory Backup must be configured in Novell iManager.
- Backup Task with Type OES Novell Directory
- Source must be identifier for eDirectory Tree or Subtree. With the scan function of the program ndsbackup the eDirectory identifiers on OES Linux System may be retrieved:
ndsbackup s
- Set 'Backup Options' and 'Restore Options' of backup task to:
-f @@sbc_nds -F none -a user={User},pass={Password}
Path for ndsbackup since eDirectory 8.8.1
Since eDirectory version 8.8.1 ndsbackup is not located in /usr/bin any longer but in /opt/novell/eDirectory/bin/ndsbackup
To enable an execution with SEP sesam a link into the SEP sesam bin directory is necessary.
Use the following command in case of a standard installation:
ln -sf /opt/novell/eDirectory/bin/ndsbackup /opt/sesam/bin/sesam
Restore in case of OES1-Linux
There is no selective restore possible, but you can filter specific subtrees. To do this you have to choose "Expert Options" in the restore wizard and put the requested subtree under tab 'Filter'.
- Target '/' restores all data into original tree.
- With 'Filter' in 'Expert Options' only the given subtree or object will be restored.
Example: Restore of the user 'sesam' of the domain 'sep'
HINT: The identifier for the object may be extracted from the backup protocol.
Backup protocol eDirectory OESNIX1:
2007-05-16 20:55:26: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR UNIX FILE SYSTEMS, VERSION: 1.8R2 Build: 1.149 ... 2007-05-16 20:55:26: sbc-3063: Info: -------------------- Operation Parameters -------------------- 2007-05-16 20:55:26: sbc-3100: Info: Program PID: 30213 2007-05-16 20:55:26: sbc-3030: Info: Operation: BACKUP, Level: COPY 2007-05-16 20:55:26: sbc-3031: Info: Storage Host: miraculix.sep.de:11001,0-0:: 2007-05-16 20:55:26: sbc-3032: Info: Control Host: miraculix:11001:: 2007-05-16 20:55:26: sbc-3033: Info: Device: SMS:disk4:SHARE:0 2007-05-16 20:55:26: sbc-3207: Info: sbc: Found libacl.so -> implicitly switching to acl mode. 2007-05-16 20:55:26: sbc-3034: Info: Saveset Target: SC20070516090544:job=oesnix1_nds,nod=oesnix1,cmd=sbc,src=OESNIX1,... 2007-05-16 20:55:26: sbc-3064: Info: --------------------- Operation Messages --------------------- 2007-05-16 20:55:26: sbc-3002: Info: Building file list from: [sbc_nds /opt/sesam/bin/sesam/sbc -b -C miraculix:11001 -S ... 2007-05-16 20:55:26: sbc-3003: Info: Opening saveset: SC20070516090544 2007-05-16 20:55:27: sbc-3104: Info: Saveset info: [SEGMENT=2] 2007-05-16 20:55:27: sbc-3004: Info: Begin writing to saveset... 2007-05-16 20:55:27: sbc-3074: Info: Backup start time [20070516205527] a .T=OESNIX1. a .O=sep. a .CN=admingroup.O=sep. a .CN=admingrp.O=sep. a .CN=novlxtier.O=sep. a .CN=www.O=sep. a .CN=admin.O=sep. a .CN=eGuidePublicUser_9392.O=sep. a .CN=novlwww.O=sep. a .CN=novlxregd.O=sep. a .CN=novlxsrvd.O=sep. a .CN=oesnix1admin.O=sep. a .CN=sesam.O=sep. a .CN=wwwrun.O=sep. a .CN=oesnix1_NSS.O=sep. a .CN=oesnix1_SYS.O=sep. a .CN=oesnix1.O=sep. a .CN=oesnix1-PS.O=sep. a .CN=LDAP Server - oesnix1.O=sep. a .CN=LDAP Group - oesnix1.O=sep. a .CN=Http Server - oesnix1.O=sep. a .CN=SAS Service - oesnix1.O=sep. a .CN=SSL CertificateDNS - oesnix1.O=sep. a .CN=SSL CertificateIP - oesnix1.O=sep. a .CN=SNMP Group - oesnix1.O=sep. a .CN=UNIX Workstation - oesnix1.O=sep. a .CN=UNIX Config.O=sep. a .sambaDomainName=OESNIX1-W.O=sep. a .sambaDomainName=OESNIX2-W.O=sep. a .CN=oesnix1_NSS_POOL_POOL.O=sep. a .CN=oes1dom.O=sep. a .CN=MTA.CN=oes1dom.O=sep. a .CN=post.O=sep. a .CN=POA.CN=post.O=sep. a .CN=test.O=sep. a .CN=post Bibliothek.O=sep. a .CN=Security. a .CN=KAP.CN=Security. a .CN=W0.CN=KAP.CN=Security. a .CN=OESNIX1 CA.CN=Security. a .CN=Authorized Login Methods.CN=Security. a .CN=NDS.CN=Authorized Login Methods.CN=Security. a .CN=Challenge Response.CN=Authorized Login Methods.CN=Security. a .CN=Authorized Post Login Methods.CN=Security. a .CN=Login Policy.CN=Security. a .CN=Security Policy.CN=Security. a .CN=Password Policies.CN=Security. ...
To restore the user 'sesam' of the domain 'sep'
.CN=sesam.O=sep.
must be set in the Restore Wizard in Expert Options in Tab Filter.
Restore in case of OES2-Linux
When using OES2-Linux it's possible to restore an eDirectory object.
Backup of NSS volumes with trustees by Unix Extended Attributes (Xattr)
From SEP sesam version 4.0 and higher and Novell OES 2 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:
/ListXattrNWMetadata /CtimeIsMetadataModTime
The file nssstart.cfg is located in the directory /etc/opt/novell/nss on an OES2. 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.
Example:
oes2k1:/media/nss/VOL1/home/hg/Downloads # getfattr -m- -d Christmas_Binary.gif # file: Christmas_Binary.gif netware.metadata=0s//4BAAAAAADvAwAYAAAAACAAAEAAAAAA //////////G2CtLAAAAAAAAAAAAAAAAPjMrSwAAAAAAAAAAAAAAALVmsEsAAAAAAAAAAAAAAAAaLCIh5mqtQhCcGiwiIeZqAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAA AAAAAADAAAAAAAAAAAAAAAAAAAA////////////////AQAAAPN9ifnydiFCjabzfYn58nZJAAAAAAAAAAAAAAAAAAAA user.test="This works"
Then you can create a Linux file backup task (e.g. NSS volume DATA):
Backup type: Path-Backup Source : /media/nss/DATA
and the file trustees will be backed up too.
| ATTENTION |
|
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 (172.16.1.202) respectively lnode2 (172.16.1.203) and the resource DATENPOOL_SERVER (172.16.1.207).
Check via netstat:
#> netstat -apn | grep 40193 tcp 0 0 172.16.1.203:40193 0.0.0.0:* LISTEN 7539/smdrd
#> netstat -apn | grep 40193 tcp 0 0 172.16.1.202:40193 0.0.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 service:smdr.novell://172.16.1.203:413/LNODE2,65535 service:smdr.novell://172.16.1.202:413/LNODE1,65535
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):
ip: 172.16.1.203
Post SLP registration for IP of Cluster:
#> slptool register service:smdr.novell://172.16.1.203:413/CLUSTER_DATENPOOL_SERVER
Check with
#> slptool findsrvs smdr.novell service:smdr.novell://172.16.1.203:413/LNODE2,65535 service:smdr.novell://172.16.1.207:413/CLUSTER_DATENPOOL_SERVER,65535 service:smdr.novell://172.16.1.202:413/LNODE1,65535
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:
The source Full Pool backs up all volumes from a 'NetWare Cluster File System'.
Restore an OES Netware backup onto an OES Linux system
| Caution! |
|
To restore a backup type OES Netware onto a OES Linux system a SEP sesam Server version 3.4.1.27 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 perform the database command you should set the SEP sesam profile described
here. Now you can execute the sm_db command line.
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").
Novell Teaming
SEP support the backup for Novell Teaming. This product can be installed as a stand-alone solution for Teaming 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 backup here:
SEP sesam Teaming Backup part 1
SEP sesam Teaming Backup part 2
Troubleshooting
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:
