Source:Troubleshooting NetWare/de: Difference between revisions
(Created page with "NetWare Fehlerbehebung") |
(No difference)
|
Revision as of 12:05, 30 July 2020
NetWare
Checking the reachability of the TSA services
Problem 1
- Determining all available TSAs of a NetWare/OES Server.
⇒ Solution
- On a NetWare Server (the sbc_smdr command must be executed on a machine with the sesam-novell-client package installed):
#> /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 - ,
In this case, the TSAFS (NW1.NetWare File System) and TSANDS (NW1.Novell Directory) are loaded.
- On an OES(2)-Linux server:
#> /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 - ,
The TSAFSGW (OESNIX1.GroupWise System) and TSAFS (OESNIX1.Linux File System) are loaded.
Problem 2
- Determining the sources (resources) of a Target Service File System.
⇒ Solution
- Depending on your installed services, these TSA's are visible:
- NetWare File System
- Linux File System
- GroupWise System
- Novell Directory
- iFolder Store
- Linux Cluster File System
- NetWare Cluster File System
Hinweis | |
To enable debug mode for TSA, see Enabling the Debug Options in TSAFS on OES Linux. |
Unable to browse or backup a NetWare Server
Problem
- It is not possible to browse or back up a NetWare Server.
Possible causes
- No TSA is loaded, or
- The wrong data mover was inserted.
⇒ Solution
- Restart the NetWare file system with unload TSAFS and load TSAFS.
- Edit the properties of the NetWare Server in SEP sesam and adjust the data mover in the NetWare Access tab.
When using OES 2018 SP2 with SMDR/TSA, the TSA backup may fail
Problem
- When using OES 2018 SP2 with SMDR/TSA, the following problem occurs: If two TSA modules (e.g., tsafs and tsands) are loaded via smdr.conf, one of them does not work. Consequently, the TSA backup may fail under certain circumstances.
⇒ Workaround
- Start only one TSA module via smdr.conf, the other module should be loaded manually later. As this is a Micro Focus bug, see the Micro Focus community issue smdr on OES2018SP2 not working for more details.
Sesam Error: Client returns no data
Problem
- Th following error message appears in /var/log/messages on OES Linux client:
nds_nss_GetGroupsbyMember: failed to init socket, status = 0 nds_nss_GetPwdbyName: init sock returned 0 nds_nss_GetPwdbyName: init sock returned 0 nds_nss_GetPwdbyName: init sock returned 0
⇒ Solution
- Fix the lum setup so that eDirectory authentication can complete.
Error messages during a backup
Message 1
- (0XFFFDFFD7) "Login denied".
Possible causes
- Invalid username or password.
⇒ Solution
- Edit the properties of the client in SEP sesam and adjust the login data in the NetWare Access and Novell SMS tabs.
Message 2
- (0XFFFDFFCD) "A data stream cannot be opened." "Unable to open a data stream."
Possible causes
- The user does not have permission to access all data.
⇒ Solution
- Change the user name or adjust the permissions.
Message 3
- 0XFFFEFFCC) "Could not write an object to NDS or write to a stream", or
- (0XFFFEFFB1) "Connection to remote host is lost. Remote host might have disconnected."
Possible causes
- The TSA or the smdr deamon is not running.
⇒ Solution
- Check TSA with opt/novell/sms/bin/smsconfig -t.
Message 4
- (0XFFFDFFDC) "An invalid path was used."
Possible causes
- A wrong backup path was used or the TSAFS was loaded in an incorrect mode.
⇒ Solution
- In the event of --tsamode=dual, it is possible to simply use a Linux path.
- The source NetWare server backs up all existing volumes respectively.
- "VOL-NAME:" backs up a specific volume when using --tsamode=netware.
- The option --tsamode=linux supports path to the volumes/volumename only.
- In the event of a restore, insufficient access rights could be a reason for this message.
Files are locked after backup, server freezes
Problem
- Files are locked for several minutes after a backup and the server freezes spontaneously, requiring a reset.
⇒ Solution
- Update the sesam-novell-client to version 3.4.1.78 or higher to solve this problem.
File-based backup is faster than Novell volume backup
Problem
- The file-based backup is faster than the Novell volume backup.
⇒ Solution
- Disabling the TSA-cache will increase the performance of a Novell-based backup and also decrease the system load.
- Edit the file /etc/opt/novell/sms/tsafs.conf, change the line "cachingmode=enable" to "cachingmode=disable" and apply the settings with rcnovell-smdrd restart.
Checking the performance and availability of a NSS volume via tsatest on OES2
- Back up the resource '/' using the supplied credentials. tsatest -u root -p unsecure
- Back up the resource /home using the supplied credentials. tsatest --path=/home -u root -p unsecure
- Back up the NetWare target SYS:\SYSTEM on ACME_SERVER using the supplied credentials. tsatest -s ACME_SERVER -v SYS: --path=SYSTEM -u root -p unsecure
- Back up the '/' resource using the supplied credentials and a buffer size of 131072 bytes. tsatest -b 131072 -u root -p unsecure
- Back up the resource '/' on server ACME_SERVER using the supplied credentials. This will perform a remote backup if ACME_SERVER is not the server on which tsatest is loaded/executed. tsatest -s ACME_SERVER -u root -p unsecure
- Back up the resource /proc/usb using the supplied credentials. Excludes all datastreams and extended attributes. The value 6144 is arrived by a bitwise ORing of the values for NWSM_EXCLUDE_EXTENDED_ATTRIBUTS (0x0800) and NWSM_EXCLUDE_DATA_STREAMS (0x1000). tsatest --path=/proc/usb -u root -p unsecure -c 6144
- Back up the NetWare virtual server node represented by CLUSTER_OBJECT_CLUSTERPOOL_SERVER. tsatest --cluster -s CLUSTER_OBJECT_CLUSTERPOOL_SERVER
- Back up the specified volume, RESOURCE_ON_THE_CLUSTER_POOL on the NetWare virtual server node represented by CLUSTER_OBJECT_CLUSTERPOOL_SERVER. tsatest --cluster -s CLUSTER_OBJECT_CLUSTERPOOL_SERVER -v RESOURCE_ON_THE_CLUSTER_POOL
To check the performance on a NetWare Server, use these instructions: http://support.novell.com/docs/Tids/Solutions/10092890.html
== See also ==