Each object in the TSM database takes the same amount of space,
no matter the object's size.
It might be the directory structure. The backed up directory
structure takes up entries in the DB, but they are kind of "invisible".
If you do a "q occ" on a node, it will show you the number of files, but
not the number of directories. If you have deeply nested directory
structures, your DB can grow very large even though you don't seem to
have much data being backed up.
just my guess.
Ben
Message
From: ADSM: Dist Stor Manager [mailto:ADSM-L (AT) VM (DOT) MARIST.EDU] Behalf
Ribeiro, Ricardo
Sent: Wednesday, 25, 2006 8:33 AM
To: ADSM-L (AT) VM (DOT) MARIST.EDU
Subject: TSM DB occupied space
Hello,
Can somebody please tell me if the TSM DB occupy's more space if a node
has more data then a node that has more files?
Example:
Node A has 200 files but 1 TB of storage on the TSM pool Node B has
20000 files but 200 GB of storage on the TSM pool Which occupies more
space on the TSM DB?
Thanks!