Re: Equating current 3494 configuration to TS3500
Hi, I am pretty sure it depends on your support contract. Upgrading drive/library firmware is customer resp. Unless stated otherwise. Kind regards, Karel - Oorspronkelijk bericht - Van: Remco Post r.p...@plcs.nl Verzonden: dinsdag 30 april 2013 19:46 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] Equating current 3494 configuration to TS3500 On 30 apr. 2013, at 19:33, Zoltan Forray zfor...@vcu.edu wrote: Sounds like something from the 3-Stooges ;-) No HA here - could barely afford the upgrade. Besides, I though library firmware was IBM's responsibility? My drives are fairly current and will upgrade to the latest, just to be sure. I'm not sure, but you can download the lib firmware from the IBM support site, and my CE's have naver complained that we do it ourself. Welcome to the world of midrange I guess. On Tue, Apr 30, 2013 at 1:28 PM, Remco Post r.p...@plcs.nl wrote: be sure to get the latest firmware... in a HA lib the accessors might collide at full speed when accessing the cap with older versions of the firmware. Yes, that'll give carnage in your lib, pieces of accessors and grippers flying around. On 30 apr. 2013, at 19:14, Zoltan Forray zfor...@vcu.edu wrote: As long as it has good brakes! I remember one tech working on our 3494 with the side panel off. The accessor nearly took his head off Once the stop here switch at the end of the frame broke off and the accessor nearly jumped out At this point with TSM being the sole user, speed is not an issue - reliability is (thus the reason to replace the 3494). On Tue, Apr 30, 2013 at 1:09 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Oh yeah!! Everybody has that reaction. It's zippy. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, April 30, 2013 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picke [Het originele bericht is niet volledig opgenomen]
Re: Equating current 3494 configuration to TS3500
One more question about this. The book isn't very clear about whether a separate fibre cable is needed between the library and our SAN switch for communications. From the book: *The host server attaches to the library by using fiber cables that connect directly to a drive canister or through the library’s patch panel.* Does that mean a separate fibre cable goes to the second connector of the 3592 designated as the control path drive(s)? On Thu, Apr 25, 2013 at 1:22 PM, Richard Rhodes rrho...@firstenergycorp.com wrote: We only have one virt lib defined. You can see the virt CAP slots in a show slots cmd . . . . ImpExp 0, element number 769 ImpExp 1, element number 770 ImpExp 2, element number 771 ImpExp 3, element number 772 ImpExp 4, element number 773 ImpExp 5, element number 774 ImpExp 6, element number 775 ImpExp 7, element number 776 ImpExp 8, element number 777 ImpExp 9, element number 778 ImpExp 10, element number 779 ImpExp 11, element number 780 ImpExp 12, element number 781 ImpExp 13, element number 782 ImpExp 14, element number 783 ImpExp 15, element number 784 I've at times wondered if you have more than one virt lib if the element numbers would be the same for them, or, unique. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 01:04 PM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I have seen similar weirdness and I never could figure it out exactly, either. From watching the web interface, as far as I can tell when you put tapes in the door, the arm moves them into a slot, and those slots are assigned a SCSI slot address that corresponds to an I/O door. When they are checked in by TSM, I don't think the cartridges actually move, they just get assigned new slot numbers that correspond to a storage slot. So I'm not sure when you need physical slots free and when you don't. (I just learned not to put more tapes in the I/O door than there are virtual slots defined, or the checkin won't find them.) Anybody else have rapport with virtual I/O slots? W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 25, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 The virtual I/O slots can be very confusing. One time we filled our library up due to needing as many tape as possible. Every slot was full with either a real tape or cleaning cartridge. Later we tried to eject a tape that was bad. The checkout cmd failed. Long store short - there were no open slots in the library, and this made it so the checkout couldn't move the tape to to the virtual export slot, which would have put the tape in the CAP. I really don't understand this - you would think it could checkout a tape into the CAP door without needing open slots. After we removed a cleaning cartridges (freeing up one slot), the checkout worked correctly. From what we understand, you need as many open slots in the library as you have virtual I/O slots (CAP door slots), or at least for as many tapes you would want to checkout concurrently. At least that's what we think happened, which could very well be wrong! As I said, I've found this confusing. The manuals for the 3584 don't really explain this interaction. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 09:47 AM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search =YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't' know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take
Re: Equating current 3494 configuration to TS3500
No. You can define the control path on any (and all) drives. The 2nd cable is if you want to have path failover configured on the drive. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 30, 2013 10:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 One more question about this. The book isn't very clear about whether a separate fibre cable is needed between the library and our SAN switch for communications. From the book: *The host server attaches to the library by using fiber cables that connect directly to a drive canister or through the library's patch panel.* Does that mean a separate fibre cable goes to the second connector of the 3592 designated as the control path drive(s)? On Thu, Apr 25, 2013 at 1:22 PM, Richard Rhodes rrho...@firstenergycorp.com wrote: We only have one virt lib defined. You can see the virt CAP slots in a show slots cmd . . . . ImpExp 0, element number 769 ImpExp 1, element number 770 ImpExp 2, element number 771 ImpExp 3, element number 772 ImpExp 4, element number 773 ImpExp 5, element number 774 ImpExp 6, element number 775 ImpExp 7, element number 776 ImpExp 8, element number 777 ImpExp 9, element number 778 ImpExp 10, element number 779 ImpExp 11, element number 780 ImpExp 12, element number 781 ImpExp 13, element number 782 ImpExp 14, element number 783 ImpExp 15, element number 784 I've at times wondered if you have more than one virt lib if the element numbers would be the same for them, or, unique. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 01:04 PM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I have seen similar weirdness and I never could figure it out exactly, either. From watching the web interface, as far as I can tell when you put tapes in the door, the arm moves them into a slot, and those slots are assigned a SCSI slot address that corresponds to an I/O door. When they are checked in by TSM, I don't think the cartridges actually move, they just get assigned new slot numbers that correspond to a storage slot. So I'm not sure when you need physical slots free and when you don't. (I just learned not to put more tapes in the I/O door than there are virtual slots defined, or the checkin won't find them.) Anybody else have rapport with virtual I/O slots? W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 25, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 The virtual I/O slots can be very confusing. One time we filled our library up due to needing as many tape as possible. Every slot was full with either a real tape or cleaning cartridge. Later we tried to eject a tape that was bad. The checkout cmd failed. Long store short - there were no open slots in the library, and this made it so the checkout couldn't move the tape to to the virtual export slot, which would have put the tape in the CAP. I really don't understand this - you would think it could checkout a tape into the CAP door without needing open slots. After we removed a cleaning cartridges (freeing up one slot), the checkout worked correctly. From what we understand, you need as many open slots in the library as you have virtual I/O slots (CAP door slots), or at least for as many tapes you would want to checkout concurrently. At least that's what we think happened, which could very well be wrong! As I said, I've found this confusing. The manuals for the 3584 don't really explain this interaction. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 09:47 AM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search =YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't' know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management
Re: Equating current 3494 configuration to TS3500
That is what I understood from previous emails but wanted to make sure but someone here keeps insisting there should be another cable just for the library. As for internally, how does the library talk to the drives/canisters? In the 3494, it used RS422 cables from the drive cages/frames to the RTIC cards. My understanding is there is a fibre patch-panel in each D-frame to which you connect 2m cables to the drives and then I guess to connect the fibre cables from the SAN switch to this same patch-panel? I really wish I had the maintenance manual for the 3584! On Tue, Apr 30, 2013 at 10:06 AM, Prather, Wanda wanda.prat...@icfi.comwrote: No. You can define the control path on any (and all) drives. The 2nd cable is if you want to have path failover configured on the drive. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 30, 2013 10:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 One more question about this. The book isn't very clear about whether a separate fibre cable is needed between the library and our SAN switch for communications. From the book: *The host server attaches to the library by using fiber cables that connect directly to a drive canister or through the library's patch panel.* Does that mean a separate fibre cable goes to the second connector of the 3592 designated as the control path drive(s)? On Thu, Apr 25, 2013 at 1:22 PM, Richard Rhodes rrho...@firstenergycorp.com wrote: We only have one virt lib defined. You can see the virt CAP slots in a show slots cmd . . . . ImpExp 0, element number 769 ImpExp 1, element number 770 ImpExp 2, element number 771 ImpExp 3, element number 772 ImpExp 4, element number 773 ImpExp 5, element number 774 ImpExp 6, element number 775 ImpExp 7, element number 776 ImpExp 8, element number 777 ImpExp 9, element number 778 ImpExp 10, element number 779 ImpExp 11, element number 780 ImpExp 12, element number 781 ImpExp 13, element number 782 ImpExp 14, element number 783 ImpExp 15, element number 784 I've at times wondered if you have more than one virt lib if the element numbers would be the same for them, or, unique. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 01:04 PM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I have seen similar weirdness and I never could figure it out exactly, either. From watching the web interface, as far as I can tell when you put tapes in the door, the arm moves them into a slot, and those slots are assigned a SCSI slot address that corresponds to an I/O door. When they are checked in by TSM, I don't think the cartridges actually move, they just get assigned new slot numbers that correspond to a storage slot. So I'm not sure when you need physical slots free and when you don't. (I just learned not to put more tapes in the I/O door than there are virtual slots defined, or the checkin won't find them.) Anybody else have rapport with virtual I/O slots? W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 25, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 The virtual I/O slots can be very confusing. One time we filled our library up due to needing as many tape as possible. Every slot was full with either a real tape or cleaning cartridge. Later we tried to eject a tape that was bad. The checkout cmd failed. Long store short - there were no open slots in the library, and this made it so the checkout couldn't move the tape to to the virtual export slot, which would have put the tape in the CAP. I really don't understand this - you would think it could checkout a tape into the CAP door without needing open slots. After we removed a cleaning cartridges (freeing up one slot), the checkout worked correctly. From what we understand, you need as many open slots in the library as you have virtual I/O slots (CAP door slots), or at least for as many tapes you would want to checkout concurrently. At least that's what we think happened, which could very well be wrong! As I said, I've found this confusing. The manuals for the 3584 don't really explain this interaction. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 09:47 AM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot
Re: Re: Equating current 3494 configuration to TS3500
The only non-drive external cables to the library would be Ethernet for access to the web interface and either an analog phone line for the call-home modem or a second Ethernet for the TS3000 if you have one. (We missed the phone line requirement at first, so we had to scramble to get those in.) Internally, each drive has a couple power connections and one or two RS422 or similar connections to a library node card, plus one or two fibre connections (newer LTO and 3592 support dual connections) to the patch panel (just a piece of sheet metal to snap in LC-LC couplers). IBM will be responsible for connections from the back of the patch, and you will be responsible for external connections to the patch. With multiple drive frames, you will also have connections from one frame to the next to connect up the node cards. I believe they are daisy-chained, so any given frame would only have one cross-frame cable going each direction. (Mine are both 2-frame libraries, but the second is an S24, aka HD frame, so there is no node card in use.) =Dave Zoltan Forray wrote: That is what I understood from previous emails but wanted to make sure but someone here keeps insisting there should be another cable just for the library. As for internally, how does the library talk to the drives/canisters? In the 3494, it used RS422 cables from the drive cages/frames to the RTIC cards. My understanding is there is a fibre patch-panel in each D-frame to which you connect 2m cables to the drives and then I guess to connect the fibre cables from the SAN switch to this same patch-panel? I really wish I had the maintenance manual for the 3584! On Tue, Apr 30, 2013 at 10:06 AM, Prather, Wanda wanda.prat...@icfi.comwrote: No. You can define the control path on any (and all) drives. The 2nd cable is if you want to have path failover configured on the drive. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 30, 2013 10:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 One more question about this. The book isn't very clear about whether a separate fibre cable is needed between the library and our SAN switch for communications. From the book: *The host server attaches to the library by using fiber cables that connect directly to a drive canister or through the library's patch panel.* Does that mean a separate fibre cable goes to the second connector of the 3592 designated as the control path drive(s)? [...trimming the rest...] -- Hello World.David Bronder - Systems Architect Segmentation Fault ITS-EI, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. david-bron...@uiowa.edu
Re: Re: Equating current 3494 configuration to TS3500
Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. On Tue, Apr 30, 2013 at 11:03 AM, David Bronder david-bron...@uiowa.eduwrote: The only non-drive external cables to the library would be Ethernet for access to the web interface and either an analog phone line for the call-home modem or a second Ethernet for the TS3000 if you have one. (We missed the phone line requirement at first, so we had to scramble to get those in.) Internally, each drive has a couple power connections and one or two RS422 or similar connections to a library node card, plus one or two fibre connections (newer LTO and 3592 support dual connections) to the patch panel (just a piece of sheet metal to snap in LC-LC couplers). IBM will be responsible for connections from the back of the patch, and you will be responsible for external connections to the patch. With multiple drive frames, you will also have connections from one frame to the next to connect up the node cards. I believe they are daisy-chained, so any given frame would only have one cross-frame cable going each direction. (Mine are both 2-frame libraries, but the second is an S24, aka HD frame, so there is no node card in use.) =Dave Zoltan Forray wrote: That is what I understood from previous emails but wanted to make sure but someone here keeps insisting there should be another cable just for the library. As for internally, how does the library talk to the drives/canisters? In the 3494, it used RS422 cables from the drive cages/frames to the RTIC cards. My understanding is there is a fibre patch-panel in each D-frame to which you connect 2m cables to the drives and then I guess to connect the fibre cables from the SAN switch to this same patch-panel? I really wish I had the maintenance manual for the 3584! On Tue, Apr 30, 2013 at 10:06 AM, Prather, Wanda wanda.prat...@icfi.com wrote: No. You can define the control path on any (and all) drives. The 2nd cable is if you want to have path failover configured on the drive. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 30, 2013 10:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 One more question about this. The book isn't very clear about whether a separate fibre cable is needed between the library and our SAN switch for communications. From the book: *The host server attaches to the library by using fiber cables that connect directly to a drive canister or through the library's patch panel.* Does that mean a separate fibre cable goes to the second connector of the 3592 designated as the control path drive(s)? [...trimming the rest...] -- Hello World.David Bronder - Systems Architect Segmentation Fault ITS-EI, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. david-bron...@uiowa.edu -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
That is what I understood from previous emails but wanted to make sure but someone here keeps insisting there should be another cable just for the library. Our libraries have one fiber cable per tape drive, and two lan cables. The lan cables are for the specialist web interface. One lan cable plugs into the lan port in the first frame. The other plugs into the lan port of a node card in one of the other frames that has drives. You can assign IP numbers to these lan ports via the front panel. As for internally, how does the library talk to the drives/canisters? In the 3494, it used RS422 cables from the drive cages/frames to the RTIC cards. I don't know if it's RS422, but the 3584 is similar. It has a internal bus connects to the drives with the controllers. This allows you to power cycle a drive, load microcode, etc. My understanding is there is a fibre patch-panel in each D-frame to which you connect 2m cables to the drives and then I guess to connect the fibre cables from the SAN switch to this same patch-panel? Exactly. Each drive has two fibre ports. Both ports have cables to a patch panel at the bottom of a frame. You connect from the patch panel to your switch. I really wish I had the maintenance manual for the 3584! If you haven't already, download these manuals: TS3500 Introduction and Planning Guide. (lots of gory details) Redbook: IBM TotalStorage Tape Libraries Guide for Open Systems The full maintenance manual comes with the library. IBm has it stashed in the back of one of the frames. So it's probably in the boxes from IBM . . . go hunting! - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Equating current 3494 configuration to TS3500
Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Equating current 3494 configuration to TS3500
Thanks for the response. The library hasn't arrived (scheduled for 05/15) so I don't have access to any books other than what is on the web. Yes I have scoured the I P Guide. I had heard numbers like ~60-seconds to scan/inventory a frame? On Tue, Apr 30, 2013 at 11:57 AM, Richard Rhodes rrho...@firstenergycorp.com wrote: Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
Oh yeah!! Everybody has that reaction. It's zippy. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, April 30, 2013 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Equating current 3494 configuration to TS3500
As long as it has good brakes! I remember one tech working on our 3494 with the side panel off. The accessor nearly took his head off Once the stop here switch at the end of the frame broke off and the accessor nearly jumped out At this point with TSM being the sole user, speed is not an issue - reliability is (thus the reason to replace the 3494). On Tue, Apr 30, 2013 at 1:09 PM, Prather, Wanda wanda.prat...@icfi.comwrote: Oh yeah!! Everybody has that reaction. It's zippy. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, April 30, 2013 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
be sure to get the latest firmware... in a HA lib the accessors might collide at full speed when accessing the cap with older versions of the firmware. Yes, that'll give carnage in your lib, pieces of accessors and grippers flying around. On 30 apr. 2013, at 19:14, Zoltan Forray zfor...@vcu.edu wrote: As long as it has good brakes! I remember one tech working on our 3494 with the side panel off. The accessor nearly took his head off Once the stop here switch at the end of the frame broke off and the accessor nearly jumped out At this point with TSM being the sole user, speed is not an issue - reliability is (thus the reason to replace the 3494). On Tue, Apr 30, 2013 at 1:09 PM, Prather, Wanda wanda.prat...@icfi.comwrote: Oh yeah!! Everybody has that reaction. It's zippy. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, April 30, 2013 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: Equating current 3494 configuration to TS3500
Sounds like something from the 3-Stooges ;-) No HA here - could barely afford the upgrade. Besides, I though library firmware was IBM's responsibility? My drives are fairly current and will upgrade to the latest, just to be sure. On Tue, Apr 30, 2013 at 1:28 PM, Remco Post r.p...@plcs.nl wrote: be sure to get the latest firmware... in a HA lib the accessors might collide at full speed when accessing the cap with older versions of the firmware. Yes, that'll give carnage in your lib, pieces of accessors and grippers flying around. On 30 apr. 2013, at 19:14, Zoltan Forray zfor...@vcu.edu wrote: As long as it has good brakes! I remember one tech working on our 3494 with the side panel off. The accessor nearly took his head off Once the stop here switch at the end of the frame broke off and the accessor nearly jumped out At this point with TSM being the sole user, speed is not an issue - reliability is (thus the reason to replace the 3494). On Tue, Apr 30, 2013 at 1:09 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Oh yeah!! Everybody has that reaction. It's zippy. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, April 30, 2013 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622 -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
On 30 apr. 2013, at 19:33, Zoltan Forray zfor...@vcu.edu wrote: Sounds like something from the 3-Stooges ;-) No HA here - could barely afford the upgrade. Besides, I though library firmware was IBM's responsibility? My drives are fairly current and will upgrade to the latest, just to be sure. I'm not sure, but you can download the lib firmware from the IBM support site, and my CE's have naver complained that we do it ourself. Welcome to the world of midrange I guess. On Tue, Apr 30, 2013 at 1:28 PM, Remco Post r.p...@plcs.nl wrote: be sure to get the latest firmware... in a HA lib the accessors might collide at full speed when accessing the cap with older versions of the firmware. Yes, that'll give carnage in your lib, pieces of accessors and grippers flying around. On 30 apr. 2013, at 19:14, Zoltan Forray zfor...@vcu.edu wrote: As long as it has good brakes! I remember one tech working on our 3494 with the side panel off. The accessor nearly took his head off Once the stop here switch at the end of the frame broke off and the accessor nearly jumped out At this point with TSM being the sole user, speed is not an issue - reliability is (thus the reason to replace the 3494). On Tue, Apr 30, 2013 at 1:09 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Oh yeah!! Everybody has that reaction. It's zippy. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, April 30, 2013 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for the details. So, there really isn't that big of a difference from the 3494 to the 3584 other than the lack of an internal PC/LM and a redesigned, mostly plastic picker/gripper mechanism. The first time you stand at one end and watch the robot come toward you, you will probably jump! It's quite a bit faster than the 3494. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622 -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html -- Met vriendelijke groeten/Kind Regards, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: Equating current 3494 configuration to TS3500
be sure to get the latest firmware... in a HA lib the accessors might collide at full speed when accessing the cap with older versions of the firmware. Yes, that'll give carnage in your lib, pieces of accessors and grippers flying around. That's a good catch! Make sure IBM installs the latest microcode for both the library and drives. - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Equating current 3494 configuration to TS3500
No HA here - could barely afford the upgrade. Besides, I though library firmware was IBM's responsibility? My drives are fairly current and will upgrade to the latest, just to be sure. You can upgrade the library and drive firmware yourself. For the library, you download the file from IBM to your pc. Then through the web gui, you run library firmware upgrade. It's a simple procedure where you point to the firmware file, and it upgrade the library. Takes about 1hr. The library is offline during this process. For Drives, you download the latest firmware file to your pc. Then through the GUI you tell it to upgrade drives. You can upgrade all drives at once, or individually one at a time. THere are a couple options for how to install/activate the code. The easiest way is to tell the library to load, then activate it when the next time the drive is empty. At that point the library power cycles the drive. This works for all except the drives that are defined for control paths. Those you need to powercycle yourself at some point. You can certainly have IBM do it, but sometimes it's just easier yourself. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Equating current 3494 configuration to TS3500
Slight tangent, Wanda's volume location comment spurred this: We upgraded our SCSI 3584 offsite lib to ALMS, no problems...but the onsite ALMS install went horribly wrong...(maint windows are rare, we did several things). Afterwards the lib couldn't reliably find a particular tape with both (robot) hands. Some days it could find some vols, other days those had slid out and it would forget others -- and not just a few, but 60 to 100 of them (10-25% of the lib)!...NO extraordinary measures (like emptying frames and re-inserting) resolved the problem. Our OEM maintenance could not find the problem and shrugged and walked off after a couple of months, intimating it was OUR problem and would not bring in IBM. A lot of time was spent looking through all 3 frames for a particular volume that was needed; reclamation couldn't find volumes either. We took outages, powered down the lib...lib and server...the problem persisted. It was ugly, VERY ugly. Oddly, no regular pub (TSM books, IBM hardware/operator manuals, device manuals or stuff online) told you where the *hardware* stores the volume locations...I stumbled on an obscure 4-5 page blurb from a tape plant engineer with that magic sentence: the volume physical location information is stored in the robot's node cards!! That was the key! We resolved the problem by killing it deadpowered it down (nicely), pulled the physical power, then pulled the (?9V?) battery from the robot to clear the CMOS, waited awhile for all memory to die, and powered everything back up. Of course it was a blithering idiot...all upgrades were lost. (We were delayed a bit because of the upgrade keys -- the lib was shipped with the capacity expansion feature but the plant didn't put a code sticker in the lib or on any documents...after confirming a key was required, I finally found a nice guy in Mexico who could still generate the code!). Does ALMS change the node cards' function? I suspect not but don't know for sure. For some reason I haven't screwed up the courage to reinstall ALMS, but may do so -- we recently went back to IBM maintenance.:) - Susie - The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search=YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take cartridge from slot 1024, load in drive position 6). That's why the checkin commands are different.
Re: Equating current 3494 configuration to TS3500
We had a ugly incident with both of our 3584 libraries. Symptom: The robot picker was getting stuck. When it tried to grab a tape from a slot or put a tape into a drive (or put a tape back into a slot), it would get stuck with the tape partially in the slot/drive and the robot picker. This pinned the robot so it couldn't move. IBM replaced multiple picker assemblies. After a replacement it would work for a while, then start having the problems again, and would get progressively worse. We were getting multiple events per day! The library error log showed many more errors than just then ones that caused the robot to hang. These other errors it was able to recover from. Long story short . . . As tapes were inserted removed from and inserted into cells, the cells were creating a dust which was causing ware on the picker. This is a known issue with some plastic cells from a certain date/time of manufacture. IBM replaced all the plastic cells in the library. Yup . . .on an outage IBM opened up the the frames, removed all the tapes, removed the plastic cells, installed new cells, put the tapes back in. When done we inventoried the library and all was good. Rick From: Stout, Susie (NIH/CIT) [E] sto...@mail.nih.gov To: ADSM-L@VM.MARIST.EDU Date: 04/26/2013 10:00 AM Subject:Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Slight tangent, Wanda's volume location comment spurred this: We upgraded our SCSI 3584 offsite lib to ALMS, no problems...but the onsite ALMS install went horribly wrong...(maint windows are rare, we did several things). Afterwards the lib couldn't reliably find a particular tape with both (robot) hands. Some days it could find some vols, other days those had slid out and it would forget others -- and not just a few, but 60 to 100 of them (10-25% of the lib)!...NO extraordinary measures (like emptying frames and re-inserting) resolved the problem. Our OEM maintenance could not find the problem and shrugged and walked off after a couple of months, intimating it was OUR problem and would not bring in IBM. A lot of time was spent looking through all 3 frames for a particular volume that was needed; reclamation couldn't find volumes either. We took outages, powered down the lib...lib and server...the problem persisted. It was ugly, VERY ugly. Oddly, no regular pub (TSM books, IBM hardware/operator manuals, device manuals or stuff online) told you where the *hardware* stores the volume locations...I stumbled on an obscure 4-5 page blurb from a tape plant engineer with that magic sentence: the volume physical location information is stored in the robot's node cards!! That was the key! We resolved the problem by killing it deadpowered it down (nicely), pulled the physical power, then pulled the (?9V?) battery from the robot to clear the CMOS, waited awhile for all memory to die, and powered everything back up. Of course it was a blithering idiot...all upgrades were lost. (We were delayed a bit because of the upgrade keys -- the lib was shipped with the capacity expansion feature but the plant didn't put a code sticker in the lib or on any documents...after confirming a key was required, I finally found a nice guy in Mexico who could still generate the code!). Does ALMS change the node cards' function? I suspect not but don't know for sure. For some reason I haven't screwed up the courage to reinstall ALMS, but may do so -- we recently went back to IBM maintenance.:) - Susie - The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search=YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take cartridge from slot 1024, load in drive position 6). That's why the checkin commands are different. - The information contained in this message
Re: Equating current 3494 configuration to TS3500
Again thank you for this additional useful piece of information. But now this brings up another issue/question. If I am limited to no more than 255 unassigned tapes, how do I do a mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494? - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html On Apr 24, 2013 10:34 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.edu wrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
Hello Zoltan, When you have that many tapes to input into the library, you can simply open the door and manually insert the tapes. You would need to run the tape library audit to index the tape locations. You can then proceed to the checkin process from the TSM servers. Based on some of my experiences, you can use the I/O Slots and insert 32 tapes at a time, and the library will fill up the Max Virtual I/O slots. It will keep on grabbing media inserted. The catch is when you do a checkin on TSM, it will only checkin the value set for Max Virtual, you can keep re-running the checkin command until all the media has been checked in. I'm assuming from the library manager you would be doing something like checkin libv 3584lib search=bulk checkl=barcode status=Private waitt=0 You can set the MAX VIO slots to 255, the Library will keep this many slots empty in order to accommodate the movement of tapes, either from inputting them, or with the DRM process when sending them offsite. In our environment the balance that works for us is set to set VIO to 150. This ensures that when I run the DRM command I have enough slots free to eject and move all media, and not have the process waiting for someone to remove tapes. You would need to fine tune this depending on the library capacity available empty slots. With a max Capacity of 970, I have 150 set for VIO. This leaves me 820 data slots. Don't forget about the cleaning tapes as well. There is one gotcha you don't want to get yourself into which is inputting tapes as you are ejecting them. I was reading a tech note where you if you are ejecting 150 tapes, decide to load scratch tapes as your unloading where it would end up not having room to place media in VIO or eject media since now the I/O slot door is locked with media waiting to be inputted. I've found that when I was tweaking the VIO limits, I would re-audit the library and re-audit from within the TSM library and each client. -Nick On Thu, Apr 25, 2013 at 4:37 AM, Zoltan Forray zfor...@vcu.edu wrote: Again thank you for this additional useful piece of information. But now this brings up another issue/question. If I am limited to no more than 255 unassigned tapes, how do I do a mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494? - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html On Apr 24, 2013 10:34 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.edu wrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better
Re: Equating current 3494 configuration to TS3500
Ya, I had to look it up too/ ;-) -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dave Canan Sent: Wednesday, April 24, 2013 9:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 And now I've learned what BTDTGTTS stands for. My education for the day. Thanks Wanda. Dave Canan From: Prather, Wanda Sent: 4/24/2013 7:35 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.eduwrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit https://urldefense.proofpoint.com/v1/url?u=http://infosecurity.vcu.edu/phishing.htmlk=Kv4nkNfjdxVgeJz6Pg57qw%3D%3D%0Ar=I1HLMFJ6m%2BiVcavWgCBtVd78uShy4GoDLiStkJAJ6wk%3D%0Am=AiH2kRI9yYLM%2BektHw2fkSiQ1UuURQIXQyXaIFTJr%2BE%3D%0As=b7415ce3fe751e58530dc30b979c98e20ef94d90b16cef231719994c91f9b973 -- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Blue Cross of Idaho, 3000 E. Pine Ave, Meridian, ID 83642 -- This Message Was Secured With The BCI PPS Email System
Re: Equating current 3494 configuration to TS3500
The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search =YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't' know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take cartridge from slot 1024, load in drive position 6). That's why the checkin commands are different. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, April 25, 2013 4:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Again thank you for this additional useful piece of information. But now this brings up another issue/question. If I am limited to no more than 255 unassigned tapes, how do I do a mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494? - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html On Apr 24, 2013 10:34 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.edu wrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal
Re: Equating current 3494 configuration to TS3500
The virtual I/O slots can be very confusing. One time we filled our library up due to needing as many tape as possible. Every slot was full with either a real tape or cleaning cartridge. Later we tried to eject a tape that was bad. The checkout cmd failed. Long store short - there were no open slots in the library, and this made it so the checkout couldn't move the tape to to the virtual export slot, which would have put the tape in the CAP. I really don't understand this - you would think it could checkout a tape into the CAP door without needing open slots. After we removed a cleaning cartridges (freeing up one slot), the checkout worked correctly. From what we understand, you need as many open slots in the library as you have virtual I/O slots (CAP door slots), or at least for as many tapes you would want to checkout concurrently. At least that's what we think happened, which could very well be wrong! As I said, I've found this confusing. The manuals for the 3584 don't really explain this interaction. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 09:47 AM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search =YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't' know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take cartridge from slot 1024, load in drive position 6). That's why the checkin commands are different. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, April 25, 2013 4:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Again thank you for this additional useful piece of information. But now this brings up another issue/question. If I am limited to no more than 255 unassigned tapes, how do I do a mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494? - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html On Apr 24, 2013 10:34 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much
Re: Equating current 3494 configuration to TS3500
I have seen similar weirdness and I never could figure it out exactly, either. From watching the web interface, as far as I can tell when you put tapes in the door, the arm moves them into a slot, and those slots are assigned a SCSI slot address that corresponds to an I/O door. When they are checked in by TSM, I don't think the cartridges actually move, they just get assigned new slot numbers that correspond to a storage slot. So I'm not sure when you need physical slots free and when you don't. (I just learned not to put more tapes in the I/O door than there are virtual slots defined, or the checkin won't find them.) Anybody else have rapport with virtual I/O slots? W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 25, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 The virtual I/O slots can be very confusing. One time we filled our library up due to needing as many tape as possible. Every slot was full with either a real tape or cleaning cartridge. Later we tried to eject a tape that was bad. The checkout cmd failed. Long store short - there were no open slots in the library, and this made it so the checkout couldn't move the tape to to the virtual export slot, which would have put the tape in the CAP. I really don't understand this - you would think it could checkout a tape into the CAP door without needing open slots. After we removed a cleaning cartridges (freeing up one slot), the checkout worked correctly. From what we understand, you need as many open slots in the library as you have virtual I/O slots (CAP door slots), or at least for as many tapes you would want to checkout concurrently. At least that's what we think happened, which could very well be wrong! As I said, I've found this confusing. The manuals for the 3584 don't really explain this interaction. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 09:47 AM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search =YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't' know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take cartridge from slot 1024, load in drive position 6). That's why the checkin commands are different. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, April 25, 2013 4:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Again thank you for this additional useful piece of information. But now this brings up another issue/question. If I am limited to no more than 255 unassigned tapes, how do I do a mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494? - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html On Apr 24, 2013 10:34 PM, Prather, Wanda wanda.prat...@icfi.com wrote: Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door
Re: Equating current 3494 configuration to TS3500
We only have one virt lib defined. You can see the virt CAP slots in a show slots cmd . . . . ImpExp 0, element number 769 ImpExp 1, element number 770 ImpExp 2, element number 771 ImpExp 3, element number 772 ImpExp 4, element number 773 ImpExp 5, element number 774 ImpExp 6, element number 775 ImpExp 7, element number 776 ImpExp 8, element number 777 ImpExp 9, element number 778 ImpExp 10, element number 779 ImpExp 11, element number 780 ImpExp 12, element number 781 ImpExp 13, element number 782 ImpExp 14, element number 783 ImpExp 15, element number 784 I've at times wondered if you have more than one virt lib if the element numbers would be the same for them, or, unique. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 01:04 PM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I have seen similar weirdness and I never could figure it out exactly, either. From watching the web interface, as far as I can tell when you put tapes in the door, the arm moves them into a slot, and those slots are assigned a SCSI slot address that corresponds to an I/O door. When they are checked in by TSM, I don't think the cartridges actually move, they just get assigned new slot numbers that correspond to a storage slot. So I'm not sure when you need physical slots free and when you don't. (I just learned not to put more tapes in the I/O door than there are virtual slots defined, or the checkin won't find them.) Anybody else have rapport with virtual I/O slots? W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 25, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 The virtual I/O slots can be very confusing. One time we filled our library up due to needing as many tape as possible. Every slot was full with either a real tape or cleaning cartridge. Later we tried to eject a tape that was bad. The checkout cmd failed. Long store short - there were no open slots in the library, and this made it so the checkout couldn't move the tape to to the virtual export slot, which would have put the tape in the CAP. I really don't understand this - you would think it could checkout a tape into the CAP door without needing open slots. After we removed a cleaning cartridges (freeing up one slot), the checkout worked correctly. From what we understand, you need as many open slots in the library as you have virtual I/O slots (CAP door slots), or at least for as many tapes you would want to checkout concurrently. At least that's what we think happened, which could very well be wrong! As I said, I've found this confusing. The manuals for the 3584 don't really explain this interaction. Rick From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@VM.MARIST.EDU Date: 04/25/2013 09:47 AM Subject:Re: Equating current 3494 configuration to TS3500 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU The virtual I/O slots only get involved when you put cartridges in through the 16/32 slot physical I/O door. For the initial library load, just open the BIG doors and put the tapes directly into the slots yourself. Then for a SCSI library, the syntax for CHECKIN is slightly different than for your 3494. checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0 volrange=TS1000,TS1999 checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0 Search =YES tells TSM to checkin from the INSIDE library slots. Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a virtual I/O door, but TSM doesn't' know that.) FWIW: For the 3494, TSM just tells the 3494 what it wants done, and doesn't know or care where in the library tapes are located. All the inventory management is done outboard by the 3494. If TSM tells the 3494 to mount a cartridge, he doesn't need to know where the cartridge is, that's handled by the 3494 For a SCSI library, including the TS3500 doing business as a 3584, TSM has to figure out what tapes are in what slots at checkin time, and saves the slot numbers in devconfig so he can send the appropriate commands for cartridge movement. (e.g., take cartridge from slot 1024, load in drive position 6). That's why the checkin commands are different. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, April 25, 2013 4:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Again thank you for this additional useful piece of information. But now this brings up another issue/question. If I am limited to no more than 255 unassigned tapes, how do I do a mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494
Re: Equating current 3494 configuration to TS3500
Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University
Re: Equating current 3494 configuration to TS3500
Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.eduwrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500 - drive sharing
Hi Zoltan You can share drives between your logical libraries in the TS3500 when you have ALMS. Doing this might give you more flexibility in your drive assignments. I am doing a similar 3494 to TS3500 migration at the moment. The person who sized the TS3500 did it by TB and not by slots so I can't fit all my old TS1120 JA-E05 format tapes into the new library, which has TS1140s and is writing JC-E07 format, but they want to get the old library off the floor asap. Fortunately there is enough floor space that the two can co-exist for a while. In the new library I have two logical libraries A and B. There are 12 TS1140 drives. A has 6 dedicated drives and 5 shared. B has 1 dedicated drive and 5 shared. Control paths cannot be shared. At the moment all new data is being written to the A library and it has 11 drives in use. The B library is not in use, but is defined. There is a library manager in this mix but I won't detail that as it adds nothing to the argument here. The 5 shared drives have paths defined in library A and library B, the device names used in these paths are the same but obviously the complete paths are different eg - this is on AIX def path server1 f1d7 srct=server destt=drive library=libA device=/dev/rmt74 online=yes def path server1 f1d7 srct=server destt=drive library=libB device=/dev/rmt74 online=no. When they make me retire the 3494 I will move its remaining tapes into libraryb, and vary on enough of the shared paths on server1/library b as necessary to support the workload, while varying them off to server1/library a. As the workload drops off I will vary on/off so that more drives are available to lib a and fewer to lib b. Caveats 1. So far this is set up and lib A access works, but I have not tried lib B 2. It is possible that this could work with drives varied on to both libraries simultaneously, and the sharing controlled by SCSI reserve/release, but I already have this shared with a library manager, I don't like SCSI reserves and I'm not willing to try hardware level sharing. Hope this helps Steve Steven Harris TSM Admin Canberra Australia On 25/04/2013 4:39 AM, Zoltan Forray wrote: Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.eduwrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.eduwrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
And now I've learned what BTDTGTTS stands for. My education for the day. Thanks Wanda. Dave Canan From: Prather, Wanda Sent: 4/24/2013 7:35 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thank you both for the kind words; I think it's just a matter of surviving long enough to have all the battle scars - BTDTGTTS. In the interest of completeness, here's one other thing that is different from the 3494: When you create your logical libraries, modify the maximum VIO cartridges setting. I believe the default is still 16. AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O door, and it will keep filing them away with an INSERT category code. In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and the library puts them into the virtual I/O door of the appropriate library partition. But if you put more through the physical door than the library has virtual I/O slots (before you do a checkin and clear the virtual I/O slots), weirdness will ensue. Your checkin will not see the extra cartridges. I don't' know of any reason not to set the maximum VIO cartridges to the max setting, which I think is 255. Somebody else might have a better idea if there is a downside to that. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Wednesday, April 24, 2013 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 Thanks for all the responses - it has been immensely educational and I have much less trepidation about the upcoming unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss my 3494 - been using it since 1995! I agree that Wanda has some of the best documentation/experiences with TSM, et-al - she should be writing for IBM/Redbooks! On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K warbo...@indiana.eduwrote: Zoltan, The Web Specialist can be used with an https interface, and a physical console to the 3584 is available. I have little experience with the physical console, but you could determine whether it has the features and suits your needs better than the Web Specialist. Wanda just wrote the Red Book on setting up a 3584. It's more complete, easier to comprehend and better organized than anything you will find in the official documentation. With best wishes to all, Keith Arbogast Indiana University -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Equating current 3494 configuration to TS3500
As you are aware from previous posts, we are replacing our 3494 with a TS3500/3584. I am trying wrap my mind around the proper way to configure the TS3500 so it functions the same way our 3494 does. If changing our current configuration makes things easier for the transition, now would be the time to do it since the install is tentatively scheduled for May. This is our current config: We have 2-TSM servers acting at Library Managers/Owner, thus each LM has its own 3494 category codes, each owns n-3592 drives, etc. This was done for redundancy, fail-over, etc. We have tape drives spinning most of the time so having all library functionality and drives attached to only 1-TSM server is not a good idea. From the server perspective, there is one control path to the library via the IP address/connection. In the 3494, each Library Manager is defined, via the servers IP address. Do I define 2-virtual libraries, 1-per library manager server? Does this mean the drives as well as storage cells are defined/associated to each virtual library? From reading through the various TS3500 books, they cite multiple ways to configure Library Sharing, including virtual stuff since we are getting the ALMS feature. Since I have never dealt with the issue of a tape drive path being used for library control path/function, I guess I need to define more than one of these paths, in case the drive has a problem? Thoughts? Suggestions? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
When you say in your 3494 that each owns n-3592 drives: Do your current TSM servers share the drives, or do you use it as if it is 2 separate physical libraries? Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 23, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Equating current 3494 configuration to TS3500 As you are aware from previous posts, we are replacing our 3494 with a TS3500/3584. I am trying wrap my mind around the proper way to configure the TS3500 so it functions the same way our 3494 does. If changing our current configuration makes things easier for the transition, now would be the time to do it since the install is tentatively scheduled for May. This is our current config: We have 2-TSM servers acting at Library Managers/Owner, thus each LM has its own 3494 category codes, each owns n-3592 drives, etc. This was done for redundancy, fail-over, etc. We have tape drives spinning most of the time so having all library functionality and drives attached to only 1-TSM server is not a good idea. From the server perspective, there is one control path to the library via the IP address/connection. In the 3494, each Library Manager is defined, via the servers IP address. Do I define 2-virtual libraries, 1-per library manager server? Does this mean the drives as well as storage cells are defined/associated to each virtual library? From reading through the various TS3500 books, they cite multiple ways to configure Library Sharing, including virtual stuff since we are getting the ALMS feature. Since I have never dealt with the issue of a tape drive path being used for library control path/function, I guess I need to define more than one of these paths, in case the drive has a problem? Thoughts? Suggestions? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
2-libraries with fixed drives. One library has 9 drives the other one has 8. - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html When you say in your 3494 that each owns n-3592 drives: Do your current TSM servers share the drives, or do you use it as if it is 2 separate physical libraries? Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 23, 2013 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Equating current 3494 configuration to TS3500 As you are aware from previous posts, we are replacing our 3494 with a TS3500/3584. I am trying wrap my mind around the proper way to configure the TS3500 so it functions the same way our 3494 does. If changing our current configuration makes things easier for the transition, now would be the time to do it since the install is tentatively scheduled for May. This is our current config: We have 2-TSM servers acting at Library Managers/Owner, thus each LM has its own 3494 category codes, each owns n-3592 drives, etc. This was done for redundancy, fail-over, etc. We have tape drives spinning most of the time so having all library functionality and drives attached to only 1-TSM server is not a good idea. From the server perspective, there is one control path to the library via the IP address/connection. In the 3494, each Library Manager is defined, via the servers IP address. Do I define 2-virtual libraries, 1-per library manager server? Does this mean the drives as well as storage cells are defined/associated to each virtual library? From reading through the various TS3500 books, they cite multiple ways to configure Library Sharing, including virtual stuff since we are getting the ALMS feature. Since I have never dealt with the issue of a tape drive path being used for library control path/function, I guess I need to define more than one of these paths, in case the drive has a problem? Thoughts? Suggestions? -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
We have 2-TSM servers acting at Library Managers/Owner, thus each LM has its own 3494 category codes, each owns n-3592 drives, etc. This was done for redundancy, fail-over, etc. We have tape drives spinning most of the time so having all library functionality and drives attached to only 1-TSM server is not a good idea. Here is our config. It may not answer your direct questions, but show how we designed and set things up. - We have two 3584, one at each of our data centers. - We do not have the 3584 HA feature (HA frame with 2nd robot). - Each tape drive is singly attached to the san. - The SAN that has the tape drive spans the datacenters. So all tape drives are visible to all TSM servers at both data centers. - Each is configured as one library (A virtual lib via ASLM, but there is only one. We wanted to allow for future virt libs, but haven't needed them.) - Each library is serviced by one library manager, since there is only one virt lib in each. - Since there is only one virt lib, all tape drives are assigned to it, as are all tapes. - Each library manager handles it's library for ALL TSM instances from both data centers. PRI pools and copy pools are defined to different libraries, so offsite tapes are written to what looks like local tapes, but are in fact at the other datacenter. We are fortunate to have the interconnect to allow this. - The library manager TSM instances are dedicated to this task. - The virt libs have two tape drives defined with control paths. One SMC device (AIX) is defined to TSM, while Atape provides multi-pathing. - The SAN for the tape drives spans the datacenters, so all TSm instances at both data centers have access to both library managers and all tape drives. - All TSM instances have access to all tape drives. So as you can see, the driving design of our setup was that every tsm instance has assess to every tape drive in both libraries. This allows for very efficient use of the drives. When we've have major library problems where an entire library is down, and we've had several of these, we have scrambled to add disk space to the staging disk pools to keep backups running. Our Oracle databases are (supposedly) configured to have archive areas big enough to hold 24 hours of logs, just in case TSM is down that long. What you describe, splitting the lib into two virt libs is good, but it depends on what you are trying to protect against. Do I define 2-virtual libraries, 1-per library manager server? What are you trying to protect against? - An entire library outage? - A frame being out? - A robot going down? (do you have the HA feature?) - A library manager being down? - TSM having problems and being down? - The library manager server being down? - The tape drive san being down? - Are you using dual san connections of the tape drives? If so, are they on separate san's, or at least separate switches? Walk through the pieces/parts of your design and ask what happens if any one piece goes down. Then two pieces, then 3 . . . . Does this mean the drives as well as storage cells are defined/associated to each virtual library? Drives are assigned to a virt lib. But, If you check the 3584 Operator Guide you will find a way to setup and allow a tape drive to be shared between partitions, but no info on how it's used. Since I have never dealt with the issue of a tape drive path being used for library control path/function, I guess I need to define more than one of these paths, in case the drive has a problem? Yes, you should define at least 2 drives with control paths. And, that would be per virt lib. So if you have 2 virt libs you would have 4 drives defined with control paths. (at least that's my understanding, but then I've never done this) Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Equating current 3494 configuration to TS3500
On Tue, Apr 23, 2013 at 1:05 PM, Richard Rhodes rrho...@firstenergycorp.com wrote: What are you trying to protect against? Library Manager server/outage - We have massive backups that overflow our disk storage pools, all the time. Plus we have to perform Linux kernel patching/maintenance monthly, which means shutting down and rebooting. If *1* TSM server exclusively manages ALL of the tape drives/offline storage, then shutting it down disrupts *ALL* tape activity. -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Equating current 3494 configuration to TS3500
When we've have major library problems where an entire library is down, and we've had several of these, we have scrambled to add disk space to the staging disk pools to keep backups running. I don't have this luxury. 5 of my 7 production servers do not have any external/SAN disk - only what the Dell x86 server came with. Our Oracle databases are (supposedly) configured to have archive areas big enough to hold 24 hours of logs, just in case TSM is down that long. We have everything from Oracle to Notes to MS-SQL to MySQL database systems and many of them are fixed on disk/logging space, thus the demand on the TSM servers being there to empty logs Are you using dual san connections of the tape drives? If so, are they on separate san's, or at leastseparate switches? Again a luxury I don't have. All tape drives have 1-fibre attachment. Don't have enough switches to go beyond that. Currently all on one SAN/fibre - supposed to be getting a new switch that will give me more ports but no redundancy. Drives are assigned to a virt lib. But, If you check the 3584 Operator Guide you will find a way to setup and allow a tape drive to be shared between partitions, but no info on how it's used. How is TSM setup to use virtual drives - my current understanding is that Drives are defined to a Library and Paths connect the Library and Drives to a TSM server. The Library Manager (drive owner) server delegates the drives it owns/manages to a TSM server that needs it. So, how would a virtual drive move from one TSM server to another if the TSM server that owns it is down, without redefining the paths/drives to another Library Manager? Are all drives defines/assigned to multiple Library Manager servers? Yes, you should define at least 2 drives with control paths. And, that would be per virt lib. So if you have 2 virt libs you would have 4 drives defined with control paths. (at least that's my understanding, but then I've never done this) I've meant to ask - how does the library appear to the TSM server OS? Is it /dev/smc0,1,2,etc or /dev/IBMchanger0,1,2,etc? On Tue, Apr 23, 2013 at 1:05 PM, Richard Rhodes rrho...@firstenergycorp.com wrote: We have 2-TSM servers acting at Library Managers/Owner, thus each LM has its own 3494 category codes, each owns n-3592 drives, etc. This was done for redundancy, fail-over, etc. We have tape drives spinning most of the time so having all library functionality and drives attached to only 1-TSM server is not a good idea. Here is our config. It may not answer your direct questions, but show how we designed and set things up. - We have two 3584, one at each of our data centers. - We do not have the 3584 HA feature (HA frame with 2nd robot). - Each tape drive is singly attached to the san. - The SAN that has the tape drive spans the datacenters. So all tape drives are visible to all TSM servers at both data centers. - Each is configured as one library (A virtual lib via ASLM, but there is only one. We wanted to allow for future virt libs, but haven't needed them.) - Each library is serviced by one library manager, since there is only one virt lib in each. - Since there is only one virt lib, all tape drives are assigned to it, as are all tapes. - Each library manager handles it's library for ALL TSM instances from both data centers. PRI pools and copy pools are defined to different libraries, so offsite tapes are written to what looks like local tapes, but are in fact at the other datacenter. We are fortunate to have the interconnect to allow this. - The library manager TSM instances are dedicated to this task. - The virt libs have two tape drives defined with control paths. One SMC device (AIX) is defined to TSM, while Atape provides multi-pathing. - The SAN for the tape drives spans the datacenters, so all TSm instances at both data centers have access to both library managers and all tape drives. - All TSM instances have access to all tape drives. So as you can see, the driving design of our setup was that every tsm instance has assess to every tape drive in both libraries. This allows for very efficient use of the drives. When we've have major library problems where an entire library is down, and we've had several of these, we have scrambled to add disk space to the staging disk pools to keep backups running. Our Oracle databases are (supposedly) configured to have archive areas big enough to hold 24 hours of logs, just in case TSM is down that long. What you describe, splitting the lib into two virt libs is good, but it depends on what you are trying to protect against. Do I define 2-virtual libraries, 1-per library manager server? What are you trying to protect against? - An entire library outage? - A frame being out? - A robot going down? (do you have the HA feature?) - A library manager being down? - TSM having
Re: Equating current 3494 configuration to TS3500
OK. The equivalent way to do the TS3500, treating as 2 separate libraries: Using the TS3500 web interface, create 2 logical libraries/partitions in the TS3500. Name them Manny and Moe (or whatever you want - TSM will not know or care what the partition names are). One logical library or partition would correspond to each of your current category codes. I will call them libraries from here on. Assign 9 drives to one and 8 to the other. Create at least one, preferably 2 control paths on any drive in each library (more about control paths later). Rescan device addresses from the OS, and the control path(s) will be presented to the OS as a media changer device(s). Define one library (Manny) on your TSM1 server, define the library path using the media changer address, define the drives, define the paths using the drive device addresses. . TSM only knows the library by the Name you give it when you DEFINE LIBRARY, and the device name when you define the library path. Doesn't know that it's living in a partition in a bigger library, or what the library partition name is from the TS3500. Define Moe to your TSM2 server, etc. I don't know how you were managing cartridges in your 3494; I always made sure I had different ranges of volsers for each TSM. Assuming you did that, in the TS3500 web interface, you create a cartridge assignment policy for each logical library. If your barcodes are TSM1xx for TSM server 1 and TSM2xx for TSM server 2, you create a cartridge assignment policy in the Manny library that says all barcodes TSM1xx go to the Manny partition. In the Moe partition, you create a cartridge assignment policy that assigns all TSM2xx barcodes to Moe. The cartridge assignment policy just affects what happens when you put tapes in the I/O door. When you put tapes in through the door, the cartridge assignment policy causes tapes in the door to be assigned to the virtual I/O door of the appropriate library, so when you do a checkin from TSM1, it gets only his barcodes. If you don't create a cartridge assignment policy, I believe what still happens with ALMS is that when you put tapes in the door, you get a prompt on the library display asking which library to assign the cartridges to. Now all you'll need to do is change the syntax of your CHECKIN command appropriately, and from there on you can pretend everything works exactly like it did with the 3494. Note: From a TSM point of view, this is NOT library sharing, this is 2 separate libraries (which could be physical or logical). Differences: if you are library sharing with TSM, you have 1 partition, 1 set of barcodes, 1 shared scratch pool, one of the TSM servers is the library manager/owner, and each TSM server can use all the drives. Control paths: You can go in the library web interface and define a control path on EVERY drive in the logical library. If you do, then you will have 8 or 9 media changer devices presented to the OS, and you can use any one of them you want to define the library path. But, having multiple control paths defined doesn't do you much practical good unless you also have I/O path failover working in the O/S. (I've seen it set up for AIX, never had a Windows customer do it.) If you don't have I/O path failover working in the O/S, and the drive fails that you are using for the library path, you're down anyway, whether you have more control paths defined or not. If that happens, you go into TSM and update the library path to use one of the other media changer device names, and you can work that way until the failed drive is replaced. But that is still a manual process/outage. So you can define a 2nd control path at that time, or have an extra one defined ahead. No point in defining all of them, really. The main thing you need to remember, which is different from the 3494, is that if you have IBM come in and do firmware updates, and it takes the control path drive out of service, you are going down until you redefine the library path from TSM. Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 23, 2013 12:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 2-libraries with fixed drives. One library has 9 drives the other one has 8. - Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html When you say in your 3494 that each owns n-3592 drives: Do your current TSM servers share the drives, or do you use it as if it is 2 separate physical libraries
Re: Equating current 3494 configuration to TS3500
As always, thanks Wanda. That clears up / confirms a lot of what I was thinking. Don't know about the I/O path failover for these SAN paths - need to ask my OS guy. Having to do everything from the web interface is going to be a really pain if not a security concern/issue. Currently, the 3494 is on the same private subnet as all servers and nodes that perform backups - isolated/locked-down. Never used it for anything more than LM functionality from the Linux TSM servers - no GUI, no web, just CLI. I wonder if you can define more than one IP connection? On Tue, Apr 23, 2013 at 2:27 PM, Prather, Wanda wanda.prat...@icfi.comwrote: OK. The equivalent way to do the TS3500, treating as 2 separate libraries: Using the TS3500 web interface, create 2 logical libraries/partitions in the TS3500. Name them Manny and Moe (or whatever you want - TSM will not know or care what the partition names are). One logical library or partition would correspond to each of your current category codes. I will call them libraries from here on. Assign 9 drives to one and 8 to the other. Create at least one, preferably 2 control paths on any drive in each library (more about control paths later). Rescan device addresses from the OS, and the control path(s) will be presented to the OS as a media changer device(s). Define one library (Manny) on your TSM1 server, define the library path using the media changer address, define the drives, define the paths using the drive device addresses. . TSM only knows the library by the Name you give it when you DEFINE LIBRARY, and the device name when you define the library path. Doesn't know that it's living in a partition in a bigger library, or what the library partition name is from the TS3500. Define Moe to your TSM2 server, etc. I don't know how you were managing cartridges in your 3494; I always made sure I had different ranges of volsers for each TSM. Assuming you did that, in the TS3500 web interface, you create a cartridge assignment policy for each logical library. If your barcodes are TSM1xx for TSM server 1 and TSM2xx for TSM server 2, you create a cartridge assignment policy in the Manny library that says all barcodes TSM1xx go to the Manny partition. In the Moe partition, you create a cartridge assignment policy that assigns all TSM2xx barcodes to Moe. The cartridge assignment policy just affects what happens when you put tapes in the I/O door. When you put tapes in through the door, the cartridge assignment policy causes tapes in the door to be assigned to the virtual I/O door of the appropriate library, so when you do a checkin from TSM1, it gets only his barcodes. If you don't create a cartridge assignment policy, I believe what still happens with ALMS is that when you put tapes in the door, you get a prompt on the library display asking which library to assign the cartridges to. Now all you'll need to do is change the syntax of your CHECKIN command appropriately, and from there on you can pretend everything works exactly like it did with the 3494. Note: From a TSM point of view, this is NOT library sharing, this is 2 separate libraries (which could be physical or logical). Differences: if you are library sharing with TSM, you have 1 partition, 1 set of barcodes, 1 shared scratch pool, one of the TSM servers is the library manager/owner, and each TSM server can use all the drives. Control paths: You can go in the library web interface and define a control path on EVERY drive in the logical library. If you do, then you will have 8 or 9 media changer devices presented to the OS, and you can use any one of them you want to define the library path. But, having multiple control paths defined doesn't do you much practical good unless you also have I/O path failover working in the O/S. (I've seen it set up for AIX, never had a Windows customer do it.) If you don't have I/O path failover working in the O/S, and the drive fails that you are using for the library path, you're down anyway, whether you have more control paths defined or not. If that happens, you go into TSM and update the library path to use one of the other media changer device names, and you can work that way until the failed drive is replaced. But that is still a manual process/outage. So you can define a 2nd control path at that time, or have an extra one defined ahead. No point in defining all of them, really. The main thing you need to remember, which is different from the 3494, is that if you have IBM come in and do firmware updates, and it takes the control path drive out of service, you are going down until you redefine the library path from TSM. Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 23, 2013 12:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 2
Re: Equating current 3494 configuration to TS3500
You only need to do this stuff at config time, you won't need the web interface on a day to day basis, any more than with the 3494. (although it is surely nice to have just to check on what's happening in there). You can also forego the web interface and use the library panel for the definitions, but THAT is indeed a pain. And there is a CLI, but I've never used it; and that's the same IP connection, so I don't think that would help you. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Tuesday, April 23, 2013 2:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500 As always, thanks Wanda. That clears up / confirms a lot of what I was thinking. Don't know about the I/O path failover for these SAN paths - need to ask my OS guy. Having to do everything from the web interface is going to be a really pain if not a security concern/issue. Currently, the 3494 is on the same private subnet as all servers and nodes that perform backups - isolated/locked-down. Never used it for anything more than LM functionality from the Linux TSM servers - no GUI, no web, just CLI. I wonder if you can define more than one IP connection? On Tue, Apr 23, 2013 at 2:27 PM, Prather, Wanda wanda.prat...@icfi.comwrote: OK. The equivalent way to do the TS3500, treating as 2 separate libraries: Using the TS3500 web interface, create 2 logical libraries/partitions in the TS3500. Name them Manny and Moe (or whatever you want - TSM will not know or care what the partition names are). One logical library or partition would correspond to each of your current category codes. I will call them libraries from here on. Assign 9 drives to one and 8 to the other. Create at least one, preferably 2 control paths on any drive in each library (more about control paths later). Rescan device addresses from the OS, and the control path(s) will be presented to the OS as a media changer device(s). Define one library (Manny) on your TSM1 server, define the library path using the media changer address, define the drives, define the paths using the drive device addresses. . TSM only knows the library by the Name you give it when you DEFINE LIBRARY, and the device name when you define the library path. Doesn't know that it's living in a partition in a bigger library, or what the library partition name is from the TS3500. Define Moe to your TSM2 server, etc. I don't know how you were managing cartridges in your 3494; I always made sure I had different ranges of volsers for each TSM. Assuming you did that, in the TS3500 web interface, you create a cartridge assignment policy for each logical library. If your barcodes are TSM1xx for TSM server 1 and TSM2xx for TSM server 2, you create a cartridge assignment policy in the Manny library that says all barcodes TSM1xx go to the Manny partition. In the Moe partition, you create a cartridge assignment policy that assigns all TSM2xx barcodes to Moe. The cartridge assignment policy just affects what happens when you put tapes in the I/O door. When you put tapes in through the door, the cartridge assignment policy causes tapes in the door to be assigned to the virtual I/O door of the appropriate library, so when you do a checkin from TSM1, it gets only his barcodes. If you don't create a cartridge assignment policy, I believe what still happens with ALMS is that when you put tapes in the door, you get a prompt on the library display asking which library to assign the cartridges to. Now all you'll need to do is change the syntax of your CHECKIN command appropriately, and from there on you can pretend everything works exactly like it did with the 3494. Note: From a TSM point of view, this is NOT library sharing, this is 2 separate libraries (which could be physical or logical). Differences: if you are library sharing with TSM, you have 1 partition, 1 set of barcodes, 1 shared scratch pool, one of the TSM servers is the library manager/owner, and each TSM server can use all the drives. Control paths: You can go in the library web interface and define a control path on EVERY drive in the logical library. If you do, then you will have 8 or 9 media changer devices presented to the OS, and you can use any one of them you want to define the library path. But, having multiple control paths defined doesn't do you much practical good unless you also have I/O path failover working in the O/S. (I've seen it set up for AIX, never had a Windows customer do it.) If you don't have I/O path failover working in the O/S, and the drive fails that you are using for the library path, you're down anyway, whether you have more control paths defined or not. If that happens, you go into TSM and update the library path to use one of the other media changer device names, and you can work
Re: Equating current 3494 configuration to TS3500
I've meant to ask - how does the library appear to the TSM server OS? Is it /dev/smc0,1,2,etc or /dev/IBMchanger0,1,2,etc? As /dev/smcX to AIX; as /dev/IBMchangerX to linux. David
Re: Equating current 3494 configuration to TS3500
How is TSM setup to use virtual drives - my current understanding is that Drives are defined to a Library and Paths connect the Library and Drives to a TSM server. The Library Manager (drive owner) server delegates the drives it owns/manages to a TSM server that needs it. So, how would a virtual drive move from one TSM server to another if the TSM server that owns it is down, without redefining the paths/drives to another Library Manager? Are all drives defines/assigned to multiple Library Manager servers? exactly! I read about that feature and have no idea how it would work. It doesn't make sense unless TSM is somehow aware of it, which it isn't. Yes, you should define at least 2 drives with control paths. And, that would be per virt lib. So if you have 2 virt libs you would have 4 drives defined with control paths. (at least that's my understanding, but then I've never done this) I've meant to ask - how does the library appear to the TSM server OS? Is it /dev/smc0,1,2,etc or /dev/IBMchanger0,1,2,etc? For AIX you get SMC device files (smc1, smc2, etc). They are discovered by AIX after you've zoned up the drives and run cfgmgr. I have 2 drives with control paths. Each TSM server has 2 HBA's into the tape drive san. Each HBA is zoned to both control path drive. (Actually, each hba is zoned to all tape drives, which included the control path drives.) So 2 drives times 2 hba's gives 4 SMC device files in AIX for one of our libraries. One of those SMC devices gets used on the define path for the library. On AIX the multi-path sftw is called Atape. After running it's setup, Atape driver provides failover between the four SMC devices. I assume IBM has something similar for Linux. It seems to me IBM has a redbook about setting up a 3584 to TSM . . . Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
