1. Prerequisites for the TSM client for Novell NetWare 6.50
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.
You will need a standard (10Mb or faster) connection to the University Network ( Not Broadband / Cable or Dial-up ).
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:
SYS:/tivoli/tsm/client/ba), save the files
dsm.optto an alternative location.
TSM.PWDto a safe location. Please look at the troubleshooting section for further information on this.
NWCONFIG.NLMmodule to install the previous version of the TSM client (as we will do below), you should use this module to deregister the previous version:
3. Obtaining, installing and configuring the TSM client
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.
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.
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).
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:
Nodenameline to name your client, as registered with the HFS service. This will be of the form MACHINE.DEPT in most cases.
Domainline 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.
Excludedirectives. 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
4. Running the TSM client for Novell NetWare 6.5
load TSAFS load TSANDS
dsmcIf you have copied a saved password file
TSM.PWDinto 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.
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)
tsm> q tsa tsm> q tsa ndsYou 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> quitThen, 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
.PWDfiles, 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.
tsm> incr sys:etc/test.txt
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 newpasswordNow quit the TSM session, and restart to ensure that the new password has been stored correctly.
6. Troubleshooting and further help
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.
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=1This will prompt TSAFS to allocate memory in smaller amounts.
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.
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
The only workaround is to rename these files / folders to include only
characters in the local Code Page.
The TSM client is unable to backup legitimate files which contain square brackets with four digits inside them, i.e. , 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
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
and restart the TSM client (load DSMC). You will then be prompted for the TSM password
which will then be saved again to disk.
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.
In addition to the
README.htm file mentioned above, further sources
of information and help are listed below:
Please report any comments on the accuracy, completeness and usefulness of the material above to email@example.com.