IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual, Page: 587 / 828

Chapter 16. Leveraging SAN environments
557
Depending on the platform and Storage Agent configuration, you may use
different communication methods between the client and the Storage Agent, as
follows:
򐂰
TCP/IP
򐂰
Shared memory
򐂰
Named pipes
Our Storage Agent is configured for TCP/IP communication only. If you want to
use other methods, you must enable them in the Storage Agent configuration file,
dsmsta.opt.
We added the following options to our client options file, dsm.opt, on the Storage
Agent, DIOMEDE. See Example 16-27.
Example 16-27 Client customization for LAN-free
ENABLELANFREE YES
LANFREECOMMMETHOD TCPIP
LANFREETCPSERVERADDRESS diomede.itsosj.sanjose.ibm.com
LANFREETCPPORT 1502
These options specify that the client will use the Storage Agent to access
SAN-attached devices when the path is available during backup, restore,
archive, and retrieve processing.
With TCP/IP as a configured communication method, a client can use a Storage
Agent that is running on a different machine as well. Data traffic will be via LAN
from the client to the Storage Agent and via SAN from the Storage Agent to the
final storage device.
As well as the necessary communication parameters, you may need to bind
client data to a LAN-free capable management class. Use an
include
statement
in the client options file, as follows:
INCLUDE c:\console\...\* LANFREE
Note: For Data Protection clients, such as Data Protection for SQL, you must
ensure that the API client is installed on the same machine as the Data
Protection module. Then add the options specified in Example 16-27 to the
API client options file, referenced to by the DSM_CONFIG system variable, to
enable the LAN-free path.
For detailed prerequisites for using LAN-free with API clients, see the IBM
Tivoli Storage Manager for SAN Storage Agent User’s Guide for your platform.