IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual

Page: 582 / 828

552
IBM Tivoli Storage Manager Implementation Guide
In Example 16-20, we define the required paths.
Example 16-20 Storage agent path definition to the shared tape drives
tsm: ATLANTIC>d
efine path sta_diomede dr00 srctype=server desttype=drive \
cont> library=3582_shared device=mt0.0.0.2
ANR1720I A path from STA_DIOMEDE to 3582_SHARED DR00 has been defined.
tsm: ATLANTIC>
define path sta_diomede dr01 srctype=server desttype=drive \
cont> library=3582_shared device=mt1.0.0.2
ANR1720I A path from STA_DIOMEDE to 3582_SHARED DR01 has been defined.
We review our settings using the
query path
command, which reveals all defined
paths, as shown in Example 16-21.
Example 16-21 Defined path summary using query path command
tsm: ATLANTIC>
query path
Source Name Source Type Destination Destination On-Line
Name Type
----------- ----------- ----------- ----------- -------
ATLANTIC SERVER 3582_SHARED LIBRARY Yes
ATLANTIC SERVER DR00 DRIVE Yes
ATLANTIC SERVER DR01 DRIVE Yes
STA_DIOMEDE SERVER DR00 DRIVE Yes
STA_DIOMEDE SERVER DR01 DRIVE Yes
16.4 SAN device discovery support
With Tivoli Storage Manager V5.3 and later, the server and Storage Agent option
sandiscovery, if specified, means that the server will perform SAN discovery
during both server initialization and if the device path has changed.
Essentially, if the SAN device identification has been changed due to SAN
environmental changes, such as device, cabling changes, or bus resets, the
server or Storage Agent will discover these changes during server or Storage
Agent startup or when accessing the paths during operations with the drives and
will perform the necessary changes to the path definition, based on the drive
serial number. Thus, the path will not go offline. Instead, it stays online and
available for the operation.
On Windows platforms this option is set by default. On other platforms enable
SAN discovery using the SANDISCOVERY on option in the server options file