It appears by doing a select on the occupancy table; the full amount of
data is reported in the Logical Column, and reporting is deduped
tsm: TSMLAB1>select NODE_NAME, STGPOOL_NAME, NUM_FILES, PHYSICAL_MB,
LOGICAL_MB, REPORTING_MB from occupancy where STGPOOL_NAME='DISK-DEDUPE'
NODE_NAME STGPOOL_NAME NUM_FILES
PHYSICAL_MB LOGICAL_MB REPORTING_MB
------------------ ------------------ ------------
----------------- ----------------- -----------------
LABW9236 DISK-DEDUPE -2620
0.00 1852.71 5.10
LABW9236 DISK-DEDUPE 0
0.00 0.01 0.00
LABW9236 DISK-DEDUPE 0
0.00 0.04 0.00
LABW9236 DISK-DEDUPE 0
0.00 0.10 0.00
LABW9236 DISK-DEDUPE 0
0.00 0.13 0.00
LABW9236 DISK-DEDUPE 0
0.00 0.23 0.00
LABW9236 DISK-DEDUPE 0
0.00 0.87 0.00
LABW9236 DISK-DEDUPE 0
0.00 0.94 0.00
LABW9236 DISK-DEDUPE 0
0.00 1.19 0.00
LABW9236 DISK-DEDUPE 0
0.00 14.51 0.00
LABW9236 DISK-DEDUPE 0
0.00 17.57 0.00
LABW9236 DISK-DEDUPE 0
0.00 31.43 0.00
LABW9236 DISK-DEDUPE 0
0.00 24.59 0.01
LABW9236 DISK-DEDUPE 0
0.00 45.27 0.01
LABW9236 DISK-DEDUPE 0
0.00 82.46 0.01
LABW9236 DISK-DEDUPE 0
0.00 229.62 0.03
LABW9236 DISK-DEDUPE 0
0.00 300.47 0.04
LABW9236 DISK-DEDUPE 0
0.00 418.44 0.05
LABW9236 DISK-DEDUPE 0
0.00 470.74 0.06
LABW9236 DISK-DEDUPE 0
0.00 925.03 0.12
LABW9236 DISK-DEDUPE 0
0.00 939.91 0.12
LABW9236 DISK-DEDUPE 0
0.00 1257.26 0.16
LABW9236 DISK-DEDUPE 0
0.00 1572.13 0.19
LABW9236 DISK-DEDUPE 0
0.00 2152.09 0.28
LABW9236 DISK-DEDUPE 0
0.00 3131.19 0.39
LABW9236 DISK-DEDUPE 0
0.00 3191.17 0.39
LABW9236 DISK-DEDUPE 0
0.00 3322.11 0.41
LABW9236 DISK-DEDUPE 0
0.00 5474.88 0.67
LABW9236 DISK-DEDUPE 0
0.00 6981.77 0.87
LABW9236 DISK-DEDUPE 0
0.00 7247.60 0.89
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jim Neal
Sent: Monday, April 18, 2011 1:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] How do you allocate costs for deduplicated data?
Importance: High
Hi All,
We are in the process of testing TSM's Deduplication
feature and I have a question about how the cost of the deduplicated
data gets allocated. For example:
Two systems that have 80% of their data in common and that belong to
two different departments get backed up. The first system gets
deduplicated and is billed for 100% of the deduplicated data. The
second system only has 20% of unique data and so is only billed for that
20% after deduplication? Is this correct? If so, is there a way to get
around this so that the cost is fairly divided?
Any information or advice on this would be greatly appreciated. Thanks
much!
Jim Neal
Sr. TSM Administrator
U.C. Berkeley
Storage and Backup Group
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
|
