Backup Central

Hello,

I was wondering if anyone is experiencing memory issues since upgrading to
TSM server 5.5 and installation of Centera SDK 3.2.1?

Starting with TSM 5.5 the Centera SDK had to be installed separately where
in the past the Centera SDK was part of the install package. We have
noticed that since upgrading our TSM server from 5.2 to 5.5 that large
amount of memory is being used which we suspected it was coming from the
dsmserv process. Each time the pages are freed is when we have killed
the dsmserv process. We made NO changes to the OS and the only change
was the upgrade of the TSM server from 5.2 to 5.5.

We opened a call with IBM TSM support which in turn had us run some data
collection scripts for a few days. In summary, IBM confirmed that a
large amount of memory is being used. It is not being used by any dsmserv
subsystem however.

We opened a ticket with AIX support which in turn rerouted the ticket back
to IBM TSM support. We are hashing out where the ticket is supposed to
be assigned and worked. Meanwhile, there has been no movement on the
call and was curious to see if anyone else using the Centera SDK and TSM
5.5 has experienced the same problem.






Background:
Upgraded our TSM server from 5.2 to 5.5.0.
OS: Aix 5.3
Installed SDK 3.2.1 per IBM TSM install instruction



Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979

CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original
message.

Nancy -

Confer with your AIX people on identifying processes using the most
memory in your server system, where 'ps' and various other monitoring
facilities can report what's using what.

In TSM, you can use the SHow MEMory command to report a summary of
memory usage and the SHow ALLOC command to report by module. SHow
THReads will report what threads are in play.

Also, note that you are running base level TSM code, with no
maintenance, which is not a good idea.

Richard Sims

Richard,

Thanks for the reply and suggestions. We have a tried a few of your
suggestions. IBM TSM support did have us run the following show
commands. I just tried to run 'show memory' on this server and had to
break out of the command because it began to cause failures with object
retrievals memory/paging. AIX is having us run perfpmr as the next
troubleshooting step so hopefully that will help us get down to the bottom
of the memory hog. IBM did have us run a few commands that I left out
from original email.


1. restart the dsmserv process
2. collect the output of 'SHOW ALLOC' one time per hour for the next 48
hours. Also collect AIX command output for 'ps aux | grep dsmserv' at the
same time.
3. at the end of step 2 collect the last 48 hours of unfiltered activity
log


Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979



Richard Sims <rbs < at > BU.EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>
07/28/2008 11:03 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>


To
ADSM-L < at > VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] Memory Issue: Since Upgrading TSM Server from 5.2 to TSM 5.5
and installation of Centera SDK 3.2.1 - anyone experiencing similar
problem?






Nancy -

Confer with your AIX people on identifying processes using the most
memory in your server system, where 'ps' and various other monitoring
facilities can report what's using what.

In TSM, you can use the SHow MEMory command to report a summary of
memory usage and the SHow ALLOC command to report by module. SHow
THReads will report what threads are in play.

Also, note that you are running base level TSM code, with no
maintenance, which is not a good idea.

Richard Sims



CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original
message.