SV: Desperation, DR, and four TS3100 libraries...
Hi Wanda, On my way to work this morning I have been thinking about your situation and I think I have an idea how you can get it to work. But only for restore not for backup... :) I haven't try this yet and probably don't have time to test it for you. But I think this will work. Define 4 SCSI Libraries Define 4 Drives. 1 to each Library Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and 4 (CopyClass2, CopyClass3, CopyClass4) And Update one Device Class to point to the 1st Library. Now do a Audit of the library with Owner=YOUR TSM SERVER In this stage does TSM know that ALL Tape are available but in different libraries. Technically it should work. The database knows what tape TSM need and only change the data entry-path for the tape in the same way it does with the "primary" (1st) Library you have. This is still just an crazy idea like always that I normally have. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda Prather [wprat...@jasi.com] Skickat: den 10 juli 2009 03:33 Till: ADSM-L@VM.MARIST.EDU Ämne: Desperation, DR, and four TS3100 libraries... I'm drawing a blank here, any suggestions welcomed. I have a TSM customer who makes their copypool tapes using a TS3200 with LTO4 drives. The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII library. No issues. One copy pool, tapes vaulted and sent offsite. They want to go to a commercial DR vendor site and do a DR test next week. The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable libraries. Instead, they want us to use 4 (count 'em, four) TS3100 libraries. The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII library. There's only 1 copy pool, so all tapes were created on the same device class. Ignoring the which-carts-would-go-in-which-library issue, I can't have a device class pointing to 4 libraries. And, the TS3100 is built in such a way that unlike a TS3500, you can't open the doors and access the drives for manual mounting. (I'd be happy to pull the covers off and try it, ignoring any warranties I might void, but I doubt the vendor will let me attack the thing with a screwdriver/wrench/hacksaw.) If I put all the carts in one TS3100 that will work, but that leaves me only 1 drive to restore all the clients, and they won't likely get done in the desired time window. The only thing I can think of to use all 4 drives, is to define those four TS3100's as 1 manual library with 4 manual drives, and use the front panel of each TS3100 to move tapes from the I/O slot to the drive when TSM requests a mount. (Actually the FIRST thing I thought of, was "cancel the DR contract, this is nonsense". But my customer isn't convinced yet...) Anybody got a better solution? I've already tried a margarita, it didn't help W
Re: Desperation, DR, and four TS3100 libraries...
Thanks John - I like your idea of the script to do the mounts! It also reminds me, those puppies have a web interface. We could do the moves with that, as well, if I can talk them into setting up 4 IP connections. If not, I'll crank up my perl skills... W On Fri, Jul 10, 2009 at 12:06 AM, John D. Schneider < john.schnei...@computercoachingcommunity.com> wrote: > Wanda, > My solution isn't much better, but here goes: > > 1) Like you said, define 1 manual library, 1 device class, with 4 LTO4 > drives, and get them all working and defined to the DR environment. > 2) You will be using the IBM drives, of course, so I am presuming the > IBM drivers will be installed by you or your DR vendor. > 3) Start a TSM administrator window in -console mode, so you can see the > tape mount requests. > 4) When your tape operator sees a tape mount request, he puts the > appropriate tape in the I/O door belonging to that tape drive's library. > 5) You didn't say if you were Unix, Linux, or Windows. I will explain > it as if it is AIX, and you can transpose. From a Unix shell window, > your tape operator uses tapeutil, the linemode library manager that > comes with the IBM drivers, to do the tape mounts for you. He can issue > the commands to move the tape from the element number of the I/O door > straight to the tape drive. > 6) When he sees an unmount request, he issues the tapeutil command to > move the tape from the drive to the I/O door, and puts the tape back in > the stack. > > If it were me tackling this one, I would write two short ksh scripts > called "tape_mount" and "tape_unmount" where the tape operator just puts > in which tape volser he is mounting, and which drive it should go in, > and let the ksh scripts translate that into the actual device name, and > tapeutil syntax, so there would be fewer mistakes. > > Also if it were me, I would build this experimentally using a tape > library or libraries and drives while still back home, so I could build > the script and debug it, then bring it with me to the DR exercise, and > all I would have to change would be the /dev/smcX and /dev/rmtX device > names, and start mounting tapes. > > Do you see any fatal flaws in this? It is a lot like your original > idea, but typing the mounts and unmounts on the faceplate of four > different TS3100's would drive me buggy. Hopefully this would be less > tedious. > > Best Regards, > > John D. Schneider > The Computer Coaching Community, LLC > Office: (314) 635-5424 > Toll Free: (866) 796-9226 > Cell: (314) 750-8721 > > > Original Message > Subject: [ADSM-L] Desperation, DR, and four TS3100 libraries... > From: Wanda Prather > Date: Thu, July 09, 2009 8:33 pm > To: ADSM-L@VM.MARIST.EDU > > I'm drawing a blank here, any suggestions welcomed. > > I have a TSM customer who makes their copypool tapes using a TS3200 with > LTO4 drives. > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > library. No issues. > One copy pool, tapes vaulted and sent offsite. > > They want to go to a commercial DR vendor site and do a DR test next > week. > The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable > libraries. > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > library. > > There's only 1 copy pool, so all tapes were created on the same device > class. > Ignoring the which-carts-would-go-in-which-library issue, I can't have a > device class pointing to 4 libraries. > > And, the TS3100 is built in such a way that unlike a TS3500, you can't > open > the doors and access the drives for manual mounting. > (I'd be happy to pull the covers off and try it, ignoring any warranties > I > might void, but I doubt the vendor will let me attack the thing with a > screwdriver/wrench/hacksaw.) > > If I put all the carts in one TS3100 that will work, but that leaves me > only > 1 drive to restore all the clients, and they won't likely get done in > the > desired time window. > > The only thing I can think of to use all 4 drives, is to define those > four > TS3100's as 1 manual library with 4 manual drives, and use the front > panel > of each TS3100 to move tapes from the I/O slot to the drive when TSM > requests a mount. > > (Actually the FIRST thing I thought of, was "cancel the DR contract, > this is > nonsense". But my customer isn't convinced yet...) > > Anybody got a better solution? > I've already tried a margarita, it didn't help > > W >
Re: SV: Desperation, DR, and four TS3100 libraries...
Thanks Christian, and everyone, for the suggestions. Even if I can convince TSM to work with the tapes spread across the 4 libraries, I think I still lose too much throughput. If I want to restore multiple clients/filespaces in parallel, I think we could easily get into the situation that client 1 is using the drive in library 1, and the restore for client 2 needs a tape that is also in library 1. The only way I can see to keep all 4 drives busy is to use them in manual mode. (Short of doing MOVE NODEDATA to guarantee that every client is on its own tape, which is highly unrealistic for a copy pool. Not that this scenario is realistic to begin with!) Thanks everyone! Wanda (maybe another margarita will bring more enlightenment..) On Fri, Jul 10, 2009 at 5:58 AM, Christian Svensson < christian.svens...@cristie.se> wrote: > Hi Wanda, > On my way to work this morning I have been thinking about your situation > and I think I have an idea how you can get it to work. But only for restore > not for backup... :) > I haven't try this yet and probably don't have time to test it for you. But > I think this will work. > > Define 4 SCSI Libraries > Define 4 Drives. 1 to each Library > Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and 4 > (CopyClass2, CopyClass3, CopyClass4) > And Update one Device Class to point to the 1st Library. > Now do a Audit of the library with Owner=YOUR TSM SERVER > > In this stage does TSM know that ALL Tape are available but in different > libraries. > > Technically it should work. The database knows what tape TSM need and only > change the data entry-path for the tape in the same way it does with the > "primary" (1st) Library you have. > > This is still just an crazy idea like always that I normally have. > > > Best Regards > Christian Svensson > > Cell: +46-70-325 1577 > E-mail: christian.svens...@cristie.se > Skype: cristie.christian.svensson > > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda > Prather [wprat...@jasi.com] > Skickat: den 10 juli 2009 03:33 > Till: ADSM-L@VM.MARIST.EDU > Ämne: Desperation, DR, and four TS3100 libraries... > > I'm drawing a blank here, any suggestions welcomed. > > I have a TSM customer who makes their copypool tapes using a TS3200 with > LTO4 drives. > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > library. No issues. > One copy pool, tapes vaulted and sent offsite. > > They want to go to a commercial DR vendor site and do a DR test next week. > The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable > libraries. > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > library. > > There's only 1 copy pool, so all tapes were created on the same device > class. > Ignoring the which-carts-would-go-in-which-library issue, I can't have a > device class pointing to 4 libraries. > > And, the TS3100 is built in such a way that unlike a TS3500, you can't open > the doors and access the drives for manual mounting. > (I'd be happy to pull the covers off and try it, ignoring any warranties I > might void, but I doubt the vendor will let me attack the thing with a > screwdriver/wrench/hacksaw.) > > If I put all the carts in one TS3100 that will work, but that leaves me > only > 1 drive to restore all the clients, and they won't likely get done in the > desired time window. > > The only thing I can think of to use all 4 drives, is to define those four > TS3100's as 1 manual library with 4 manual drives, and use the front panel > of each TS3100 to move tapes from the I/O slot to the drive when TSM > requests a mount. > > (Actually the FIRST thing I thought of, was "cancel the DR contract, this > is > nonsense". But my customer isn't convinced yet...) > > Anybody got a better solution? > I've already tried a margarita, it didn't help > > W >
Re: SV: Desperation, DR, and four TS3100 libraries...
It is like you are trying to re-invent ACSLS. Our library was basically two libraries managed by ACSLS. To TSM ACSLS was the library. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, July 10, 2009 11:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: Desperation, DR, and four TS3100 libraries... Thanks Christian, and everyone, for the suggestions. Even if I can convince TSM to work with the tapes spread across the 4 libraries, I think I still lose too much throughput. If I want to restore multiple clients/filespaces in parallel, I think we could easily get into the situation that client 1 is using the drive in library 1, and the restore for client 2 needs a tape that is also in library 1. The only way I can see to keep all 4 drives busy is to use them in manual mode. (Short of doing MOVE NODEDATA to guarantee that every client is on its own tape, which is highly unrealistic for a copy pool. Not that this scenario is realistic to begin with!) Thanks everyone! Wanda (maybe another margarita will bring more enlightenment..) On Fri, Jul 10, 2009 at 5:58 AM, Christian Svensson < christian.svens...@cristie.se> wrote: > Hi Wanda, > On my way to work this morning I have been thinking about your > situation and I think I have an idea how you can get it to work. But > only for restore not for backup... :) I haven't try this yet and > probably don't have time to test it for you. But I think this will > work. > > Define 4 SCSI Libraries > Define 4 Drives. 1 to each Library > Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and > 4 (CopyClass2, CopyClass3, CopyClass4) And Update one Device Class to > point to the 1st Library. > Now do a Audit of the library with Owner=YOUR TSM SERVER > > In this stage does TSM know that ALL Tape are available but in > different libraries. > > Technically it should work. The database knows what tape TSM need and > only change the data entry-path for the tape in the same way it does > with the "primary" (1st) Library you have. > > This is still just an crazy idea like always that I normally have. > > > Best Regards > Christian Svensson > > Cell: +46-70-325 1577 > E-mail: christian.svens...@cristie.se > Skype: cristie.christian.svensson > > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda > Prather [wprat...@jasi.com] > Skickat: den 10 juli 2009 03:33 > Till: ADSM-L@VM.MARIST.EDU > Ämne: Desperation, DR, and four TS3100 libraries... > > I'm drawing a blank here, any suggestions welcomed. > > I have a TSM customer who makes their copypool tapes using a TS3200 > with > LTO4 drives. > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > library. No issues. > One copy pool, tapes vaulted and sent offsite. > > They want to go to a commercial DR vendor site and do a DR test next week. > The commercial DR vendor, unbelievably, has no multi-drive > LTO4-capable libraries. > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > library. > > There's only 1 copy pool, so all tapes were created on the same device > class. > Ignoring the which-carts-would-go-in-which-library issue, I can't have > a device class pointing to 4 libraries. > > And, the TS3100 is built in such a way that unlike a TS3500, you can't > open the doors and access the drives for manual mounting. > (I'd be happy to pull the covers off and try it, ignoring any > warranties I might void, but I doubt the vendor will let me attack the > thing with a > screwdriver/wrench/hacksaw.) > > If I put all the carts in one TS3100 that will work, but that leaves > me only > 1 drive to restore all the clients, and they won't likely get done in > the desired time window. > > The only thing I can think of to use all 4 drives, is to define those > four TS3100's as 1 manual library with 4 manual drives, and use the > front panel of each TS3100 to move tapes from the I/O slot to the > drive when TSM requests a mount. > > (Actually the FIRST thing I thought of, was "cancel the DR contract, > this is nonsense". But my customer isn't convinced yet...) > > Anybody got a better solution? > I've already tried a margarita, it didn't help > > W > IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not us
Re: SV: Desperation, DR, and four TS3100 libraries...
Wanda, We actually tried 2 TS3100s in a test recovery. It didn't go very well. If you attempt it. The Gresham product should be able to present 1 library image to TSM. I don't know at what cost. Without Gresham: Make sure your incremental DB backups are directed to disk or someplace other than the already overloaded libraries. If you have a few months to prepare, break the copypool down to several that will individually fit in a 3100 and give each copypool it's own devclass. Even though the devclass breakdown is not needed at the home site, it will allow you to re-design as needed in a recovery scenario. Bob. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, July 10, 2009 10:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: Desperation, DR, and four TS3100 libraries... Thanks Christian, and everyone, for the suggestions. Even if I can convince TSM to work with the tapes spread across the 4 libraries, I think I still lose too much throughput. If I want to restore multiple clients/filespaces in parallel, I think we could easily get into the situation that client 1 is using the drive in library 1, and the restore for client 2 needs a tape that is also in library 1. The only way I can see to keep all 4 drives busy is to use them in manual mode. (Short of doing MOVE NODEDATA to guarantee that every client is on its own tape, which is highly unrealistic for a copy pool. Not that this scenario is realistic to begin with!) Thanks everyone! Wanda (maybe another margarita will bring more enlightenment..) On Fri, Jul 10, 2009 at 5:58 AM, Christian Svensson < christian.svens...@cristie.se> wrote: > Hi Wanda, > On my way to work this morning I have been thinking about your > situation and I think I have an idea how you can get it to work. But > only for restore not for backup... :) I haven't try this yet and > probably don't have time to test it for you. But I think this will > work. > > Define 4 SCSI Libraries > Define 4 Drives. 1 to each Library > Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and > 4 (CopyClass2, CopyClass3, CopyClass4) And Update one Device Class to > point to the 1st Library. > Now do a Audit of the library with Owner=YOUR TSM SERVER > > In this stage does TSM know that ALL Tape are available but in > different libraries. > > Technically it should work. The database knows what tape TSM need and > only change the data entry-path for the tape in the same way it does > with the "primary" (1st) Library you have. > > This is still just an crazy idea like always that I normally have. > > > Best Regards > Christian Svensson > > Cell: +46-70-325 1577 > E-mail: christian.svens...@cristie.se > Skype: cristie.christian.svensson > > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda > Prather [wprat...@jasi.com] > Skickat: den 10 juli 2009 03:33 > Till: ADSM-L@VM.MARIST.EDU > Ämne: Desperation, DR, and four TS3100 libraries... > > I'm drawing a blank here, any suggestions welcomed. > > I have a TSM customer who makes their copypool tapes using a TS3200 > with > LTO4 drives. > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > library. No issues. > One copy pool, tapes vaulted and sent offsite. > > They want to go to a commercial DR vendor site and do a DR test next week. > The commercial DR vendor, unbelievably, has no multi-drive > LTO4-capable libraries. > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > library. > > There's only 1 copy pool, so all tapes were created on the same device > class. > Ignoring the which-carts-would-go-in-which-library issue, I can't have > a device class pointing to 4 libraries. > > And, the TS3100 is built in such a way that unlike a TS3500, you can't > open the doors and access the drives for manual mounting. > (I'd be happy to pull the covers off and try it, ignoring any > warranties I might void, but I doubt the vendor will let me attack the > thing with a > screwdriver/wrench/hacksaw.) > > If I put all the carts in one TS3100 that will work, but that leaves > me only > 1 drive to restore all the clients, and they won't likely get done in > the desired time window. > > The only thing I can think of to use all 4 drives, is to define those > four TS3100's as 1 manual library with 4 manual drives, and use the > front panel of each TS3100 to move tapes from the I/O slot to the > drive when TSM requests a mount. > > (Actually the FIRST thing I thought of, was "cancel the DR contract, > this is nonsense". But my customer isn't convinced yet...) > > Anybody got a better solution? > I've already tried a margarita, it didn't help > > W > This electronic transmission and any documents accompanying this electronic transmission contain confidential inform
Re: SV: Desperation, DR, and four TS3100 libraries...
Thanks - that's what I suspected! On Fri, Jul 10, 2009 at 1:01 PM, Bob Levad wrote: > Wanda, > > We actually tried 2 TS3100s in a test recovery. It didn't go very well. > > If you attempt it. > > The Gresham product should be able to present 1 library image to TSM. I > don't know at what cost. > > Without Gresham: > > Make sure your incremental DB backups are directed to disk or someplace > other than the already overloaded libraries. > > If you have a few months to prepare, break the copypool down to several > that > will individually fit in a 3100 and give each copypool it's own devclass. > > Even though the devclass breakdown is not needed at the home site, it will > allow you to re-design as needed in a recovery scenario. > > Bob. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Wanda Prather > Sent: Friday, July 10, 2009 10:31 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] SV: Desperation, DR, and four TS3100 libraries... > > Thanks Christian, and everyone, for the suggestions. > > Even if I can convince TSM to work with the tapes spread across the 4 > libraries, I think I still lose too much throughput. > > If I want to restore multiple clients/filespaces in parallel, I think we > could easily get into the situation that client 1 is using the drive in > library 1, and the restore for client 2 needs a tape that is also in > library > 1. The only way I can see to keep all 4 drives busy is to use them in > manual mode. (Short of doing MOVE NODEDATA to guarantee that every client > is on its own tape, which is highly unrealistic for a copy pool. Not that > this scenario is realistic to begin with!) > > Thanks everyone! > Wanda (maybe another margarita will bring more enlightenment..) > > > On Fri, Jul 10, 2009 at 5:58 AM, Christian Svensson < > christian.svens...@cristie.se> wrote: > > > Hi Wanda, > > On my way to work this morning I have been thinking about your > > situation and I think I have an idea how you can get it to work. But > > only for restore not for backup... :) I haven't try this yet and > > probably don't have time to test it for you. But I think this will > > work. > > > > Define 4 SCSI Libraries > > Define 4 Drives. 1 to each Library > > Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and > > 4 (CopyClass2, CopyClass3, CopyClass4) And Update one Device Class to > > point to the 1st Library. > > Now do a Audit of the library with Owner=YOUR TSM SERVER > > > > In this stage does TSM know that ALL Tape are available but in > > different libraries. > > > > Technically it should work. The database knows what tape TSM need and > > only change the data entry-path for the tape in the same way it does > > with the "primary" (1st) Library you have. > > > > This is still just an crazy idea like always that I normally have. > > > > > > Best Regards > > Christian Svensson > > > > Cell: +46-70-325 1577 > > E-mail: christian.svens...@cristie.se > > Skype: cristie.christian.svensson > > > > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda > > Prather [wprat...@jasi.com] > > Skickat: den 10 juli 2009 03:33 > > Till: ADSM-L@VM.MARIST.EDU > > Ämne: Desperation, DR, and four TS3100 libraries... > > > > I'm drawing a blank here, any suggestions welcomed. > > > > I have a TSM customer who makes their copypool tapes using a TS3200 > > with > > LTO4 drives. > > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > > library. No issues. > > One copy pool, tapes vaulted and sent offsite. > > > > They want to go to a commercial DR vendor site and do a DR test next > week. > > The commercial DR vendor, unbelievably, has no multi-drive > > LTO4-capable libraries. > > > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > > library. > > > > There's only 1 copy pool, so all tapes were created on the same device > > class. > > Ignoring the which-carts-would-go-in-which-library issue, I can't have > > a device class pointing to 4 libraries. > > > > And, the TS3100 is built in such a way that unlike a TS3500, you can't > > open the doors and access the drives for manual mounting. > > (I'd be happy to pull the covers off and try it, ignoring any > > warranties I might void, but I doubt the vendor will let me attack the > > thing with a > > screwdriver/wrench/hacksaw.) > > > > If I put all the carts in one TS3100 that will work, but that leaves > > me only > > 1 drive to restore all the clients, and they won't likely get done in > > the desired time window. > > > > The only thing I can think of to use all 4 drives, is to define those > > four TS3100's as 1 manual library with 4 manual drives, and use the > > front panel of each TS3100 to move tapes from the I/O slot to the > > drive when TSM requests a mount. > > > > (Actually the FIRST thing I thought of, wa
Re: Desperation, DR, and four TS3100 libraries...
Wanda, This is Tom Wright from Gresham and Nick is correct. Our Clareti Storage Director can manage the 4 small libraries off of the back-end and present one virtual TS3500 (3584) to TSM. That would solve your problem but would require our product to be in the mix. If that is of interest or if you would like more information please let me know. Regards, Tom twri...@greshamstorage.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Thursday, July 09, 2009 10:58 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Desperation, DR, and four TS3100 libraries... Off the top of my head, Wanda, I wonder if Gresham's library virtualization software can make those four T3100s look like one larger library? This, of course, would be the responsibility of the DR site, not your client, assuming the client's contract with the DR site is well written Just a thought, Nick
Re: Desperation, DR, and four TS3100 libraries...
Here are my thoughts: Since this is a DR instance, all TSM data should be read-only. With that said, you can restore the production TSM instance four times, so that you'll essentially have 4 identical TSM instances running. Each TSM instance should have its own tape library. Mark all copy volumes readonly or unavailable to start off with. To determine which tapes should go where, you can run off of one instance and run volumeusage or content selects for specific DR nodes. That'll get you a tape list and you can more accurately load/checkin tapes to balance the restores across all 4 instances. Since these tapes probably aren't collocated, there will inevitably be some tape swapping between libraries, but at least you'll be able to run restores off of 4 drives and you'll minimize the number of tape swaps you'll need to do (if you balanced correctly). Invariably, you'll be doing some amount of tape swaps, so maybe your just better off running the one instance with manual drives. Oh well, I tried. HTH, Sergio -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Thursday, July 09, 2009 9:34 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Desperation, DR, and four TS3100 libraries... I'm drawing a blank here, any suggestions welcomed. I have a TSM customer who makes their copypool tapes using a TS3200 with LTO4 drives. The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII library. No issues. One copy pool, tapes vaulted and sent offsite. They want to go to a commercial DR vendor site and do a DR test next week. The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable libraries. Instead, they want us to use 4 (count 'em, four) TS3100 libraries. The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII library. There's only 1 copy pool, so all tapes were created on the same device class. Ignoring the which-carts-would-go-in-which-library issue, I can't have a device class pointing to 4 libraries. And, the TS3100 is built in such a way that unlike a TS3500, you can't open the doors and access the drives for manual mounting. (I'd be happy to pull the covers off and try it, ignoring any warranties I might void, but I doubt the vendor will let me attack the thing with a screwdriver/wrench/hacksaw.) If I put all the carts in one TS3100 that will work, but that leaves me only 1 drive to restore all the clients, and they won't likely get done in the desired time window. The only thing I can think of to use all 4 drives, is to define those four TS3100's as 1 manual library with 4 manual drives, and use the front panel of each TS3100 to move tapes from the I/O slot to the drive when TSM requests a mount. (Actually the FIRST thing I thought of, was "cancel the DR contract, this is nonsense". But my customer isn't convinced yet...) Anybody got a better solution? I've already tried a margarita, it didn't help W
Re: SV: Desperation, DR, and four TS3100 libraries...
Wanda, What about setting up a TSM Library Manager and have him control the library and drives for a TSM Library Client doing all the restores. From: Wanda Prather To: ADSM-L@VM.MARIST.EDU Sent: Friday, July 10, 2009 1:06:53 PM Subject: Re: SV: Desperation, DR, and four TS3100 libraries... Thanks - that's what I suspected! On Fri, Jul 10, 2009 at 1:01 PM, Bob Levad wrote: > Wanda, > > We actually tried 2 TS3100s in a test recovery. It didn't go very well. > > If you attempt it. > > The Gresham product should be able to present 1 library image to TSM. I > don't know at what cost. > > Without Gresham: > > Make sure your incremental DB backups are directed to disk or someplace > other than the already overloaded libraries. > > If you have a few months to prepare, break the copypool down to several > that > will individually fit in a 3100 and give each copypool it's own devclass. > > Even though the devclass breakdown is not needed at the home site, it will > allow you to re-design as needed in a recovery scenario. > > Bob. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Wanda Prather > Sent: Friday, July 10, 2009 10:31 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] SV: Desperation, DR, and four TS3100 libraries... > > Thanks Christian, and everyone, for the suggestions. > > Even if I can convince TSM to work with the tapes spread across the 4 > libraries, I think I still lose too much throughput. > > If I want to restore multiple clients/filespaces in parallel, I think we > could easily get into the situation that client 1 is using the drive in > library 1, and the restore for client 2 needs a tape that is also in > library > 1. The only way I can see to keep all 4 drives busy is to use them in > manual mode. (Short of doing MOVE NODEDATA to guarantee that every client > is on its own tape, which is highly unrealistic for a copy pool. Not that > this scenario is realistic to begin with!) > > Thanks everyone! > Wanda (maybe another margarita will bring more enlightenment..) > > > On Fri, Jul 10, 2009 at 5:58 AM, Christian Svensson < > christian.svens...@cristie.se> wrote: > > > Hi Wanda, > > On my way to work this morning I have been thinking about your > > situation and I think I have an idea how you can get it to work. But > > only for restore not for backup... :) I haven't try this yet and > > probably don't have time to test it for you. But I think this will > > work. > > > > Define 4 SCSI Libraries > > Define 4 Drives. 1 to each Library > > Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and > > 4 (CopyClass2, CopyClass3, CopyClass4) And Update one Device Class to > > point to the 1st Library. > > Now do a Audit of the library with Owner=YOUR TSM SERVER > > > > In this stage does TSM know that ALL Tape are available but in > > different libraries. > > > > Technically it should work. The database knows what tape TSM need and > > only change the data entry-path for the tape in the same way it does > > with the "primary" (1st) Library you have. > > > > This is still just an crazy idea like always that I normally have. > > > > > > Best Regards > > Christian Svensson > > > > Cell: +46-70-325 1577 > > E-mail: christian.svens...@cristie.se > > Skype: cristie.christian.svensson > > > > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda > > Prather [wprat...@jasi.com] > > Skickat: den 10 juli 2009 03:33 > > Till: ADSM-L@VM.MARIST.EDU > > Ämne: Desperation, DR, and four TS3100 libraries... > > > > I'm drawing a blank here, any suggestions welcomed. > > > > I have a TSM customer who makes their copypool tapes using a TS3200 > > with > > LTO4 drives. > > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > > library. No issues. > > One copy pool, tapes vaulted and sent offsite. > > > > They want to go to a commercial DR vendor site and do a DR test next > week. > > The commercial DR vendor, unbelievably, has no multi-drive > > LTO4-capable libraries. > > > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > > library. > > > > There's only 1 copy pool, so all tapes were created on the same device > > class. > > Ignoring the which-carts-would-go-in-which-library issue, I can't have > > a device class pointing to 4 libraries. > > > > And, the TS3100 is built in such a way that unlike a TS3500, you can't > > open the doors and access the drives for manual mounting. > > (I'd be happy to pull the covers off and try it, ignoring any > > warranties I might void, but I doubt the vendor will let me attack the > > thing with a > > screwdriver/wrench/hacksaw.) > > > > If I put all the carts in one TS3100 that will work, but that leaves > > me only > > 1 drive to restore all the clients, and they won't likely get done in > > th
Re: Replacing tape drives (or "there has to be a better way")
Well the consensus is to change the serial number of the replaced drive, which I did. However, since I had already rebooted the library owning server, to discover the new serial number, I rebooted it again and it seems to access the replaced drive, just fine. However (isn't there always a "however" or "but"), none of the library client servers can mount a tape on this drive!. They all fail with a "Unable to open drive" error. I have tried updating the paths to this drive, on the library manager server, telling it to autodetect, which it does just fine. Even tried deleting and redefining all the paths to the library client servers.nada.zip...all library client servers still fail trying to get to this drive. More thoughts on how to resolve this? Do I need to bounce each of the TSM servers (not the whole machine..just the server)? From: "Costa, Justino" To: ADSM-L@VM.MARIST.EDU Date: 07/09/2009 07:38 PM Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better way") Sent by: "ADSM: Dist Stor Manager" There must be a reason why sandiscovery defaults to off on non-windows platforms. Anyway, I think you're right and that *should* be the correct behavior of SANDISCOVERY=ON. However, I prefer to stick with persistent binding and tight control on SAN changes. This way, I can at least avoid spending time on false positives like this one described here http://www-01.ibm.com/support/docview.wss?uid=swg1IC59807, even for the latest 5.5.x and 6.1.x versions. jmC -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: quinta-feira, 9 de Julho de 2009 18:11 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better way") I've been following this thread and have a question about AUTODETECT: I've seen this message: ANR8955I Drive drive name in library library name with serial number serial number is updated with the newly discovered serial number serial number . as a result of having the drives defined with AUTODETECT=YES and also SANDISCOVERY ON with the appropriate HBA library installed. Can anyone expand on why this does or doesn't always work when changing a drive serial #? Or does it only work when the device number changes? W > >Subject > >[ADSM-L] Replacing tape drives (or "there has to be a better way") > > > > > > > > > > > > > >I need thoughts/suggestions/help on how to deal with SAN attached > >tape drive replacements when a library is shared amongst 5-servers. > > > >We just has a drive replaced, therefore giving us a new serial number > >(3494ATL - TS1130). All servers that use these drives/libraries are > >RedHat Linux and use very current lin_tape drivers. > > > >Currently, the method we use is to bounce each server so the system > >rescans the SAN and gets the new serial number. > > > >In the past, just stopping the TSM server and then restarting the > >lin_tape driver would often be enough. Now with the latest lin_tape > >drivers, I don't see the lin_taped daemon running any more. > > > >Yes, I have tried updating the paths on the library manager server > >and telling it to autodetect but that didn't help. > > > >There has to be a better way! If you have a similar configuration, > >how > > >do you handle this scenario? > >
Re: Replacing tape drives (or "there has to be a better way")
Zoltan, In playing with various DR scenarios and working through occasional hardware problems, I found it difficult to get all the right commands entered correctly and in the correct sequence and with the library/drives in the correct states so I created scripts that delete and re-define everything. If things are healthy as far as the hardware is concerned, they work flawlessly and everything gets redefined and if there is a problem, looking for the first failure usually tells me where the problem lies. Bob. /* define ltolib2 */ del_path: delete path tsmsrvb mt0.0.0.1 srctype=server desttype=drive library=ltolib2 etc... del_drive: delete drive ltolib2 mt0.0.0.1 Etc... drop_library_path: delete path tsmsrvb ltolib2 srctype=server desttype=library drop_library: delete library ltolib2 create_library: define library ltolib2 libtype=scsi create_library_path: define path tsmsrvb ltolib2 srctype=server desttype=library device=lb0.1.0.1 online=yes def_drive: define drive ltolib2 mt0.0.0.1 element=autodetect serial=autodetect online=yes Etc... def_path: define path tsmsrvb mt0.0.0.1 srctype=server desttype=drive library=ltolib2 device=mt0.0.0.1 online=yes Etc... Checkin_scratch: checkin libv ltolib2 search=yes checklabel=barcode status=scratchCheckin_scratch: Checkin_private: checkin libv ltolib2 search=yes checklabel=barcode status=private -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, July 10, 2009 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better way") Well the consensus is to change the serial number of the replaced drive, which I did. However, since I had already rebooted the library owning server, to discover the new serial number, I rebooted it again and it seems to access the replaced drive, just fine. However (isn't there always a "however" or "but"), none of the library client servers can mount a tape on this drive!. They all fail with a "Unable to open drive" error. I have tried updating the paths to this drive, on the library manager server, telling it to autodetect, which it does just fine. Even tried deleting and redefining all the paths to the library client servers.nada.zip...all library client servers still fail trying to get to this drive. More thoughts on how to resolve this? Do I need to bounce each of the TSM servers (not the whole machine..just the server)? From: "Costa, Justino" To: ADSM-L@VM.MARIST.EDU Date: 07/09/2009 07:38 PM Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better way") Sent by: "ADSM: Dist Stor Manager" There must be a reason why sandiscovery defaults to off on non-windows platforms. Anyway, I think you're right and that *should* be the correct behavior of SANDISCOVERY=ON. However, I prefer to stick with persistent binding and tight control on SAN changes. This way, I can at least avoid spending time on false positives like this one described here http://www-01.ibm.com/support/docview.wss?uid=swg1IC59807, even for the latest 5.5.x and 6.1.x versions. jmC -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: quinta-feira, 9 de Julho de 2009 18:11 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better way") I've been following this thread and have a question about AUTODETECT: I've seen this message: ANR8955I Drive drive name in library library name with serial number serial number is updated with the newly discovered serial number serial number . as a result of having the drives defined with AUTODETECT=YES and also SANDISCOVERY ON with the appropriate HBA library installed. Can anyone expand on why this does or doesn't always work when changing a drive serial #? Or does it only work when the device number changes? W > >Subject > >[ADSM-L] Replacing tape drives (or "there has to be a better way") > > > > > > > > > > > > > >I need thoughts/suggestions/help on how to deal with SAN attached > >tape drive replacements when a library is shared amongst 5-servers. > > > >We just has a drive replaced, therefore giving us a new serial number > >(3494ATL - TS1130). All servers that use these drives/libraries are > >RedHat Linux and use very current lin_tape drivers. > > > >Currently, the method we use is to bounce each server so the system > >rescans the SAN and gets the new serial number. > > > >In the past, just stopping the TSM server and then restarting the > >lin_tape driver would often be enough. Now with the latest lin_tape > >drivers, I don't see the lin_taped daemon running any more. > > > >Yes, I have tried updating the paths on the library manager server > >and telling it to autodetect but that didn't help. > > > >There has to be a better way! If you have a similar configuration, > >how > > >do you handle this scenario? > > This
Re: Desperation, DR, and four TS3100 libraries...
Wanda, I read all the replies already, and the Gresham idea looks the most promising. You will be telling your customer that their "DR vendor" is retarded, right? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Thursday, July 09, 2009 6:34 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Desperation, DR, and four TS3100 libraries... I'm drawing a blank here, any suggestions welcomed. I have a TSM customer who makes their copypool tapes using a TS3200 with LTO4 drives. The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII library. No issues. One copy pool, tapes vaulted and sent offsite. They want to go to a commercial DR vendor site and do a DR test next week. The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable libraries. Instead, they want us to use 4 (count 'em, four) TS3100 libraries. The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII library. There's only 1 copy pool, so all tapes were created on the same device class. Ignoring the which-carts-would-go-in-which-library issue, I can't have a device class pointing to 4 libraries. And, the TS3100 is built in such a way that unlike a TS3500, you can't open the doors and access the drives for manual mounting. (I'd be happy to pull the covers off and try it, ignoring any warranties I might void, but I doubt the vendor will let me attack the thing with a screwdriver/wrench/hacksaw.) If I put all the carts in one TS3100 that will work, but that leaves me only 1 drive to restore all the clients, and they won't likely get done in the desired time window. The only thing I can think of to use all 4 drives, is to define those four TS3100's as 1 manual library with 4 manual drives, and use the front panel of each TS3100 to move tapes from the I/O slot to the drive when TSM requests a mount. (Actually the FIRST thing I thought of, was "cancel the DR contract, this is nonsense". But my customer isn't convinced yet...) Anybody got a better solution? I've already tried a margarita, it didn't help W
Re: Desperation, DR, and four TS3100 libraries...
On Fri, Jul 10, 2009 at 5:18 PM, W. Curtis Preston wrote: > Wanda, > > I read all the replies already, and the Gresham idea looks the most > promising. > > You will be telling your customer that their "DR vendor" is retarded, > right? Been there, done that! Hasn't sunk in yet. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Wanda Prather > Sent: Thursday, July 09, 2009 6:34 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Desperation, DR, and four TS3100 libraries... > > I'm drawing a blank here, any suggestions welcomed. > > I have a TSM customer who makes their copypool tapes using a TS3200 with > LTO4 drives. > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > library. No issues. > One copy pool, tapes vaulted and sent offsite. > > They want to go to a commercial DR vendor site and do a DR test next week. > The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable > libraries. > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > library. > > There's only 1 copy pool, so all tapes were created on the same device > class. > Ignoring the which-carts-would-go-in-which-library issue, I can't have a > device class pointing to 4 libraries. > > And, the TS3100 is built in such a way that unlike a TS3500, you can't open > the doors and access the drives for manual mounting. > (I'd be happy to pull the covers off and try it, ignoring any warranties I > might void, but I doubt the vendor will let me attack the thing with a > screwdriver/wrench/hacksaw.) > > If I put all the carts in one TS3100 that will work, but that leaves me > only > 1 drive to restore all the clients, and they won't likely get done in the > desired time window. > > The only thing I can think of to use all 4 drives, is to define those four > TS3100's as 1 manual library with 4 manual drives, and use the front panel > of each TS3100 to move tapes from the I/O slot to the drive when TSM > requests a mount. > > (Actually the FIRST thing I thought of, was "cancel the DR contract, this > is > nonsense". But my customer isn't convinced yet...) > > Anybody got a better solution? > I've already tried a margarita, it didn't help > > W >
Re: Desperation, DR, and four TS3100 libraries...
Wanda, Yes, the Web interface would work, you would just have to pay attention to which screen you were on, since all four would look alike. I think it is a lot of key clicks for each tape mount, too, since the Web interface isn't meant to be a regular operator's interface, and doesn't have speed or ease-of-use in mind. Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 Toll Free: (866) 796-9226 Cell: (314) 750-8721 Original Message Subject: Re: [ADSM-L] Desperation, DR, and four TS3100 libraries... From: Wanda Prather Date: Fri, July 10, 2009 10:15 am To: ADSM-L@VM.MARIST.EDU Thanks John - I like your idea of the script to do the mounts! It also reminds me, those puppies have a web interface. We could do the moves with that, as well, if I can talk them into setting up 4 IP connections. If not, I'll crank up my perl skills... W On Fri, Jul 10, 2009 at 12:06 AM, John D. Schneider < john.schnei...@computercoachingcommunity.com> wrote: > Wanda, > My solution isn't much better, but here goes: > > 1) Like you said, define 1 manual library, 1 device class, with 4 LTO4 > drives, and get them all working and defined to the DR environment. > 2) You will be using the IBM drives, of course, so I am presuming the > IBM drivers will be installed by you or your DR vendor. > 3) Start a TSM administrator window in -console mode, so you can see the > tape mount requests. > 4) When your tape operator sees a tape mount request, he puts the > appropriate tape in the I/O door belonging to that tape drive's library. > 5) You didn't say if you were Unix, Linux, or Windows. I will explain > it as if it is AIX, and you can transpose. From a Unix shell window, > your tape operator uses tapeutil, the linemode library manager that > comes with the IBM drivers, to do the tape mounts for you. He can issue > the commands to move the tape from the element number of the I/O door > straight to the tape drive. > 6) When he sees an unmount request, he issues the tapeutil command to > move the tape from the drive to the I/O door, and puts the tape back in > the stack. > > If it were me tackling this one, I would write two short ksh scripts > called "tape_mount" and "tape_unmount" where the tape operator just puts > in which tape volser he is mounting, and which drive it should go in, > and let the ksh scripts translate that into the actual device name, and > tapeutil syntax, so there would be fewer mistakes. > > Also if it were me, I would build this experimentally using a tape > library or libraries and drives while still back home, so I could build > the script and debug it, then bring it with me to the DR exercise, and > all I would have to change would be the /dev/smcX and /dev/rmtX device > names, and start mounting tapes. > > Do you see any fatal flaws in this? It is a lot like your original > idea, but typing the mounts and unmounts on the faceplate of four > different TS3100's would drive me buggy. Hopefully this would be less > tedious. > > Best Regards, > > John D. Schneider > The Computer Coaching Community, LLC > Office: (314) 635-5424 > Toll Free: (866) 796-9226 > Cell: (314) 750-8721 > > > Original Message > Subject: [ADSM-L] Desperation, DR, and four TS3100 libraries... > From: Wanda Prather > Date: Thu, July 09, 2009 8:33 pm > To: ADSM-L@VM.MARIST.EDU > > I'm drawing a blank here, any suggestions welcomed. > > I have a TSM customer who makes their copypool tapes using a TS3200 with > LTO4 drives. > The TS3200 is a rack-mounted, 2 drive, 40-mumble slot standard ASCII > library. No issues. > One copy pool, tapes vaulted and sent offsite. > > They want to go to a commercial DR vendor site and do a DR test next > week. > The commercial DR vendor, unbelievably, has no multi-drive LTO4-capable > libraries. > > Instead, they want us to use 4 (count 'em, four) TS3100 libraries. > The TS3100 is a rack-mounted, 1 drive, 20-mumble slot standard ASCII > library. > > There's only 1 copy pool, so all tapes were created on the same device > class. > Ignoring the which-carts-would-go-in-which-library issue, I can't have a > device class pointing to 4 libraries. > > And, the TS3100 is built in such a way that unlike a TS3500, you can't > open > the doors and access the drives for manual mounting. > (I'd be happy to pull the covers off and try it, ignoring any warranties > I > might void, but I doubt the vendor will let me attack the thing with a > screwdriver/wrench/hacksaw.) > > If I put all the carts in one TS3100 that will work, but that leaves me > only > 1 drive to restore all the clients, and they won't likely get done in > the > desired time window. > > The only thing I can think of to use all 4 drives, is to define those > four > TS3100's as 1 manual library with 4 manual drives, and use the front > panel > of each TS3100 to move tapes from the I/O slot to the drive when TSM > requests a mount. > > (Actually the FIRST thing I thought of, was "
Re: SV: Desperation, DR, and four TS3100 libraries...
Michael, I don't see how a TSM Library Manager would help in this case. Perhaps you could explain further. It seems like to me the TSM Library Manager would still have to view the four TS3100 libraries as separate libraries, and then so would the client. And that is the rub; four separate libraries won't work if all tapes are in a single pool, single device class. Unless you are thinking of a configuration I am having trouble seeing. The Gresham software could perform this obfuscation, but unless the customer is already using it, it is another expense and another product to get to know just to support this one facet of their DR plan. I would have trouble arguing it was the "best" solution, since there are at least two other viable ways that have already been suggested that don't cost anything, and use the tools already at Wanda's disposal. Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 Toll Free: (866) 796-9226 Cell: (314) 750-8721 Original Message Subject: Re: [ADSM-L] SV: Desperation, DR, and four TS3100 libraries... From: Michael Hedden Date: Fri, July 10, 2009 12:44 pm To: ADSM-L@VM.MARIST.EDU Wanda, What about setting up a TSM Library Manager and have him control the library and drives for a TSM Library Client doing all the restores. From: Wanda Prather To: ADSM-L@VM.MARIST.EDU Sent: Friday, July 10, 2009 1:06:53 PM Subject: Re: SV: Desperation, DR, and four TS3100 libraries... Thanks - that's what I suspected! On Fri, Jul 10, 2009 at 1:01 PM, Bob Levad wrote: > Wanda, > > We actually tried 2 TS3100s in a test recovery. It didn't go very well. > > If you attempt it. > > The Gresham product should be able to present 1 library image to TSM. I > don't know at what cost. > > Without Gresham: > > Make sure your incremental DB backups are directed to disk or someplace > other than the already overloaded libraries. > > If you have a few months to prepare, break the copypool down to several > that > will individually fit in a 3100 and give each copypool it's own devclass. > > Even though the devclass breakdown is not needed at the home site, it will > allow you to re-design as needed in a recovery scenario. > > Bob. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Wanda Prather > Sent: Friday, July 10, 2009 10:31 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] SV: Desperation, DR, and four TS3100 libraries... > > Thanks Christian, and everyone, for the suggestions. > > Even if I can convince TSM to work with the tapes spread across the 4 > libraries, I think I still lose too much throughput. > > If I want to restore multiple clients/filespaces in parallel, I think we > could easily get into the situation that client 1 is using the drive in > library 1, and the restore for client 2 needs a tape that is also in > library > 1. The only way I can see to keep all 4 drives busy is to use them in > manual mode. (Short of doing MOVE NODEDATA to guarantee that every client > is on its own tape, which is highly unrealistic for a copy pool. Not that > this scenario is realistic to begin with!) > > Thanks everyone! > Wanda (maybe another margarita will bring more enlightenment..) > > > On Fri, Jul 10, 2009 at 5:58 AM, Christian Svensson < > christian.svens...@cristie.se> wrote: > > > Hi Wanda, > > On my way to work this morning I have been thinking about your > > situation and I think I have an idea how you can get it to work. But > > only for restore not for backup... :) I haven't try this yet and > > probably don't have time to test it for you. But I think this will > > work. > > > > Define 4 SCSI Libraries > > Define 4 Drives. 1 to each Library > > Create 3 NEW Copypool Device Class that is pointing to Library 2,3 and > > 4 (CopyClass2, CopyClass3, CopyClass4) And Update one Device Class to > > point to the 1st Library. > > Now do a Audit of the library with Owner=YOUR TSM SERVER > > > > In this stage does TSM know that ALL Tape are available but in > > different libraries. > > > > Technically it should work. The database knows what tape TSM need and > > only change the data entry-path for the tape in the same way it does > > with the "primary" (1st) Library you have. > > > > This is still just an crazy idea like always that I normally have. > > > > > > Best Regards > > Christian Svensson > > > > Cell: +46-70-325 1577 > > E-mail: christian.svens...@cristie.se > > Skype: cristie.christian.svensson > > > > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Wanda > > Prather [wprat...@jasi.com] > > Skickat: den 10 juli 2009 03:33 > > Till: ADSM-L@VM.MARIST.EDU > > Ämne: Desperation, DR, and four TS3100 libraries... > > > > I'm drawing a blank here, any suggestions welcomed. > > > > I have a TSM customer who makes their copypool tapes using a TS3200 > > with > > LTO4 dri
