IBM Tivoli Storage Manager for Space Management, Version 7.1

General installation prerequisites and considerations

Before installing the Tivoli® Storage Manager for 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 Tivoli Storage Manager for Space Management client.

You must have root user authority to install, set up, and use the Tivoli Storage Manager for Space Management client on your workstation.
You must install and set up the Tivoli Storage Manager backup-archive client before you install the Tivoli Storage Manager for Space Management client. Both the Tivoli Storage Manager for Space Management client and Tivoli Storage Manager backup-archive clients share common code, the same options files, communication protocols, node registration, and storage.
For more information about the Tivoli Storage Manager backup-archive clients, see the IBM® Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation and User's Guide.

Note: See the IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation and User's Guide for supported languages and locales.

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 Tivoli Storage Manager for 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.

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 Tivoli Storage Manager for Space Management client.
Follow your system-specific installation procedure.
When you complete the installation, register your workstation as a node with a Tivoli Storage Manager server.
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 Tivoli Storage Manager for 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 Tivoli Storage Manager for 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.

Tivoli Storage Manager for Space Management client GUI requirements and considerations

There are requirements for using the Tivoli Storage Manager for Space Management client graphical user interface (GUI).

The space management agent and the Tivoli Storage Manager for Space Management client GUI versions must match, otherwise the authentication with the space management agent is not possible.
The Tivoli Storage Manager node name and password are required to use the Tivoli Storage Manager for Space Management client GUI. The node name and password are the same the Tivoli Storage Manager for Space Management client uses to authenticate with the Tivoli Storage Manager server.
Before you can connect to a Tivoli Storage Manager client node using the Tivoli Storage Manager for Space Management client GUI, that client node must be registered and authenticated with a Tivoli Storage Manager server.
The Tivoli Storage Manager for Space Management client GUI requires the following software:
- The Tivoli Storage Manager API, Tivoli Storage Manager backup-archive client, and Tivoli Storage Manager Tivoli Storage Manager for Space Management client
- The Oracle Java™ Runtime Environment (JRE) version 6.
You can access Internet resources by clicking the Help menu, by clicking the top banner area or by downloading the required version of the JRE.
The PATH environment variable must include the path to the Java executable file. To verify that you have the right JRE installed, issue the java -version command from a UNIX terminal window.
If you do not have the requisite version of the JRE, you must download the required version of the JRE.

Tivoli Storage Manager for Space Management client limitations and considerations

The Tivoli Storage Manager for Space Management client has limitations.

The Tivoli Storage Manager for 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 Tivoli Storage Manager for Space Management client for AIX GPFS systems is installed.
The Tivoli Storage Manager for 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.
The Tivoli Storage Manager for Space Management client is not supported on JFS2 Encrypted File Systems (EFS).
Extended attributes (EAv2) are supported by the Tivoli Storage Manager for 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.

Feedback