Linux operating systems

Installing the Linux on System z client

You can install the Linux on System z® backup-archive client from the product DVD, or other installation media.

Before you begin

You must be logged in as root to install the product.

About this task

If you have Tivoli® Storage Manager Version 6.2 (or an earlier version) installed, remove it (rpm -e) and any other dependent software programs before you install a newer version.

If you have Tivoli Storage Manager V6.3 (or newer) installed, you can use the rpm upgrade option (rpm -U) or the rpm freshen option (rpm -F) to upgrade the existing software to a newer version. The rpm -U command can be used to install new packages or upgrade existing packages; rpm -F can update only packages that are already installed.

Stop any running client processes before you uninstall or upgrade the Tivoli Storage Manager API or backup-archive client. If you are running a V7.1.2 or earlier client, you must uninstall any language packages before you proceed with the upgrade.

The following installation options are available in uncompressed packages on the DVD.

Table 1. Package names, contents, and default directory
Package Name Contents Default directory

gskcrypt64-8.x.x.x.linux.s390x.rpm
gskssl64-8.x.x.x.linux.s390x.rpm

64-bit Global Security Kit (GSKit) packages /usr/local/ibm/gsk8
TIVsm-API64.s390x.rpm Application programming interface (API), which contains the Tivoli Storage Manager API shared libraries and samples. /opt/tivoli/tsm/client/api/bin64
TIVsm-BA.s390x.rpm Backup-archive client (command-line and GUI), administrative client (dsmadmc), and the web client. /opt/tivoli/tsm/client/ba

This directory is considered to be the default installation directory for many backup-archive client files. The sample system-options file (dsm.sys.smp) is written to this directory. If the DSM_DIR environment variable is not set, the dsmc executable file, the resource files, and the dsm.sys file are stored in this directory.

If DSM_CONFIG is not set, the client user-options file must be in this directory.

If you do not define DSM_LOG, the backup-archive client writes messages to the dsmerror.log and dsmsched.log files in the current working directory.

TIVsm-APIcit.s390x.rpm

TIVsm-BAcit.s390x.rpm

Optional. These files provide the Common Inventory Technology components that you can use to obtain information about the number of client and server devices that are connected to the system, and the utilization of processor value units (PVUs) by server devices. For more information about PVUs, see Estimating processor value units in the Tivoli Storage Manager server documentation.

APIcit is installed in tivoli/tsm/client/api/bin64/cit/

BAcit is installed in tivoli/tsm/client/ba/bin/cit/

TIVsm-filepath-version-linuxOS.s390x.rpm

Where: version indicates the Tivoli Storage Manager version, and linuxOS indicates the Linux operating system that you are installing the filepath component on.

TIVsm-filepath-source.tar.gz

TIVsm-JBB.s390x.rpm

Files needed to support journal-based backups.

Filepath is installed in /opt/filepath

JBB is installed in /opt/tivoli/tsm/client/ba/bin

This installation procedure can be used to install new distributions or updates from a DVD or other media. If you download files from Passport Advantage® or other IBM® website, the files that you use to install the client might be compressed. Depending on the package file format, either copy or extract the files to disk and use these instructions to install the components. Install the packages in the order shown.

Procedure

  1. Mount the volume or DVD that you are installing from.
  2. Change to the directory where the packages are stored. If you are installing from a DVD, change to the /dvd/linux390 directory.
  3. Install the 64-bit GSKit packages. In this example, the "8.x.x.x" characters represent the GSKit version on the DVD:
    rpm -U gskcrypt64-8.x.x.x.linux.s390x.rpm gskssl64-8.x.x.x.linux.s390x.rpm
  4. Install the Tivoli Storage Manager API, and optionally install the Common Inventory Technology package that is needed to support processor value unit (PVU) calculations.
    1. Required: Install the API:
      rpm -i TIVsm-API64.s390x.rpm
    2. Optional: Install the Common Inventory Technology package that is used by the API. This package is dependent on the API so it must be installed after the API package is installed.
      rpm -i TIVsm-APIcit.s390x.rpm

    If you need only the API installed, you can stop here. The rest of the steps in this procedure describe how to install the backup-archive client components and an optional client package that is needed only if you want the client to send PVU metrics to the server. Also described in subsequent steps are the installation of the packages that are needed if you want to perform journal-based backups.

  5. Install the backup-archive client, and optionally install the Common Inventory Technology package that is needed to support processor value unit (PVU) calculations.
    1. Install the backup-archive client components.
      rpm -i TIVsm-BA.s390x.rpm
    2. Optional: Install the Common Inventory Technology package the client uses to send PVU metrics to the server. This package is dependent on the client package so it must be installed after the client package is installed.
      rpm -i TIVsm-BAcit.s390x.rpm
  6. Optional: If you want to use journal-based backups, install the packages that are needed to support the filepath component and journal-based backups. Install the filepath component first and ensure that you install the filepath package that is appropriate for the operating system on the client computer. Specify one of the following package names for the filepath package name.
    • TIVsm-filepath-version-rhel64.s390x.rpm, for Red Hat Enterprise Linux 6.4.
    • TIVsm-filepath-version-rhel70.s390x.rpm, for Red Hat Enterprise Linux 7.0.
    • TIVsm-filepath-version-sles11sp2.s390x.rpm, for SUSE Linux Enterprise Server 11, SP 2.

    Use the ls command to display the names of the filepath packages that are included in this release. Then, use rpm -i filepath_package_name.rpm to install the appropriate filepath package.

    If you are running GPFS™ for Linux on z Systems, you must specify the filepath package name for either Red Hat Enterprise Linux 7.0 or SUSE Linux Enterprise Server 11, SP 2.

    If the filepath packages in the distribution do not apply to your Linux version, you must compile filepath from source code. Extract TIVsm-filepath-source.tar.gz and see the README file for compile and install instructions. The Linux Filepath kernel module is licensed pursuant to the terms of the GNU General Public License ("GPL").