Dedup reporting

[chriscain]

Hi,
We have a TSM 6.12 set up and I am trying to understand the Dedup reporting.
I *THOUGHT* after much reading that:-
Logical_mb = actual ammount of data in the fiespace. i.e. how much space is being used in the stgpool by the client data.

Reporting_mb = the ammount of space the data would have taken in the stgpool if you had not used dedup.

Hence I thought that reporting_MB would always be >= logical_mb

But it isnt! - see below.
What is the reason for this, it looks like dedup is actually taking up MORE space than an undeduped storage pool for these clients ?


tsm: RDG-DP3TSM>select * from occupancy where logical_mb>reporting_mb order by logical_mb desc
NODE_NAME: 195520
TYPE: Bkup
FILESPACE_NAME: \\c26-server-vmho\e$
STGPOOL_NAME: GENERAL_ONSITE
NUM_FILES: 1606
PHYSICAL_MB: 0.00
LOGICAL_MB: 7005268.41
REPORTING_MB: 3221424.46
FILESPACE_ID: 4
NODE_NAME: 349219
TYPE: Bkup
FILESPACE_NAME: \\sasp-04\h$
STGPOOL_NAME: GENERAL_ONSITE
NUM_FILES: 1497
PHYSICAL_MB: 0.00
LOGICAL_MB: 430126.61
REPORTING_MB: 214392.86
FILESPACE_ID: 8

 

[staham]

I think you should contact IBM support about this. From what I've read, reporting_mb should always be larger or the same as logical_mb.