Re: Configuring tape drives in TSM - Document Available
Me too will be glad to have a copy. E-Mail id -- [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Scott Sent: Wednesday, March 29, 2006 9:47 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Configuring tape drives in TSM - Document Available So would I - Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Wednesday, 29 March 2006 3:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Configuring tape drives in TSM - Document Available Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned. This email has been scanned for any virus infection at the sending end.
Re: Configuring tape drives in TSM - Document Available
Hello Miles, Could you send me a copy. My email address is [EMAIL PROTECTED] Best Regards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles This message and attachments are confidential and intended solely for the individual(s) stated in this message. If you received this message although you are not the addressee, you are responsible to keep the message confidential. The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments. Our company shall have no liability for any changes or late receiving, loss of integrity and confidentiality, viruses and any damages caused in anyway to your computer system. Bu mesaj ve ekleri, mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve gizlidir. Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi zorunlulugu tarafiniz icin de soz konusudur. Mesaj ve eklerinde yer alan bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin herhangi bir sorumlulugu bulunmamaktadir. Sirketimiz mesajin ve bilgilerinin size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize verebilecegi herhangi bir zarardan sorumlu tutulamaz.
Re: Antwort: Re: Configuring tape drives in TSM - Document Availa ble
As it seems, everyone would like to have a copy. It wouldn't be a bad idea to store it on a public ftp or website for everyone to download. If no one else will, I will donate some bandwith on my personal website. Otherwise, I would really appreciate a copy as well. Kind regards, Ilja G. Coolen ABP ES / EIS / EIO / Storage Management Telefoon : +31(0)45 579 7938 Fax : +31(0)45 579 3990 Email: [EMAIL PROTECTED] Centrale Mailbox : Centrale Mailbox - CM-Storage (eumbx05) - Everybody has a photographic memory, some just don't have film. - -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Christian Demnitz Sent: woensdag 29 maart 2006 8:53 To: ADSM-L@VM.MARIST.EDU Subject: Antwort: Re: Configuring tape drives in TSM - Document Available I would glad to get a copy! Christian Demnitz mailto:[EMAIL PROTECTED] =DISCLAIMER= De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u contact op te nemen met de afzender per kerende e-mail. Verder verzoeken wij u in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan niemand openbaar te maken. Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor daarbij overgebrachte virussen. The information contained in this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail; please delete in this case the e-mail and do not disclose its contents to any person. We don't accept liability for any errors, omissions, delays of receipt or viruses in the contents of this message which arise as a result of e-mail transmission.
Antwort: Re: Configuring tape drives in TSM - Document Available
I would glad to get a copy! Christian Demnitz mailto:[EMAIL PROTECTED]
Re: Configuring tape drives in TSM - Document Available
Miles, Would love to have a copy myself as well... My email address is [EMAIL PROTECTED] Regards. David Wellington Senior IT Specialist IBM Global Services - ITS Mobile : 07808 203796 Mobx : 276302 "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 28/03/2006 20:37 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Configuring tape drives in TSM - Document Available Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles
Re: Configuring tape drives in TSM - Document Available
I wish I had a copy of the original email Miles to be able to email you privately but unfortunately I must have deleted it. I am in the process of powering up 2 3584's now and sure would love a copy of this. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, March 28, 2006 11:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Configuring tape drives in TSM - Document Available Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles
Re: Configuring tape drives in TSM - Document Available
I am too would love a copy !!! Cheers Robert Ouzen [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, March 28, 2006 9:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Configuring tape drives in TSM - Document Available Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles
Re: Configuring tape drives in TSM - Document Available
Hi, I will be glad if u can share that document with me. sandeep -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Wednesday, March 29, 2006 1:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Configuring tape drives in TSM - Document Available Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles This email has been scanned for any virus infection at the sending end.
Re: Configuring tape drives in TSM - Document Available
So would I - Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Wednesday, 29 March 2006 3:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Configuring tape drives in TSM - Document Available Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned.
Survey question for all TSM users
TSM Development is interested in understanding how the following commands are used, if at all, in your environment: MOVE MEDIA - Do you use this command (Yes/No)? - If you use this command, what are your usage scenarios, i.e., how do you typically use this command? - Other comments? QUERY MEDIA - Do you use this command (Yes/No)? - If you use this command, what are your usage scenarios, i.e., how do you typically use this command? - Other comments? MOVE NODEDATA - Do you use this command (Yes/No)? - If you use this command, what are your usage scenarios, i.e., how do you typically use this command? - Other comments? QUERY NODEDATA - Do you use this command (Yes/No)? - If you use this command, what are your usage scenarios, i.e., how do you typically use this command? - Other comments? Please send your responses to me at [EMAIL PROTECTED] Responses sent directly to me will remain confidential within the IBM TSM development community. Thank you, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence.
dsmcad stops on linux servers
We have TSM Server and clients 5.2 On our Red Hat linux AS 3.0 clients I find that after I use the Backup-Archive GUI via Internet Explorer to perform backups or restores, the dsmcad process on that linux server dies within an hour or so. Is there any way to stop this from happening? Thanks Paul Dudley ANL IT Operations Dept. ANL Container Line [EMAIL PROTECTED] ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: TSM SERVER MIGRATION from STK ACSLS tape library to IBM 3584
Thank you. To ADSM-L@VM.MARIST.EDU cc From Sent by "Allen S. Rout" <[EMAIL PROTECTED]> on 03/28/2006 08:48 AM "ADSM: Dist Stor Manager" Subject Re: [ADSM-L] TSM SERVER MIGRATION from STK ACSLS tape library to IBM 3584 Please respond to "ADSM: Dist Stor Manager" >> On Tue, 28 Mar 2006 11:32:19 +1000, Steven Harris <[EMAIL PROTECTED]> said: > Here is one way to do a gradual migration. Superb advice. I'd suggest one embellishment: Set up the new primary stgpools, and the new-primary->new-copy housekeeping at the outset (step 2) . Then, set the old-primary stgpools to have RECLAIMSTGPOOLS of the corresponding new-primary. This takes one usually very heavy use of tape drives, and contributes its' efforts to the migration. It introduces the possibility that something might get written to old-primary, and then reclaimed to new-primary before it gets copied to old-copy, but that doesn't seem particularly likely, and the data in new-primary -will- get copied to new-copy. > 1. Set up your new library and devclasses to use it. > 2. set up a new set of copypools parallel to your old set of copypools, and > run backup stg commands on all your primary pools until the copypools on the > new library are up to date - this may take weeks, depending on how much data > is to be copied, but can be stopped and restarted as necessary. Change > housekeeping to copy new data to both new and old copypools. If you are > using 5.3 parallel processing commands watch for the limit of 16 parallel > commands at once. > 3. Once the copypools are caught up, you can change your housekeeping to > stop copying data to the old copypools. > 4. create a new set of primary pools to parallel your old setup. Change > your diskpools to migrate to the new primary pools. Change your > managementclasses that go straight to tape to point to the new primary > pools. Change your housekeeping to backup the new primary pools to the new > copypools. > 5. Make the nextstg of each of the old primary pools to be its new > equivalent. Run migration on the old pools to move the data off to the new > pools. The new migrate stg command with a duration will drip feed this over > time. > 6. Finally, when everything is copied, run del vol on each of the old > copypool volumes (discardd=yes will be needed) and any old primary pool > volumes (discardd=no) that need it, and clean up old definitions. - Allen S. Rout DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication does not form any contractual obligation on behalf of the sender or, the sender's employer, or the employer's parent company, affiliates or subsidiaries.
Re: TDP MSSQL on X86-64
Hi Paul, As Steve said... this is something we are working on right now. Look for something in the next month or so... standard disclaimers apply, i.e. this is not a guarantee and IBM reserves the right to change these dates and plans. Thanks, Del "ADSM: Dist Stor Manager" wrote on 03/28/2006 03:37:49 PM: > Hello all, > > > > > >Does somebody have any info about the release of a TDP for SQL Server > on x86_64? I know there is a version that runs on IA64 (Itanium), but we > are starting to get several requests from customers who are installing > W2K3 64bit/SQL Server 64bit on their new Xeon Servers and naturally > want to back up their databases. >
Re: TDP MSSQL on X86-64
Hi Paul ! Data Protection for SQL V5.2.1.3 does not work on the x64 Windows 2003 Advanced server on xeon processors. IBM has plans to add x64 support in 2006. Steve Paul van Dongen <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/28/2006 03:37:49 PM Please respond to "ADSM: Dist Stor Manager" Sent by:"ADSM: Dist Stor Manager" To:ADSM-L@VM.MARIST.EDU cc: Subject:TDP MSSQL on X86-64 Hello all, Does somebody have any info about the release of a TDP for SQL Server on x86_64? I know there is a version that runs on IA64 (Itanium), but we are starting to get several requests from customers who are installing W2K3 64bit/SQL Server 64bit on their new Xeon Servers and naturally want to back up their databases. Thanks in advance Paul Gondim van Dongen VANguard - Value Added Network guardians MCSE IBM Certified Deployment Professional Tivoli Storage Manager 5.2 & 5.3 Tivoli Workload Scheduler 8.2 IBM Certified Storage Administrator - ITSM V5 http://www.vanguard-it.com.br http://www.vanguard-it.com.br/> +55 81 3419-8094
TDP MSSQL on X86-64
Hello all, Does somebody have any info about the release of a TDP for SQL Server on x86_64? I know there is a version that runs on IA64 (Itanium), but we are starting to get several requests from customers who are installing W2K3 64bit/SQL Server 64bit on their new Xeon Servers and naturally want to back up their databases. Thanks in advance Paul Gondim van Dongen VANguard - Value Added Network guardians MCSE IBM Certified Deployment Professional Tivoli Storage Manager 5.2 & 5.3 Tivoli Workload Scheduler 8.2 IBM Certified Storage Administrator - ITSM V5 http://www.vanguard-it.com.br http://www.vanguard-it.com.br/> +55 81 3419-8094
Draft Redbook: IBM Tivoli Storage Management Concepts
Dear TSM'ers. A new draft (updated for TSM V5.3.2) of the popular Redbook IBM Tivoli Storage Management Concepts - is available for download at http://www.redbooks.ibm.com/redpieces/abstracts/sg244877.html?Open Note this is still a draft - it hasn't been completely tidied up yet - check back for updated versions till it goes final. A new version of the TSM Implementation Guide Redbook is also in the pipeline. Regards, Charlotte Brooks Project Leader and Certified IT Specialist IBM TotalStorage Solutions, ITSO San Jose email: [EMAIL PROTECTED] http://ibm.com/redbooks
Re: Configuring tape drives in TSM - Document Available
Would love to have a copy - thanks! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miles Purdy Sent: Thursday, March 23, 2006 12:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Configuring tape drives in TSM - Document Available Serval years ago a wrote a document on configuring tape drives in TSM for performance/redundancy. We had some problems today and I had to dig out the document. I looked through it and made a couple of minor updates. It still seems pretty relevant. I have not made updates to the sections on SCSI drives, but they are still included. The document includes a detailed example for AIX using fibre drives in an IBM 3584. Please email me directly if you would like the document. Miles
SUMMARY table tape mounts for Lan-Free
If you have a Lan-free client, so that your library is defined as SHARED, do the TAPE MOUNTS that show up in the SUMMARY table include the mounts for the Lan-free agent, or just the primary TSM server instance? Thanks for any insight.. Wanda Prather "* I/O, I/O, It's all about I/O *" -(me)
Re: Update - Tape problem after moving TSM to new server
Interesting. I've never seen one of our tapes do that. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Tuesday, March 28, 2006 1:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Update - Tape problem after moving TSM to new server >> On Tue, 28 Mar 2006 12:28:00 -0500, "Prather, Wanda" <[EMAIL PROTECTED]> said: > If a tape is is marked READWRITE/READINLY, it doesn't become > eligible for reclaimation until it is marked FULL. If a tape is > marked OFFSITE, it becomes eligible for reclamation as soon as > %reclaim is below the STGPOOL threshold. I don't think this is the case any more. Here's an onsite reclamation example taken from today on one of my servers; the stgpool is collocated, and this volume, while mostly empty, is also mostly reclaimable. I included two snapshots of the reclamation process to show it's not just picking the last or the first aggregate off the filling tape. Now, my batting percentage isn't too high these last few weeks; if there's something else bearing on reclamation target selection I'm neglecting, please someone point it out. but in any case, there are some filling tapes that are getting reclaimed. This is the behavior I wish wouldn't happen, instead leaving those drives idle so I could do something else with them. tsm: INT>q proc Process Process Description Status Number - 2,216 Space ReclamationVolume KA1402 (storage pool C-3590), Moved Files: 276838, Moved Bytes: 144,304,254,632, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 4,206,166 Current input volume: KA1402. Current output volume: KA0604. [...] Process Process Description Status Number - 2,216 Space ReclamationVolume KA1402 (storage pool C-3590), Moved Files: 276848, Moved Bytes: 144,309,809,938, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 195,800 Current input volume: KA1402. Current output volume: KA0604. tsm: INT>q vol KA1402 f=d Volume Name: KA1402 Storage Pool Name: C-3590 Device Class Name: 3590DEV Estimated Capacity: 40,960.0 Scaled Capacity Applied: Pct Util: 12.8 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 55.3 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 77 Write Pass Number: 1 Approx. Date Last Written: 03/28/06 08:16:35 Approx. Date Last Read: 03/28/06 13:15:51 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): Last Update Date/Time: 11/11/05 12:53:05 Begin Reclaim Period: End Reclaim Period: - Allen S. Rout
Re: Update - Tape problem after moving TSM to new server
>> On Tue, 28 Mar 2006 12:28:00 -0500, "Prather, Wanda" <[EMAIL PROTECTED]> >> said: > If a tape is is marked READWRITE/READINLY, it doesn't become > eligible for reclaimation until it is marked FULL. If a tape is > marked OFFSITE, it becomes eligible for reclamation as soon as > %reclaim is below the STGPOOL threshold. I don't think this is the case any more. Here's an onsite reclamation example taken from today on one of my servers; the stgpool is collocated, and this volume, while mostly empty, is also mostly reclaimable. I included two snapshots of the reclamation process to show it's not just picking the last or the first aggregate off the filling tape. Now, my batting percentage isn't too high these last few weeks; if there's something else bearing on reclamation target selection I'm neglecting, please someone point it out. but in any case, there are some filling tapes that are getting reclaimed. This is the behavior I wish wouldn't happen, instead leaving those drives idle so I could do something else with them. tsm: INT>q proc Process Process Description Status Number - 2,216 Space ReclamationVolume KA1402 (storage pool C-3590), Moved Files: 276838, Moved Bytes: 144,304,254,632, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 4,206,166 Current input volume: KA1402. Current output volume: KA0604. [...] Process Process Description Status Number - 2,216 Space ReclamationVolume KA1402 (storage pool C-3590), Moved Files: 276848, Moved Bytes: 144,309,809,938, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 195,800 Current input volume: KA1402. Current output volume: KA0604. tsm: INT>q vol KA1402 f=d Volume Name: KA1402 Storage Pool Name: C-3590 Device Class Name: 3590DEV Estimated Capacity: 40,960.0 Scaled Capacity Applied: Pct Util: 12.8 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 55.3 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 77 Write Pass Number: 1 Approx. Date Last Written: 03/28/06 08:16:35 Approx. Date Last Read: 03/28/06 13:15:51 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): Last Update Date/Time: 11/11/05 12:53:05 Begin Reclaim Period: End Reclaim Period: - Allen S. Rout
Re: Update - Tape problem after moving TSM to new server
If a tape is is marked READWRITE/READINLY, it doesn't become eligible for reclaimation until it is marked FULL. If a tape is marked OFFSITE, it becomes eligible for reclamation as soon as %reclaim is below the STGPOOL threshold. For most sites, this means tapes in the primary pool don't reclaim until they become full, tapes in the copy pool become eligible as soon as they are marked OFFSITE. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roger Deschner Sent: Tuesday, March 28, 2006 2:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Update - Tape problem after moving TSM to new server I have never seen reclamation take a Filling volume. I thought the Big Idea ever since the product was called WDSF was to fill up the Filling volumes until they are Full, let expiration gradually eat holes in them, and then reclaim them. What's the point in reclaiming a tape that isn't full yet? Even with collocation, I don't get it. If it isn't full yet, the only thing you should be doing to it is writing more data to it. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = What if there were no rhetorical questions? == On Mon, 27 Mar 2006, Richard Sims wrote: >On Mar 27, 2006, at 1:56 AM, Rainer Wolf wrote: > >> Hi, >> >> Roger Deschner wrote: >> >>> >>> 3. The Full tapes should reclaim themselves normally. However, >>> reclamation will not select any tape that is still marked as >>> Filling, so >>> you've got to reclaim them manually yourself with MOVE DATA. Might >>> take >>> a while, which is OK as long as you don't run out of tapes. >> >> Is it true ? I thought that reclamation can also affect >> volumes in filling state - why not ? > >Reclamation operates on any usable volume, regardless of Full or >Filling. Of course, when you get to the point of reclaiming Filling >volumes, reclamation may not then be a productive thing to do. > > Richard Sims >
Re: Prognosis for APAR IC45931
- Gerhard Ginzler wrote: - >I think, the problem is Open APAR IC48382, which causes the >significant >performance degradation. We start backup stgpool >xy to copypool, and 4 hours later we get either ANR2111W (There >is no data to process for stgpool xy) or the backup process >starts. The backup process itself is very slow, seems to hang. >Very annoying ... You are quite right. The question I should have asked is: When is there likely to be a TSM server maintenance level that fixes both IC48382 and IC47731 (preferably without introducing a third crippling performance bug)?
Re: TSM SERVER MIGRATION from STK ACSLS tape library to IBM 3584
>> On Tue, 28 Mar 2006 11:32:19 +1000, Steven Harris <[EMAIL PROTECTED]> said: > Here is one way to do a gradual migration. Superb advice. I'd suggest one embellishment: Set up the new primary stgpools, and the new-primary->new-copy housekeeping at the outset (step 2) . Then, set the old-primary stgpools to have RECLAIMSTGPOOLS of the corresponding new-primary. This takes one usually very heavy use of tape drives, and contributes its' efforts to the migration. It introduces the possibility that something might get written to old-primary, and then reclaimed to new-primary before it gets copied to old-copy, but that doesn't seem particularly likely, and the data in new-primary -will- get copied to new-copy. > 1. Set up your new library and devclasses to use it. > 2. set up a new set of copypools parallel to your old set of copypools, and > run backup stg commands on all your primary pools until the copypools on the > new library are up to date - this may take weeks, depending on how much data > is to be copied, but can be stopped and restarted as necessary. Change > housekeeping to copy new data to both new and old copypools. If you are > using 5.3 parallel processing commands watch for the limit of 16 parallel > commands at once. > 3. Once the copypools are caught up, you can change your housekeeping to > stop copying data to the old copypools. > 4. create a new set of primary pools to parallel your old setup. Change > your diskpools to migrate to the new primary pools. Change your > managementclasses that go straight to tape to point to the new primary > pools. Change your housekeeping to backup the new primary pools to the new > copypools. > 5. Make the nextstg of each of the old primary pools to be its new > equivalent. Run migration on the old pools to move the data off to the new > pools. The new migrate stg command with a duration will drip feed this over > time. > 6. Finally, when everything is copied, run del vol on each of the old > copypool volumes (discardd=yes will be needed) and any old primary pool > volumes (discardd=no) that need it, and clean up old definitions. - Allen S. Rout
Re: Update - Tape problem after moving TSM to new server
>> On Tue, 28 Mar 2006 00:59:53 -0600, Roger Deschner <[EMAIL PROTECTED]> said: > I have never seen reclamation take a Filling volume. I thought the > Big Idea ever since the product was called WDSF was to fill up the > Filling volumes until they are Full, let expiration gradually eat > holes in them, and then reclaim them. What's the point in reclaiming > a tape that isn't full yet? Even with collocation, I don't get > it. If it isn't full yet, the only thing you should be doing to it > is writing more data to it. I share this opinion. Acknowledging that there are times when it's a ridiculous distinction to make, ( i.e. 99% full volume that's 99% reclaimable ) the point of reclamation is to improve the chances you'll have somewhere to put byte N+1 that comes into your server. If you reclaim FILLING volumes, then you make them PENDING for [some time], so instead of having half-full, half-reclaimable volume, you've got a quarter-full volume and a PENDING volume; not much improvement in access, and in the meantime you are not-relcaiming the next, FULL volume. This would be especially relevant for FILE devclasses, especially**2 those sites which predefine their volumes; you deprive yourself of all of the ex-FILLING volume for reusedelay days. - Allen S. Rout
Re: Update - Tape problem after moving TSM to new server
Hello Roger I have seen it happen. We have collocate turned on for the tape storage pools. We had several clients that had very little in the way of changing data, with this usage pattern, we can see a filling tape that is mostly expired holes and it will reclaim. It does not happen very offen, but it does happen. len -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roger Deschner Sent: Tuesday, March 28, 2006 2:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Update - Tape problem after moving TSM to new server I have never seen reclamation take a Filling volume. I thought the Big Idea ever since the product was called WDSF was to fill up the Filling volumes until they are Full, let expiration gradually eat holes in them, and then reclaim them. What's the point in reclaiming a tape that isn't full yet? Even with collocation, I don't get it. If it isn't full yet, the only thing you should be doing to it is writing more data to it. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = What if there were no rhetorical questions? == On Mon, 27 Mar 2006, Richard Sims wrote: >On Mar 27, 2006, at 1:56 AM, Rainer Wolf wrote: > >> Hi, >> >> Roger Deschner wrote: >> >>> >>> 3. The Full tapes should reclaim themselves normally. However, >>> reclamation will not select any tape that is still marked as >>> Filling, so >>> you've got to reclaim them manually yourself with MOVE DATA. Might >>> take >>> a while, which is OK as long as you don't run out of tapes. >> >> Is it true ? I thought that reclamation can also affect >> volumes in filling state - why not ? > >Reclamation operates on any usable volume, regardless of Full or >Filling. Of course, when you get to the point of reclaiming Filling >volumes, reclamation may not then be a productive thing to do. > > Richard Sims >
RES: Mirroring the TSM System
Hello, I've just been through something like that. Had a customer who wanted a mirrored TSM across two sites, using disk (HDS) replication, 3584 libraries and HACMP (TSM on AIX) Please email me privately for more details. Paul Gondim van Dongen VANguard - Value Added Network guardians MCSE IBM Certified Deployment Professional Tivoli Storage Manager 5.2 & 5.3 Tivoli Workload Scheduler 8.2 IBM Certified Storage Administrator - ITSM V5 http://www.vanguard-it.com.br +55 81 3419-8094 -Mensagem original- De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Em nome de Rofie, Abu Bakar Enviada em: Monday, March 27, 2006 23:13 Para: ADSM-L@VM.MARIST.EDU Assunto: Mirroring the TSM System Hi there; My client would like to setup online mirroring for the hardware and system on their site. The problem is the have one TSM system with STK Powderhorn library; all the diskspool in Hitachi Disk (SAN). It that possible for us to setup the mirroring for the TSM; as I believe we can mirror the SAN but how with the TSM and the library. Any idea ? Thanks Abu Bakar Bin Rofie TSM System Administrator Kulicke & Soffa (OHQ) Malaysia Sdn Bhd 602, Level 6, Uptown 2 2 Jalan SS21/37 Damansara Uptown 47400 Petaling Jaya Selangor Darul Ehsan Tel : 603-7718 6684 Fax : 603-7728 5895
Re: TSM on MySQL
> One of my clients needs to perform TSM backup on MySQL. From IBM site found > that it should use adsmpipe to run it. I am unable to find the related > example and scripts for it. Any body there can help If disk space is not an issue, you may also use mysqlhotcopy to copy the database files to some other location and then backup the copy. Gruss, Andreas
Re: Update - Tape problem after moving TSM to new server
Hi, its really no problem but something changed since we are using the bigger 3592 drives - the volumes increased here from 40 GB -> 300 GB and at the same time we started to use group-collocation. After one year in use now Volumes are much more longer in 'filling'. So of course it's nothing else than to write to them. But anyway something else is happening: at the Moment the last byte is written on the volume and it changes to state 'FULL' the same volume more often will show for example 80 % reclaimable space. Just because of the longer time expiration can put the holes on it. The bigger the volumes are in use - the more you may think about those filling volumes . And I really would not care if a filling tape that already got much more than the estimated Capacity and would show let's say 80% reclaimable space then start to reclaim by the recalamation process - not by me :-) Regards, Rainer Roger Deschner wrote: > > I have never seen reclamation take a Filling volume. I thought the Big > Idea ever since the product was called WDSF was to fill up the Filling > volumes until they are Full, let expiration gradually eat holes in them, > and then reclaim them. What's the point in reclaiming a tape that isn't > full yet? Even with collocation, I don't get it. If it isn't full yet, > the only thing you should be doing to it is writing more data to it. > > Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] > = What if there were no rhetorical questions? == > > On Mon, 27 Mar 2006, Richard Sims wrote: > > >On Mar 27, 2006, at 1:56 AM, Rainer Wolf wrote: > > > >> Hi, > >> > >> Roger Deschner wrote: > >> > >>> > >>> 3. The Full tapes should reclaim themselves normally. However, > >>> reclamation will not select any tape that is still marked as > >>> Filling, so > >>> you've got to reclaim them manually yourself with MOVE DATA. Might > >>> take > >>> a while, which is OK as long as you don't run out of tapes. > >> > >> Is it true ? I thought that reclamation can also affect > >> volumes in filling state - why not ? > > > >Reclamation operates on any usable volume, regardless of Full or > >Filling. Of course, when you get to the point of reclaiming Filling > >volumes, reclamation may not then be a productive thing to do. > > > > Richard Sims > > -- Rainer Wolf eMail: [EMAIL PROTECTED] kiz - Abt. Infrastruktur Tel/Fax: ++49 731 50-22482/22471 Universitaet Ulm wwweb:http://kiz.uni-ulm.de
Re: Prognosis for APAR IC45931
I think, the problem is Open APAR IC48382, which causes the significant performance degradation. We start backup stgpool xy to copypool, and 4 hours later we get either ANR2111W (There is no data to process for stgpool xy) or the backup process starts. The backup process itself is very slow, seems to hang. Very annoying ... Regards, Gerhard Ginzler Medical University of Vienna Loon, E.J. van - SPLXM schrieb: Hi Thomas! APAR IC47731 was fixed in patch level 5.3.2.3 and IC45931 was fixed in 5.3.2.1. The most recent patch level is 5.3.2.4 and your version can be downloaded from ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/ser ver/Linux/5.3.2.4/s390x/ IBM just released a new client maintenance level and this probably means we have to wait a few months before a server maintenance release will be made available. In your case, I wouldn't wait for it and use the 5.3.2.4 patch release. Patch releases tend to be much more stable that they were in the past. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: maandag 27 maart 2006 22:20 To: ADSM-L@VM.MARIST.EDU Subject: Prognosis for APAR IC45931 We are running a mainframe Linux TSM server that is nearly out of CPU capacity. We would very much like to move to a code level with the fix for APAR IC47731, which causes a major waste of CPU capacity in mainframe Linux environments. At the moment, all levels with that fix suffer from the open APAR IC45931, which causes performance degradation for 'backup stgpool' processes reading from sequential storage pools. Since we already spend several hours per day running this type of process, this APAR would be a major problem for us. Does anyone know when there is likely to be a maintenace level that fixes both APAR's? ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Update - Tape problem after moving TSM to new server
Hi Gary I did as you suggested and commented out the entries in the /kernel/drv/st.conf file and now when I boot -r, I see just the 0 and 1 IBM entries that I wanted, so that's great news, many thanks. Now I just hope that it solves my strange little 'unable to write to filling tapes' problem. All the best Farren |-+---| | "Lee, Gary D."| | | <[EMAIL PROTECTED]>| | | | To| | 27/03/2006 15:05 | "Farren Minns" | | | <[EMAIL PROTECTED]> | | | cc| | | | | |Subject| | | Tape problem | | | | | | | | | | | | | | | | | | | |-+---| Sir: Are you ussing the same exact drives and libraries afor v2.9 as v2.7? As to your other question regarding st: Do you have a tape device other than the 3590 attached to the v2.9 server? If not, simply comment out all the scsi ids in the st.conf file. This will not let st grab a tape device. Gary Lee Senior System Programmer Ball State University -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.2/293 - Release Date: 3/26/2006 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
