Hi all,
our TSM-Server 6.2.2 with enabled Deduplication shows wrong REPORTING_MB in Table Occupancy.
The IBM Developerworks Wiki (http://www.ibm.com/developerworks/w...ation+in+Tivoli+Storage+Manager+V6.2+and+V6.1) describes that .... "REPORTING_MB is the amount of space that would be occupied if the data wasn't placed in a deduplication-enabled storage pool."
select * from occupancy where node_name='DEMONODE1'
NODE_NAME: DEMONODE1
NUM_FILES: 38108
PHYSICAL_MB: 0.00
LOGICAL_MB: 4800.00
REPORTING_MB: 413383.37
The Copy Group does allow max. 4 Versions:
Policy Domain Name: STANDARD
Policy Set Name: ACTIVE
Mgmt Class Name: STANDARD
Copy Group Name: STANDARD
Versions Data Exists: 4
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
The Server has only 19GB used Data:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 40G 19G 20G 49% /
It looks like a bug!?
cu
our TSM-Server 6.2.2 with enabled Deduplication shows wrong REPORTING_MB in Table Occupancy.
The IBM Developerworks Wiki (http://www.ibm.com/developerworks/w...ation+in+Tivoli+Storage+Manager+V6.2+and+V6.1) describes that .... "REPORTING_MB is the amount of space that would be occupied if the data wasn't placed in a deduplication-enabled storage pool."
select * from occupancy where node_name='DEMONODE1'
NODE_NAME: DEMONODE1
NUM_FILES: 38108
PHYSICAL_MB: 0.00
LOGICAL_MB: 4800.00
REPORTING_MB: 413383.37
The Copy Group does allow max. 4 Versions:
Policy Domain Name: STANDARD
Policy Set Name: ACTIVE
Mgmt Class Name: STANDARD
Copy Group Name: STANDARD
Versions Data Exists: 4
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
The Server has only 19GB used Data:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 40G 19G 20G 49% /
It looks like a bug!?
cu
