IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

Chapter 3. Client enhancements 57

3.9 HSM for GPFS on Linux86

Figure 3-14 HSM for GPFS on Linux86

Now there is not only one dsmmigfstab file in /etc/adsm/SpaceMan/config for all file systems,

but one for each file system in </fs>/.SpaceMan. The old one remains unchanged.

In addition, the failover mechanism has been improved in the area of eliminating single points

of failures. HSM failover information is now stored in the GPFS repository. And - dsmls has

been improved in regard to memory consumption when traversing deep file structures.

Installing the HSM client

Enter the following command to install the HSM client.

rpm -i TIVsm-HSM.i386.rpm

This command installs the command line and the IBM Tivoli Enterprise™ Space

Management Console.

Note: The Tivoli Storage Manager application programming interface (API) and

backup-archive packages are prerequisites of the HSM client package and must be

installed prior to the HSM GPFS package.

ibm.com/redbooks

International Technical Support Organization

45

© 2005 IBM Corporation

IBM ITSO – International Technical Support Organization

Client enhancements

•HSM for General Parallel File System (GPFS) on

Linux86

–HSM for Linux86 is one client of the Tivoli Storage Manager

HSM GPFS family.

• The Linux86 client is a port that is based on the AIX version with the

same functionality and same features.

• The real difference is based on the packaging which is done with

Red Hat Package Manager (RPM) for the supported Linux86

platforms.

–It offers a simplified installation.

–HSM cluster installations are certified on IBM Linux Cluster

1350. See

Linux Clustering with CSM and GPFS, SG24-6601.

–See the README file for the exact system requirements.

58 IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

Simplified installation

For an initial installation, perform the following the steps in the order shown.

1. Install Tivoli SpaceManager on each HSM node.

2. Define your Tivoli Storage Manager server and Tivoli Storage Manager client configuration

in dsm.sys and dsm.opt.

3. Restart the HSM daemons using dsmmigfs restart.

4. After the installation, make sure that the dsmrecalld daemon is up on at least one node.

5. Unmount all GPFS file systems on all nodes within the GPFS nodeset, that will be HSM

managed.

6. Activate DMAPI management for these GPFS file systems:

mmchfs <device> -z yes

7. Remount all GPFS file systems on all nodes within the GPFS nodeset.

8. On the HSM session nodes, add HSM management to all desired GPFS file systems

(dsmmigfs add <fs>). The installation process creates the following HSM-specific files for

each GPFS node set and stores them in the GPFS internal repository:

– DSMNodeset

– DSMSDRVersion

It also starts the space management daemons.

For an upgrade from Tivoli SpaceManager 5.2.x, perform the following steps:

1. Ensure that all HSM nodes (session and backup) are in a consistent state and that all

HSM-managed file systems are mounted on all HSM nodes.

2. Globally deactivate HSM on every node using:

dsmmigfs globaldeactivate

3. Disable failover on every node using:

dsmmigfs disablefailover

4. To know which node is a session node for which file system, save the output of the

following command on one node.

dsmmigfs q -f'

5. Remove the Tivoli SpaceManager from all nodes following the instruction in the README

file.

6. Install Tivoli SpaceManager on all nodes as explained earlier.

7. Globally reactivate HSM on every node using this command:

dsmmigfs globalreactivate

8. Enable failover on every node using the command:

dsmmigfs enablefailover

9. Take over each file system on its session node as it is known in step 4.

To start, stop, or restart daemons (for example to let them update the configuration set in

dsm.opt and dsm.sys), perform the following command, specifying the correct start, stop, or

restart function:

dsmmigfs start/stop/restart

Note: The daemons are started with the same environment as dsmwatchd, meaning that

dsm.opt and dsm.sys in the default installation path /opt/tivoli/tsm/client/ba/bin are used.