1. Yet their device support website (http://www.tivoli.com/support/storage_mgr/devices/all.html) lists the element matrix for Gator, where slot 1 is element 1, but TSM actually sees it as 1 + 29, or 30. And drive 1 is supposed to be 646, but TSM sees it as 646 + 29, or 675. Again, despite their own matrix, TSM seems to have added 29 to the element addresses they list.
2. The reason I do "move data" is to consolidate the data that is offsite. So, if I have a volume offsite that is "under-utilized" (let's say only 22% utilized), then I would want to check that tape in, and do a "move data" onto a pool-copy "filling" tape. But it won't let me do a "move data" unless the tapes associated with that one are also in the library. 3. Yes, as I mentioned, it's most likely a SpectraLogic issue. Just wanted to see if other folks were having similar issues. johnn On Friday, November 2, 2001, at 05:04 PM, George Lesho wrote: > 1.,The element numbers below 31 are associated with bulk load, I/O port > and > other functions on my IBM 3575L32 Magstar tape library. Not Tivoli's > fault > or responsibility how the element numbers are mapped. > 2. I let TSM worry about where it sticks the data on the tapes > 3. Speak to your library vendor and ask them why their device driver > microcode doesn't work right. The IBM Magstar doesn't behave this way. > > George Lesho > AFC Enterprises > Storage/System Admin > > > > > > > "Johnn D. Tan" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/02/2001 > 03:47:23 PM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > To: [EMAIL PROTECTED] > cc: (bcc: George Lesho/Partners/AFC) > Fax to: > Subject: TSM annoyances > > > I have a few annoyances with Tivoli -- not many, as it's a great > product, just a handful. > > 1) We have TSM 4.1.3 server connected to SpectraLogic Gator/64000. > Despite what Tivoli says on their website, the element number of Slot 1 > in the library is not 1, but 30! This is very annoying! If I do a "q > libv lib1" and look up a volume's home element, I have to subtract 29 in > order to really know what slot it's in on the library. Can this be > corrected so that it is what Tivoli's website says it should be -- i.e., > element 1 matches slot 1? > > 2) Is there a simple way to find out which volumes are associated to any > other? For instance, let's say I have to do a "move data" on 000115. > Right now, here's what I do: > q content 000115 count=-1 f=d > q content 000115 count=1 f=d > If either one of these has a segment 1/1, then everything's > great, > as there is no associated volume. But if either or both have 1/2 (or > 2/2) then I have to issue: > audit v 000115 > And find the associated volume. The catch is, if there are *two* > associated volumes, you have to check one of them in first and update > its status, before you can do another audit to find the other associated > volume. > Is there any way to find these associated volumes in one swift > command?! > > 3) [I think this is more a SpectraLogic issue, but I'll gripe > anyway ;).] When I want to "bulk load" a bunch of tapes into the Gator > tape library, I have to make sure no tapes are mounted in the drives. > Otherwise, the bulk load will just blindly put the new tapes into the > slots of the tapes in the drive. Doesn't TSM "talk" to the tape library > and tell it the home elements (or slots) of the tapes that are mounted > in the drives, so that the robotic picker won't put tapes into those > slots?? > > Thanks for any advice. > johnn >
