ADSM-L

Re: tsa600.nlm memory leak on NW6 client

2003-09-27 19:02:52
Subject: Re: tsa600.nlm memory leak on NW6 client
From: Matt Zufelt <mzufelt AT SUU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 27 Sep 2003 17:02:14 -0600
Loading TSANDS is only necessary if you're backing up eDirectory itself.  Not 
sure why the admin wouldn't want it loaded, but I guess that's a different 
issue.  Regarding the memory leak: I've seen it documented somewhere (though I 
don't remember where) that the problem isn't a leak so much as it is dsmc.nlm 
not releasing resources (but then again, that sounds a lot like a leak).

The more files you back up, the more memory that is required by dsmc.  The 
problem is, even after the backup is finished, dsmc.nlm does not release the 
memory resources it has consumed.  Over a period of time, the memory usage 
grows until it reaches a point that it is affecting server performance.  Once 
you unload and then reload dsmc.nlm, the memory is released.

I would recommend switching your method of loading the scheduler.  Instead of 
loading dsmc sched to handle the scheduling, add schedule to the 
managedservices line in your dsm.opt file.  For example:

MANAGEDSERVICES         schedule webclient

Then, when you load dsmcad.nlm, it will handle the scheduling instead of 
dsmc.nlm.  The advantage of this method is reduced memory usage.  When it is 
time to perform the backups, dsmcad loads dsmc, does the backup, and then 
unloads dsmc thereby freeing the memory.  This method has worked wonders for 
memory utilization on our servers here.

Matt Zufelt
Southern Utah University


>>> dieter AT SNRGY DOT COM 9/26/2003 4:53:51 PM >>>
All,

Environment:

AIX 5.1 ML4 server with TSM 5.1.7.0 code.

Client is a NW6 machine, 2GB memory, with TSA600.NLM (6.00.05), TSANDS.NLM
(version unknown), and SMDR.NLM (6.50.03).  Backing up via 100/full
network connection.

For reasons that I do not fully understand, the Netware admin does not
want to load TSANDS, which is apparently used only to back up the NDS.
They only wish to get certain user files.

The backups run OK manually (dsmc i), but if I "load dsmc sched" and let
the scheduler handle it (server prompted), memory usage goes through the
roof...after one night, TSA600 will be using well over 1GB, and close to
2GB on the second night.  The second night will not complete.

Is TSANDS *required*?  I'm thinking that this might be the cause for the
memory consumption that I'm seeing.

Any comments would be appreciated.

-Lloyd

<Prev in Thread] Current Thread [Next in Thread>