rt/IBMTivoliStorageManager.html
>
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" wrote on 10/12/2009
> 07:58:58 AM:
>
> > [image remo
Yeah, I'm leaning towards memory or maybe network right now.
I'm seeing some of these during client backups:
ANR0132E smnode.c(27085): Memory allocation failed: object sessP->qryBuf, size
1048576. (SESSION: 5518)
This is on a win32 system so 2GB mem is max. I'll try reducing the
bufpool to give
uot; wrote on 10/12/2009
07:58:58 AM:
> [image removed]
>
> instrumentation for the server?
>
> km
>
> to:
>
> ADSM-L
>
> 10/12/2009 08:05 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager"
>
> Please respond to "ADSM: Dist Stor Manage
I once saw this when we had set BUFPOOLSIZE way too high.Giving the TSM
server lots of memory starved the OS for memory; things slowed down horribly
until we set BUFPOOLSIZE back to the Performance-tuning-guide
recommendations ( I forget - 1/4 of available memory?)
On Mon, Oct 12, 2009 at 7:58 AM
Hello,
I am currently analyzing a TSM server which uses 100% CPU on 4 cores
when doing client backups. Almost all of it is privileged times, but
there are very few IO's and low disk queues for both stgpools, db and log.
Are there any trace flags similar to the client testflag instrument:detail
bu
