https://www-304.ibm.com/support/docview.wss?context=SSGSG7&lang=all&rs=2077&wv=1&loc=en_US&cs=UTF-8&uid=swg27018576&q1=tste_webcast&dc=DA410
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark Mooney Sent: Tuesday, June 21, 2011 2:53 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Deduplication and Collocation Cool, Thanks :) I have questions about client dedup. Do you know of any redbook detail on that? Thanks, Mooney "Prather, Wanda" <wprat...@icfi.com> wrote: Dedup only works in TSM storage pools that reside on disk (specifically devtype=FILE pools). If you have data that goes to a dedup pool, then gets migrated off to tape, it is reduped (rehydrated, reinflated, whatever you want to call it.) So collocation will still be in effect for that pool. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mark Mooney Sent: Tuesday, June 21, 2011 2:17 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Deduplication and Collocation Hello, I had a student ask me today "What happens if you have collocation turned on for a storage pool that you are deduplicating?" I did not know what to answer because in my mind I thought "well, if the data is collocated then I need to have a copy of that data on that client's tape, otherwise I am going to be mounting another client's tape to get back a de-duped piece of data which would negate the collocation" I'm looking at the redbooks for this but I only see 6.1 and in 6.2 they added client side dedup as well (which I also have questions about) Can anyone shed some light on this? Thanks! Mooney