Re: Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?

2009-04-23 Thread David McClelland
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:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: 21 April 2009 13:45
To: ADSM-L@VM.MARIST.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


Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?

2009-04-21 Thread David McClelland
Hi Team,

I’ve performed an EXPORT NODE operation from a source TSM server (Windows
5.4.3.2) to a target server (AIX 5.5.1.1) over TCP/IP with the TOSERVER
option. All appears to have completed successfully, the processes on both
TSM Servers report SUCCESS with no errors. However, being of a cautious
nature (particularly with others’ data) I’m doing some additional
verification, and it’s a comparison of the `Q OCC` output on the two servers
that I want to double-check as there's something which has me a little
concerned.

On the source server (i.e. that from which I issued the EXPORT NODE) the
relevant exported filespace looks like this:

tsm: CENTSM02q occ CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT

Node Name  Type Filespace   FSID StorageNumber of
Physical   Logical
Name Pool Name  Files
Space Space
 
Occupied  Occupied
 
(MB)  (MB)
--  -- - -- -
- -
NODENAME Bkup FILESPACE 5 LTOCONTC  85,299
16,119.97 16,119.97


On the target server it looks like this:

tsm: ARCTSM01q occ CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT
ANR2017I Administrator DAVID.MCCLELLAND issued command: QUERY OCCUPANCY
CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT

Node Name  Type Filespace   FSID StorageNumber of
Physical   Logical
Name Pool Name  Files
Space Space
 
Occupied  Occupied
 
(MB)  (MB)
--  -- - -- -
- -
NODENAME Bkup FILESPACE 2 CONT_DISK85,299
16,098.71 16,098.71


Apols if this doesn't come out clearly when converted to plain text, but in
summary the NUMBER OF FILES reported is identical (85,299) between source
and target, and the PHYSICAL SPACE OCCUPIED (MB) is not - which is down to
empty space in aggregates on the source. 

However, what I want to double check is why the LOGICAL SPACE OCCUPIED (MB)
isn't the same - I'd have expected that these would have identical. There's
a 20MB difference between the source and target, with less on the target.
The variables that I can immediately think of are different TSM Server code
and platform, and the storage media (LTO2 on source, DISK on target).

Any ideas? I'm certainly happy that the number of files adds up and that the
EXPORT/IMPORT NODE commands completed apparently successfully, but I'd like
to be able to explain the difference in LOGICAL SPACE OCCUPIED, or
understand if this figure is indeed definitive or subject to rounding etc.

Thanks  Rgds,

David Mc
London, UK

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
 


Re: Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?

2009-04-21 Thread Richard Sims

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