[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    Re: TSM 6.1 deduplication is invalid option for disk primary pools
From:       Grigori Solonovitch <G.Solonovitch () BKME ! COM>
Date:       2009-04-30 6:23:24
Message-ID: 15954812EB5FA74190A718051E178B10016F007EE1BB () AUBKWMAIL ! KUWAIT ! AUB ! NET
[Download RAW message or body]

Thank you very much Colin.
I will configure storage pools with device class FILE.

Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch@bkme.com

Please consider the environment before printing this Email


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Colin Dawson
Sent: Wednesday, April 29, 2009 6:48 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 6.1 deduplication is invalid option for disk primary pools

Grigori,

     The primary decision for limiting deduplication to device classes of
DEVTYPE=FILE has to do with the deduplication processing itself.  Once a
data chunk has been identified as being a duplicate of an existing data
chunk, the TSM server leverages the reclamation and aggregate
reconstruction algorithms.  These algorithms are only available for device
classes that exploit a device type of sequential media.  So, the design
decision or rational was to do this for DEVTYPE=FILE because the necessary
infrastructure was more readily in place then what was available for
DEVTYPE=DISK.

Thanks,
Colin

-----------------------------------------------------
Colin Dawson
TSM Server Development
colind@us.ibm.com



  From:       Grigori Solonovitch <G.Solonovitch@BKME.COM>

  To:         ADSM-L@VM.MARIST.EDU

  Date:       04/29/2009 05:38 AM

  Subject:    [ADSM-L] TSM 6.1 deduplication is invalid option for disk primary pools






Hello Everybody,
I am testing TSM 6.1 under AIX.
I have tried to enable de-duplication for primary disk pool:
tsm: BKME>upd stg daily_1 dedup=y
ANR2344E UPDATE STGPOOL: The "DEDUPLICATE" option is not valid for device
class DISK.
ANS8001I Return code 3.
tsm: BKME>
I have been affected too much by this message, because most of our primary
pools are on FATA disks.
Could somebody explain me why IBM is not able to use de-duplication for
device class DISK?
What is behind this?
I understand I was reading all available before documentation not enough
carefully, because I was sure that it is much easier to de-duplicate data
on disks in comparison with tape drives.
Kindest regards,


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail:
G.Solonovitch@bkme.com<mailto:G.Solonovitch@bkme.com>

Please consider the environment before printing this Email


Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are not
the named recipient(s), please delete this email after notifying the sender
immediately. BKME cannot guarantee the integrity of this communication and
accepts no liability for any damage caused by this email or its attachments
due to viruses, any other defects, interception or unauthorized
modification. The information, views, opinions and comments of this message
are those of the individual and not necessarily endorsed by BKME."

"This email message and any attachments transmitted with it may contain confidential \
and proprietary information, intended only for the named recipient(s). If you have \
received this message in error, or if you are not the named recipient(s), please \
delete this email after notifying the sender immediately. BKME cannot guarantee the \
integrity of this communication and accepts no liability for any damage caused by \
this email or its attachments due to viruses, any other defects, interception or \
unauthorized modification. The information, views, opinions and comments of this \
message are those of the individual and not necessarily endorsed by BKME."


[prev in list] [next in list] [prev in thread] [next in thread]