Joni,

The capacity and utilization statistics from QUERY FILESPACE are those of
the actual file system on the client machine (as of the last incremental
backup). It is not a representation of how much space the client is
utilizing on your TSM server.

The most likely cause of what you are seeing is directory backups that
reside in the database but not the storage pools. QUERY OCCUPANCY only
shows you storage pool occupancy, not database occupancy. You can check
this by examining the contents of the BACKUPS and ARCHIVES tables:

   SELECT * FROM BACKUPS WHERE NODE_NAME='NNNNN'
   SELECT * FROM ARCHIVES WHERE NODE_NAME='NNNNN'

(substitute the node name -- in all upper case -- for NNNNN)

The DELETE FILESPACE command should handle the removal of any residual
data.

Regards,

Andy

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

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Joni Moyer <joni.moyer AT HIGHMARK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/11/2003 07:19
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        delete node discrepancy



Hello!

I have tried to delete a node from tsm and I received the message that
there were references that still existed for that node, but when I did a
query occupancy I found nothing.  I then did a query filespace for that
particular node and it showed 1 filespace with approximately 2GB of space.
How is this possible?  Where would this data reside if it doesn't show up
with the query occupancy?

Thanks in advance for any help!

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338