![]() |
![]() |
Tivoli Storage Manager uses the capability of the 349X library manager, which allows you to partition libraries that reside on a LAN between multiple Tivoli Storage Manager server applications. Library partitioning differs from library sharing in that there are no Tivoli Storage Manager library managers or clients. Each server has the same access to the library. Each drive that resides in the library is assigned to one server. Each server can then only access those drives it has been assigned. Tape volume categories must also be assigned to each server that has access to the library. As a result, library partitioning does not allow dynamic sharing of drives or tape volumes since they are pre-assigned to different servers using different names and category codes.
In the following example, an IBM 3494 library containing four drives is attached to a Tivoli Storage Manager server system named ASTRO and to another Tivoli Storage Manager server system named JUDY.
You must first set up the 349X library on the server system. This involves the following tasks:
define library 3494lib libtype=3494 privatecategory=400 scratchcategory=600The PRIVATECATEROY and SCRATCHCATEGORY are set differently from the default settings. See Categories in an IBM 349X Automated Library.
define path astro 3494lib srctype=server desttype=library device=/dev/lmcp0
The DEVICE parameter specifies the device special file for the LMCP.
See Defining Libraries and SCSI Libraries. For more information about paths, see Defining Paths.
define drive 3494lib drive1 define drive 3494lib drive2
define path astro drive1 srctype=server desttype=drive library=3494lib device=/dev/rmt0 define path astro drive2 srctype=server desttype=drive library=3494lib device=/dev/rmt1
The DEVICE parameter specifies the device special file for the drive. In this example, each drive is given a Tivoli Storage Manager name that is unique to the device special file. For more about device names, see Determining Device Special File Names. For more information about paths, see Defining Paths.
define devclass 3494_class library=3494lib devtype=3590 format=drive
query library query drive query path query devclass
See Requesting Information About Libraries, Requesting Information about Drives, Requesting Information about a Device Class, and Requesting Information About Paths.
define stgpool 3494_pool 3494_class maxscratch=20
Key choices:
For more information, see Defining or Updating Primary Storage Pools.
define library 3494lib libtype=3494 privatecategory=112 scratchcategory=300The privatecategory and scratchcategory are defined differently that the first server's definition. See Categories in an IBM 349X Automated Library.
define path judy 3494lib srctype=server desttype=library device=/dev/lmcp0
The DEVICE parameter specifies the device special files for the LMCP.
See Defining Libraries and SCSI Libraries. For more information about paths, see Defining Paths.
define drive 3494lib drive3 define drive 3494lib drive4
define path judy drive3 srctype=server desttype=drive library=3494lib device=/dev/rmt2 define path judy drive4 srctype=server desttype=drive library=3494lib device=/dev/rmt3
The DEVICE parameter gives the device special file for the drive. In this example, each drive is given a Tivoli Storage Manager name that is unique to the device special file. For more about device names, see Determining Device Special File Names. For more information about paths, see Defining Paths.
define devclass 3494_class library=3494lib devtype=3590 format=drive
query library query drive query path query devclass
See Requesting Information About Libraries, Requesting Information about Drives, and Requesting Information about a Device Class.
define stgpool 3494_pool 3494_class maxscratch=20
Key choices:
For more information, see Defining or Updating Primary Storage Pools.