Jack,

I think its txnbytelimit (on the client end), and the max is 25600 - WAY
below a gig.
Aggregates are not your problem.

I suggest you check your client stats (either from the activity log, or
from TOR) to figure out which clients are likely to be sending the big
chunks, then check their scheduler logs to find the file names.

(Are you sure that you are excluding your .dsm files on the TSM server -
not backing up your TSM storage pool files, etc...?)

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Coats, Jack
Sent: Tuesday, November 23, 2004 8:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Size of aggrigated files - How can it be controlled?


On my little windows TSM server (with 2G of RAM), I am being killed by
12 to
19 GIGABYTE files.



There are some that 'naturally' come from our Exchange servers (4 per
day).
But there seem to be to many of them for that to be the only source.



Knowing my user data, thinking that these are really aggregates seems
reasonable to me.



Is there a way to control the maximum size of an aggregate?





If the group has a better idea, I am always open to suggestions!



TIA, Jack