On Thursday, Jul 15, 2004, at 23:40 Australia/Sydney, Chang, Calvin
wrote:

Good Morning Everyone!

Good evening! Actually, it is morning, just...

What does the number for "Physical Space Occupied" in the output of q
occupancy represents?  Is it total compressed space? or non-compressed
space? The help on the q occupancy was pretty vague...

"Physical Space Occupied (MB)

     The amount of physical space occupied by the file space. Physical
space

     includes empty space within aggregate files, from which files may
have

     been deleted or expired."

Let's says if I want to restore my entire node including Active and
Inactive files through the TSM GUI.  When I hit the "Estimate" button
in the GUI to get a total number of Bytes to restore, it actually
represents a much higher number than the q occupancy's output.

Is the "Physical Space Occupied" due to client and drive side
compression?

Any info would be appreciated.

OK... first, drive compression is transparent to TSM - that is, TSM
has no real way of determining how much something was compressed by
the tape drive. So "q occ" shows how much was sent to the drive.

Next, the TSM server only sees what was sent by the client. So if
client-side compression is going on, "q occ" is the compressed size.

I have no idea, however, how the TSM client does the estimates.

Cheers,
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams