Hehe... When using SQL BackTrack, it isn't real comforting to look at all
those filespaces (query filespace) with big goose eggs next to them.  One
way to do it would be to not view the filespaces to calculate how much is
being backed up on a node but to use a select statement:

select stgpool_name, sum(physical_mb) from occupancy where node_name
='<NODE>' group by stgpool_name

Querying the files spaces will give you a capacity based on an estimate and
it will take a while to compute the percentage
utilized anyway.

George Lesho
Storage/System Admin
AFC Enterprises






"MacMurray, Andrea (CC-ETS Ent Storage Svcs)"
<Andrea.MacMurray AT CONAGRAFOODS DOT COM>@VM.MARIST.EDU> on 01/22/2002 11:40:46
AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  TSM and capacity planning



Hi everybody,
I have been tasked with capacity planning for TSM. We are running on AIX
4.3.3 TSM version 4.2.1.9. Most of the information is in the log with some
scripting you can all this ata into a database. The problem I have is SQL
backtrack. All those database instances backup to tsm without leaving any
stats, I do know where the backtrack logs are, but they are not very pretty
. So my question is if there is anybody out there who had to do something
like that before.
Thanks in advance


Andrea Mac Murray
Sen. Systems Administrator
ConAgra Foods, Inc.
7300 World Communication Drive
Omaha,NE 68122
Tel: (402) 577-3603
andrea.macmurray AT conagrafoods DOT com