Peter,
I have had an open issue with both Novell and IBM concerning this topic.
We only have the problem with the TSM 3.7 client and Netware 5.1. This
issue, according to IBM is a Novell issue.I just received an update from
IBM on this yesterday which follows.
IC28444 APAR - NDS BACKUP CONSUMES LARGE AMOUNT OF MEMORY IN
SMDR.NLM, MEMORY. SMDR doesn't release memory after closing of NDS
object. SMDR memory will be freed only when connection to TSA is release
It is concerning ONLY TSANDS and ONLY Netware 5.x .
Novell has opened an incident 2510018 to resolve this issue.
So, this TSM APAR as closed ISV indicating other vender problem. Local
fix would be to use a 4.11 machine to perform the NDS backup.
As you can see IBM has closed this problem as an other vendor issue.
Although I am not entirely happy with the resolution at least someone has
taken ownership of this issue. We have found if we allocate enough memory
on the server that executes the NDS backup we can get through the backup.
Please let me know if you need any more information on this topic or if
you would like to discuss this in more detail.
Regards,
Brian
Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900
E-MAIL: [EMAIL PROTECTED]
PHONE: (860)403-2281
Peter Hadikin
<Peter_Hadiki To: [EMAIL PROTECTED]
[EMAIL PROTECTED]> cc:
Sent by: Subject: Memory consumption by SMDR.NLM
"ADSM: Dist backing up NDS
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
10/24/2000
06:33 PM
Please
respond to
"ADSM: Dist
Stor Manager"
Hello group,
I hope somebody can help me. We are trying to backup our NDS and are
running into a problem. As the NDS backs up, the amount of memory
'consumed' by SMDR.NLM grows and grows until no more short term memory
can be allocated on the server. Our NDS is relatively large but for the
life of me I cannot understand why SMDR keeps eating more and more
memory. This has been an ongoing problem for us regardless of versions
of software. We are currently running Netware 5 with SMDR.NLM (V5.04),
TSANDS.NLM (V5.25), TSA500.NLM (V5.03) and DSMC.NLM (V4.01A). Does
anybody out there have a clue how to get around this or do we just sit
back and watch Tivoli and Netware point the finger at each other?
Any help would be most appreciated. Let me know if you need any more
info before you can comment.
Thanks, Peter
