IBM provides a list with the latest TSM/SP client versions and the supported Linux versions for them (see FAQ "Client-Versions" and "supporteted Linux-distributions", respectively).
This guide mentions specific paths to TSM/SP-Client packages. Experience shows that IBM occasionally withdraws published versions leading to dead links. The latest version is 8.1.24.0.
If in doubt check starting at the base path:
Look for the latest version
of deb packages at:
of rpm packages at:
Remark:
https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/
hosts the initial maintenance-releases of the clients, not fixes added later on.
The installation is achieved by installing the RPM packages:
mkdir /tmp/TSM/ cd /tmp/TSM wget https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/v8r1/Linux/LinuxX86/BA/v8124/8.1.24.0-TIV-TSMBAC-LinuxX86.tar tar xf 8.1.24.0-TIV-TSMBAC-LinuxX86.tar dnf install -y ./gskcrypt64-*.linux.x86_64.rpm ./gskssl64-*.linux.x86_64.rpm dnf install ./TIVsm-API64.x86_64.rpm TIVsm-BA.x86_64.rpm
Important: first install the gsk* packages, then the TIVsm-API64* and finally install the actual TIVsm-BA* client.
analogous to RHEL
mkdir /tmp/TSM cd /tmp/TSM wget https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/v8r1/Linux/LinuxX86_DEB/BA/v8124/8.1.24.0-TIV-TSMBAC-LinuxX86_DEB.tar tar xf 8.1.24.0-TIV-TSMBAC-LinuxX86_DEB.tar dpkg -i gskcrypt64_*.linux.x86_64.deb gskssl64_*.linux.x86_64.deb dpkg -i tivsm-api64.amd64.deb dpkg -i tivsm-ba.amd64.deb
Important: first install the gsk* packages, then the TIVsm-API64* and finally install the actual TIVsm-BA* client.
Please note FAQ regarding the error message /opt/tivoli/tsm/client/ba/bin/dsmcad: error while loading shared libraries: libgpfs.so: wrong ELF class: ELFCLASS32, die beim Update einer alten TSM-Version auf ISP 7.1.3 oder neuer auftritt!
Remark regarding Ubuntu 20.04 and TSM-clients newer than 8.1.x
In Ubuntu versions from 20.04 onwards, not all libs are linked correctly. A solution is provided by adding an entry in the /etc/ld.so.conf.d/:
echo "/usr/local/ibm/gsk8_64/lib64" >> /etc/ld.so.conf.d/tsm.conf /sbin/ldconfig
In order to backup locale-specific characters - e.g. german umlauts - locales with representations of these characters have to be installed. In Ubuntu this can be achieved by running
dpkg-reconfigure locales
and picking the necessary locales form the list. In any case, you have to select en_US to prevent dsmc returning a ANS4042E for file paths with special characters. For proper support of German umlaut characters also de_DE.UTF-8 UTF-8 should to be picked. en_US.UTF-8 UTF-8 is optional but reccomended as well.
Refer to Arch User Repository and the comments regarding the package.
The TSM packages provided for RedHat Enterprise Linux (RHEL) can be used in the same way for the corresponding versions of CentOS and Scientific Linux.
The TSM packages provided for Ubuntu can be used in the same way for Debian.
Hinweis zu Debian und TSM-Clients neuer 8.1.x
in Debian-Versionen ab 12 bzw. Bookworm not all libs are linked correctly. A solution is provided by adding an entry in the /etc/ld.so.conf.d/:
echo "/usr/local/ibm/gsk8_64/lib64" >> /etc/ld.so.conf.d/tsm.conf /sbin/ldconfig
The TSM GUI is implemented in Java. In order to use it, you may need to install the necessary Java packages.
Remark: The TSM UI works with OpenJDK only - not with IBM Java oder Oracle Java!
Check for installed OpenJDK:
$ dnf list installed |grep openjdk java-21-openjdk.x86_64 1:21.0.3.0.9-1.el9 @appstream java-21-openjdk-headless.x86_64 1:21.0.3.0.9-1.el9 @appstream
if not, install:
$ dnf install java-21-openjdk java-21-openjdk-headless
Check for installed OpenJDK:
$ dpkg -l | grep jdk ii openjdk-17-jre:amd64 17.0.10+7-1~20.04.1 amd64 OpenJDK Java runtime, using Hotspot JIT ii openjdk-17-jre-headless:amd64 17.0.10+7-1~20.04.1 amd64 OpenJDK Java runtime, using Hotspot JIT (headless)
if not, install:
$ apt-get install openjdk-17-jre
An upgrade of the TSM/ISP client is usually done by installing the new client. Removing the old one is not necessary. Deleting the old directory will result in the loss of the configuration settings!
However, it is important to restart the TSM scheduler or the dsmcad service/daemon, as this is part of the installation package.