Upgrade to TSM Client for Linux v7.1 (EZ-Backup)
This article applies to: EZ-Backup
Use these upgrade instructions for the following Linux distros:
- SUSE Linux Enterprise Server (SLES) 11
- Red Hat Enterprise Linux 5, 6, or 7 for Server or Desktop (64-bit)
- Other Linux Distros based on Linux kernel 2.16.x/2.32.x/3/10.x with Limited Support
- Supported File Systems
These instructions assume that anyone administering a Linux system is technically savvy.
These instructions also assume the language used by the client is English and the locale code is either en_US or EN_US.
This procedure requires that the computer is registered with the EZ-Backup service, and has an older version of the TSM client installed. If you do not have an earlier version installed, please use our Install instructions instead of these instructions.
The following instructions are the Cornell condensed version of the IBM/Tivoli process, which is documented in the Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Version 7.1 Installation and User's Guide.
Review the README file for requirements (software and hardware) and limitations (filesystem types supported, known problems) and a list of changes since prior client releases.
Logon to system as root
Stop any TSM client processes running with these commands:
Check for previous install:
/bin/rpm -q -a | grep -i 'TIV'
There should be 2 packages installed: TIVsm-BA and TIVsm-API. On 64-bit systems, there will be a third package: TIVsm-API64. And for some newer TSM clients, there will be a package called TIVsm-BAhdw. These packages must be removed ("erased") in the order shown (see note below as to why "upgrade" is not used):
(All systems) Remove the TIVsm-BAhdw (if present):
/bin/rpm -e TIVsm-BAhdw
(64-bit systems) Remove the backup/archive client:
/bin/rpm -e TIVsm-BA64
(All systems) Remove the backup/archive client:
/bin/rpm -e TIVsm-BA
(64-bit systems) Remove the 64-bit API:
/bin/rpm -e TIVsm-API64
(All systems) Remove the base API:
/bin/rpm -e TIVsm-API
- (All systems) Remove the TIVsm-BAhdw (if present):
Some previous versions of the TSM client (22.214.171.124 for certain; may be others) have an additional package, TIVguid. If it exists, it must also be removed:
/bin/rpm -e TIVguid
Follow the install instructions in the Install the TSM client section of the fresh install instructions.
Follow the instructions in the Configure the GUI (Java) Client section of the fresh install instructions.
Follow the instructions in the Method 1 subsection of the Configure Automated (Scheduled) Backups section of the fresh install instructions.
Notes on Upgrade
Ensure that you install these packages in the given order. This is required because the TSM API package is a prerequisite of the B/A Client package.
The Web Client is an integral part of the Backup-Archive Client package and cannot be installed without it.
Our beta testers discovered that doing an rpm "upgrade" - i.e., "rpm -Uvh" - fails, because a number of shared libraries in /usr/lib end up "missing". Thus the documented method of using "erase" (rpm -e) followed by "install" (rpm -i) as recommended by IBM. This has been reported to IBM, but no fix is anticipated.
The EZ-Backup team is aware that there is an rpm naming convention that IBM choses not to follow (IBM does not include the version number in the rpm packages). The following alternate install instructions (for 32-bit systems only) for the install command listed above have been used by an internal CIT Linux Sys Admin. Be aware that, if you use this method, we will not be able to respond to future documentation or upgrade issues that result. Caveat emptor.
mv /tmp/TIVsm-API.i386.rpm /tmp/TIVsm-API-126.96.36.199.i386.rpm
mv /tmp/TIVsm-BA.i386.rpm /tmp/TIVsm-BA-188.8.131.52.i386.rpm
/bin/rpm -e TIVsm-API TIVsm-BA
/bin/rpm -ivh /tmp/TIVsm-API-184.108.40.206.i386.rpm /tmp/TIVsm-BA-220.127.116.11.i386.rpm
Validate the existing dsm.sys and dsm.opt files. (They are in the TSM home directory, /opt/tivoli/tsm/client/ba/bin/, and should have not been altered by the upgrade in any way). If you were using the VirtualMountPoint option as a workaround to backup EXT3 format filesystems in a previous version of TSM, these are no longer required and should be removed from your dsm.sys file.