Archive:SEP sesam Extension für Novell OES Linux & OES Netware
Copyright © SEP AG 1999-2024. Alle Rechte vorbehalten.
Jede Form der Reproduktion der Inhalte dieses Benutzerhandbuches, ganz oder in Teilen, ist nur mit der ausdrücklichen schriftlichen Erlaubnis der SEP AG gestattet. Bei der Erstellung dieses Benutzerhandbuches wurde mit größtmöglicher Sorgfalt gearbeitet, um korrekte und fehlerfreie Informationen bereit stellen zu können. Trotzdem kann die SEP AG keine Gewähr für die Richtigkeit der Inhalte dieses Benutzerhandbuches übernehmen.
|
DER INHALT DIESER SEITE IST VERALTET |
| Die SEP AG hat die Unterstützung für veraltete SEP sesam Versionen eingestellt. Anleitungen stehen nach wie vor für diese SEP sesam Produkte zur Verfügung, jedoch übernimmt SEP AG keine Verantwortung oder Haftung für Fehler oder Ungenauigkeiten in den Anleitungen oder für die falsche Bedienung veralteter SEP sesam Software. Es wird dringend empfohlen Ihre SEP sesam Software auf die neueste Version zu aktualisieren. Die neueste Dokumentation für SEP sesam finden Sie unter Dokumentation. |
Description
The SEPsesam client SBC_SMDR is a Novell "Storage Management Data Requester" (SMDR) allowing backups of Novell Open Enterprise Server (OES) on NetWare or Linux.
The backup architecture of Novell Netware systems consists of Storage Management Services (SMS) that 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).
There are several SMS target service agents (TSAs) available to back up data sources like eDirectory, iFolder, GroupWise or the NSS file system (Novell Storage Services). The SMS architecture allows to address Cluster resources supporting failover and failback functionality.
System Requirements
SEP sesam Server
- Sesam server with version 3.4 or higher.
OES Linux Client
- 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) has to be installed.
Configuration of TSAs on the OES client
Start of SMDRD deamon
Usually the SMS is started in Run Level 3 and 5. To manually start or stop use
/etc/init.d/novell-smdrd start/stop
Start of the TSAs
For availability 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 Sicherung: tsafs
- GroupWise System: tsafsgw
- Novell eDirectory: - at present not available - (see section "Backup of OES Novell Directory on Linux")
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 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
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 backuped. 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 in case of a server crash it is automatically continued on the available cluster server.
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 SEPsesam Client
Please use recent SEPsesam client from http://download.sep.de/netware/sesam-novell-client-*-*.*.*.rpm Install with
rpm -ivh sesam-novell-client-*-*.*.*.rpm
To update you have to use rpm option -U
rpm -Uvh sesam-novell-client-*-*.*.*.rpm
OES Netware Client
A Linux system is required to back up OES Netware via SMS. SMS must be installed like described under "2.2.2 SMS Architecture". If SEPsesam server runs on Linux this system may be used to back up OES Netware otherwise an adequate SEPsesam Linux client must be used.
The Linux system must be choosen as 'Data Mover' in the properties of the OES NetWare Client.
SMS Architecure
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
| Notes |
| Restart TSAs:
Use scripts to allow automatic load of required TSAs. GroupWise Backup: With the current TSAFS version a file system backup supports GroupWise with TSAFS /EnableGW But this does not allow to back up specific GroupWise resources. It only takes care that GroupWise files are backed up consistently. TSA versions: Novell recommends explicitly the use of the recent TSA versions! E.g. under http://support.novell.com/filefinder/ with keyword: TSA |
Configuration
The further configuration is continued using the SEPsesam GUI
- Introduce the new Novell OES Netware/Linux server. Here 'Netware' respectively 'Linux' has to be selected as platform.
- Netware Password. In the properties of the client in the tab 'Novell SMS' 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 SEPsesam database.
- 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 build from 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 explicitely indicated, the first target services is used by default. The indication is therefor only necessary in case of more than one Target Service.
Example:
TS.GroupWise System@2[SEP]SEPDMUG:
The following Backup Types are available:
'Netware' - 'NSS File System'
The type 'Netware' (since SEP Sesam Version 3.8 'NSS File System') is used for the backup of the NSS 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 all NSS file systems 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.
eDirectory
TSANDS is only available for OES Netware and Microsoft Windows. 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 Microsoft Windows. As source the NDS identifier, e.g. 'NDS1' is sufficient.
OES Novell Directory
On OES Linux there is no TSANDS available. Instead the program 'ndsbackup' has to be used. The configuration is described in chapter "Backup of OES Novell Directory on Linux"
GroupWise
For backup of GroupWise systems the GroupWise resource must be indicated as source. For the backup of the entire system
GroupWise Mail Server
is used.
In case of a restore pathes or resources may be used. Resources may be used together with pathes, 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
| Note |
|
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.
Examples
To determine all available SMDRs
#> sbc_smdr -b -s test.save -S localhost -v 3 -N ":::::"
2005-09-29 10:23:14: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE ...
...
2005-09-29 10:24:10: sbc-3500: Info: Visible Storage Management Data Requestors:
2005-09-29 10:24:15: sbc-3500: Info: ES
2005-09-29 10:24:15: sbc-3500: Info: ODALIX
2005-09-29 10:24:15: sbc-3500: Info: SINFONIX
2005-09-29 10:24:15: sbc-3500: Info: TS
...
To determine all available TSAs of a SMDR
- Example for Netware
#> /opt/sesam/bin/sesam/sbc_smdr -D -N "nw1:::admin.admins.mydomain:novell:0" "/NetWare" 2007-03-21 16:42:50: sbc-3500: Info: ::/NetWare 2007-03-21 16:42:50: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R3 Build: 1.161 20070320 17:31:00 Linux i386 abas # 2007-03-21 16:42:50: sbc-3074: Info: Backup start time [20070321164250] 2007-03-21 16:42:50: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 16:42:52: sbc-3500: Info: NW1.NetWare File System "NW1.NetWare File System" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:42:52: sbc-3500: Info: NW1.Novell Directory "NW1.Novell Directory" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - ,
- Example for Linux
#> /opt/sesam/bin/sesam/sbc_smdr -D -N "oesnix1::oesnix1:backup:novell:0" "/NetWare" 2007-03-21 15:55:01: sbc-3500: Info: ::/NetWare 2007-03-21 15:55:01: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R3 Build: 1.161 20070320 17:31:00 Linux i386 abas # 2007-03-21 15:55:01: sbc-3074: Info: Backup start time [20070321155501] 2007-03-21 15:55:01: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 15:55:01: sbc-3500: Info: OESNIX1.GroupWise System "OESNIX1.GroupWise System" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:01: sbc-3500: Info: OESNIX1.Linux File System "OESNIX1.Linux File System" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - ,
To determine the sources (resources) of a Target Service File System
TSA is one of
- Netware File System
- Linux File System
- Cluster File System
Netware File System
Indication of user and password is necessary, in this case 'admin.admins.mydomain' and 'novell'.
#> /opt/sesam/bin/sesam/sbc_smdr -D -N "nw1:::admin.admins.mydomain:novell:0" "/NetWare/NW1.NetWare File System" 2007-03-21 16:43:31: sbc-3500: Info: ::/NetWare/NW1.NetWare File System 2007-03-21 16:43:31: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R3 Build: 1.161 20070320 17:31:00 Linux i386 abas # 2007-03-21 16:43:31: sbc-3074: Info: Backup start time [20070321164331] 2007-03-21 16:43:31: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 16:43:34: sbc-3500: Info: Connection established 2007-03-21 16:43:34: sbc-3500: Info: StartSession: set isUTF8Supp = TRUE 2007-03-21 16:43:34: sbc-3500: Info: Init_Cluster_Params OK 2007-03-21 16:43:34: sbc-3500: Info: Function: LIST_RESOURCES 2007-03-21 16:43:34: sbc-3500: Info: Search for netware resources... 2007-03-21 16:43:34: sbc-3304: Info: Resource: [NetWare server] "NetWare server" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:43:34: sbc-3304: Info: Resource: [Server Specific Info] "Server Specific Info" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:43:34: sbc-3304: Info: Resource: [SYS:] "SYS:" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:43:34: sbc-3500: Info: End of list of netware resources ...
Linux File System
Indication of user and password is necessary, in this case 'backup' and 'novell'.
#> /opt/sesam/bin/sesam/sbc_smdr -D -N "oesnix1::oesnix1:backup:novell:0" "/NetWare/OESNIX1.Linux File System" 2007-03-21 15:55:22: sbc-3500: Info: ::/NetWare/OESNIX1.Linux File System 2007-03-21 15:55:22: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R3 Build: 1.161 20070320 17:31:00 Linux i386 abas # 2007-03-21 15:55:22: sbc-3074: Info: Backup start time [20070321155522] 2007-03-21 15:55:22: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 15:55:22: sbc-3500: Info: Connection established 2007-03-21 15:55:22: sbc-3500: Info: StartSession: set isUTF8Supp = TRUE 2007-03-21 15:55:22: sbc-3500: Info: Init_Cluster_Params OK 2007-03-21 15:55:22: sbc-3500: Info: Function: LIST_RESOURCES 2007-03-21 15:55:22: sbc-3500: Info: Search for netware resources... 2007-03-21 15:55:22: sbc-3304: Info: Resource: [/] "/" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:22: sbc-3304: Info: Resource: [/media/cdrom] "/media/cdrom" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:22: sbc-3304: Info: Resource: [/media/floppy] "/media/floppy" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:22: sbc-3304: Info: Resource: [/media/nss/NSS] "/media/nss/NSS" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:22: sbc-3304: Info: Resource: [/homes] "/homes" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:22: sbc-3500: Info: End of list of netware resources ...
To determine NSS Volumes on OES Linux you may use 'mount' as an alternative.
#> mount /dev/mapper/syslnx-Root on / type ext3 (rw,acl,user_xattr) ... usbfs on /proc/bus/usb type usbfs (rw) /dev/evms/SEP on /opt/novell/nss/mnt/.pools/SEP type nsspool (rw,name=SEP) admin on /_admin type nssadmin (rw) VOL1 on /media/nss/VOL1 type nssvol (rw,name=VOL1)
To determine sources of the Target Service GroupWise System
Indication of user and password is necessary, in this case 'backup' and 'novell'.
#> /opt/sesam/bin/sesam/sbc_smdr -D -N "oesnix1::oesnix1:backup:novell:0" "/NetWare/OESNIX1.GroupWise System" 2007-03-21 15:55:44: sbc-3500: Info: ::/NetWare/OESNIX1.GroupWise System 2007-03-21 15:55:44: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R3 Build: 1.161 20070320 17:31:00 Linux i386 abas # 2007-03-21 15:55:44: sbc-3074: Info: Backup start time [20070321155544] 2007-03-21 15:55:44: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 15:55:44: sbc-3500: Info: Connection established 2007-03-21 15:55:44: sbc-3500: Info: Init_Cluster_Params OK 2007-03-21 15:55:44: sbc-3500: Info: Function: LIST_RESOURCES 2007-03-21 15:55:44: sbc-3500: Info: Search for netware resources... 2007-03-21 15:55:44: sbc-3304: Info: Resource: [GroupWise Mail Server] "GroupWise Mail Server" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:44: sbc-3304: Info: Resource: [1[DOM]:] "1[DOM]:" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:44: sbc-3304: Info: Resource: [2[PO]:] "2[PO]:" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 15:55:44: sbc-3500: Info: End of list of netware resources ...
To determine the sources (resources) of a Target Service eDirectory
Indication of user and password is necessary, in this case 'admin.admins.mydomain' and 'novell'.
ATTENTION: TSANDS is only available on Netware.
#> /opt/sesam/bin/sesam/sbc_smdr -D -N "nw1:::admin.admins.mydomain:novell:0" -v 3 "/NetWare/NW1.Novell Directory" 2007-03-21 16:33:12: sbc-3500: Info: ::/NetWare/NW1.Novell Directory 2007-03-21 16:33:12: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R3 Build: 1.161 20070320 17:31:00 Linux i386 abas # 2007-03-21 16:33:12: sbc-3500: Info: Ending sbc_analyze_opt 0 2007-03-21 16:33:12: sbc-3074: Info: Backup start time [20070321163312] 2007-03-21 16:33:12: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 16:33:12: sbc-3500: Info: Got SMDR from spGlobal->sSBCNlm.szSMDR: nw1 2007-03-21 16:33:12: sbc-3500: Info: Got TSA from spGlobal->sSBCNlm.szTSA: 2007-03-21 16:33:12: sbc-3500: Info: Call NWSMConnectToTSA( [NW1.Novell Directory], ...): retry 0 2007-03-21 16:33:14: sbc-3500: Info: call NWSMTSListTargServices(.) 2007-03-21 16:33:15: sbc-3500: Info: Target Service(s): 2007-03-21 16:33:15: sbc-3500: Info: SEP 2007-03-21 16:33:15: sbc-3500: Info: spGlobal->sSBCNlm.szTS set to default (1'st from list) SEP 2007-03-21 16:33:15: sbc-3500: Info: Got target service from structure - SEP 2007-03-21 16:33:15: sbc-3500: Info: User name copied: admin.admins.mydomain 2007-03-21 16:33:15: sbc-3500: Info: Password copied 2007-03-21 16:33:15: sbc-3500: Info: Connection established 2007-03-21 16:33:15: sbc-3500: Info: Init_Cluster_Params OK 2007-03-21 16:33:15: sbc-3500: Info: Function: LIST_RESOURCES 2007-03-21 16:33:15: sbc-3500: Info: Search for netware resources... 2007-03-21 16:33:15: sbc-3304: Info: Resource: [Full Directory Backup] "Full Directory Backup" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:33:15: sbc-3304: Info: Resource: [Schema] "Schema" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:33:15: sbc-3304: Info: Resource: [.SEP.] ".SEP." d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - , 2007-03-21 16:33:15: sbc-3500: Info: End of list of netware resources ...
SBC_SMDR Options
The Sesam Backup module sbc_smdr allows several switches to control the backup or restore behaviour.
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 OES Novell Directory on Linux
At the moment there is no TSANDS available for eDirectory on Novell OES Linux. SEPsesam provides a special backup type "OES Novell Directory". This backup type is using SEP's sbc_nds and Novell's ndsbackup to back up eDirectory. sbc_nds is generating an apropriate commandline for backup level FULL/DIFF and INCR. ndsbackup needs User and Password. This 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
Requirements
- sesam-novell-client >= 3.0.1.15
Configuration
- Client configured with User and Password
- If not already exisitng 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 any longer located in /usr/bin but under /opt/novell/eDirectory/bin/ndsbackup
To enable an execution with SEPsesam a link into the SEPsesam bin directory is necessary.
Use the following comand in case of a standard installation:
ln -sf /opt/novell/eDirectory/bin/ndsbackup /opt/sesam/bin/sesam
Restore
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 to 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 user sesam of domain sep
HINT: The identifier for the object may be extracted from 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 user sesam of domain sep in RestoreWizard in Expert Options in Tab Filter
.CN=sesam.O=sep.
must be set.
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.
Test of Cluster Node on Commandline:
Change into directory /opt/sesam/bin/sesam
#> ./sbc_smdr -D -N "GEW01:::admin.gew:{passwd}:" /NetWare
returns error 0xFFFEFFB2 NWSMDR_CONNECT_FAILURE SMDR connection failed
#> ./sbc_smdr -D -N "NODE101:::admin.gew:{passwd}:" /NetWare
"NODE101.Linux File System" d_ 2000.01.01 00:00:00 2000.01.01 00:00:00 4096 - ,
#> ./sbc_smdr -b -s test.save -v 3 / 2007-04-16 22:24:52: sbc-3036: Info: # @(#)SESAM BACKUP CLIENT FOR NETWARE FILE SYSTEMS, VERSION: 1.8R6 Build: 1.165 20070405 13:09:58 Linux i686 abas # 2007-04-16 22:24:52: sbc-3063: Info: -------------------- Operation Parameters -------------------- 2007-04-16 22:24:52: sbc-3100: Info: Program PID: 29157 2007-04-16 22:24:52: sbc-3030: Info: Operation: BACKUP, Level: COPY 2007-04-16 22:24:52: sbc-3031: Info: Storage Host: localhost:11001,0-0:SESAM_SECURE_AUTHENTICATION: 2007-04-16 22:24:52: sbc-3032: Info: Control Host: localhost:11001:SESAM_SECURE_AUTHENTICATION: 2007-04-16 22:24:52: sbc-3033: Info: Device: .::SHARE:0 2007-04-16 22:24:52: sbc-3500: Info: Netware argument: ::::****:0 2007-04-16 22:24:52: sbc-3500: Info: Ending sbc_analyze_opt 0 2007-04-16 22:24:52: sbc-3074: Info: Backup start time [20070416222452] 2007-04-16 22:24:52: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-04-16 22:24:52: sbc-3500: Info: Visible Storage Management Data Requestors: 2007-04-16 22:24:58: sbc-3500: Info: NODE101 2007-04-16 22:24:58: sbc-3500: Info: NODE102 2007-04-16 22:24:58: sbc-3500: Info: SMDR set to 1'st from list (default) NODE101 ...
May be Cluster was not registered in SLP (Service Locator Protocol).
Check with (smdrd must be in state LISTEN on Cluster-IP 10.0.2.1:40193)
#> netstat -apn | grep smdrd tcp 0 0 10.0.2.201:40193 0.0.0.0:* LISTEN 7539/smdrd
Here smdrd is bind to Cluster-IP GEW01.
For a Cluster Backup smdrd must be bind to Cluster IP therefor a SLP registration for service smdr.novell is necessary.
Check with:
#> slptool findsrvs smdr.novell service:smdr.novell://10.0.2.201:413/NODE101,65535 service:smdr.novell://10.0.2.202:413/NODE102,65535
Here GEW01 is missing!
Check /etc/opt/novell/sms/smdrd.conf
Entry for IP of Cluster must be present:
ip: 10.0.2.1
This entry must be set automatically during Cluster Resource Switch.
Post SLP registration for IP of Cluster:
#> slptool register service:smdr.novell://10.0.2.1:413/GEW01
Check with
#> slptool findsrvs smdr.novell service:smdr.novell://10.0.2.201:413/NODE101,65535 service:smdr.novell://10.0.2.202:413/NODE102,65535 service:smdr.novell://10.0.2.1:413/GEW01,65535
Restart SMDRD
#> /etc/init.d/novell-smdrd restart
Check SMDRD
#> netstat -apn | grep smdrd tcp 0 0 10.0.2.201:40193 0.0.0.0:* LISTEN 7580/smdrd tcp 0 0 10.0.2.1:40193 0.0.0.0:* LISTEN 7580/smdrd
Further Links/Literature
- The configuration of the Novell Storage Management Services is described in Storage Management Services Administration Guide
- In the documents GroupWise 7 Administration Guide
the specific TSAs are described.