Re: [ADSM-L] AW: How can I exclude files from dedupe processing?

Michael,

Thank you for pointing out the exclude.dedup option.  But this appears to only 
controls client-side deduplication.  Wouldn't the TSM server still try to 
deduplicate these objects?

..Paul

At 09:08 AM 8/3/2015, Michael malitz wrote:
>Hallo John, Paul,
>
> 
>
>for client dedup, have a look to exclude.dedup  option
>
> 
>
>And: compressed objects can also be good candidates for deduplication. Have
>a try and test reduction(s) 
>
> 
>
>Rgds Michael Malitz
>
> 
>
> 
>
>-----Ursprüngliche Nachricht-----
>Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
>von
>Paul Zarnowski
>Gesendet: Montag, 3. August 2015 14:29
>An: ADSM-L AT VM.MARIST DOT EDU
>Betreff: Re: How can I exclude files from dedupe processing?
>
> 
>
>Deduplication is an attribute of a a storage pool.  If you have data you
>don't wish to de duplicate, you would need a separate storage pool.
>
> 
>
>..Paul
>
>(sent from my iPhone)
>
> 
>
>On Aug 3, 2015, at 8:19 AM, Dury, John C. <
><mailto:JDury AT DUQLIGHT DOT COM%3cmailto:JDury AT DUQLIGHT DOT COM>
>JDury AT DUQLIGHT DOT COM<mailto:JDury AT DUQLIGHT DOT COM>> wrote:
>
> 
>
>Unfortunately the final storage pool is the dedupe pool.
>
> 
>
> 
>
> 
>
> 
>
> 
>
>Date:    Sun, 2 Aug 2015 16:32:17 +0000
>
> 
>
>From:    Paul Zarnowski <
><mailto:psz1 AT CORNELL DOT EDU%3cmailto:psz1 AT CORNELL DOT EDU>
>psz1 AT CORNELL DOT EDU<mailto:psz1 AT CORNELL DOT EDU>< <mailto:psz1 AT 
>CORNELL DOT EDU>
>mailto:psz1 AT CORNELL DOT EDU>>
>
> 
>
>Subject: Re: How can I exclude files from dedupe processing?
>
> 
>
> 
>
> 
>
>Since the files are already using a separate management class, you can just=
>change the destination storage pool for that class to go to a non-duplicat=
>ed storage pool.
>
> 
>
> 
>
> 
>
>..Paul
>
> 
>
>(sent from my iPhone)
>
> 
>
> 
>
> 
>
>On Aug 2, 2015, at 11:07 AM, Dury, John C. <
><mailto:JDury AT DUQLIGHT DOT COM%3cmailto:JDury AT DUQLIGHT DOT COM>
>JDury AT DUQLIGHT DOT COM<mailto:JDury AT DUQLIGHT DOT COM><
><mailto:JDury=%20 AT DUQLIGHT DOT COM%3chttp://DUQLIGHT.COM> mailto:JDury=
>@DUQLIGHT.COM<http://DUQLIGHT.COM><
><mailto:JDury AT DUQLIGHT DOT COM%3cmailto:JDury=%20 AT DUQLIGHT DOT 
>COM%3cmailto:20@DUQLI
>GHT.COM>
>mailto:JDury AT DUQLIGHT DOT COM%3cmailto:JDury=%20 AT DUQLIGHT DOT 
>COM<<mailto:20@DUQLIGHT>mailto:20@DUQLIGHT
>.COM>>>> wrote:
>
> 
>
> 
>
> 
>
>I have a 6.3.5.100 Linux server and several TSM 7.1.0.0 Linux clients. Thos=
>e linux clients are dumping several Large Oracle databases using compressio=
>n, and then those files are being backed up to TSM. Because the files are c=
>ompressed when dumped via RMAN, they are not good candidates for dedupe pro=
>cessing. Is there any way to have them excluded from dedupe server processi=
>ng ? I know I can exclude them from client dedupe processing which I am not=
>doing on this client anyways. I have the SERVERDEDUPTXNLIMIT limit set to =
>200, but these rman dumps are smaller than 200g. I have our DBAs investigat=
>ing using TDP for Oracle, but until then, I would like to exclude these fil=
>es from dedupe processing as I suspect it is causing issues with space recl=
>amation. If it helps, these files are in their own management class also.
>
> 
>
>Ideas?


--
Paul Zarnowski                            Ph: 607-255-4757
Assistant Director for Storage Services   Fx: 607-255-8521
IT at Cornell / Infrastructure            Em: psz1 AT cornell DOT edu
719 Rhodes Hall, Ithaca, NY 14853-3801