My Favorites


Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

Tape backup software can't see cluster volumes Show up as VOLID for the name An invalid path was used Internal tsa error

This document (3405548) is provided subject to the disclaimer at the end of this document.


Novell Open Enterprise Server (Linux based) OES1 sp2
Tape backup software
Mixed Netware and Linux cluster


The backup would start but no data would be backed up. The tsa debug logs obtained from the logging functionality in tsafs showed that all the cluster enabled volumes had the name "VOLID" showing up instead of the correct volume names. Since there were no volume names with the name VOLID, the backup failed. There are some API calls that tsafs uses to get information about the clustered volumes. SMS uses the cluster SDK on Linux. The SDK calls used are:
The call NCS_WhatVolumes was returning VOLID back to SMS for each of the clustered volumes. The problem was that the cluster was in a mixed Netware Linux environment. When resources are failed over from Netware to Linux nodes, the load/unload scripts must be translated from Netware format to Linux format. The Netware scripts are stored in edirectory but not the Linux scripts. Any changes made to the Netware scripts are translated to Linux format and stored on the Linux cluster nodes. This situation only happens in mixed clusters. If the nodes were all Netware or all Linux, then the scripts would be stored in edirectory. When tsafs makes the API calls to the cluster SDK to return information about the cluster volumes, the SDK does this by parsing the load scripts in edirectory only, to get the volume names list and then passes this information back to SMS. The problem is the Linux load scripts are not kept in edirectory in a mixed cluster, only the Netware load scripts are. So the wrong format was being passed back to SMS resulting in the VOLID name problem. Multiple tape software solutions had issues with this. Nbackup looked like this:

/opt/novell/sms/bin # ./nbackup -xvf normal_bak.sidf -r"/media/nss/VOL1/linux/ /tmp/linux" -U root
Total data size: 3.00 KB
Elapsed time: 0.00 minutes
/opt/novell/sms/bin # ./nbackup -xvf normal_bak.sidf -r"/media/nss/VOL1/linux/ /tmp/linux" -U root --target-type=netware
nbackup: ( 6.50.0 291) An invalid path was used.
nbackup: ( 6.50.0 334) An internal TSA error has occurred. See error log for details.

Total data size: 7.00 KB
Elapsed time: 0.00 minutes


09/24/2007 12:55 PM 51,419
09/14/2007 10:15 AM 8,076,124 novell-cluster-services-km-
You can extract the clstrlib.ko file that matches the kernel from the rpm such as bigsmp, default, etc. This rpm is for the 286 kernel.
The file is copied into /usr/lib
The clstrlib.ko file is kernel dependent and must be copied into the correct directory that pertains to your kernel such as:
You must find out what kernel you have loaded. This can be done with the uname -a command at the Linux console. Then the correct clstrlib.ko file must be copied into that directory. Make sure to rename the existing files first to preserve them. These files will be out on the channel after they have been approved. They are available from Novell support.


Reported to Engineering


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3405548
  • Creation Date:27-SEP-07
  • Modified Date:27-APR-12
    • SUSESUSE Linux Enterprise Server
      SUSE Linux Enterprise Software Development Kit

Did this document solve your problem? Provide Feedback

< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center