Before you begin
Ensure that your systems meet licensing requirements
for library sharing. An
IBM® Tivoli Storage Manager for Storage Area Networks
entitlement is required for each
Tivoli Storage
Manager server that
is configured as a library client or a library manager in a SAN environment.
About this task
With LAN-free data movement,
Tivoli Storage
Manager client systems
can directly access storage devices that are defined to a
Tivoli Storage
Manager server.
Storage agents are installed and configured on the client systems
to perform the data movement. For more information, see
Configuring IBM Tivoli Storage Manager for LAN-free data movement.
To
set up library sharing, you must define one Tivoli Storage
Manager server as
the library manager for your shared library configuration. Then, you
must define additional Tivoli Storage
Manager servers
as library clients that communicate and request storage resources
from the library manager. The library manager server must be at the
same version or a newer version as the server or servers that are
defined as library clients.
The following tasks are required
for Tivoli Storage
Manager servers
to share library resources on a SAN:
- Set up server-to-server communications.
To
share a storage device on a SAN, define servers to each other using
the cross-define function. See Setting up communications among servers for details.
- Define a shared library and set up devices on the server
systems.
Use the procedure that is described in Configuring libraries for use by one server to define a library
for use in the shared environment. Modify the procedure to define
the library as shared, by specifying the SHARED=YES parameter
for the DEFINE LIBRARY command.
- Define the library manager server.
- Define the shared library on the library client server.
- From the library manager server, define paths from the
library client to each drive that the library client can access. The device name must reflect the way that the library client
system recognizes the device. A path from the library manager to each
drive must be defined in order for the library client to use the drive.
It
is best practice for any library-sharing configuration to have all
drive path definitions that are defined for the library manager also defined
for each library client. For example, if the library manager defines
three drives, the library client must also define three drives. If
you want to limit the number of drives that a library client can use
at a time, use the MOUNTLIMIT parameter of the
device class on the library client instead of limiting the drive path
definitions for the library client.
- Define device classes for the shared library.
A
good practice is to make the device class names the same on both servers
to avoid confusion when you define multiple device classes with the
same device type and library parameters. Some operations, such as
database backup, use the device class name to identify the data for
backup.
The
device class parameters that are specified on the library manager
override the parameters that are specified for the library client
whether the device class names are the same on both servers or not. If
the device class names are different, the library manager uses the
parameters that are specified in a device class that matches the device
type that is specified for the library client.
- Define a storage pool for the shared library.
- Repeat the steps to define a library client for additional
library client servers in your configuration.
