Re: TSM 6.2 Slowness
Andrew, Perform the following action to see what is wrong with the volume: audit vol /tsmstg/001E.BFS fix=yes best regards, Kurt -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] Namens Andrew Carlson Verzonden: woensdag 12 mei 2010 4:32 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] TSM 6.2 Slowness I have been testing TSM 6.2 on a P570 P5 8 core 32GB box (I'm kinda lucky right now to have that as a test box). I am attending TSM 6.1 Advanced Admin and Tuning class right now, and found out some stuff about Deduplication that I didn't know. So, I went to delete all the filespaces in the system, which were very few, and it took much longer than I thought it would. The number on the process went up very slowly. This is a file type stgpool, so there is no shredding going on. Image my surprise, when I was done, the volumes were all still there! Query content showed no files, but delete volume creates a process, and each one runs forever. I just noticed this one, that failed: Session established with server TSMCAB1: AIX Server Version 6, Release 2, Level 0.0 Server date/time: 05/11/10 21:18:01 Last access: 05/11/10 20:59:16 ANS8000I Server command: 'del vol /tsmstg/001E.BFS discardd=yes wait=yes' ANR0984I Process 49 for DELETE VOLUME (DISCARD DATA) started in the FOREGROUND at 21:18:01. Error 82 deleting chunk 25026787 from volume /tsmstg/001E.BFS ANR0988I Process 49 for DELETE VOLUME (DISCARD DATA) running in the FOREGROUND processed 33,581,789,624 bytes with a completion state of FAILURE at 21:26:59. ANS8001I Return code 4. ANS8002I Highest return code was 4. So, server data/time of 20:59, the process didn't start until 21:18, and didn't finish until 21:26. I could understand this if it was a busy system, but this is ALL that it is doing. Any ideas out there? I checked before I wrote this, and there is no maintenance or patches for 6.2 yet. Thanks for any insight you might have. -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. *** Disclaimer *** Vlaamse Radio- en Televisieomroeporganisatie Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/disclaimer
Re: TSM 6.2 Slowness
You probably have database damage, which can result from running the server without the safeguards recommended in the Admin Guide manual. Running Query CONtent ... DAmaged=Yes on the volume may reveal the files in trouble. Richard Sims http://people.bu.edu/rbs/
Re: Securing TSM Client
Leandro - The problem you're dealing with is a personnel management one, which can't be solved by technology alone. The management there is the only avenue of solution. Technology can help, though. You can harvest records from the dsmaccnt.log to compile a report to management demonstrating the times and data amounts that inappropriate people have been performing TSM actions on that client, by virtue of field 7 containing a username whenever dsmc is invoked by an individual. You could go further by having a dsmadmc-based monitor performing Query SEssion Format=Detailed to look for sessions from that node: where the User Name is inappropriate, the monitor could then cancel the session and send a notification of the usage violation. Richard Simsat Boston University
Re: TSM 6.2 Slowness
Sorry, should have mentioned that I tried that. The audit did nothing. On Wed, May 12, 2010 at 2:03 AM, BEYERS Kurt kurt.bey...@vrt.be wrote: Andrew, Perform the following action to see what is wrong with the volume: audit vol /tsmstg/001E.BFS fix=yes best regards, Kurt -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] Namens Andrew Carlson Verzonden: woensdag 12 mei 2010 4:32 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] TSM 6.2 Slowness I have been testing TSM 6.2 on a P570 P5 8 core 32GB box (I'm kinda lucky right now to have that as a test box). I am attending TSM 6.1 Advanced Admin and Tuning class right now, and found out some stuff about Deduplication that I didn't know. So, I went to delete all the filespaces in the system, which were very few, and it took much longer than I thought it would. The number on the process went up very slowly. This is a file type stgpool, so there is no shredding going on. Image my surprise, when I was done, the volumes were all still there! Query content showed no files, but delete volume creates a process, and each one runs forever. I just noticed this one, that failed: Session established with server TSMCAB1: AIX Server Version 6, Release 2, Level 0.0 Server date/time: 05/11/10 21:18:01 Last access: 05/11/10 20:59:16 ANS8000I Server command: 'del vol /tsmstg/001E.BFS discardd=yes wait=yes' ANR0984I Process 49 for DELETE VOLUME (DISCARD DATA) started in the FOREGROUND at 21:18:01. Error 82 deleting chunk 25026787 from volume /tsmstg/001E.BFS ANR0988I Process 49 for DELETE VOLUME (DISCARD DATA) running in the FOREGROUND processed 33,581,789,624 bytes with a completion state of FAILURE at 21:26:59. ANS8001I Return code 4. ANS8002I Highest return code was 4. So, server data/time of 20:59, the process didn't start until 21:18, and didn't finish until 21:26. I could understand this if it was a busy system, but this is ALL that it is doing. Any ideas out there? I checked before I wrote this, and there is no maintenance or patches for 6.2 yet. Thanks for any insight you might have. -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. *** Disclaimer *** Vlaamse Radio- en Televisieomroeporganisatie Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/disclaimer -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
Re: TSM 6 database space performance question
While they are getting the advantage of the disk subsystem spreading the lun over many drives, they are not getting an advantage at the OS level of balanced I/O between the luns unless they are using some kind of OS level stripping. I'm not really familiar with Linux . . . are they using LVM and spreading the physical partitions across both luns, or, some kind of true striping across the luns? A lun is not just capacity, but also X amount of iops. If the 2 luns are simply concatinated then the iops of the new lun is going to be way under utilizied until the db grows into the space, and even then it will probably be unbalanced. This is also true for the disks in the storage system - the drives represent capacity (mb) as well as iops. A disk iin the array not carrying it's share of the i/o load is being wasted. Rick John D. Schneider john.schnei...@c To OMPUTERCOACHINGCO ADSM-L@VM.MARIST.EDU MMUNITY.COM cc Sent by: ADSM: Dist Stor Subject Manager TSM 6 database space performance ads...@vm.marist question .EDU 05/11/2010 04:21 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Greetings, I have a customer running TSM 6.1.3 on a Linux RedHat 5.4 server. They are using high-performance SAN attached disk for the TSM database and logs. They have created the TSM database all in one directory under one filesystem. Recently then needed to add more space, and they carved out a lun from another RAID group, and then added that lun to the existing filesystem. TSM shows that it now has the additional space, but it is still all under one directory. In reading the Performance Guide and Admin Guide, they both recommend spreading the data out over multiple directories, putting each directory behind separate disks/luns. This certainly makes sense to spread the I/O out over multiple luns, and I get that. But is there anything wrong with the way my customer has done it? They are using multiple luns from different RAID groups, but they are all put together behind one directory. Is this going to become a problem as they add more and more load to this instance? If TSM has lots of separate directories and they are across multiple luns, does TSM do it's database I/O differently? Best Regards, John D. Schneider The Computer Coaching Community, LLC Cell: (314) 750-8721 - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: TSM 6.2 Slowness
q content damaged=yes shows nothing also, just as q content showed nothing. Is it possible, that since I had deduplication turned on, it turned the files into chunks and it has way more chunks obviously than files, and that's why it's taking so long? I never got any deduplication, because the data never moved through reclamation or migration, but it might have still broken it up into chunks and stored extra DB entries for that. On Wed, May 12, 2010 at 5:44 AM, Richard Sims r...@bu.edu wrote: You probably have database damage, which can result from running the server without the safeguards recommended in the Admin Guide manual. Running Query CONtent ... DAmaged=Yes on the volume may reveal the files in trouble. Richard Sims http://people.bu.edu/rbs/ -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
Re: TSM 6.2 Slowness
Andy - This might be APAR IC67982. You are running TSM 6.1 with no maintenance, and looks like it needs some. Richard Sims
Re: TSM 6.2 Slowness
I am running TSM 6.2 . . . with no maintenance. On Wed, May 12, 2010 at 8:50 AM, Richard Sims r...@bu.edu wrote: Andy - This might be APAR IC67982. You are running TSM 6.1 with no maintenance, and looks like it needs some. Richard Sims -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
Re: Securing TSM Client
Humm...that's interesting...I'll take a look ! Thanks Richard ! On Wed, May 12, 2010 at 8:18 AM, Richard Sims r...@bu.edu wrote: Leandro - The problem you're dealing with is a personnel management one, which can't be solved by technology alone. The management there is the only avenue of solution. Technology can help, though. You can harvest records from the dsmaccnt.log to compile a report to management demonstrating the times and data amounts that inappropriate people have been performing TSM actions on that client, by virtue of field 7 containing a username whenever dsmc is invoked by an individual. You could go further by having a dsmadmc-based monitor performing Query SEssion Format=Detailed to look for sessions from that node: where the User Name is inappropriate, the monitor could then cancel the session and send a notification of the usage violation. Richard Simsat Boston University -- __ Leandro Mazur
Re: Securing TSM Client
Intended for firewall security, the sessioninitiation property on the nodes may work for this. You will have to disable the setting if anyone actually wanted to do a manual backup or restore from the client side, but that's a quick upd n Only the TSM Server would be allowed to start client sessions. Regards, Shawn Shawn Drew Internet leandroma...@gmail.com Sent by: ADSM-L@VM.MARIST.EDU 05/11/2010 04:08 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Securing TSM Client Hello everyone ! I don't know if somebody has this kind of problem, but I have the following situation in the company I work for: - We have a TSM team to install, configure and maintain the whole backup process, server and client; - We have sysadmins that take care of the operational system and the applications; - When there's a need for any action to do with backup, they should open a ticket for the TSM team; The problem that we have is that the sysadmins are doing backups/archives and restores/retrieves without our knowledge, with great impact on our database (among other things...). We would like to block the access on the client, but we were not successful. If we use password generate on dsm.sys, the password is prompted only at first access. If we use password prompt, the scheduler doesn't work (ANS2050E)... Any sugestions from the experts ? Maybe it could be a improvement to IBM implement on the future... __ Leandro Mazur This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: TSM 6.2 Slowness
Have you tried to restore failed volume from copy pool? Copy pools are without deduplication and damaged deduplicated data can be recovered and thaen removed. From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Andrew Carlson [naclos...@gmail.com] Sent: Wednesday, May 12, 2010 4:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 6.2 Slowness q content damaged=yes shows nothing also, just as q content showed nothing. Is it possible, that since I had deduplication turned on, it turned the files into chunks and it has way more chunks obviously than files, and that's why it's taking so long? I never got any deduplication, because the data never moved through reclamation or migration, but it might have still broken it up into chunks and stored extra DB entries for that. On Wed, May 12, 2010 at 5:44 AM, Richard Sims r...@bu.edu wrote: You probably have database damage, which can result from running the server without the safeguards recommended in the Admin Guide manual. Running Query CONtent ... DAmaged=Yes on the volume may reveal the files in trouble. Richard Sims http://people.bu.edu/rbs/ -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: reclamation no longer working
I had the same problem and offsitereclaimlimit=20 (or whatever you want to limit it to) worked for me. In my particular situation my server is 5.4.1.0 (I know, very old!) running on AIX 5.3 (5300-09-01-0847). I have a few (less than 5-10) tapes at a 99% reclaimable level in my offsite COPYPOOL01 tapes, but about 500 tapes that are 98% reclaimable. If I do NOT specify a offsitereclaimlimit number it seems to process tapes to reclaim at about 3 tapes per minute. So for 500 tapes it just sits there for about 3 HOURS before it even starts mounting tapes to start the reclamation. I stumbled onto how useful this particular option was about 3 or 4 months ago thanks to this forum, before that I didn't have a clue what it was supposed to be used for. Limiting it to 20 tapes lets it actually start mounting tapes and moving files in about 6 or 7 minutes. I also noted that in a recent posting in this forum, IBM has fixed the order in which tapes are reclaimed, and if you specify something like 90%, it will start with 99% first, then 98%, 97%, and so on until it finishes or runs out of time. This solves my biggest gripe about reclamation that I have had. I have two new servers that will soon be in production, and they are running the 6.2 TSM, so they should reclaim much faster. John John M. Ritter Systems Software Specialist Vanderbilt University Medical Center Email: john.rit...@vanderbilt.edu -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Tyree, David Sent: Friday, May 07, 2010 7:46 AM To: ADSM-L@vm.marist.edu Subject: Re: reclamation no longer working I started a reclamation on that pool yesterday afternoon and it sat there for several hours before it finally started moving anything. I guess I got behind doing the reclamation. But that doesn't make any sense because the offsite pool and the onsite pool have the same settings and the same content. Only difference is that one goes off site. I use the same settings when I run reclamation on both pools but I run them at completely different times and the times don't overlap. When I run the onsite copypool script the process starts without delay. The same settings for the offsite copypool takes forever to actually kick off. I guess I'll need to keep a closer eye on things -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Allen S. Rout Sent: Thursday, May 06, 2010 2:17 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] reclamation no longer working On Thu, 6 May 2010 11:11:34 -0400, Tyree, David david.ty...@sgmc.org said: I've run the threshold up and down from a few percentage points up to 80-90% hoping something would change but no difference. I have plenty of scratch tapes and mount points. Try running one at 99% and _no_ time limit, and expect it to run for days. There's a huge amount of bookkeeping work TSM does at the outset. If you've gotten yourself stuck somewhere, and lots of time has passed, you may have a large backlog. In that case, trying little nibbles is the only way to go. You could also approach this from the -OFFSITERECLAIMLimit--=--number_of_volumes- side, limiting it to just a few at a time. - Allen S. Rout
RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers
Greetings, I have a customer running TSM 6.1.3.3 under RedHat Linux 5.2. The Library Master instance on this server has a HP ESL722 tape library with LTO4 tape drives, and a HP VTL emulating a ESL tape library with LTO3 drives. They are running the TSMscsi drivers to talk to the drives, version TIVsm-tsmscsi-6.1.3-1.x86_64. Any time they reboot the server, they execute: cd /opt/tivoli/tsm/devices/bin ./autoconf -a which loads the tsmscsi driver and configures the drives. This has been working fine for months now. The output is: ** * IBM TIVOLI STORAGE MANAGER * * Autoconf Utility Program for Linux * ** Licensed Materials - Property of IBM (C) Copyright IBM Corporation 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Added the read and write permissions for all users to /dev/sg35. Added the read and write permissions for all users to /dev/sg36. Added the read and write permissions for all users to /dev/sg37. Added the read and write permissions for all users to /dev/sg38. Added the read and write permissions for all users to /dev/sg39. Added the read and write permissions for all users to /dev/sg40. Added the read and write permissions for all users to /dev/sg41. Added the read and write permissions for all users to /dev/sg42. Added the read and write permissions for all users to /dev/sg43. Added the read and write permissions for all users to /dev/sg44. Added the read and write permissions for all users to /dev/sg45. Added the read and write permissions for all users to /dev/sg46. Added the read and write permissions for all users to /dev/sg47. Added the read and write permissions for all users to /dev/sg48. Added the read and write permissions for all users to /dev/sg49. Added the read and write permissions for all users to /dev/sg50. Added the read and write permissions for all users to /dev/sg51. Added the read and write permissions for all users to /dev/sg52. Added the read and write permissions for all users to /dev/sg53. Added the read and write permissions for all users to /dev/sg54. Added the read and write permissions for all users to /dev/sg55. Added the read and write permissions for all users to /dev/sg56. Added the read and write permissions for all users to /dev/sg57. Added the read and write permissions for all users to /dev/sg58. Added the read and write permissions for all users to /dev/sg59. Added the read and write permissions for all users to /dev/sg60. Added the read and write permissions for all users to /dev/sg61. Added the read and write permissions for all users to /dev/sg62. Added the read and write permissions for all users to /dev/sg63. Added the read and write permissions for all users to /dev/sg64. Added the read and write permissions for all users to /dev/sg65. Added the read and write permissions for all users to /dev/sg66. Tivoli Tape Drives: === Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number Product_ID Rev. 000 035 001 000 000 000 001 HPMXP09210N5 Ultrium 4-SCSI H36W 001 036 001 000 001 000 001 HPHU18282JH5 Ultrium 4-SCSI H36W 002 037 001 000 002 000 001 HPHU17340A0J Ultrium 4-SCSI H36W 003 038 001 000 003 000 001 HPMXP09210MC Ultrium 4-SCSI H36W 004 040 003 000 001 000 001 HPHU18494CGF Ultrium 4-SCSI H36W 005 041 003 000 002 000 001 HPMXP09190H5 Ultrium 4-SCSI H36W 006 042 003 000 003 000 001 HPHU19024M8Y Ultrium 4-SCSI H36W 007 044 004 000 000 001 001 HP025qFkNO01 Ultrium 3-SCSI R210 008 045 004 000 000 002 001 HP025qFkNO02 Ultrium 3-SCSI R210 009 046 004 000 000 003 001 HP025qFkNO03 Ultrium 3-SCSI R210 010 047 004 000 000 004 001 HP025qFkNO04 Ultrium 3-SCSI R210 011 048 004 000 000 005 001 HP025qFkNO05 Ultrium 3-SCSI R210 012 049 004 000 000 006 001 HP025qFkNO06 Ultrium 3-SCSI R210 013 050 004 000 000 007 001 HP025qFkNO07 Ultrium 3-SCSI R210 014 051 005 000 000 000 001 HPHU17430JKJ Ultrium 4-SCSI H36W 015 052 005 000 001 000 001 HPMXP09190H4 Ultrium 4-SCSI H36W 016 053 005 000 002 000 001 HPHU18413JBJ Ultrium 4-SCSI H36W 017 054 005 000 003 000 001 HPMXP09170DG Ultrium 4-SCSI H36W 018 055 006 000 000 000 001 HP025qFkNO08 Ultrium 3-SCSI R210 019 056 006 000 000 001 001 HP025qFkNO09 Ultrium 3-SCSI R210 020 057 006 000 000 002 001 HP025qFkNO0a Ultrium 3-SCSI R210 021
Re: Securing TSM Client
I've tested this optionit works well, but in cases where the schedule calls a script, didn't worked because the client could not start the session... On Wed, May 12, 2010 at 12:32 PM, Shawn Drew shawn.d...@americas.bnpparibas.com wrote: Intended for firewall security, the sessioninitiation property on the nodes may work for this. You will have to disable the setting if anyone actually wanted to do a manual backup or restore from the client side, but that's a quick upd n Only the TSM Server would be allowed to start client sessions. Regards, Shawn Shawn Drew Internet leandroma...@gmail.com Sent by: ADSM-L@VM.MARIST.EDU 05/11/2010 04:08 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Securing TSM Client Hello everyone ! I don't know if somebody has this kind of problem, but I have the following situation in the company I work for: - We have a TSM team to install, configure and maintain the whole backup process, server and client; - We have sysadmins that take care of the operational system and the applications; - When there's a need for any action to do with backup, they should open a ticket for the TSM team; The problem that we have is that the sysadmins are doing backups/archives and restores/retrieves without our knowledge, with great impact on our database (among other things...). We would like to block the access on the client, but we were not successful. If we use password generate on dsm.sys, the password is prompted only at first access. If we use password prompt, the scheduler doesn't work (ANS2050E)... Any sugestions from the experts ? Maybe it could be a improvement to IBM implement on the future... __ Leandro Mazur This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. -- __ Leandro Mazur
Re: RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers
Did you upgrade the tape drivers? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 5:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Greetings, I have a customer running TSM 6.1.3.3 under RedHat Linux 5.2. The Library Master instance on this server has a HP ESL722 tape library with LTO4 tape drives, and a HP VTL emulating a ESL tape library with LTO3 drives. They are running the TSMscsi drivers to talk to the drives, version TIVsm-tsmscsi-6.1.3-1.x86_64. Any time they reboot the server, they execute: cd /opt/tivoli/tsm/devices/bin ./autoconf -a which loads the tsmscsi driver and configures the drives. This has been working fine for months now. The output is: ** * IBM TIVOLI STORAGE MANAGER * * Autoconf Utility Program for Linux * ** Licensed Materials - Property of IBM (C) Copyright IBM Corporation 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Added the read and write permissions for all users to /dev/sg35. Added the read and write permissions for all users to /dev/sg36. Added the read and write permissions for all users to /dev/sg37. Added the read and write permissions for all users to /dev/sg38. Added the read and write permissions for all users to /dev/sg39. Added the read and write permissions for all users to /dev/sg40. Added the read and write permissions for all users to /dev/sg41. Added the read and write permissions for all users to /dev/sg42. Added the read and write permissions for all users to /dev/sg43. Added the read and write permissions for all users to /dev/sg44. Added the read and write permissions for all users to /dev/sg45. Added the read and write permissions for all users to /dev/sg46. Added the read and write permissions for all users to /dev/sg47. Added the read and write permissions for all users to /dev/sg48. Added the read and write permissions for all users to /dev/sg49. Added the read and write permissions for all users to /dev/sg50. Added the read and write permissions for all users to /dev/sg51. Added the read and write permissions for all users to /dev/sg52. Added the read and write permissions for all users to /dev/sg53. Added the read and write permissions for all users to /dev/sg54. Added the read and write permissions for all users to /dev/sg55. Added the read and write permissions for all users to /dev/sg56. Added the read and write permissions for all users to /dev/sg57. Added the read and write permissions for all users to /dev/sg58. Added the read and write permissions for all users to /dev/sg59. Added the read and write permissions for all users to /dev/sg60. Added the read and write permissions for all users to /dev/sg61. Added the read and write permissions for all users to /dev/sg62. Added the read and write permissions for all users to /dev/sg63. Added the read and write permissions for all users to /dev/sg64. Added the read and write permissions for all users to /dev/sg65. Added the read and write permissions for all users to /dev/sg66. Tivoli Tape Drives: === Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number Product_ID Rev. 000 035 001 000 000 000 001 HPMXP09210N5 Ultrium 4-SCSI H36W 001 036 001 000 001 000 001 HPHU18282JH5 Ultrium 4-SCSI H36W 002 037 001 000 002 000 001 HPHU17340A0J Ultrium 4-SCSI H36W 003 038 001 000 003 000 001 HPMXP09210MC Ultrium 4-SCSI H36W 004 040 003 000 001 000 001 HPHU18494CGF Ultrium 4-SCSI H36W 005 041 003 000 002 000 001 HPMXP09190H5 Ultrium 4-SCSI H36W 006 042 003 000 003 000 001 HPHU19024M8Y Ultrium 4-SCSI H36W 007 044 004 000 000 001 001 HP025qFkNO01 Ultrium 3-SCSI R210 008 045 004 000 000 002 001 HP025qFkNO02 Ultrium 3-SCSI R210 009 046 004 000 000 003 001 HP025qFkNO03 Ultrium 3-SCSI R210 010 047 004 000 000 004 001 HP025qFkNO04 Ultrium 3-SCSI R210 011 048 004 000 000 005 001 HP025qFkNO05 Ultrium 3-SCSI R210 012 049 004 000 000 006 001 HP025qFkNO06 Ultrium 3-SCSI R210 013 050 004 000 000 007 001 HP025qFkNO07 Ultrium 3-SCSI R210 014 051 005 000 000 000 001 HPHU17430JKJ Ultrium 4-SCSI H36W 015 052 005 000 001 000 001 HPMXP09190H4 Ultrium 4-SCSI H36W 016 053 005 000 002 000 001 HPHU18413JBJ Ultrium 4-SCSI H36W 017 054 005 000 003 000 001 HP
Re: RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers
Len, Thanks for your reply. No, we did not upgrade any of the TSM software, including the tape drivers. We were running the TIVsm-tsmscsi-6.1.3-1.x86_64 version both before and after the RedHat 5.2 to 5.4 upgrade. I have since found out that there is a 6.1.3-3 version of the driver. Since they are running the 6.1.3.3 version of TSM, they probably should be running that version of the driver, too. I don't know why or why not, since that is before they became my customer. The previous TSM admins that set all this up are no longer working for this company. But I hesitate to recommend upgrading the drivers as a course of action unless I can point to a concrete reason why. I went through the Release Notes and Readmes and could not find any hint of a driver problem being addressed. None of the tape driver APARs described since 6.1.3 in this Technote sound like they have anything to do with our problem: http://www-01.ibm.com/support/docview.wss?uid=swg21320763 Any insight would be appreciated. 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] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Len Boyle len.bo...@sas.com Date: Wed, May 12, 2010 8:53 pm To: ADSM-L@VM.MARIST.EDU Did you upgrade the tape drivers? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 5:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Greetings, I have a customer running TSM 6.1.3.3 under RedHat Linux 5.2. The Library Master instance on this server has a HP ESL722 tape library with LTO4 tape drives, and a HP VTL emulating a ESL tape library with LTO3 drives. They are running the TSMscsi drivers to talk to the drives, version TIVsm-tsmscsi-6.1.3-1.x86_64. Any time they reboot the server, they execute: cd /opt/tivoli/tsm/devices/bin ./autoconf -a which loads the tsmscsi driver and configures the drives. This has been working fine for months now. The output is: ** * IBM TIVOLI STORAGE MANAGER * * Autoconf Utility Program for Linux * ** Licensed Materials - Property of IBM (C) Copyright IBM Corporation 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Added the read and write permissions for all users to /dev/sg35. Added the read and write permissions for all users to /dev/sg36. Added the read and write permissions for all users to /dev/sg37. Added the read and write permissions for all users to /dev/sg38. Added the read and write permissions for all users to /dev/sg39. Added the read and write permissions for all users to /dev/sg40. Added the read and write permissions for all users to /dev/sg41. Added the read and write permissions for all users to /dev/sg42. Added the read and write permissions for all users to /dev/sg43. Added the read and write permissions for all users to /dev/sg44. Added the read and write permissions for all users to /dev/sg45. Added the read and write permissions for all users to /dev/sg46. Added the read and write permissions for all users to /dev/sg47. Added the read and write permissions for all users to /dev/sg48. Added the read and write permissions for all users to /dev/sg49. Added the read and write permissions for all users to /dev/sg50. Added the read and write permissions for all users to /dev/sg51. Added the read and write permissions for all users to /dev/sg52. Added the read and write permissions for all users to /dev/sg53. Added the read and write permissions for all users to /dev/sg54. Added the read and write permissions for all users to /dev/sg55. Added the read and write permissions for all users to /dev/sg56. Added the read and write permissions for all users to /dev/sg57. Added the read and write permissions for all users to /dev/sg58. Added the read and write permissions for all users to /dev/sg59. Added the read and write permissions for all users to /dev/sg60. Added the read and write permissions for all users to /dev/sg61. Added the read and write permissions for all users to /dev/sg62. Added the read and write permissions for all users to /dev/sg63. Added the read and write permissions for all users to /dev/sg64. Added the read and write permissions for all users to /dev/sg65. Added the read and write permissions for all users to /dev/sg66. Tivoli Tape Drives: === Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number Product_ID Rev. 000 035 001 000 000 000 001 HP MXP09210N5 Ultrium 4-SCSI H36W 001 036 001 000 001 000 001 HP HU18282JH5 Ultrium 4-SCSI H36W 002 037 001 000 002 000 001 HP HU17340A0J Ultrium 4-SCSI
Re: RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers
Hello John, I have not used tsm on Linux, but I have used ibm tape drives on linux. I used the ibm lintape driver. These tape drives were fc based. I am not sure if your tape drives are fc based. I am also not sure if the lintape driver supports scsi tape drives. I do have a tsm server running on windows and they recommended that we use the ibm tape drivers and not the tsm drivers for the newer tape drives. So I am doing a bit of guessing here. Since the tape driver is the piece between the os and the hardware I would expect that be the first part that needs looking at. It might be a change in the o/s api used by the tape driver. With the lintape driver you can test out the tape drive without tsm running. Do you have another box that you can test out the different tape drivers and tape drives? I just looked at the lintape readme and it appears that it only is supported with IBM devices. Does HP supply drivers for use with their tape drives and Linux? You might want to call IBM service for tsm and see what they might suggest. - I remember seeing this note on a past adsm-l mailing list entry. Re: Library unavailable Michael Green Mon, 06 Jul 2009 23:23:45 -0700 I don't know about 3583, but with 3584 one shouldn't use the TSM supplied drivers. IBM provides a so called 'lintape' (ex IBMtape) driver on their FTP. -- len -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 11:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Len, Thanks for your reply. No, we did not upgrade any of the TSM software, including the tape drivers. We were running the TIVsm-tsmscsi-6.1.3-1.x86_64 version both before and after the RedHat 5.2 to 5.4 upgrade. I have since found out that there is a 6.1.3-3 version of the driver. Since they are running the 6.1.3.3 version of TSM, they probably should be running that version of the driver, too. I don't know why or why not, since that is before they became my customer. The previous TSM admins that set all this up are no longer working for this company. But I hesitate to recommend upgrading the drivers as a course of action unless I can point to a concrete reason why. I went through the Release Notes and Readmes and could not find any hint of a driver problem being addressed. None of the tape driver APARs described since 6.1.3 in this Technote sound like they have anything to do with our problem: http://www-01.ibm.com/support/docview.wss?uid=swg21320763 Any insight would be appreciated. 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] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Len Boyle len.bo...@sas.com Date: Wed, May 12, 2010 8:53 pm To: ADSM-L@VM.MARIST.EDU Did you upgrade the tape drivers? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 5:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Greetings, I have a customer running TSM 6.1.3.3 under RedHat Linux 5.2. The Library Master instance on this server has a HP ESL722 tape library with LTO4 tape drives, and a HP VTL emulating a ESL tape library with LTO3 drives. They are running the TSMscsi drivers to talk to the drives, version TIVsm-tsmscsi-6.1.3-1.x86_64. Any time they reboot the server, they execute: cd /opt/tivoli/tsm/devices/bin ./autoconf -a which loads the tsmscsi driver and configures the drives. This has been working fine for months now. The output is: ** * IBM TIVOLI STORAGE MANAGER * * Autoconf Utility Program for Linux * ** Licensed Materials - Property of IBM (C) Copyright IBM Corporation 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Added the read and write permissions for all users to /dev/sg35. Added the read and write permissions for all users to /dev/sg36. Added the read and write permissions for all users to /dev/sg37. Added the read and write permissions for all users to /dev/sg38. Added the read and write permissions for all users to /dev/sg39. Added the read and write permissions for all users to /dev/sg40. Added the read and write permissions for all users to /dev/sg41. Added the read and write permissions for all users to /dev/sg42. Added the read and
Re: RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers
Len, The IBMTape drivers are intended only for the IBM tape drives. For all others (such as the HP in my case), the TSM drivers are what TSM wants us to use. So I believe that we are using the right sort of driver, and it has been working for some months; the problem only arose when we upgraded RedHat from 5.2 to 5.4. 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] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Len Boyle len.bo...@sas.com Date: Wed, May 12, 2010 11:29 pm To: ADSM-L@VM.MARIST.EDU Hello John, I have not used tsm on Linux, but I have used ibm tape drives on linux. I used the ibm lintape driver. These tape drives were fc based. I am not sure if your tape drives are fc based. I am also not sure if the lintape driver supports scsi tape drives. I do have a tsm server running on windows and they recommended that we use the ibm tape drivers and not the tsm drivers for the newer tape drives. So I am doing a bit of guessing here. Since the tape driver is the piece between the os and the hardware I would expect that be the first part that needs looking at. It might be a change in the o/s api used by the tape driver. With the lintape driver you can test out the tape drive without tsm running. Do you have another box that you can test out the different tape drivers and tape drives? I just looked at the lintape readme and it appears that it only is supported with IBM devices. Does HP supply drivers for use with their tape drives and Linux? You might want to call IBM service for tsm and see what they might suggest. - I remember seeing this note on a past adsm-l mailing list entry. Re: Library unavailable Michael Green Mon, 06 Jul 2009 23:23:45 -0700 I don't know about 3583, but with 3584 one shouldn't use the TSM supplied drivers. IBM provides a so called 'lintape' (ex IBMtape) driver on their FTP. -- len -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 11:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Len, Thanks for your reply. No, we did not upgrade any of the TSM software, including the tape drivers. We were running the TIVsm-tsmscsi-6.1.3-1.x86_64 version both before and after the RedHat 5.2 to 5.4 upgrade. I have since found out that there is a 6.1.3-3 version of the driver. Since they are running the 6.1.3.3 version of TSM, they probably should be running that version of the driver, too. I don't know why or why not, since that is before they became my customer. The previous TSM admins that set all this up are no longer working for this company. But I hesitate to recommend upgrading the drivers as a course of action unless I can point to a concrete reason why. I went through the Release Notes and Readmes and could not find any hint of a driver problem being addressed. None of the tape driver APARs described since 6.1.3 in this Technote sound like they have anything to do with our problem: http://www-01.ibm.com/support/docview.wss?uid=swg21320763 Any insight would be appreciated. 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] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Len Boyle len.bo...@sas.com Date: Wed, May 12, 2010 8:53 pm To: ADSM-L@VM.MARIST.EDU Did you upgrade the tape drivers? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 5:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Greetings, I have a customer running TSM 6.1.3.3 under RedHat Linux 5.2. The Library Master instance on this server has a HP ESL722 tape library with LTO4 tape drives, and a HP VTL emulating a ESL tape library with LTO3 drives. They are running the TSMscsi drivers to talk to the drives, version TIVsm-tsmscsi-6.1.3-1.x86_64. Any time they reboot the server, they execute: cd /opt/tivoli/tsm/devices/bin ./autoconf -a which loads the tsmscsi driver and configures the drives. This has been working fine for months now. The output is: ** * IBM TIVOLI STORAGE MANAGER * * Autoconf Utility Program for Linux * ** Licensed Materials - Property of IBM (C) Copyright IBM Corporation 2009. All rights reserved. U.S.
