Tivoli Header
Administrator's Guide
Using a SAN with Tivoli Storage Manager allows the following
functions:
- Multiple Tivoli Storage Manager servers share storage devices.
- Tivoli Storage Manager clients directly access storage devices, both tape
libraries and disk storage, that are defined to a Tivoli Storage Manager
server (LAN-free data movement). See Configuring Tivoli Storage Manager for LAN-free Data Movement.
- Note:
- Tivoli Storage Manager supports library sharing and LAN-free features with
IBM 349X libraries. If you are already using an IBM 349X library with
Tivoli Storage Manager in a non-SAN environment, see Migrating an IBM 349X Library to SAN Support.
The following tasks are required for Tivoli Storage Manager servers to
share library devices over a SAN:
- Set up server-to-server communications.
- Set up the library on the library manager server. In the following
example, the library manager server is named MANAGER.
- Set up the library on the library client server. In the following
example, the library client server is named CLIENT.
See Categories in an IBM 349X Automated Library and Enabling Support for IBM 3590 Drives in Existing 349X Libraries for additional information about
configuring 349X libraries.
Before Tivoli Storage Manager servers can share a storage device over a
SAN, you must set up server communications. This requires configuring
each server for Enterprise Administration and defining the servers to each
other, using the cross-define function. See Setting Up Communications Among Servers for details. For a discussion regarding the
interaction between library clients and the library manager in processing
Tivoli Storage Manager operations, see Performing Operations with Shared Libraries.
You must first set up the device on the server system. This involves
the following tasks:
- Set the 349X Library Manager Control Point (LMCP). This procedure
is described in the IBM SCSI Tape Drive, Medium Changer, and Library
Device Drivers Installation and User's Guide for AIX.
- Physically attach the devices to the server hardware.
- Install and configure the appropriate device drivers for the
devices.
- Determine the device names that are needed to define the devices to Tivoli
Storage Manager.
For details, see Attaching an Automated Library Device and Installing and Configuring Device Drivers.
Use the following procedure as an example of how to set up a Tivoli Storage
Manager server as a library manager named MANAGER:
- Define a 349X library named 3494SAN:
define library 3494san libtype=349x shared=yes
- Define a path from the server to the library:
define path manager 3494san srctype=server desttype=library
device=/dev/lmcp0,/dev/lmcp1
For more information about paths, see Defining Paths.
- Define the drives in the library:
define drive 3494san drivea
define drive 3494san driveb
- Define a path from the server to each drive:
define path manager drivea srctype=server desttype=drive library=3494san
device=/dev/rmt0
define path manager driveb srctype=server desttype=drive library=3494san
device=/dev/rmt1
For more information about paths, see Defining Paths.
- Define at least one device class associated with the shared
library. Set the mount wait times to different values for each
server.
define devclass 3494_class library=3494san devtype=3590 mountretention=2 mountwait=10
- Check in the library inventory. The following shows two
examples. In both cases, the server uses the name on the barcode label
as the volume name.
To check in volumes that are already labeled, use the following
command:
checkin libvolume 3494san search=yes status=scratch checklabel=no
To label and check in the volumes, use the following command:
label libvolume 3494san checkin=scratch search=yes
- Set up a storage pool for the shared library with a maximum of 50 scratch
volumes.
define stgpool 3494_sanpool tape maxscratch=50
Use the following sample procedure for each Tivoli Storage Manager server
that will be a library client server.
- Define the server that is the library manager:
define server manager serverpassword=secret hladdress=9.115.3.45 lladdress=1580
crossdefine=yes
- Define a shared library named 3494SAN, and identify the library
manager:
- Note:
- Ensure that the library name agrees with the library name on the library
manager.
define library 3494san libtype=shared primarylibmanager=manager
- Define the drives in the library by using the same names as the drives on
the library manager. Element addresses are not required for shared
libraries when defining drives on the library client.
define drive 3494san drivea
define drive 3494san driveb
- Note:
- We recommend that you define all the drives in the shared library to both the
library client and library manager servers.
- Define a path from the library client server to each drive:
define path client drivea srctype=server desttype=drive
library=3494san device=/dev/rmt0
define path client driveb srctype=server desttype=drive
library=3494san device=/dev/rmt1
For more information about paths, see Defining Paths.
- Define at least one device class associated with the shared
library. Set the mount wait times to different values for each
server.
define devclass 3494_class library=3494san devtype=3590 mountretention=2 mountwait=15
- Define the storage pool, BACKTAPE, that will use the shared
library.
define stgpool backtape 3494_class maxscratch=50
- Repeat this procedure to define additional servers as library
clients. For a discussion regarding the interaction between library
clients and the library manager in processing Tivoli Storage Manager
operations, see Performing Operations with Shared Libraries.
After you have attached and defined your devices, you can store client data
in two ways:
If you are already using an IBM 349X library with Tivoli Storage Manager in
a non-SAN environment, you will have to perform the following procedure to
migrate and correctly configure the library for a SAN environment. You
must ensure that the 3494SHARED option is disabled in the dsmserv.opt
file:
- Do the following on each server sharing a 3494 library:
- Update the storage pools using the UPDATE STGPOOL command. Set the
value for the HIGHMIG and LOWMIG parameters to 100%.
- Stop the server by issuing the HALT command or accessing the TSM Console
and clicking Stop for the server.
- Edit the dsmserv.opt file:
- Comment out the 3494SHARED YES option line
- Activate the disablescheds yes option line if it is not active
- Activate the expinterval x option line if it is not
active and change the value to 0; expinterval 0
- Start the server.
- Enter the following Tivoli Storage Manager command:
disable sessions
- Set up the library manager on a Tivoli Storage Manager server of your
choosing.
- Do the following on the remaining Tivoli Storage Manager servers:
- Save the volume history file.
- Check out all the volumes in the library inventory. Use the
CHECKOUT LIBVOLUME command with REMOVE=NO.
- Follow the library client setup procedure.
- Do the following on the library manager server:
- Check in each library client's volumes. Use the CHECKIN
LIBVOLUME command with the following parameter settings:
- STATUS=PRIVATE
- OWNER=<library client name>
- Note:
- You can use the saved volume history files from the library clients as a
guide.
- Check in any remaining volumes as scratch volumes. Use the CHECKIN
LIBVOLUME command with STATUS=SCRATCH.
- Halt all the servers.
- Edit the dsmserv.opt file and comment out the disablescheds
yes and expinterval 0 option lines.
- Start the servers.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]