Tivoli Storage Manager for AIX Administrator's Guide
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.
- Obtain the library and drive information for the SAN library
device.
- Run the SMIT program.
- Select Devices.
- Select Tivoli Storage Manager Devices.
- Select Fibre Channel SAN Attached devices
- Select Discover Devices Supported by TSM. (The discovery
process can take some time.)
- Go back to the Fibre Channel menu, and select List Attributes of a
Discovered Device.
- Note the 3-character identifier for the device, which you will use in
defining the device to TSM. For example, in the list a tape drive has
the identifier, mt2. When defining the drive to TSM, use
/dev/mt2 as the device name. For example:
define drive lib1 drive2 device=/dev/mt2
- Define a library named SANGROUP, using the SHARED=YES parameter.
define library sangroup libtype=scsi device=/dev/lb0 shared=yes
- Define the drives in the library.
define drive sangroup drivea device=/dev/mt4 element=1030
define drive sangroup driveb device=/dev/mt5 element=1031
- Define a device class for the drives.
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 a storage pool, SANPOOL.
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:
- On the server, define the client's storage agent as if it were a
server. The name must match the name specified during storage agent
configuration. For example, if the storage agent's name is IRIS,
issue the following command:
define server iris serverpassword=jonquil
hladdress=sanclient.tucson.ibm.com lladdress=1500
- On the client system, do the following:
- Start the TSM device driver.
- Determine the device name by which the storage agent knows the
device.
For details on these steps, see TSM Managed System for SAN Storage
Agent User's Guide.
- On the server, define drive mapping for every drive that the storage agent
will access, by using the DEFINE DRIVEMAPPING command. For the device
name, specify the device name by which the storage agent knows the
device.
define drivemapping iris sangroup drivea device=mt5.0.0.1
define drivemapping iris sangroup driveb device=mt5.2.0.1
- Set up the policy so that the client uses the new storage pool as the
destination for backup operations. See Configuring Policy for Managed System for SAN for details.
- On the client system, do the following:
- Start the storage agent.
- Start a backup operation to verify that the setup is complete.
For details on these steps, see TSM Managed System for SAN Storage
Agent User's Guide.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]