Tivoli Header
Administrator's Guide
The following tasks are required to share tape library devices over a
SAN:
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.
- Note:
- Set up each server with a unique name.
Use the following procedure as an example of how to set up a Tivoli Storage
Manager server as a library manager named ASTRO:
- Verify that the Tivoli Storage Manager library manager server is running,
and start it if it is not:
- From the TSM Console, expand the tree for the server instance
you are configuring.
- Expand Reports.
- Click
Service Information in the TSM Console tree in the left
panel. The Service Information window appears in the right
panel.
- Check to see if the Tivoli Storage Manager library manager server is
running. If it is stopped, right click on the server name. A
pop-up menu appears.
- Click Start in the pop-up menu.
- Verify that the Tivoli Storage Manager device driver is running, and start
it if it is not:
- From the TSM Console, expand the tree for the machine you are
configuring.
- Expand Reports.
- Click
Service Information in the TSM Console tree in the left
panel. The Service Information window appears in the right
panel.
- Check to see if the Tivoli Storage Manager device driver is
running. If it is stopped, right click TSM Device
Driver. A pop-up menu appears.
- Click Start in the pop-up menu.
- Obtain the library and drive information for the shared library
device:
- From the TSM Console, expand the tree for the machine you are
configuring.
- Expand TSM Device Driver and Reports.
- Click Device Information. The Device
Information window appears in the right pane.
- Define a library whose library type is SCSI. For
example:
define library sangroup libtype=scsi shared=yes
- Define the path from the server to the library.
define path astro sangroup srctype=server desttype=library
device=lb0.0.0.2
- Define the drives in the library.
define drive sangroup drivea element=1030
define drive sangroup driveb element=1031
- Define the path from the server to each of the drives.
define path astro drivea srctype=server desttype=drive library=sangroup
device=mt0.1.0.2
define path astro driveb srctype=server desttype=drive library=sangroup
device=mt0.2.0.2
- Define at least one device class. Use a low mount retention time
(1-2 minutes) and mount wait time for shared library devices. Set
the mount wait times to different values for each server.
define devclass tape devtype=dlt mountretention=1 mountwait=10
library=sangroup
- Check in the library inventory. The following example checks all
volumes into the library inventory as scratch volumes. The server uses
the name on the bar code label as the volume name.
checkin libvolume sangroup search=yes status=scratch
checklabel=barcode
- Set up a storage pool for the shared library with a maximum of 50 scratch
volumes.
define stgpool backtape tape
description='storage pool for shared sangroup' maxscratch=50
Use the following procedure as an example of how to set up a Tivoli Storage
Manager server named JUDY as a library client. You must define the
library manager server before setting up the library client server.
- Verify that the Tivoli Storage Manager library client server is running,
and start it if it is not:
- From the TSM Console, expand the tree for the server instance
you are configuring.
- Expand Reports.
- Click
Service Information in the TSM Console tree in the left
panel. The Service Information window appears in the right
panel.
- Check to see if the Tivoli Storage Manager library client server is
running. If it is stopped, right click on the server name. A
pop-up menu appears.
- Click Start in the pop-up menu.
- Verify that the Tivoli Storage Manager device driver is running, and start
it if it is not:
- From the TSM Console, expand the tree for the machine you are
configuring.
- Expand Reports.
- Click
Service Information in the TSM Console tree in the left
panel. The Service Information window appears in the right
panel.
- Check to see if the Tivoli Storage Manager device driver is
running. If it is stopped, right click TSM Device
Driver. A pop-up menu appears.
- Click Start in the pop-up menu.
- Obtain the library and drive information for the shared library
device:
- From the TSM Console, expand the tree for the machine you are
configuring.
- Expand TSM Device Driver and Reports.
- Click Device Information. The Device
Information window appears in the right pane.
- Define the shared library, SANGROUP and identify the library
manager.
- Note:
- Ensure that the library name agrees with the library name on the library
manager.
define library sangroup libtype=shared primarylibmanager=astro
- Define the drives to 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 sangroup drivea
define drive sangroup driveb
- Note:
- You do not have to specify all of the drives in the shared library
device.
- Define the paths from the client server to each of the
drives.
define path judy drivea srctype=server desttype=drive library=sangroup
device=mt0.1.0.3
define path judy driveb srctype=server desttype=drive library=sangroup
device=mt0.2.0.3
- Define at least one device class. Use a low mount retention time
(1-2 minutes) and mount wait time for shared library devices. Set
the mount wait times to different values for each server.
define devclass tape devtype=dlt mountretention=1 mountwait=10
library=sangroup
- Define the storage pool, BACKTAPE, that will use the shared
library.
define stgpool backtape tape
description='storage pool for shared sangroup' maxscratch=50
- Repeat this procedure to define additional servers as library
clients.
When the library manager server starts and the storage device initializes,
or after a library manager server is defined to a library client server, the
library client server contacts the library manager server. The library
client server confirms that the contacted server is the library manager for
the named library device. The library client server also compares drive
definitions with the library manager server for consistency. The
library client server contacts the library manager server for each of the
following operations:
- Volume Mount
- A library client server sends a request to the library manager server for
access to a particular volume in the shared library device. For a
scratch volume, the library client server does not specify a volume
name. If the library manager server cannot access the requested volume,
or if scratch volumes are not available, the library manager server denies the
mount request. If the mount is successful, the library manager server
returns the name of the drive where the volume is mounted.
- Volume Release (free to scratch)
- When a library client server no longer needs to access a volume, it
notifies the library manager server that the volume should be returned to
scratch. The library manager server database is updated with the
volume's new owner. The volume is deleted from the volume
inventory of the library client server.
Table 11 shows the interaction between library client servers and the
library manager server in executing Tivoli Storage Manager commands.
Table 11. How SAN-enabled Servers Execute Common Tivoli Storage Manager Commands
Server command
| Library Manager Server
| Library Client Server
|
QUERY LIBVOLUME
| Displays the volumes that are checked into the library. For
private volumes, the owner server is also displayed.
| Not applicable.
|
CHECKIN LIBVOLUME
CHECKOUT LIBVOLUME
| Performs the commands to the library device.
| Not applicable.
When a check-in operation must be performed because of a client restore, a
request is sent to the library manager server.
|
MOVE MEDIA
MOVE DRMEDIA
| Only valid for volumes used by the library manager server.
| Requests that the library manager server perform the operations.
Generates a checkout process on the library manager server.
|
AUDIT LIBRARY
| Performs the inventory synchronization with the library device.
| Performs the inventory synchronization with the library manager
server.
|
LABEL LIBVOLUME
| Performs the labeling and check-in of media.
| Not applicable.
|
DISMOUNT VOLUME
| Sends the request to the library device.
| Requests that the library manager server perform the operation.
|
QUERY VOLUME
| Checks whether the volume is owned by the requesting library client
server and checks whether the volume is in the library device.
| Requests that the library manager server perform the operation.
|
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]