TSM V7.1 : libraries and devices Flashcards
What is the purpose of the “perform libaction” command?
to define or delete all drives and their paths for a single library in one step.
It can be used when you set up a library environment or modify an existing hardware setup that requires changes to many drive definitions. After you define a library, issue PERFORM LIBACTION to define or delete all drives and their paths for the library.
Which prerequisites must be met before “perform libaction” can be used?
- library must be defined of type SCSI or VTL
* SANDISCOVERY option must be supported and enabled (for ACTION=DEFINE to be possible)
what is the purpose of defining a library libtype as “external” ?
When connecting to a StorageTek library in a SAN environment, where the StorageTek library and drives are controlled by ACSLS software (external media mamagement). No drive definition is possible in TSM for such a library.
When must a library be defined of libtype “shared” ?
when you are defining a library that is shared over a SAN with another TSM server. The other TSM server is the library manager and must be have been defined in your local TSM environment with “define server” . Your own TSm server has the role of a library client.
the cmd is (on the library client):
tsm>define library SHARLIB libtype=shared PRIMarylibmanager=TSMLIBHOST
In terms of library/path/drive definition: what is a DATAMOVER?
the source type in case of a NAS device.
Manually defining a SCSI library, paths and drives:
tsm>define library LIBMAN libtype=scsi
tsm>define path SERVERMAN LIBMAN srctype=server desttype=library device=/dev/lb0
tsm>define drive LIBMAN DRIVE01
tsm>define path SERVERMAN DRIVE01 srctyp=server desttype=drive library=LIBMAN device=/dev/mt1
What is the purpose of the path definition?
1) in case of a library?
2) in case of a drive
to connect a source to it’s destination by specifying the corresponding device:
1) the source is a server and the destination is a library (corresponding device eg /dev/lb0
2) the source is a server and the destination is a drive eg /dev/mt1 (or simply “mt1” on Windows)
define a device class …
…