Here's what I would do:

On a regular basis, do something like this:

dsmadmc -id=xxxxx -password=yyyyy -commadelimited  "select node_name,
sum(logical_MB), sum(num_files) from occupancy where stgpool_name in
('DISKPOOLNAME','PRIMARYTAPENAME1')  group by node_name>outputfile

Many other people have posted various was of getting the same data,
including using the ODBC interface, but I like this because I can schedule
it with a host script via cron.  You'll need to doctor it a bit to deal with
your own stgpool names, and run it twice - once for Archive and once for
backups.

Since it's in commadelimited form, you can point EXCEL to the outputfile and
open it directly. (Or if you want more automation, process it with a perl
script or a SAS pgm, etc.

Take the same information from a different day, and it's easy to have the
spreadsheet compare the values of either logical_mb  or num_files for each
node; that way you can PROVE for sure which node is hitting you with the
biggest increase in num_files..



-----Original Message-----
From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL AT SAIC DOT COM]
Sent: Sunday, May 25, 2003 6:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: DB Growing


I know this was discussed recently but it seems like the adsm.org web site
is down and I can't search the archives.



I've seen my DB grow about 10gb in the past couple of weeks and I need to
find the culprit. What was the solution to tracking down a node that could
be causing this?



Thanks,

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 905-7154