General installation prerequisites and considerations

Before installing the space management client on any system, review the general requirements and considerations.

Installation prerequisites

You must install the Tivoli® Storage Manager backup-archive client and you must have authority to install the space management client.

  • You must have root user authority to install, set up, and use the space management client on your workstation.
  • You must install and set up the Tivoli Storage Manager backup-archive client before you install the space management client. Both the space management client and Tivoli Storage Manager backup-archive clients share common code, the same options files, communication protocols, node registration, and storage.

Pre-existing files in the installation directory can be deleted

The /usr/tivoli/tsm/client/hsm/bin directory is one of the base directories into which the space management client product is installed. Any files that you place in this directory might be deleted during installation. Do not place the following files into this directory:
  • dsm.opt files
  • dsm.sys files
  • Include-exclude files
  • User-created files

Installation steps overview

The following steps are an overview of the installation procedure.

  1. Before installing anything, read all of these general requirements. Read your system installation overview, specific environment requirements, and each installation step to ensure that you are ready to install the space management client.
  2. Follow your system-specific installation procedure.
  3. When you complete the installation, register your workstation as a node with the Tivoli Storage Manager server.
  4. Modify the dsm.sys and dsm.opt configuration files. Both files are in the following directory:
    • For AIX®: /usr/tivoli/tsm/client/ba/bin
    • For Linux: /opt/tivoli/tsm/client/ba/bin

Reinstallation or upgrade overview

Before you reinstall the space management client, stop all activity and do not access any files on file systems to which you added space management. The installation process fails otherwise. Follow the upgrade procedure as described for your operating system. If the steps tell you to uninstall and reinstall the backup archive client and API, you must complete those steps. Uninstalling and reinstalling brings those packages to the same level as the space management client.

You must not upgrade with a command like rpm -U. You must not refresh with a command like rpm -F. You must uninstall the old version and then install the new version.

The space management client limitations and considerations

The space management client has limitations.

  • The space management client for AIX GPFS™ systems is not compatible with the backup-archive client for JFS2. Journal-based backup is not supported when the space management client for AIX GPFS systems is installed.
  • The space management client for GPFS systems manages only file systems belonging to the local (home) GPFS cluster; it does not manage remotely mounted file systems.
  • In a GPFS environment, a small file that is less than the size of a GPFS block size can become larger after an HSM migration. GPFS adds meta information to the file during the migration. Because another block on the file system is allocated for the meta information, the space allocated for the file increases. If a file system is filled to its maximum capacity with many small files, it can run out of space during the file migration.
  • On a GPFS cluster with Linux and AIX nodes, install the space management client on Linux nodes only or on AIX nodes only. Do not install the space management client on Linux nodes and AIX nodes that are on the same GPFS cluster.
  • On a GPFS cluster with Windows systems and UNIX systems nodes, you must run backup-archive client processes on the same node that runs HSM processes.
  • The space management client is not supported on JFS2 Encrypted File Systems (EFS).
  • Extended attributes (EAv2) are supported by the space management client. However, if you delete a stub file and use the dsmmigundelete command to re-create the stub file, the extended attributes are not restored.
  • The space management client is not compatible with DMAPI applications that use any of the following DMAPI events on the space managed file system:
    • DM_EVENT_READ
    • DM_EVENT_WRITE
    • DM_EVENT_TRUNCATE
    • DM_EVENT_PREUNMOUNT
    • DM_EVENT_NOSPACE
    • DM_EVENT_DESTROY
    Any DMAPI application on the space managed file system must respond to the DM_EVENT_MOUNT event with DM_RESP_DONTCARE.
Related concepts:
Configuring the space management client
Space requirement for HSM control files
Related information:
Installing the backup-archive clients
Journal-based backup