My 6 boxes are TSM 5.5.3.0 on AIX 5.3.11. The change was to upgrade a driver from SDD to SDDPCM 2.2.03, whatever that means. On each machine I/O went to hell. On 3 backups went normally, but migration crawled. On the other 3 migrations went fine but backups were almost non-existent. The exception on all 6 was that TDP and SQLBacktrack went normally. We backed out the changes and things are back to normal.
The unanswered question that management wants to know is why the TDP weren't affected. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Xav Paice Sent: Wednesday, December 09, 2009 11:55 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] I/O thruput ----- "Fred Johanson" <f...@uchicago.edu> wrote: > Del and/or Andy can probably answer this, hopefully in a way that a > non-hardware/OS person, like me, can understand. > > Our hardware guy upgraded a driver on my 6 AIX boxen. As a result, my > thruput went to hell, with backups running, not at Kb/s, but bits/s. > But not on clients with the MSSQL or ORACLE TDP, or SQL-Backtrack. > Those clients went thru at the expected rate. My supposition is that > clients using the API use a different I/O path than regular clients. > > Enquiring minds want to know. this enquiring mind would like to know a bit more info: - what was updated and where - surely there's some details in the change request? - what is the TSM server, version, OS, hardware, etc? Is that where the update went? - what/where is the client? - I gather it's file backups from the AIX boxes that's slow? But the Windows ones are OK? What's the difference other than platform - do they go to different storage pools?
