Just beware of one side effect when you do the delete and redefine on
drives/paths/library. (Which you DO need to do, as John Schneider has
correctly said below.) Any libvols which you had reserved for TSM not to
use by setting status=private even though they are not also defined as
volumes, will lose their "last use" information. This can cause subtle
failures of any carefully crafted SELECT commands you might have that
examine the lastuse. This initially horrified me that I was going to let
TSM reuse tapes that I didn't want it to, but after I figured out what
was going on I realized it was a harmless effect. (Whew!)
Just beware that this will happen, so it won't panic you when it does.
Roger Deschner University of Illinois at Chicago rogerd AT uic DOT edu
== You are making progress when every mistake you make is a new one. ===
On Fri, 28 Sep 2007, Schneider, John wrote:
>Chip,
> I hope I am not proven ignorant in this case, but I don't think
>there is a way to update the slot count without deleting the
>drives/path/library, and then redefining them. The reason is that when
>the library path is first defined is when TSM queries the library device
>and receives back a list of the element numbers of the library. There
>is an element number assigned to each slot, tape drive, and I/O slot.
>TSM uses the element numbers from the resulting list to know what
>instructions it can give the library robot. I am not aware of a way to
>update that list on the fly.
> The good news is you don't have to reboot the TSM instance to do
>this, just quiet down all the tape drives so nothing is using the drives
>or library, then delete it and recreate it.
> If you haven't already done this, now would be a good time to
>trap all the commands used to delete and redefine the library from the
>activity log, and put them in a macro or text file for reuse in the
>future. It can save you a lot of typing the next time you have upgrade
>the library.
>
>Best Regards,
>
>John D. Schneider
>Sr. System Administrator - Storage
>Sisters of Mercy Health System
>3637 South Geyer Road
>St. Louis, MO. 63127
>Email: schnjd AT stlo.mercy DOT net
>Office: 314-364-3150, Cell: 314-486-2359
>
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
>Bell, Charles (Chip)
>Sent: Friday, September 28, 2007 2:39 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: [ADSM-L] Library slot count manipulation in TSM
>
>
>How does TSM know how many slots are available, say, from the output of
>the 'show slots' command below? I have a Sepaton VTL, and I would like
>to expand the slot count from the Sepaton side from 400 to 1000. What
>could I do from the TSM side to see the 1000 slots and not have to
>delete drives/paths/library definitions for the library (3584_vtl1)
>shown below? Reboot the TSM server? Perhaps just an audit library? It
>would great to not even have to reboot the TSM server, but we can if
>necessary. It's less of a pain than rebuilding the library environment
>from the TSM side.
>
>
>
>tsm: TSM>show slots 3584_vtl1
>
>PVR slot information for library 3584_VTL1.
>
>Library : 3584_VTL1
>
>Product Id : 03584L32
>
>Support module : 4
>
>Mount count : 1
>
>Drives : 16
>
>Slots : 400
>
>Changers : 1
>
>Import/Exports : 32
>
>
>
>God bless you!!!
>
>Chip Bell
>Network Engineer I
>IBM Tivoli Certified Deployment Professional
>Baptist Health System
>Birmingham, AL
>
>
>
>
>
>
>
>
>-----------------------------------------
>Confidentiality Notice:
>The information contained in this email message is privileged and
>confidential information and intended only for the use of the individual
>or entity named in the address. If you are not the intended recipient,
>you are hereby notified that any dissemination, distribution, or copying
>of this information is strictly prohibited. If you received this
>information in error, please notify the sender and delete this
>information from your computer and retain no copies of any of this
>information.
>
|
