Thanks Richard, I suspected as much - even within the same server looking at
the same data in different storage pools (i.e. fully synchronised primary
and copy stgpools) I see the same number of objects but a different logical
space value reported.

/DMc

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: 21 April 2009 13:45
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Verifying EXPORT NODE is successful with Q OCC -
LOGICAL SPACE OCCUPIED (MB) differences?

David -

The Admin Ref manual description of the Physical and Logical Space
report element from Query OCCupancy is superficial, leading the
customer to believe that the Logical value is just the amount of space
occupied by client files.  According to info I've seen, logical space
also includes headers housing control information for each file, such
as magic numbers, CRC info, segment numbering, server ID, etc.  The
size of the header info can vary as TSM evolves, and so may differ
across TSM releases.  The header size can be seen in the output of the
SHow INVObject command for a given ObjectID.

    Richard Sims   http://people.bu.edu/rbs

No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 270.12.0/2068 - Release Date: 19/04/2009
20:04


No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 270.12.0/2068 - Release Date: 19/04/2009
20:04