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

List:       adsm-l
Subject:    Re: "Compressed data grew" retries?
From:       Erwann SIMON <erwann.simon () FREE ! FR>
Date:       2016-07-01 5:36:34
Message-ID: 1178785058.69137934.1467351394637.JavaMail.root () zimbra59-e10 ! priv ! proxad ! net
[Download RAW message or body]

Tom,

In order to be able to use client side LZ4 compression, the server must be at least \
at 7.1.5 and the client at 7.1.6. Moreover, client-side compression and client-side \
deduplication must be used and the data must be backed up in a container storage \
pool.

See what the client documentation says about the compression option :

The type of compression that the client uses is determined by the combination of \
compression and client-side data deduplication that is used during backup or archive \
processing. The following types of compression are used: 

LZ4 A faster and more efficient compression method that the client uses when \
client-deduplicated data is sent to an LZ4-compatible container storage pool on the \
Tivoli Storage Manager server. The server must be at version 7.1.5 or later, and must \
use container storage pools. Client-side LZ4 compression is used only when \
client-side data deduplication is enabled.

LZW A traditional type of compression that the client uses in any of the following \
situations: v Client-deduplicated data is sent to traditional (non-container) storage \
pools on the server. v The client data does not undergo client-side data \
deduplication. (Does not apply to Data Protection for VMware and Data Protection for \
Microsoft Hyper-V, in which only client-deduplicated data can be compressed.)

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

----- Mail original -----
De: "Tom Alverson" <tom.alverson@GMAIL.COM>
À: ADSM-L@VM.MARIST.EDU
Envoyé: Vendredi 1 Juillet 2016 05:50:11
Objet: Re: [ADSM-L] "Compressed data grew" retries?

If the server is at 6.3.x and the client is at 7.1.x can it use LZ4 or does
that require the server to also be at 7.1.x?

On Thu, Jun 30, 2016 at 12:06 PM, Paul Zarnowski <psz1@cornell.edu> wrote:

> At 09:31 AM 6/30/2016, Tom Alverson wrote:
> > I will
> > try the compressalways yes setting but hopefully that won't override the
> > exclusions I have set up for common compressed files.
> 
> No, compressalways will not override exclude.compress.  The option simply
> says not to retry if compression grows the size.
> 
> The legacy LZW compression can grow files that are already in a compressed
> format.  The newer LZ4 compression should not grow an already compressed
> file.  In that respect, it's similar to the compression that LTO tape
> drives can do.
> 
> ..Paul
> 
> 
> 
> --
> Paul Zarnowski                            Ph: 607-255-4757
> Assistant Director for Storage Services   Fx: 607-255-8521
> IT at Cornell / Infrastructure            Em: psz1@cornell.edu
> 719 Rhodes Hall, Ithaca, NY 14853-3801
> 


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

Configure | About | News | Add a list | Sponsored by KoreLogic