Linux operating systems

Installing the Linux on System z client

Edit online

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

Before you begin

  • You must be logged in as root to install the product.
  • If you plan to install the client on the same system as the IBM® Storage Protect 8.1.2 or later server, ensure that you halt the IBM Storage Protect server before you install the client. This action will prevent the client installation process from forcing the system to reboot. After you install the client, you can restart the IBM Storage Protect server.
  • 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 IBM Storage Protect API or backup-archive client.
  • If you are running a version 7.1.2 or earlier client, you must uninstall any language packages before you proceed with the upgrade.
Restriction: FIPS installable packages are not available for the client on Linux on Power® Systems (Little Endian) client. You can install the backup-archive client in non-FIPS mode and then restart the operating system in FIPS mode to use the backup-archive client.

About this task

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

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 IBM Storage Protect 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 IBM Storage Protect server documentation.

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

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

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
TIVsm-WEBGUI.s390x.rpm Provides the files that are required to perform remote client operations by using the web user interface. /opt/tivoli/tsm/tdpvmware

This installation procedure can be used to install new distributions or updates from downloaded installation media. The downloaded 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.

You can download the appropriate package file from one of the following websites:
Before installation, you must first check the GSKit signature of the rpm package as follows:
  1. Download the GSKit public PGP key GSKit.pubn.pgp from the download sites that also contain the client packages, where n represents a number. For now, the value of n is 4.
  2. Import the GSKit public key by issuing the following command:
    rpm --import GSKit.pub4.pgp
  3. Verify the GSKit rpm file by issuing the following command:
    rpm --checksig <GSKit rpm file> --verbose
    where <GSKit rpm file> is the name of a GSKit rpm package that is listed in Table 1 - Package names, contents, and default directory.
You must then check the signature of the client package as follows:
  1. Download the generated gpk key PRD0001289key.pub.asc from the download sites that also contain the client packages.
  2. Import the generated gpk key by issuing the following command:
    rpm --import PRD0001289key.pub.asc
  3. Verify the PGP public key by issuing the following command:
    cat PRD0001289key.pub.asc
-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBGa0+zYBEACv8/upsLxBLwv8SkiUBj1EtKV7slhZg2B7ubVBAeh1XNJh06t6
rkLZsFSBLIDhKjk0GeLfj31tZZxeyydGorUORqocfB6XooNgFk9ZB/xMKjdI8wzZ
AHJOMqskLIjGmQw1JjWei4nXmKtrb3IktP2MqGRM6L/thoaJbIDtMPto73eNL4hp
wL8VzFV0Qtgvj/cbTxQn/zmZW6yPLrH0/9xpKNXkJAvHnfxRHEtZ9H0lOCd/XUEk
KPEPpk8ROCvtpi1ZyqKGN12BWmy/byOllIZFggwFhdZF8QPE+1fWsmpPTlvdH9ip
HBoRCh2KAe5lnBgpOytQVGv48CqiYY9Yzq9WYM4aV9I1JMGoY/lXWKmRbluMN6Ad
501usqw9qACnH3K63AIFlomPYzMLt4OnPZiJ+p9Hm5UpeTPpjbQcKyVenAPtH8Er
dlov8nNOjFGbxucIemdxo6JmZ7lnHL/wjTVsb2s3/EDoyj8NvtfElD4wARf60MK6
+LqZifv5xZunDSMbGEeKwnH7ob6/xa09SDozt3DFymAisNwEGt1mL8NHInhN+zXM
HFDvIryMLzqrzYm7GYedS7PnoORrUp0ZuQdy6Y89PwhhpVFVW1+1IwPeP8bjQobJ
jdsbY2IHr+DFTp6RnilmJ8nrUH+4ORN7jPaTvB6iFgN+jHrudTRhjDWeMQARAQAB
tC5JQk0gU3BlY3RydW0gUHJvdGVjdCBDbGllbnQgPHBzaXJ0QHVzLmlibS5jb20+
iQI6BBMBCAAkBQJmtPs2AhsPBQsJCAcCBhUKCQgLAgQWAgMBAh4BBQkAAAAAAAoJ
EM5xG7blgVejJxcQAKz/xjvlRZ8KBq6vjHiQZDpd35Z9m5Em7AcubicAyHu1mPbB
y+ES7dhXo6YI9wGZhhYw9f578bkszZE7Yn46xMLzB8k1r1tfgQ7iCKAVqMi/jGl7
wBa/4P6h6YrIGPOlIft8HjEqAGf6RNCSkHJ7rOaDbEAeBM35rlXENXup/zgEm7c5
fYVA7WVr3C29GDhqiEuXdphEHElZfWz8vbvW++m0SedjOpUzLL7HZ0TXncUuxedr
iiFcJzVpMDmTlyaj2YKJRbgHrSNA2KN8VO3aU4IYeJ28tEyvz8P610V4Gqq/aU1U
fIPnGqf+3+j+/DxIBeLGlFako6QI2cuyY08sqV3iu35/TThgkiLo0wpP0NaoP/Ea
7qp8Se+Yu6KiuJ+0zeF4J5x8NzxqbKmZArr0ogiwyZJHBgclwjUrZflV/EnzPmW4
xJrzS3FTCLmsoxKaoiDyFP9GsQxHlz+mDeih4wO1uU8I5rb2eegZP9I4MQaHoAaC
qhVb0Df5hVV+skr4PYfWOFXHL5v2c5JGVENy1sHYL0oMoz2dxVPJhRVQs0GzyBlx
WpdItyx415QUqJWDHifqBzb0qOiZq5iGl0ERu0D59S3oDmstnKeCX4msAxuuOvGX
kg04zJIz6ifkfzcGoSnWq9Pbos5QsNnDNYG7+y0QsbnX4hO8vXBwCWgW4Z3q
=7qT0
-----END PGP PUBLIC KEY BLOCK-----
  4. Verify the client package by issuing the following command:
    rpm -K <client_package>.rpm
    where <client_package> is the name of an rpm package that is listed in Table 1 - Package names, contents, and default directory.

Procedure

  1. Mount the volume that you are installing from.
  2. Change to the directory where the packages are stored.
  3. Install the 64-bit GSKit packages. In this example, the "8.x.x.x" characters represent the GSKit version: 
    rpm -U gskcrypt64-8.x.x.x.linux.s390x.rpm gskssl64-8.x.x.x.linux.s390x.rpm
  4. Install the IBM Storage Protect 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
    Tip: If you are upgrading the API and the Common Inventory Technology package was previously installed, you must upgrade both the API and Common Inventory Technology packages. For example, you can run the following command:
    rpm -U TIVsm-API64.s390x.rpm 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, you must compile and install the filepath component that matches the Linux kernel on your client computer. 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").

    Occasionally, build problems can occur due to the dynamic nature of the Linux kernel. If the source does not build correctly on your Linux distribution, contact IBM Software Support to request the latest source file. Include the version of the Linux distribution and the output of the uname -a command along with the version of the IBM Storage Protect client that you are installing.

  7. Provides the files that are required to perform remote client operations by using the web user interface. 
    rpm -ivh TIVsm-WEBGUI.s390x.rpm