I'm afraid Remco is right, the server can't (or simply won't) uncompress
the older client-side compression so it will convert it compressed to the
containerpool and you will most likely get very poor deduplication on that
data.
What kind of data is it and for how long do you need to keep it?

On Thu, Apr 19, 2018 at 11:25 AM, Remco Post <r.post AT plcs DOT nl> wrote:

> it’s not a perfect world, AFAIK.
>
> > On 19 Apr 2018, at 10:36, Michael Prix <mp AT RS6000.DARKTECH DOT ORG> 
> > wrote:
> >
> > Hello *SMers,
> >
> >  just out of curiosity:
> > Given you have a storagepool with a legacy, non-deduplicated,
> file-devclass,
> > inside which files are stored with "compression yes" on the clientside.
> This
> > storagepool is converted to a directory-containerpool. How are the
> compressed
> > files handled during conversion?
> > In a perfect world, I would assume the files will be decompressed before
> > stored in the directorypool, so that the data can make use of the
> > deduplication.
> >
> > --
> > Michael Prix
>
> --
>
>  Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post AT plcs DOT nl
> +31 6 248 21 622
>