Thank you for your answer... Next question... And sorry for the anoying
questions.

If i set up a small file device class storage pool and then migrate to
VTL.... It will only dedupe against what is in the first storage pool...
correct? Not against the VTL...

I am trying to wrap my mind around the best way to set this up.

thanks,

Andrew

On Wed, Aug 10, 2011 at 10:26 AM, Erwann SIMON <erwann.simon AT free DOT fr> 
wrote:

> Hi Andrew,
>
> Client side dedup requires that destination pool is set up for dedup, so it
> must be a file device type pool.
>
> If you change this for another device type pool (VTL for instance), you'll
> loose the ability of doing client side dedup.
>
> Also note that there are restrictions to simultaneous write operations when
> dedup is partially available, like in your example (destination is file with
> dedup whereas activedata is vtl without TSM dedup).
>
> Changing from file to vtl device type will make you lost client side dedup
> capabilities.
> ------Message d'origine------
> De: Andrew Meadows
> Expéditeur : ADSM: Dist Stor Manager
> À: ADSM-L AT VM.MARIST DOT EDU
> Répondre à: ADSM: Dist Stor Manager
> Objet: Re: [ADSM-L] Dedup question
> Envoyé: 10 août 2011 17:08
>
> >
> >   I have a question about client side dedup I was hoping I could get some
> >> help with.
> >>
> >>
> >>
> >>
> >>
> >> Environment:
> >>
> >>
> >>
> >> Server TSM 6.1.3
> >>
> >> Client TSM 6.2.3
> >>
> >>
> >> We are using client side dedup to decrease the amount of data being sent
> >> over the network. The problem is we recently changed to a VTL only
> >> configuration with no disk pools.... My question is.
> >>
> >> If i set up a activa datapool with silultanious writes to the VTL pool
> (or
> >> just the oposite actually). Will client side dedup still occur? Or do
> both
> >> target pools need to be devclass of file?
> >>
> >> Thanks,
> >>
> >> Andrew
> >>
> >
> >
>
>
> --
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON