Search Google Appliance

Home >> HFS >> Need Help Using the HFS? >> HFS Backup for NetWare Help and Support >> Installing the TSM Client for Novell NetWare 6.50

Installing the TSM Client for Novell NetWare 6.50

1. Prerequisites for the TSM client for Novell NetWare 6.50

  1. This file contains instructions for installing version of the TSM backup client for Novell NetWare. You should be running version 6.50 of NetWare or NetWare OES in order to use this package.
  2. The TSM client for NetWare can be particular about the the level of SMS services with which it will run. Tivoli/IBM recommend the following minimum module levels:
    • NetWare 6.50: Netware Support Pack SP5, SP6, SP7, SP8+ with current patches
    • NetWare OES : V1 or V2 with current support patches

    Later versions of Netware Support Pack may also work.

  3. You will need a standard (10Mb or faster) connection to the University Network (Not Broadband/Cable or Dial-up).
  4. Additionally you may need anywhere from 150 - 700 bytes of free server RAM for each file per volume, when performing an incremental backup. This therefore translates to a free RAM requirement of 150MB - 700MB per million files. There are established workarounds in the troubleshooting section when either through a paucity of RAM or a very large number of files on a single volume - this requirement cannot be met.

2. Upgrading from an earlier client version

If you have an earlier version of the TSM client already installed, you should uninstall it before carrying out the install of the current version, as follows:

  1. From the installation directory of the prior version ( typically SYS:/tivoli/tsm/client/ba), save the files dsmsched.log, dsmerror.log and dsm.opt to an alternative location.
  2. If you are running TSM version 5.3 and you have used TSM data encryption to encrypt your backups, then you should make a copy of the file TSM.PWD to a safe location. Please look at the troubleshooting section for further information on this.
  3. Unload the scheduler module DSMCAD.NLM.
  4. If you used the NWCONFIG.NLM module to install the previous version of the TSM client (as we will do below), you should use this module to deregister the previous version:
  5. Load the NWCONFIG.NLM module.
  6. Select the "Product Options" option from the main menu.
  7. Select "View/Configure/Remove installed products".
  8. Delete any TSM components from the resulting list.
  9. Delete the TSM installation directory.

3. Obtaining, installing and configuring the TSM client

  1. The HFS packaged TSM client for NetWare is pre-configured to connect to a specific server.

    If this is a new installation, please download and install the following file tsmB8v5526ntw.exe and skip to step 2. below.

    If you are upgrading a current client, then examine the SERVERNAME option in your current dsm.opt file. The value of this will end in either B2, B4, B6 or B8 and this will indicate which of the packages to download and install below.

    Standard HFS server backup service tsmB2v5526ntw.exe
    Standard HFS server backup service tsmB4v5526ntw.exe
    Large server backup service tsmB6v5526ntw.exe
  2. Place the downloaded executable file in a temporary location of your choice, and run it to expand the package distribution files in the current directory. This directory will now contain, amongst other things, a package description file for NetWare with an .ips suffix.
  3. From the NetWare server console, load the module NWCONFIG.NLM, which allows the installation and configuration of software packages. From the main menu, select the option "Product Options", and from the resulting screen, select "Install a product not listed". Enter the directory path at which you unpacked the downloaded package.

    Note: if you have previously used the NWCONFIG.NLM module, when you choose to "install a product not listed", it will list the previously-used paths. If the path you require is not on the list, you need to choose one of the others to be given the opportunity to choose a different location.

  4. The configuration manager will now prompt you to select those components of the TSM software that you wish to install. The only component which is required is the first of these (the backup/archive client).

    Confirm your selection, and the package will be installed. Make a note of the directory to which the TSM software is installed (you are given the option to change the installation directory).

  5. The TSM software uses a configuration file DSM.OPT, located in the client installation directory SYS:/tivoli/tsm/client/ba. This file needs to be edited before you use the software.

    Instructions for editing this file are included at the start of the file in the form of comments. The minimum that needs to be done is the following:

    1. Amend the Nodename line to name your client, as registered with the HFS service. This will be of the form MACHINE.DEPT in most cases.
    2. Amend the Domain line to list the volumes you wish to back up. Note the comments about the inclusion of the NDS in the DOMAIN statement. Please avoid backing up volumes or directories used only for temporary files. Please also avoid backing up drives shared from other machines; these should be backed up from their home machine.
    3. At the end of this file is a sample set of Exclude directives. These name filenames or filename patterns which should not be backed up, being mainly temporary files which have no historical value. You should study this file, consider your filestore usage, and amend the file to avoid backing up unnecessary files (for example, temporary files used by programs and utilities, spool files, cached web pages etc). Additional excludes should be added to the end of this list, as TSM processes these directives bottom up. If you have an old customized set of exclusions, merge these into the new DSM.OPT file.

4. Running the TSM client for Novell NetWare 6.5

  1. First you will need to ensure that the TSM installation directory is in the NetWare load path.
  2. Load the modules TSAFS and TSANDS:
    load TSAFS
    load TSANDS
  3. Then start the TSM session:

    If you have copied a saved password file TSM.PWD into the TSM installation directory, then you should just be logged in automatically. If not, then you will be prompted first for your User Id (TSM node name), and then for your TSM password. For the User Id you can accept the default displayed in angle brackets which will be the TSM Nodename specified in the configuration file DSM.OPT. The password you enter should be the TSM password, as supplied with your registration details or set by you using a previous TSM client version.

  4. You can now query your client account on the TSM server as below:
    tsm> q inclexcl   # lists order of processing of include/exclude directives
    tsm> q sched      # displays details of client's scheduled backup 
    tsm> q files      # lists backups of partitions (if any)
  5. In order to perform automated backups, it is necessary for TSM to store encrypted NetWare passwords to access the various local resources. To ensure that this happens, run the following commands:
    tsm> q tsa
    tsm> q tsa nds

    You will be prompted at each command for a NetWare user name and password; you should enter the details for the administrator account.

    To check that the passwords have been stored successfully, you should exit the current TSM session:

    tsm> quit

    Then, from the server console, start a new session. You should not be prompted for a password at the start of the session, and you should be able to run the queries as before, again without being prompted for a password. If this does not work, it is possible that the password file is corrupted. In this case, exit the TSM session, delete all .PWD files, and try again. Note, that starting a TSM session and running a backup or query unprompted is an essential prerequisite to running automatic scheduled backups.

  6. Once you have set up your encrypted passwords correctly, you should perform a test manual backup, for example:
    tsm> incr sys:etc/test.txt
  7. Further information and syntax on running manual backups and restores of multiple files and volumes can be found at Using the TSM Client Command Line Interface for Backup & Restore. For known problems and limitations of the Tivoli Storage Manager V5.5 NetWare Backup-Archive Client please visit the troubleshooting section. For information on configuring and running automatic scheduled backups see Setting up Automatic Backups.

5. Changing the TSM password

The TSM password can be changed at any time. The initial password, given to you at registration for TSM Backup, should be changed as soon as the TSM client has logged into the TSM server. Thereafter, it should be changed at regular intervals and at least once a year as they expire after this interval. To this end, users are contacted, by mail, at the beginning of the last calendar month before their password expires, advising that the password should be changed.

Passwords should be strong and un-guessable. TSM passwords are case independent. In addition to letters and digits they can contain the characters + - _ . & (plus, minus, underscore, point, ampersand) and must be between 6 and 63 characters long.

To change the TSM password, load the dsmc module and enter:

tsm> set password oldpassword newpassword

Now quit the TSM session, and restart to ensure that the new password has been stored correctly.

6. Troubleshooting and further help

  1. If you have a problem with the TSM client for Netware please first review the complete list of known issues with the TSM Version 5.5 client for Netware.

  2. Backups may fail with an 'out of memory' or 'memory allocation' error. This may be due to the manner in which Netware and the TSAFS manage memory. Further details can be found on the Novell Netware web site in the document: 'Memory Fragmentation Issue with Netware 6.0/6.5 - TID10091980'. Additionally, TSAFS can be limited in the amount of cache memory it requests. To do this, unload the module and re-load it with the following command line switch:

    load TSAFS /CacheMemoryThreshold=1

    This will prompt TSAFS to allocate memory in smaller amounts.

  3. TSM is memory hungry. IBM/Tivoli estimate 150-700 bytes of memory per file when incrementally backing up a volume. Thus a volume of 1 million files will require 150-700MB of virtual memory space. If the host is memory-constrained then this memory requirement can be reduced by setting the option MEMORYEFFICIENTBACKUP YES in the DSM.OPT file. This causes the TSM client to process directories within a volume one at a time. Consequently memory demand will be reduced but backup duration will increase.

  4. TSM struggles with the Unicode enablement introduced into NetWare. This latest client should silently fail to backup files and folders with characters not in the local Code Page and list these in the dsmerror.log file. The only workaround is to rename these files/folders to include only characters in the local Code Page.

  5. The TSM client is unable to backup legitimate files which contain square brackets with four digits inside them, i.e. [1978], on NSS volumes. This is a consequence of Unicode support added to NetWare. If you find such files failing to be backed up, or you know that you have files so named, a workaround to allow the backup of such files is to reload the TSAFS.NLM as below:

    load TSAFS /noConvertUnmappableChars
  6. If the TSM NODENAME or NetWare Server Name are changed, the TSM password encrypted on disk will no longer work. You should remove the file TSM.PWD and restart the TSM client (load DSMC). You will then be prompted for the TSM password which will then be saved again to disk.

  7. If you are unable to login to the TSM server and backup your filestore, ensure in the first instance that you are able to run the queries documented in the sections 4 and 5 of Running the TSM Client for Netware. If these queries fail, delete all .PWD files in the TSM client installation directory and re-run the queries again to re-encrypt the TSM and Netware passwords to disk.

  8. If you use Tivoli Storage Manager client data encryption and have just updated from TSM version 5.3. If you are migrating from Tivoli Storage Manager Version 5.3, the format of the Tivoli Storage Manager password file has changed. Your existing password file will be migrated to the new format during the first session with a Tivoli Storage Manager server after you install the Tivoli Storage Manager Version client. After the password file has been migrated, previous versions of the Tivoli Storage Manager client will not process the updated password file correctly. If you use Tivoli Storage Manager client data encryption and you ever need to go back to an older client version, follow these steps to avoid problems restoring your data with the updated password file and the older client:

    1. Before installing the new version, make a copy of the password file, as advised in the Upgrading section in this document.
    2. After installing the new version, if data encryption is used, you will be prompted for the encryption key password on the first backup after the upgrade, to ensure that the correct encryption key is now used. Therefore run a manual backup first, before enabling scheduled backups (where the key prompt will not be answered).
    3. If you need to go back to an older version, follow these steps:
      1. Uninstall the client.
      2. Restore the saved passwords file.
      3. Install the older version.
  9. In addition to the README.htm file mentioned above, further sources of information and help are listed below:

    • Queries about options in the configuration file DSM.OPT may be answered by the detailed comments at the top of this file.
    • Comprehensive online help on commands and options and error messages s available by typing help at the tsm> prompt.
    • Help with common problems with the TSM client is available from the HFS FAQ pages.
    • If you are unable to find an answer for your query or problem via the resources above, then contact the Help Centre using the Help Request Form with a relevant Subject line, an explanation of the problem and importantly a copy of the files DSM.OPT and DSMERROR.LOG.
  10. Please report any comments on the accuracy, completeness and usefulness of the material above to

Written by IT Services. Latest revision 17 February 2015