ADSM-L

Re: [ADSM-L] Memory usage issues with "traditional scheduler service" on Windows

2011-01-07 12:05:44
Subject: Re: [ADSM-L] Memory usage issues with "traditional scheduler service" on Windows
From: adsm mailing list <adsm AT I-TSM.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 7 Jan 2011 17:03:10 +0000
Hi Andrew

I have previously logged a PMR for this as we are seeing the dsmcsvc process 
not releasing all the memory it uses during the backup, each day the amount of 
memory the dsmcsvc process uses increases by 20 - 50MB. This can increase until 
the dsmcsvc.exe process is consuming over 1GB (idle) which is a big problem on 
a cluster with 30 scheduler processes.

The advice from Tivoli support was to use the CAD as the traditional scheduler 
has had known problems with releasing memory since version 4. 
This memory leakage only seems to happen when were backing up 2008 servers, we 
believe it is due to the systemstate is 20x bigger than with Windows 2003. This 
also effects the 6.2.2.0 client.

Phil



________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] on behalf of Andrew 
Raibeck [storman AT US.IBM DOT COM]
Sent: 07 January 2011 14:43
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Memory usage issues with "traditional scheduler service" 
on Windows

Hi Zoltan,

Are you finding that the dsmcsvc.exe memory usage is spiking during TSM
operations? Or are you saying that after each successive operation, when
the service is idle, you see the amount of used memory creeping up on a
daily basis?

If the service starts an operation, spikes memory, then goes back down when
the operation is done, and you do not see the memory usage creeping up
(when idle) day by day, then there is no leak as such. However, if you are
seeing the memory usage creeping up when the service is idle, then please
open a PMR so we can investigate if indeed you are experiencing a memory
leak. I also suggest verifying that you are on a current code level, in
case the problem you are seeing has already been resolved.

If I have misunderstood the nature of the problem, please clarify.

Best regards,

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-01-03
16:08:38:

> From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-01-03 16:09
> Subject: Memory usage issues with "traditional scheduler service" on
Windows
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> I have a client/admin complaining about excessive memory usage by the
> client scheduler, since upgrading the client from  6.1.2.0 to 6.2.2.0.
>
> Before, dsmcsvc.exe was using around 21mb.  Now it is using from 178mb
> (today) to spiking over 1gb.
>
> They did some digging and found various articles/docs that talks about
> using the CAD/managedservices to help reduce the memory footprint.
>
> One thing that disturbs me is the statement "Tip: Restart the traditional
> scheduler periodically to free system resources previously used by system
> calls.".
>
> You can read this here:
> http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp?
> topic=/com.ibm.itsm.client.doc/t_cfg_schdcad.html
>
> This sounds like a cop-out to address memory leaks.
>
> How many of you "restart the scheduler service periodically to free
system
> resources"?
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html