This section describes the tasks involved in configuring the TSM client and server so that the client can, via a storage agent, move its data to storage on a SAN. As part of the configuration, a storage agent is installed on the client system. See TSM Managed System for SAN Storage Agent User's Guide for detailed information on the storage agent. This function is provided by the Managed System for SAN feature.
Note: | TCP/IP is the only protocol currently supported for communications between the storage agent and the TSM server. |
Setting up the client to directly access a storage device over a SAN consists of installing and configuring the storage agent on the TSM client machine and enabling the option for the API to allow the data movement. You also need to set up the TSM device driver. Thereafter, the client communicates with the storage agent, which in turn communicates with the TSM server. For details on these steps, see TSM Managed System for SAN Storage Agent User's Guide.
define library sangroup libtype=scsi device=/dev/0lb shared=yes
define drive sangroup drivea device=/dev/rmt/4mt element=1030 define drive sangroup driveb device=/dev/rmt/5mt element=1031
define devclass santape devtype=3570 mountretention=1 mountwait=10 library=sangroup
Note: | Do not use a device type of GENERICTAPE for drives to be shared on a SAN with clients. |
define stgpool sanpool santape description='SAN storage pool' maxscratch=50
For each client for which you want to enable SAN data transfer, do the following:
define server iris serverpassword=jonquil hladdress=sanclient.tucson.ibm.com lladdress=1500
define drivemapping iris sangroup drivea device=mt5.0.0.1 define drivemapping iris sangroup driveb device=mt5.2.0.1