Node OS and SP/ML level? Client level? Have you checked for the SNP bug?
[RC] On Friday, June 26, 2009, at 11:02AM, "Huebner,Andy,FORT WORTH,IT" <[email protected]> wrote: >The only times we have seen the nodes report internal program errors have been >when the TSM server was overloaded. The first time we moved the DB to faster >disks and the second time we reduced the number of simultaneous jobs. > >Andy Huebner >-----Original Message----- >From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Ochs, >Duane >Sent: Friday, June 26, 2009 11:58 AM >To: [email protected] >Subject: [ADSM-L] SAS and TSM > >Good day everyone, >I have a very interesting problem to discuss. I've been working on this since >Monday. >And think I have pinpointed the problem, but am more interested if anyone can >help me explain why it might be happening. > >We have a specific group of remote sites (14) using similar tools across the >US. >All except for two are using FC storage arrays, in all cases it is IBM DS >series hardware in one form or another. > >In two sites we are using Dell MD3000 SAS storage. >In these two sites my TSM backups are failing with Internal Program errors. >Insufficient resources. >Memoryefficientbackup is set to yes. I even set up disk caching for these two >sites. My backups are now going further but still failing. >After much searching I found a Windows KB article indicating this is a low >kernel memory issue. >And this is where we will be focusing our attention next. > >However, these two site are not very heavily utilized in comparison to the >rest of my installs. >All sites are running windows 2003 64-bit, using the exact same tools and the >data model for this site is similar to the rest, couple hundred thousand files >ranging from 2mb to 100mb with the average around 60 mb. All are using TSM >client 5.5.1.10. Server is AIX 5.3 TSM server version 5.4.3. > >My main concern is these are our only SAS sites and I'm trying to figure out >if this is inherent to the way this storage product utilizes kernel memory. >TSM is the only process on these machines that seem to be having problems. >Has anyone experienced this ? Or have any suggestions ? >Thanks, >Duane > > >This e-mail (including any attachments) is confidential and may be legally >privileged. If you are not an intended recipient or an authorized >representative of an intended recipient, you are prohibited from using, >copying or distributing the information in this e-mail or its attachments. If >you have received this e-mail in error, please notify the sender immediately >by return e-mail and delete all copies of this message and any attachments. >Thank you. > >
