This would happen if a node has backed up only directories but not files.
You have information stored only in the TSM DB but no actual files stored.
So info about the filesystem is there without occupancy.
Try yourself a empty directory or one with only subdirectories:
dsmc incr d:\tmp\
dsmc incr /tmp/lost+found/
but
dsmc incr d:\tmp\ -subdir=yes
dsmc incr /tmp/lost+found/ -subdir=yes

If you do have such nodes in your DB this means that particular filespace
didn't backed up any files. If this is let's say /tmp - that is fine but if
it is /home ....


Zlatko Krastev
IT Consultant






Pothula S Paparao <9pothula AT SG.IBM DOT COM> on 24.09.2001 13:25:26
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Q ocuupancy Vs Q filespace.

hi *smers,
It really surprising me that how q occupancy is not showing few nodes.
whereas , q file space still show .
whats happening !!!!!! can any tsm guru can help me out this.

thanks in advance
regards
sree.