$Id: README.NetWare,v 1.15 2007/08/16 10:52:32 sesam Exp $ SEP sesam backup client for Novell Open Enterprise Server on Netware or Linux 1. Product 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). Note: The configuration of the Novell Storage Management Services is described in "Storage Management Services Administration Guide" http://www.novell.com/documentation/oes/pdfdoc/smsadmin/smsadmin.pdf In the documents "GroupWise 7 Administration Guide" http://www.novell.com/documentation/gw7/pdfdoc/gw7_admin/gw7_admin.pdf, "Novell eDirectory 8.7.3 Administration Guide" http://www.novell.com/documentation/ndsedir86/pdfdoc/taoenu.pdf and "Novell iFolder 3.x Administration Guide" http://www.novell.com/documentation/ifolder3/pdfdoc/admin/admin.pdf the specific TSAs are described. 2. System requirements 2.1 Sesam Server Sesam Server with Version 3.0 or higher. 2.2 OES Linux Client 2.2.1 Operating System Lowest supported versions are - OES Linux SP1 - SuSE Linux 9.1 - SuSE Enterprise Server 9 - RedHat Enterprise Server 4.0 - Fedora 3 - Debian 3.1 (Sarge) 2.2.2 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. 2.2.3 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 2.2.4 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 "4. 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 2.2.5 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 2.2.6 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 2.2.7 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 2.3 OES NetWare Client ATTENTION: 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 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. The client must be activated with: #> sm_glbv w gv_netware_via_node {linux_client} e.g. "#> sm_glbv w gv_netware_via_node OES_LN1". 2.3.1 SMS Architecure The SMS components are part of the OES NetWare standard installation. 2.3.2 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 2.3.3 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 to back 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 3. Configuration The further configuration is continued using the SEP sesam GUI 3.1. Introduce the new Novell OES NetWare/Linux server Here 'NetWare' respectively 'Linux' has to be selected as platform. 3.2. 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. 3.2. 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: 1. 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. For instance: 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. 2. 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. 3. 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 "4. Backup of OES Novell Directory on Linux" 4. 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 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. Examples: 1. To determine all available SMDRs oesnix1:~ # /opt/sesam/bin/sesam/sbc_smdr -b -s test.save -S localhost -v 3 2007-03-21 16:07:21: 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:07:21: sbc-3063: Info: -------------------- Operation Parameters -------------------- 2007-03-21 16:07:21: sbc-3100: Info: Program PID: 26319 2007-03-21 16:07:21: sbc-3030: Info: Operation: BACKUP, Level: COPY 2007-03-21 16:07:21: sbc-3031: Info: Storage Host: localhost:11001,0-0:SESAM_SECURE_AUTHENTICATION: 2007-03-21 16:07:21: sbc-3032: Info: Control Host: localhost:11001:SESAM_SECURE_AUTHENTICATION: 2007-03-21 16:07:21: sbc-3033: Info: Device: .::SHARE:0 2007-03-21 16:07:21: sbc-3500: Info: Netware argument: ::::****:0 2007-03-21 16:07:21: sbc-3500: Info: Ending sbc_analyze_opt 0 2007-03-21 16:07:21: sbc-3074: Info: Backup start time [20070321160721] 2007-03-21 16:07:21: sbc-3500: Info: Starting Session "SESAM SBC_NLM Session" ... 2007-03-21 16:07:21: sbc-3500: Info: Visible Storage Management Data Requestors: 2007-03-21 16:07:26: sbc-3500: Info: NW1 2007-03-21 16:07:26: sbc-3500: Info: ES 2007-03-21 16:07:26: sbc-3500: Info: ODALIX 2007-03-21 16:07:26: sbc-3500: Info: OESNIX1 2007-03-21 16:07:26: sbc-3500: Info: TS 2007-03-21 16:07:26: sbc-3500: Info: SMDR set to 1'st from list (default) NW1 2007-03-21 16:07:26: sbc-3500: Info: Got SMDR from spGlobal->sSBCNlm.szSMDR: NW1 2007-03-21 16:07:26: sbc-3500: Info: Visible Target Service Agents: 2007-03-21 16:07:28: sbc-3500: Info: NW1.NetWare File System 2007-03-21 16:07:28: sbc-3500: Info: TSA set to 1'st from list (default) NW1.NetWare File System 2007-03-21 16:07:28: sbc-3500: Info: Got TSA from spGlobal->sSBCNlm.szTSA: NW1.NetWare File System 2007-03-21 16:07:28: sbc-3500: Info: Call NWSMConnectToTSA( [NW1.NetWare File System], ...): retry 0 2007-03-21 16:07:30: sbc-3500: Info: call NWSMTSListTargServices(.) 2007-03-21 16:07:30: sbc-3500: Info: Target Service(s): 2007-03-21 16:07:30: sbc-3500: Info: NW1 2007-03-21 16:07:30: sbc-3500: Info: spGlobal->sSBCNlm.szTS set to default (1'st from list) NW1 2007-03-21 16:07:30: sbc-3500: Info: Got target service from structure - NW1 2007-03-21 16:07:30: sbc-3500: Info: Taking default value ADMIN for username 2007-03-21 16:07:30: sbc-3500: Info: User name copied: ADMIN 2007-03-21 16:07:30: sbc-3500: Info: Taking default value admin for password 2007-03-21 16:07:30: sbc-3500: Info: Password copied 2007-03-21 16:07:30: sbc-1500: Error: Error code NWSMTSConnectToTargetServiceEx FFFDFFD7: Login denied 2007-03-21 16:07:30: sbc-1500: Error: Connection denied. 2007-03-21 16:07:30: sbc-3500: Info: Started Session "SESAM SBC_NLM Session" ... 2007-03-21 16:07:30: sbc-3052: Info: Items processed correctly: [0]. Not processed or incorrectly processed items: [0]. 2007-03-21 16:07:30: sbc-3053: Info: Operation failed! 2007-03-21 16:07:30: sbc-3001: Info: Exiting. 2. To determine all available TSAs of a SMDR 2.1. Example for NetWare oesnix1:~ # /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 - , 2.2. Example for Linux oesnix1:~ # /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 - , 3. To determine the sources (resources) of a Target Service File System TSA is one of 'NetWare File System', 'Linux File System' or 'Cluster File System'. 3.1 Example with NetWare File System Indication of user and password is necessary, in this case 'admin.admins.mydomain' and 'novell'. oesnix1:~ # /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 2007-03-21 16:43:34: sbc-3500: Info: supported nameSpaces of [NetWare server] 2007-03-21 16:43:34: sbc-3500: Info: default : [0: DOS] 2007-03-21 16:43:34: sbc-3500: Info: supported : [4: LONG] 2007-03-21 16:43:34: sbc-3500: Info: supported : [1: MACINTOSH] 2007-03-21 16:43:34: sbc-3500: Info: supported : [2: NFS] 2007-03-21 16:43:34: sbc-3500: Info: end of supported nameSpaces of [NetWare server] 2007-03-21 16:43:34: sbc-3500: Info: supported nameSpaces of [Server Specific Info] 2007-03-21 16:43:34: sbc-3500: Info: default : [0: DOS] 2007-03-21 16:43:34: sbc-3500: Info: supported : [4: LONG] 2007-03-21 16:43:34: sbc-3500: Info: supported : [1: MACINTOSH] 2007-03-21 16:43:34: sbc-3500: Info: supported : [2: NFS] 2007-03-21 16:43:34: sbc-3500: Info: end of supported nameSpaces of [Server Specific Info] 2007-03-21 16:43:34: sbc-3500: Info: supported nameSpaces of [SYS:] 2007-03-21 16:43:34: sbc-3500: Info: default : [0: DOS] 2007-03-21 16:43:34: sbc-3500: Info: supported : [4: LONG] 2007-03-21 16:43:34: sbc-3500: Info: supported : [1: MACINTOSH] 2007-03-21 16:43:34: sbc-3500: Info: supported : [2: NFS] 2007-03-21 16:43:34: sbc-3500: Info: end of supported nameSpaces of [SYS:] 2007-03-21 16:43:34: sbc-3052: Info: Items processed correctly: [3]. Not processed or incorrectly processed items: [0]. 2007-03-21 16:43:34: sbc-3007: Info: Operation successful. 2007-03-21 16:43:34: sbc-3001: Info: Exiting. 3.2 Example with Linux File System Indication of user and password is necessary, in this case 'backup' and 'novell'. oesnix1:~ # /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 2007-03-21 15:55:22: sbc-3500: Info: supported nameSpaces of [/] 2007-03-21 15:55:22: sbc-3500: Info: default : [2: NFS] 2007-03-21 15:55:22: sbc-3500: Info: end of supported nameSpaces of [/] 2007-03-21 15:55:22: sbc-3500: Info: supported nameSpaces of [/media/cdrom] 2007-03-21 15:55:22: sbc-3500: Info: default : [2: NFS] 2007-03-21 15:55:22: sbc-3500: Info: end of supported nameSpaces of [/media/cdrom] 2007-03-21 15:55:22: sbc-3500: Info: supported nameSpaces of [/media/floppy] 2007-03-21 15:55:22: sbc-3500: Info: default : [2: NFS] 2007-03-21 15:55:22: sbc-3500: Info: end of supported nameSpaces of [/media/floppy] 2007-03-21 15:55:22: sbc-3500: Info: supported nameSpaces of [/media/nss/NSS] 2007-03-21 15:55:22: sbc-3500: Info: default : [2: NFS] 2007-03-21 15:55:22: sbc-3500: Info: end of supported nameSpaces of [/media/nss/NSS] 2007-03-21 15:55:22: sbc-3500: Info: supported nameSpaces of [/homes] 2007-03-21 15:55:22: sbc-3500: Info: default : [2: NFS] 2007-03-21 15:55:22: sbc-3500: Info: end of supported nameSpaces of [/homes] 2007-03-21 15:55:22: sbc-3052: Info: Items processed correctly: [5]. Not processed or incorrectly processed items: [0]. 2007-03-21 15:55:22: sbc-3007: Info: Operation successful. 2007-03-21 15:55:22: sbc-3001: Info: Exiting. To determine NSS Volumes on Linux OES 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/GEBICS on /opt/novell/nss/mnt/.pools/GEBICS type nsspool (rw,name=GEBICS) admin on /_admin type nssadmin (rw) VOL1 on /media/nss/VOL1 type nssvol (rw,name=VOL1) 4. To determine sources of the Target Service GroupWise System Indication of user and password is necessary, in this case 'backup' and 'novell' oesnix1:~ # /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 2007-03-21 15:55:44: sbc-3500: Info: supported nameSpaces of [GroupWise Mail Server] 2007-03-21 15:55:44: sbc-3500: Info: default : [4: LONG] 2007-03-21 15:55:44: sbc-3500: Info: end of supported nameSpaces of [GroupWise Mail Server] 2007-03-21 15:55:44: sbc-3500: Info: supported nameSpaces of [1[DOM]:] 2007-03-21 15:55:44: sbc-3500: Info: default : [4: LONG] 2007-03-21 15:55:44: sbc-3500: Info: end of supported nameSpaces of [1[DOM]:] 2007-03-21 15:55:44: sbc-3500: Info: supported nameSpaces of [2[PO]:] 2007-03-21 15:55:44: sbc-3500: Info: default : [4: LONG] 2007-03-21 15:55:44: sbc-3500: Info: end of supported nameSpaces of [2[PO]:] 2007-03-21 15:55:44: sbc-3052: Info: Items processed correctly: [3]. Not processed or incorrectly processed items: [0]. 2007-03-21 15:55:44: sbc-3007: Info: Operation successful. 2007-03-21 15:55:44: sbc-3001: Info: Exiting. 5. 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. oesnix1:~ # /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 2007-03-21 16:33:15: sbc-3500: Info: supported nameSpaces of [Full Directory Backup] 2007-03-21 16:33:15: sbc-3500: Info: default : [4294967292: Directory Name Space] 2007-03-21 16:33:15: sbc-3500: Info: end of supported nameSpaces of [Full Directory Backup] 2007-03-21 16:33:15: sbc-3500: Info: supported nameSpaces of [Schema] 2007-03-21 16:33:15: sbc-3500: Info: default : [4294967292: Directory Name Space] 2007-03-21 16:33:15: sbc-3500: Info: end of supported nameSpaces of [Schema] 2007-03-21 16:33:15: sbc-3500: Info: supported nameSpaces of [.SEP.] 2007-03-21 16:33:15: sbc-3500: Info: default : [4294967292: Directory Name Space] 2007-03-21 16:33:15: sbc-3500: Info: end of supported nameSpaces of [.SEP.] 2007-03-21 16:33:16: sbc-3500: Info: Started Session "SESAM SBC_NLM Session" ... 2007-03-21 16:33:16: sbc-3052: Info: Items processed correctly: [3]. Not processed or incorrectly processed items: [0]. 2007-03-21 16:33:16: sbc-3007: Info: Operation successful. 2007-03-21 16:33:16: sbc-3001: Info: Exiting. 4. 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 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'. Step by Step Instructions 1. Availability of Backup Task Type 'OES Novell Directory' - Which SEP sesam version are you using? Should be version 3.0 or higher. 2. Availability of recent sbc_nds - Please use recent version: http://download.sep.de/netware/ sbc_nds_*.* or sesam-novell-client-*.* - Is sbc_nds in bin/sesam on client side available and executable? 3. Backup Task with User and Password - If not existing define a Backup User with Password for eDirectory Backup in Novell iManager. - Define Backup Task with Type 'OES Novell Directory'. The source is the identifier of your eDirectory tree or subtree. You may check with ndsbackup scan function on OES Linux ndsbackup s - Set Backup Option and Restore Option to: -f @@sbc_nds -F none -a user={your user},pass={your password} 4. Restore - Use target '/', to restore into original tree. - With 'Expert Option' you may set 'Filter' to requested subtree or object. 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 5. 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