GPFS: Administration and Programming Reference - IRA Home

2. The TSM client code must be installed on each client node specified in the file on the -n ControlFile
option. The lines changed in the dsm.opt and dsm.sys files to enable mmbackup to work with TSM
must be changed in these files on all of the TSM client nodes used by mmbackup. For example, the
dsm.opt file may be:
SErvername k164n06.kgn.ibm.com
The dsm.sys file may be:
SErvername k164n06.kgn.ibm.com
COMMethod TCPip
TCPPort 1500
TCPServeraddress 9.118.95.25
PASSWORDAccess generate
NODEname GPFSnodes
3. The TSM server code and the TSM client code must be at the same level.
4. Storage pools must be configured on the TSM server.
5. The TSM clients must be configured to communicate with the TSM server.
6. TSM must be made aware that the various TSM clients are all working on the same file system, not
different file systems having the same name on different client machines. This is accomplished by
coding the same value for the nodename keyword in the dsm.sys file located in the Tivoli client
directory (/usr/tivoli/tsm/client/ba/bin for AIX, /opt/tivoli/tsm/client/ba/bin for Linux) on each client.
7. Restoration of backed up data must be done using TSM interfaces. This can be done with the client
command line interface or the TSM web client. The TSM web client interface must be made
operational if you desire to use this interface for restoring data to the file system from the TSM server.
Attention: If you are using the TSM Backup Archive client you must use caution when you unlink
filesets that contain data backed up by TSM. TSM tracks files by pathname and does not track filesets.
As a result, when you unlink a fileset, it appears to TSM that you deleted the contents of the fileset.
Therefore, the TSM Backup Archive client inactivates the data on the TSM server which may result in
the loss of backup data during the expiration process.
You can view or download the TSM documentation at the IBM Tivoli Storage Manager Info Center:
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp?toc=/com.ibm.itstorage.doc/toc.xm.
Specifying TSM parameters with the mmbackup command
Control of the backup is accomplished by means of parameters in the control file which is specified using
the -n option on the mmbackup command. The parameters that may be specified in this control file are
the TSM backup server node, the TSM backup client nodes, and the number of backup processes per
client. The backup server node must be specified, as well as at least one backup client node. Specifying
multiple backup client nodes and a larger number of backup processes per client allows for greater
parallelism and performance.
For a discussion of the files created and maintained by the mmbackup command, see section GPFS
backup data in Appendix A. GPFS Architecture of General Parallel File System: Concepts, Planning, and
Installation Guide.
Using APIs to develop backup applications
IBM has supplied a set of subroutines that are useful to create backups or collect information about all
files in a file system. Each subroutine is described in Chapter 9, “GPFS programming interfaces,” on page
277. These subroutines are more efficient for traversing a file system, and provide more features than the
standard POSIX interfaces. These subroutines operate on a snapshot or on the active file system. They
have the ability to return all files, or only files that have changed since some earlier snapshot, which is
useful for incremental backup.
A typical use of these subroutines is the following scenario:
24 GPFS: Administration and Programming Reference