Library hardware upgrade instructions for Tivoli Storage Manager

Resolving The Problem

When a library is physically upgraded, for example, when drives, cells or columns are added to a physical library to expand it, the Tivoli Storage Manager server needs to be notified of these changes.

For Tivoli Storage Manager servers at levels below 6.1.5 and below 6.2.2 and server at 5.5.x levels,
it is necessary to restart the Tivoli Storage Manager server for the changes to be recognized by the server.

Starting with Tivoli Storage Manager servers at 6.1.5 and above, 6.2.2 and above, and 6.3.0.0 and above, rather than restarting the server, the AUDIT LIBRARY command with REFRESHSTATE=YES parameter may be used instead. For example :
audit library TS3500 checklabel=barcode refreshstate=yes

When the Tivoli Storage Manager server is restarted or the audit library command used as per above, the server will access the library. If the library inventory has changed, it will be refreshed at that time. If drives are added or deleted from the library or drive element addresses are changed, this information will be refreshed also. If the library path has changed, then the path needs to be updated with the new device name for the new library path. The same holds true when dealing with a 3584 library with the ALMS feature. This is discussed in the following document :
http://www-1.ibm.com/support/docview.wss?uid=swg21053638
That document will mention that "TSM supports the Advanced Library Management System (ALMS) and Virtual I/O Slots (VIOS) features of IBM 3584. When changing the number of drive, storage, or import/export elements for a logical library, the TSM server must be restarted."

If a restart of the Tivoli Storage Manager server, or audit library fails to recognize the hardware changes, it may be necessary to delete and redefine the library. Use the following commands to obtain the library name, drive names, device names and library inventory :

query library f=d
query drive f=d
query path f=d
query libv f=d

Once the drive names, library name and device involved are obtained from above command, the following commands may used to redefine the library and its inventory. For example, in the case where an LTO library with 2 drives is used and assuming the library is "ltolib" and the drives are "drive0" and "drive1" along with their respective device names of lb1.1.0.3, mt.0.0.3 and mt1.0.0.3, the following commands would be used to delete & redefine the library under Tivoli Storage Manager server :

1, delete path MY_SERVER1 DRIVE0 srct=server destt=drive library=LTOLIB
2. delete path MY_SERVER1 DRIVE1 srct=server destt=drive library=LTOLIB
3. delete drive LTOLIB DRIVE0
4. delete drive LTOLIB DRIVE1
5. delete path MY_SERVER1 LTOLIB srct=server destt=library
6. delete library LTOLIB
7. define library LTOLIB libtype=scsi
8. define path MY_SERVER1 LTOLIB srct=server destt=library devi=lb1.1.0.3
9. define drive LTOLIB DRIVE0
10. define drive LTOLIB DRIVE1
11. def path MY_SERVER1 DRIVE0 srct=server destt=drive library=LTOLIB devi=mt0.0.0.3
12. def path MY_SERVER1 DRIVE1 srct=server destt=drive library=LTOLIB devi=mt1.0.0.3
13. checkin libv LTOLIB search=yes status=cleaner cleanings=xx volrange=xxxxxx,yyyyyyy....optional
14.checkin libv LTOLIB search=yes checklabel=barcode status=scratch
15. checkin libv LTOLIB search=yes checklabel=barcode status=private

Notes :

• In a library client environment, make sure that the correct ownership is assigned to the volumes on the checkin commands. See knowledge item #1170083 for more information.
• If a cleaner tape was checked in, make sure to checkin the cleaner tape in step 13, otherwise skip that step.
• The above procedure also applies to the case where a library becomes physically partitioned or the existing physical partitioning is changed.