
Setting up the library manager server
You must set up the library manager server in order to configure the IBM Storage Protect servers to share SAN-connected devices.
Procedure
The following procedure is an example of how to set up an IBM Storage Protect server that is named ASTRO as a library manager:
-
Ensure that the library manager server is running:
- Start the Windows Services Management Console (services.msc).
-
Select the service. For example,
TSM Server1. - If the service is not running, right-click the service name and click Start.
- Obtain the library and drive
information
for the shared library device:
- Run the
tsmdlst.exeutility. The utility is in the \Program Files\Tivoli\TSM\server directory.
- Run the
- Define a library whose library
type is SCSI. For example:
define library sangroup libtype=scsi shared=yesThis example uses the default for the library's serial number, which is to have the server obtain the serial number from the library itself at the time that the path is defined. Depending on the capabilities of the library, the server might not be able to automatically detect the serial number. In this case, the server does not record a serial number for the device, and is not able to confirm the identity of the device when you define the path or when the server uses the device.
- Define the path from the server to the library.
define path astro sangroup srctype=server desttype=library device=lb0.0.0.2If you did not include the serial number when you defined the library, the server now queries the library to obtain this information. If you did include the serial number when you defined the library, the server verifies what you defined and issues a message if there is a mismatch.
- Define
the drives in the library.
define drive sangroup drivea define drive sangroup drivebThis example uses the default for the drive's serial number, which is to have the server obtain the serial number from the drive itself at the time that the path is defined. Depending on the capabilities of the drive, the server might not be able to automatically detect the serial number. In this case, the server does not record a serial number for the device, and is not able to confirm the identity of the device when you define the path or when the server uses the device.
This example also uses the default for the drive's element address, which is to have the server obtain the element number from the drive itself at the time that the path is defined.
The element address is a number that indicates the physical location of a drive within an automated library. The server needs the element address to connect the physical location of the drive to the drive's SCSI address. You can have the server obtain the element number from the drive itself at the time that the path is defined, or you can specify the element number when you define the drive.
Depending on the capabilities of the library, the server might not be able to automatically detect the element address. In this case, you must supply the element address when you define the drive. Element numbers for many libraries are available at IBM® Support Portal for IBM Storage Protect.
- 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.2If you did not include the serial number or element address when you defined the drive, the server now queries the drive or the library to obtain this information.
- Define at least one device class.
define devclass tape devtype=dlt 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